I bought two Kenzos, one normal and one "Prime". On the first one I installed Mokee, that's the daily driver for my wife. On the second one I tried some ROMs, and I got two bugs that are annoying to me. If some of you would please try to reproduce them, so that we know for sure that they are bugs and report them. I have tested on "ResurrectionRemix-M-v5.7.3-20160807" and "aicp_kenzo_mm-11.0-NIGHTLY-20160812", both of them first with stock kernel and after that with "Radon-V2.1-Kenzo".
1. Kenzo has a magnetic switch, for the "smart covers" to put the phone to sleep when the flip-cover is closed and wake it up when it opens. It works on Mokee, but it doesn't work neither on RR nor AICP. If you don't have a Smart Cover you can use two small (and not powerful!) magnets. In the attached picture I have marked the zone where the two magnets in the cover are. If you put your two magnets floating over the screen (without touching it, use eventually some paper) in the corresponding area (~1 and 2 centimeters below the camera) the screen should go off, and if you remove them the screen should go on. I've looked at the live logs, and in RR and AICP no events are triggered, but they appear under Mokee ("PowerManagerService( 1261): Going to sleep due to lid switch (uid 1000)... ", etc). I have attached the logs in flip2016-08-13_23.05.zip.
2. I noticed that under RR and AICP I can not access the phone trough ADB. I can switch it to MTP mode, I see it, I can transfer files, but after switching to USB debugging "adb devices" gives me no device, and in the Device Manager I have only a unknown device. In fastboot mode it's woking. I don't think it's a driver issue, because under Mokee it's working as expected. I've attached logs captured under AICP with the Radon kernel.
3. Under Settings -> Security, check "Unknown sources", exit, and go again. The setting is not saved.
Off-topic: why isn't the Ambient Display working as expected? I remember that my former MotoE under CM12 got waked up when I took it out of my pocket, and so was the MotoG under CM13. Why can Kenzo do the same thing?
Flip Covers do not work with most Custom ROMs. It may be a driver issue or maybe just the code is missing. So, if you really want that to work, you can make a request to the maintainer of your favourite Custom ROM to add support for flip covers or simply you can use those ROMs that do have support for them.
For the ADB missing device, force your "unknown device" in Device Manager to update drivers and it should work fine from thereon. I have faced this many number of times on many different devices. ADB drivers, once installed, would work fine while the phone is on one ROM but would display as "unknown device" once the ROM is changed on the phone. Thankfully, updating drivers for that device almost always does the trick.
In the meantime I've tested also the official CM13 Nightly (without Radon). As, for what I know, RR and AICP are CM-based, and I thought the problems could originate from there. And they are, under CM13 the behavior is the same.
ayush3051 said:
Flip Covers do not work with most Custom ROMs.
Click to expand...
Click to collapse
But it works under CM13 (and should work on ROMs based on it), just on other devices, not on Kenzo - just tested it on a Falcon and it works. The feature is there, it should work.
ayush3051 said:
For the ADB missing device
Click to expand...
Click to collapse
I see in your profile that you own a Kenzo. If you have any of the above ROMs please try to reproduce the adb and unknown sources issues and post your results.
Best regards.
paul_damian said:
In the meantime I've tested also the official CM13 Nightly (without Radon). As, for what I know, RR and AICP are CM-based, and I thought the problems could originate from there. And they are, under CM13 the behavior is the same.
But it works under CM13 (and should work on ROMs based on it), just on other devices, not on Kenzo - just tested it on a Falcon and it works. The feature is there, it should work.
I see in your profile that you own a Kenzo. If you have any of the above ROMs please try to reproduce the adb and unknown sources issues and post your results.
Best regards.
Click to expand...
Click to collapse
Hi,
Most likely the code to have that feature is not yet included because of the custom roms are CM based including AICP and RR and the CM's official build for Kenzo just got out. A lot of devs will test and keep working on it. Meanwhile you can submit a request to CM via their site and they will include it or post it on the CM thread by the The Strix.
last but not the least use an app from the play store they surely do work in most of the cases.
Thank you for your reply, dwaipayanray95. I wanted first to have confirmation that these are really bugs, before submitting them. That's why I asked other users for help. I've tested them on CM13 only last night, I think that I will post them on TheStrix's thread.
paul_damian said:
In the meantime I've tested also the official CM13 Nightly (without Radon). As, for what I know, RR and AICP are CM-based, and I thought the problems could originate from there. And they are, under CM13 the behavior is the same.
But it works under CM13 (and should work on ROMs based on it), just on other devices, not on Kenzo - just tested it on a Falcon and it works. The feature is there, it should work.
I see in your profile that you own a Kenzo. If you have any of the above ROMs please try to reproduce the adb and unknown sources issues and post your results.
Best regards.
Click to expand...
Click to collapse
I could have tested it, but I am travelling for the next 30 or so days. So I cannot really test a new ROM like right now. I will be happy to do so once I reach home back, though I should tell you that I do not personally own a Flip Cover or have at my hands any small magnets.
But the thing is, even though the ROMs are CM based, they do not incorporate the whole CM base and hence are not capable of doing everything the base ROM does. Hope you understand this. On the other hand, the derived ROM may have some other feature which is not even present in the base ROM.
Let me give you an example in terms of AICP and RR, themselves.
Both AICP and RR do not implement CM's onscreen Navigation Bar, instead they have opted for DUI with pulse(which I personally love).
Similar may have been the case with the Flip cover code. If you want to you can make a device specific request at AICP and RR's Google+ pages. The developers are quite active there and can guide you much better than I can.
Regards and Thanks
If you still face the unkown device adb problem install the adb driver installer its around 9 mb.it can install drivers for all phones but you will have to disable driver signature enforcement in windows first.you will be good to go by this
and can i have proxisensor flip cover? cause i use a normal one not the official plastic one. i only want flip cover where the phone is in a tpu case. but its kinda anoying that the screen doesnt turn off. and i have tried some apps but they use more battery then they help...
First one isn't working in the most roms i tried which are commonly used some features of CM/Lineage, the second one you are also right. I had to remove RR so I can't check the third one, hope to solve my problems soon because I miss my RR
these issues are also not in aosp extended. but has in most of lineage based roms.
Related
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimKat - Togari, ROM for the Sony Xperia Z Ultra
Contributors
OmarEinea, SlimRoms, prbassplayer
Source Code: https://github.com/SlimRoms
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: Build 9
Stable Release Date: 2014-12-26
Current Beta Version: Build 8.20
Beta Release Date: 2014-12-09
Created 2014-06-30
Last Updated 2014-12-29
Camera fix apk
Found here
prbassplayer said:
Build was tested that it boots. Testing the waters here. Will need testers
Click to expand...
Click to collapse
Deleted
prbassplayer said:
Build was tested that it boots. Testing the waters here. Will need testers
Click to expand...
Click to collapse
Bootlooped on a dirty flash over Carbon, but was worth a try
oh and BTW I like the low DPI
Calls, GPS and camera all seem to work
blueether said:
Bootlooped on a dirty flash over Carbon, but was worth a try
oh and BTW I like the low DPI
Calls, GPS and camera all seem to work
Click to expand...
Click to collapse
Well I don't know if Carbon is on caf or not, but generally dirty flashing between 2 different roms is a bad idea. Thats good news, though I'm going to guess camera will be flaky (similar to honami) 80% of the time perfect then every once in a while driver won't initialize.
prbassplayer said:
Well I don't know if Carbon is on caf or not, but generally dirty flashing between 2 different roms is a bad idea. Thats good news, though I'm going to guess camera will be flaky (similar to honami) 80% of the time perfect then every once in a while driver won't initialize.
Click to expand...
Click to collapse
Even though I'm building carbon I'm not sure if it is using caf either... bit I have dirty flashed between the two before when I have had a building Slim with very few issues.
The camera seems to work 99% of the time in carbon, so I cant see why it should be any worse here. I do have a flickering screen in carbon when in video mode (maybe H/W overlays not 100%?) that isn't present in this build of Slim.
Edit:
I do know that carbon is using -caf as I had to change an include path to get past a not found .h
blueether said:
Even though I'm building carbon I'm not sure if it is using caf either... bit I have dirty flashed between the two before when I have had a building Slim with very few issues.
The camera seems to work 99% of the time in carbon, so I cant see why it should be any worse here. I do have a flickering screen in carbon when in video mode (maybe H/W overlays not 100%?) that isn't present in this build of Slim.
Click to expand...
Click to collapse
Slim had problems with some video playback (browser video or Netflix) would be green unless I disabled hw overlays, when we moved caf that git fixed and camera was less problematic.
Sent from my Xperia Z1 using Tapatalk
Thanks a lot for another awesome firmware for the Z Ultra!!
Regarding the camera issue, I've been facing it on every custom firmware out there, and found a possible workaround (works for me, at least): as soon as the device boots, open the camera immediately, and it should open normally after a small delay / frame freeze. After that, it continues to work normally, without any freezes, until the next reboot. However, if you wait a while after boot before opening the camera, it will freeze with a static frame. Killing it will cause the "can't connect to camera" message to appear the next times you open the camera. And I've tested with different camera apps, it's the same thing.
Hope it helps to debug the issue.
Alright, currently running this as my main. No problems so far; Bluetooth, calling, LTE, Wi-Fi, and video all work completely. Haven't had a reason to use the camera yet, however.
all seems to be working, but it doesn't read my SD card. It's an class4 a-data 32GB card formatted as exFAT, I'm backing up its content and will format it in phone (it does recognize it, but when I tap mount sd card, more options just flash below and then it goes back to 'mount sd card')
edit: no luck, it doesn't even format the card. When I reformatted it via card reader to FAT32 or NTFS, it was recognized, but with NTFS formatting it does not see any data, so I guess it's just exFAT/NTFS support that's missing
oh and with this dpi settings, digits in PIN entry are too close together (but still possible to type them in) - see http://i.imgur.com/sNmEGOJ.jpg
awsome job buddy another device of Xperia Brigade
Due to the fact I'm going to be moving soon and won't have net for a while builds while be scarce. I haven't dropped this device just don't have bandwidth to compile anything.
Cheers
Sent from my Xperia Z1 using Tapatalk
prbassplayer said:
Due to the fact I'm going to be moving soon and won't have net for a while builds while be scarce. I haven't dropped this device just don't have bandwidth to compile anything.
Cheers
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
jouse i will do it if u want
Sure look at my github (PRJosh) for the device folder.
Sent from my Xperia Z1 using Tapatalk
prbassplayer said:
Sure look at my github (PRJosh) for the device folder.
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
I was just going to say I could do it as I have the slim-caf repo already on the destop.
Are there any plans to support the GPe version or do you want me to do an unofficial version? I'm already doing [almost] weekly builds of Carbon for both the togari and togari_gpe.
blueether said:
I was just going to say I could do it as I have the slim-caf repo already on the destop.
Are there any plans to support the GPe version or do you want me to do an unofficial version? I'm already doing [almost] weekly builds of Carbon for both the togari and togari_gpe.
Click to expand...
Click to collapse
I'm unclear on the difference, and didn't look at the gpe device folder. When I get my net all set up I'll take a look.
Sent from my Xperia Z1 using Tapatalk
prbassplayer said:
I'm unclear on the difference, and didn't look at the gpe device folder. When I get my net all set up I'll take a look.
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
Not sure of the differences either, but as soon as I got Carbon togari to build the gpe built as well. There has only been a few little issues in the gpe build for carbon. although the last silm I built for the GPe didn't boot.
There only seems to be about 30 people downloading the GPe carbon so there may not be much of a call for it.
Been a while .. No new Updates for this ROM ???
VipiN'n'DroiD said:
Been a while .. No new Updates for this ROM ???
Click to expand...
Click to collapse
Bother reading much?
prbassplayer said:
Due to the fact I'm going to be moving soon and won't have net for a while builds while be scarce. I haven't dropped this device just don't have bandwidth to compile anything.
Cheers
Sent from my Xperia Z1 using Tapatalk
Click to expand...
Click to collapse
Anyways I updated OP with new build up 2 date with this weekly. I enabled RGB color control should work on this device if not please let me know. Unsure what my net situation will be next week so might not be able to build. Lets see.
Cheers
prbassplayer said:
Bother reading much?
Anyways I updated OP with new build up 2 date with this weekly. I enabled RGB color control should work on this device if not please let me know. Unsure what my net situation will be next week so might not be able to build. Lets see.
Cheers
Click to expand...
Click to collapse
Thanks Bro for your work [emoji106]
Edit1: This issue have workaround found to be raliable-ish, see post 6.
Edit2: I've figured it out, see post 12.
Greetings!
My device is Redmi Note 4X black 3/32GB. I have an issue with the microphone not working, but only during phone calls and only when using the built-in earpiece for communication. Switching to loudspeaker mode or plugging hands-free makes it work again.
This issue is reproducible only on custom AOSP based ROMs, but works as expected on Mi A1 ported ROM and on official and customized MIUI.
It's kinda strange, because some guys here don't encounter such problems with either the RN4(SD) or the RN4X(SD), both code-named "mido".
nasko_spasko said:
Greetings!
My device is Redmi Note 4X black 3/32GB. I have an issue with the microphone not working, but only during phone calls and only when using the built-in earpiece for communication. Switching to loudspeaker mode or plugging hands-free makes it work again.
This issue is reproducible only on custom AOSP based ROMs, but works as expected on Mi A1 ported ROM and on official and customized MIUI.
It's kinda strange, because some guys here don't encounter such problems with either the RN4(SD) or the RN4X(SD), both code-named "mido".
Click to expand...
Click to collapse
Read this : https://forum.xda-developers.com/re...dia-sounds-t3682812/post74247791#post74247791
sachin n said:
Read this : https://forum.xda-developers.com/re...dia-sounds-t3682812/post74247791#post74247791
Click to expand...
Click to collapse
Thanks! I'll try and report, but I have issue with the mic, not the speaker.
nasko_spasko said:
Thanks! I'll try and report, but I have issue with the mic, not the speaker.
Click to expand...
Click to collapse
Oh, nvm! Sorry.
I have same problem and dont find a solution.
I've found some sort of a workaround for this issue. The problem described in the thread is kinda different than mine, but seems to fix my problem too. It's in this XDA thread. All i did was flashing the two zip files from zile995: fix-audio-*-zile995.zip at the bottom of the OP.
As I said, this is a workaround, not a fix. If you know some of the maintainers for the device tree for LOS, feel free to mention them in this thread. I could make a fix proposal miself, but I don't have the time to invest in this. However if no progress is observed in the next couple of week, maybe I'll try to make it work and propose a fix to be pushed to upstream, so no more dirty flashes of patches to be required for the mic to work properly during a phone call.
Ok i will test too.
Edit: I have test and its work but i dont have lte and the other side say the volume is very low.
Schrotty35 said:
Ok i will test too.
Edit: I have test and its work but i dont have lte and the other side say the volume is very low.
Click to expand...
Click to collapse
Tested ot on LOS 14.1 and RR Nougat, in my case LTE works and the other guy says it's too loud. How come?
I have test with latest rr too. I dont know what is the problem. In the other Thread i have see there is a v6. I will test with this. Have you install both fix after install Rom direct?
Schrotty35 said:
Have you install both fix after install Rom direct?
Click to expand...
Click to collapse
Yup! It's not necessary, though. Flashing the v2 version is sufficient in my case. build.prop version does nothing. I'll play with it further during the weekend.
Cheers!
I have found a good fix which work for me.
You found it here https://forum.xda-developers.com/showthread.php?t=3630473
Done, fugured it out
Greetings, ppl!
I know it's been a while, but I've finally figured it out.
The property 'persist.vendor.audio.fluence.voicecall' should be set to 'false' instead of 'true'.
In the Official and all MIUI based ROMs it's set to false, but in all AOSP based ones it's set to true, which breaks in-call audio for alot of people, at least the ones with newer revisions of the board. So next I'll try to fork the device tree from the LOS project and modify it accordingly and build the ROM with it and see if it finally works out of the box.
Oh, such a relief! The mic finally works when calling people.
Could you please try and report? You're not supposed to, though. Flashing roms and testing configs can be annoying sometimes.
Happy holidays!
nasko_spasko said:
Greetings, ppl!
I know it's been a while, but I've finally figured it out.
The property 'persist.vendor.audio.fluence.voicecall' should be set to 'false' instead of 'true'.
In the Official and all MIUI based ROMs it's set to false, but in all AOSP based ones it's set to true, which breaks in-call audio for alot of people, at least the ones with newer revisions of the board. So next I'll try to fork the device tree from the LOS project and modify it accordingly and build the ROM with it and see if it finally works out of the box.
Oh, such a relief! The mic finally works when calling people.
Could you please try and report? You're not supposed to, though. Flashing roms and testing configs can be annoying sometimes.
Happy holidays!
Click to expand...
Click to collapse
i have exactly same problem
already wrote here in this sub forum without any response from the members here
will try today at the office and report to you later
thank you for sharing
done editing to false, now incall is nice but i hear low voice from other party in speakerphone mode although volume is full. ?
but it was more than enough since i dont use speakerphone mode that much
really appreciate your finding my friend
groovepeppy said:
done editing to false, no incall is nice but i hear low voice from other party, volume is full.
Click to expand...
Click to collapse
have you tested it on clean isntall? I mean no other patches applied?
nasko_spasko said:
have you tested it on clean isntall? I mean no other patches applied?
Click to expand...
Click to collapse
pardon me, the connection is bad over here
i believe i have edited my post because it was full of typos but it turns out its not edited yet.
please re-read the post you have quoted.
fyi, i clean flashed PixelExperience 8.1 ROM right after i arrived at work
setting this and that, root the phone using latest Magisk, install Root Explorer and did what you have wrote on post #12 and yes, i did not use any patch, just your workaround
Reboot the phone, test calling and i smile very wide.
one thing i found, setting up Google Assistant can't be done
it told me to say "Ok Google" but the app didn't hear me
so i change all of the "almost identical" line to false, like this....
persist.vendor.audio.fluence.voicecall=false
persist.vendor.audio.fluence.voicerec=false
persist.vendor.audio.fluence.speaker=false
Click to expand...
Click to collapse
Google Assistant recognize my voice now
But the speakerphone mode stay the same, the voice from the other end aren't loud enough.
once again say thanks to you for your effort
feel happy that i'm not the only one suffering this problem LOL
I still face the issue after editing build prop..
hi @nasko_spasko
I'm getting a bit irritated by this phone
How come i am (maybe with you too) the only one having this problem
Last night i look at latest xiaomi.eu build prop and i decide to get all audio related lines and overwrite the related lines in pixel experience's rom build.prop
crossing my finger here, wish me luck man
edit:
still i get very small volume for speakerphone mode
anybody knows how to gain the speakerphone output level?
@nasko_spasko
finally i fixed it
mic working fine in call
loud speakerphone
i did what he told me here.....
https://forum.xda-developers.com/showpost.php?p=74000643&postcount=210
change fluencetype to none and add one line in audio_platform_info.xml
reboot
works like a charm
by the way, i still use pixel experience rom.
groovepeppy said:
@nasko_spasko
finally i fixed it
mic working fine in call
loud speakerphone
i did what he told me here.....
https://forum.xda-developers.com/showpost.php?p=74000643&postcount=210
change fluencetype to none and add one line in audio_platform_info.xml
reboot
works like a charm
by the way, i still use pixel experience rom.
Click to expand...
Click to collapse
Thanks for lot! But, can you write the line to add in audio_platform_info.xml?
I'm in pixel experience too.
See here for disclaimer and FAQs
Installation and download instructions are available on the wiki
Downloads are here
For help with Sprint, see here
XDA:DevDB Information
LineageOS 14.1 for Galaxy S5 Sport, ROM for the Sprint Samsung Galaxy S5
Contributors
javelinanddart
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: G860PVPU2BOK1
Version Information
Status: Nightly
Created 2017-12-30
Last Updated 2017-12-30
Reserved
Reserved
Just wanted to say thanks for this!
I use this phone with hangouts dialer on wifi when I'm out working (leaving my good, fragile phone safe in the house). I was using the old cyangenmod 13 rom because it was the only one that would work without missing sim errors.
This rom works perfectly for my needs, again, thanks!
javelinanddart said:
See here for disclaimer and FAQs
Installation and download instructions are available on the wiki
Downloads are here
For help with Sprint, see here
XDA:DevDB Information
LineageOS 14.1 for Galaxy S5 Sport, ROM for the Sprint Samsung Galaxy S5
Contributors
javelinanddart
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: G860PVPU2BOK1
Version Information
Status: Nightly
Created 2017-12-30
Last Updated 2017-12-30
Click to expand...
Click to collapse
Is this rom still being actively developed? I'm interested in testing if so.
FanboyStudios said:
Is this rom still being actively developed? I'm interested in testing if so.
Click to expand...
Click to collapse
EDIT: Oops, wrong thread. It's stable, I'm not working on 14.1 right now.
javelinanddart said:
EDIT: Oops, wrong thread. It's stable, I'm not working on 14.1 right now.
Click to expand...
Click to collapse
I found an issue, the stock equalizer does not seem to work at all. Also tried to install V4A and it does not work either (I suspect it's Samsung's fault with the problematic Samsung Knox). Screen recording seems to be buggy and 5GHz hotspot don't work (2.4 GHz works fine). Other than that I haven't found any other issues. Video recording works fine.
Edit: Stock equalizer seems to work on all my audio files (.wav, .flac, .m4a), except .mp3 files.
FanboyStudios said:
I found an issue, the stock equalizer does not seem to work at all. Also tried to install V4A and it does not work either (I suspect it's Samsung's fault with the problematic Samsung Knox). Screen recording seems to be buggy and 5GHz hotspot don't work (2.4 GHz works fine). Other than that I haven't found any other issues. Video recording works fine.
Click to expand...
Click to collapse
The stock equalizer works perfectly fine (I use it all the time), so is 5GHz wifi and screen recording. Video recording is an issue in 15.1, not 14.1.
javelinanddart said:
The stock equalizer works perfectly fine (I use it all the time), so is 5GHz wifi and screen recording. Video recording is an issue in 15.1, not 14.1.
Click to expand...
Click to collapse
I'm using the latest official build from the official LineageOS website. It's 14.1
There is a bug in lineage-14.1-20180222-nightly-kltesprsports-signed.zip build - no sound after installation, because "Do not disturb" option is turned on by default, but it shows like it is turned off in the drop-down menu so you have to touch the "Do not disturb" icon to see it is actually turned on, and turn it off manually.
It took a few reinstalls from 20180222 to 20180215 back and forth to find this out.
Also I am kinda upset about not functioning NFC, and I found out that LineageOS does not support NFC on many different Samsung models. Why is it so - a missing driver or something else?
I would like to pay someone to fund NFC development, if possible.
vrobo said:
There is a bug in lineage-14.1-20180222-nightly-kltesprsports-signed.zip build - no sound after installation, because "Do not disturb" option is turned on by default, but it shows like it is turned off in the drop-down menu so you have to touch the "Do not disturb" icon to see it is actually turned on, and turn it off manually.
It took a few reinstalls from 20180222 to 20180215 back and forth to find this out.
Also I am kinda upset about not functioning NFC, and I found out that LineageOS does not support NFC on many different Samsung models. Why is it so - a missing driver or something else?
I would like to pay someone to fund NFC development, if possible.
Click to expand...
Click to collapse
NFC works fine on my kltesprsports on 14.1 at least. I'm not sure why you're seeing issues. Can you give me some steps to reproduce?
javelinanddart said:
NFC works fine on my kltesprsports on 14.1 at least. I'm not sure why you're seeing issues. Can you give me some steps to reproduce?
Click to expand...
Click to collapse
Oh, that's good news! In fact I did not check the NFC function before writing that message, I think I saw somewhere that NFC does not work in LineageOS on S5.
Or maybe I got confused with S4 (jfltexx) which I also own and where NFC does not work for sure.
I've sent you a donation thru Paypal, many thanks for your work!
Just a side note for fun and general info. My bank flagged my account after using their banking app as accessing with a "known fraud device" and locked my savings and checking. In the end, I had to get new accounts because they could not turn them on after the fact. I tried to explain in vain and they would not hear it. So fair warning if you try to use your banking app on the Lineage ROM. Nothing extra added, only the current version of this ROM and open gapps.
Is there any chance to see Wireguard VPN support in this build?
vrobo said:
There is a bug in lineage-14.1-20180222-nightly-kltesprsports-signed.zip build - no sound after installation, because "Do not disturb" option is turned on by default, but it shows like it is turned off in the drop-down menu so you have to touch the "Do not disturb" icon to see it is actually turned on, and turn it off manually.
It took a few reinstalls from 20180222 to 20180215 back and forth to find this out.
Also I am kinda upset about not functioning NFC, and I found out that LineageOS does not support NFC on many different Samsung models. Why is it so - a missing driver or something else?
I would like to pay someone to fund NFC development, if possible.
Click to expand...
Click to collapse
What are the bugs with the lineage-14.1-20180222-nightly-kltesprsports-signed.zip build? I'm interested in flashing. Also, was the issue with airplane mode disconnecting LTE on the s5 sport ever resolved? Disabling airplane mode does not initiate LTE connection only until I reboot my phone. I'm on build 14.1-20170418 currently so curious to see what has improved. Also, a big thanks to everyone in this community. I moved from cm13 to this build a year ago and I've been happy. Just looking to resolve the LTE issue .
onlyoneway, this is very old version from February, you should better install the latest nightly build from here: https://download.lineageos.org/kltesprsports
I do not know about LTE as my operator frequencies do not match US ones. However 3G works nice after "Flight Mode" on/off.
P.S. bumping the question
vrobo said:
Is there any chance to see Wireguard VPN support in this build?
Click to expand...
Click to collapse
Wireguard is awesome.
I found out that calendar does not notify about forthcoming events. I use LineageOS without Google stuff (with Offline Calendar https://f-droid.org/en/packages/org.sufficientlysecure.localcalendar/ instead).
Is this a bug in Offline Calendar on in LineageOS build for kltesprsports?
vrobo said:
onlyoneway, this is very old version from February, you should better install the latest nightly build from here: https://download.lineageos.org/kltesprsports
I do not know about LTE as my operator frequencies do not match US ones. However 3G works nice after "Flight Mode" on/off.
P.S. bumping the question
Wireguard is awesome.
Click to expand...
Click to collapse
Thanks vrobo. Do you happen to know where I can find the changelog from the build I have upto the latest?
onlyoneway said:
Thanks vrobo. Do you happen to know where I can find the changelog from the build I have upto the latest?
Click to expand...
Click to collapse
https://download.lineageos.org/kltesprsports/changes/
Hey Guys! I have a Samsung S5 sport that I recently dirty flashed to the 14.1-20180803-NIGHTLY-kltesprsports build. Now my battery does not go beyond 65% no matter how long I leave my phone plugged in. I have tested different cables and adapters, and still the same thing. Didn't have this issue with the 20180720 build. Any thoughts? Bug maybe? Thanks in advance.
Hello everyone ,
So this will now be one of the most important place for you guys
This is going to be the QnA thread where you guys can ask any doubts or questions or place a review or anything that some how relates to Xiaomi Redmi 5 development then Simply post it here I will come and answer all the questions
It maybe of my roms , or kernels or it maybe developed by someone else but if you faith me and expect some good solutions to your doubt then come on and start posting your questions
Even if I get some good tips to optimize your device then I will post those here
So let's get started
Pixel Experience Calling Issue
Shreejoy Dash said:
Hello everyone ,
So this will now be one of the most important place for you guys
This is going to be the QnA thread where you guys can ask any doubts or questions or place a review or anything that some how relates to Xiaomi Redmi 5 development then Simply post it here I will come and answer all the questions
It maybe of my roms , or kernels or it maybe developed by someone else but if you faith me and expect some good solutions to your doubt then come on and start posting your questions
Even if I get some good tips to optimize your device then I will post those here
So let's get started
Click to expand...
Click to collapse
Hi, I loved using the Pixel Experience ROM. I faced a couple of issues, and had to revert back to rooted stock rom.
Issues:
1. FM Radio doesn't work. Minor issue.
2. Camera: I understand that Camera2API is enabled by default in this ROM. All is good except when I use the camera built in Whatsapp. If the flash is not enabled, the capture comes with a green overlay which is not at all usable; this happens in both front and rear camera. The photo is fine when flash is enabled. No issues in the stock camera included in the rom and opencamera app.
3. When I call someone, the in-call timer doesn't start when they answer the phone, also the Hold & Add Call buttons are not available and call waiting is not functional. It is as if the device would not register if the call has been answered. I use Jio as my only sim so I could not tell if it is an issue specific to Volte calling. Things are fine in case of incoming calls. This is a major issue and I had to revert back to stock rom with Magisk because I was not getting calls. I saw other posts on the forum with this issue.
Thanks.
Same issues here PE with nano kernel 3.1 beta
Tried the April build of PE
himodyuti said:
Hi, I loved using the Pixel Experience ROM. I faced a couple of issues, and had to revert back to rooted stock rom.
Issues:
1. FM Radio doesn't work. Minor issue.
2. Camera: I understand that Camera2API is enabled by default in this ROM. All is good except when I use the camera built in Whatsapp. If the flash is not enabled, the capture comes with a green overlay which is not at all usable; this happens in both front and rear camera. The photo is fine when flash is enabled. No issues in the stock camera included in the rom and opencamera app.
3. When I call someone, the in-call timer doesn't start when they answer the phone, also the Hold & Add Call buttons are not available and call waiting is not functional. It is as if the device would not register if the call has been answered. I use Jio as my only sim so I could not tell if it is an issue specific to Volte calling. Things are fine in case of incoming calls. This is a major issue and I had to revert back to stock rom with Magisk because I was not getting calls. I saw other posts on the forum with this issue.
Thanks.
Click to expand...
Click to collapse
I tried the April build of PE and unfortunately, these issues are still there. I cannot shake the feeling that I am doing something wrong. Are we supposed to flash anything else along with the ROM so that these issues would go away?
I have a little doubt.
Shreejoy Dash said:
Hello everyone ,
So this will now be one of the most important place for you guys
This is going to be the QnA thread where you guys can ask any doubts or questions or place a review or anything that some how relates to Xiaomi Redmi 5 development then Simply post it here I will come and answer all the questions
It maybe of my roms , or kernels or it maybe developed by someone else but if you faith me and expect some good solutions to your doubt then come on and start posting your questions
Even if I get some good tips to optimize your device then I will post those here
So let's get started
Click to expand...
Click to collapse
I have a little doubt. Does Lineage OS 14.1 will still be able to boot on our Rosy?
Lineage
Deathalw4ys said:
I have a little doubt. Does Lineage OS 14.1 will still be able to boot on our Rosy?
Click to expand...
Click to collapse
Yes you can but I don't think there is an official Lineage ROM for Rosy. There is an unofficial available on XDA. There are a couple of other options that you can try. E.g. Resurrection Remix, crDroid, Pixel Experience, CyanogenMod etc.
why I can't flash gsi roms?
everytime I flash a gsi it boots to bootloader..
and another problem..
I cannot connect my device to my pc..
when i connect to pc it charges but doesn’t show the Notification light and in my pc it says unknown device..
I tried to update device driver but it says driver is upto date.. I tried installing drivers from online but still same problem..
and in my phone there shows no option to choose mtp or anything like that too...
any solution?
Hi to all
The developers of derpfest ROM don't wanna share the links to Derpfest in xda.
We have to respect this! Don't post any links to ROM or telegram derpfest groups!
Here is the closed thread without links but with important infos:
https://forum.xda-developers.com/Mi-9/help/android-10-derpfest-rom-10-official-t4032543
So, this thread is only for advice, discussions and experiences.
Future requests
Please tell me what you want to have changed or implemented, the I would ask the developers if it could be possible.
My list
1. adding autocall record
2. Adding flip display down to mute ringer
3. Smart charge (charging only to a predefined % value)
4. Adding display saturation level
5. All closing button in recent app list
6. And last to be 100% perfect with 5 stars: a system menu with automatic timebased network disconnect... Like leandroid app
Hi guys
This TWRP (last version from 16.) is lookin and working better than all others:
https://forum.xda-developers.com/Mi-9/development/orangefox-recovery-10-mi9cepheus-test-t3987959
If you delete the empty folder root data per_boot the backup is running without faults.
Many additional functions like disable magisk modules for testing or after bootloop with a non working module....
There are 2 versions of derpfest 13.1. 20 online. Someone checked the differences?
Is it impossible to support the ok google hotword feature?
Sadly hotword don't work on most custom roms in Mi9.
Except few roms
For example, old Bootleggers ROM, EvolutionX 3.5 1224 build etc...
You can assign AI button to ok google or use screen gestures,
but in my case I really need a hotword so I can't move to another rom.
I saw some comments before.
There was a saying that moving from possible ROM to impossible ROM, but the attempt failed.
System - product - priv-app - hotwordenrollmentokgooglehexagon
coey0814 said:
Is it impossible to support the ok google hotword feature?
Sadly hotword don't work on most custom roms in Mi9.
Except few roms
For example, old Bootleggers ROM, EvolutionX 3.5 1224 build etc...
You can assign AI button to ok google or use screen gestures,
but in my case I really need a hotword so I can't move to another rom.
I saw some comments before.
There was a saying that moving from possible ROM to impossible ROM, but the attempt failed.
System - product - priv-app - hotwordenrollmentokgooglehexagon
Click to expand...
Click to collapse
I didn't use it but do you checked all settings?
Have a look here:
https://translate.googleusercontent...700271&usg=ALkJrhjVQfsolQJiA_E-Zura_IPnjE5Krw
Laptapper said:
I didn't use it but do you checked all settings?
Have a look here:
https://translate.googleusercontent...700271&usg=ALkJrhjVQfsolQJiA_E-Zura_IPnjE5Krw
Click to expand...
Click to collapse
Thanks for your comment. But the site you link to looks like the official Google site,
I tried it before and it didn't help.
coey0814 said:
Thanks for your comment. But the site you link to looks like the official Google site,
I tried it before and it didn't help.
Click to expand...
Click to collapse
Of course officially Google site, I don't know your knowledge. But now we can go deeper in system and thinking...
Did you try to restore a working google with titanium?
Google cam for derpfest (may be good for all android 10)
Hey ladies
If you want to try my personally favorite of gcam with complete settings (I'm on derpfest but I think it's working quite good in all roms with Android 10) then you can download my backup and restore it with titanium. Recommend is no gcam is installed on starting restore.
https://drive.google.com/uc?id=106vNLIqUZeaIADT6KGIVlSXi9nZLYwkv&export=download
Am I here alone?
No comments no experiences no feature requests for derpfest (some people thinking it's the best ROM for Mi9!)
Laptapper said:
Hey ladies
If you want to try my personally favorite of gcam with complete settings (I'm on derpfest but I think it's working quite good in all roms with Android 10) then you can download my backup and restore it with titanium. Recommend is no gcam is installed on starting restore.
https://drive.google.com/uc?id=106vNLIqUZeaIADT6KGIVlSXi9nZLYwkv&export=download
Click to expand...
Click to collapse
Selfie video still not working
Laptapper said:
Am I here alone?
No comments no experiences no feature requests for derpfest (some people thinking it's the best ROM for Mi9!)
Click to expand...
Click to collapse
most people looking for information about some roms go to the "ROMs" section and not here, which is why so little interest. DerpFest itself is the best rom for mi9 (with weekly releases.)
IBTD, a ROM with GAPPS included can never be 'the best ROM' for any device. YMMV but I'd like to decide by myself which Google bloatware I'd like to install.
Cheers
Toscha
rekin79 said:
most people looking for information about some roms go to the "ROMs" section and not here, which is why so little interest. DerpFest itself is the best rom for mi9 (with weekly releases.)
Click to expand...
Click to collapse
+1
stajlus said:
+1
Click to expand...
Click to collapse
Yes you are right but in case of forbidden links (btw I didn't know why the developer of derpfest didn't allow us to post links in xda) in my opinion I can't move in the ROM thread in case of xda rules.
Battery tweak
I've tested magisk module "MOD optimal battery saving for Mi 9 v3. 7" in newest derpfest
and yesterday evening I was on 71% and today in the morning around 8 hours of sleep it was also 71%!
Never seen such a low battery consumption over night.
Patricmac said:
Selfie video still not working
Click to expand...
Click to collapse
Yes, I think every gcam has some bugs.
Also this one:
https://drive.google.com/folderview?id=1-HAYDgRI2z2Z7pbWMBtmEuP8jStW5oPT
But this one (apk install, unpack my zip xml settings to sd card that you've got a GCam Folder with subfolder Configs7 and there are the xml configs / open cam app and choose the config file by double click black area or in the settings menu)
I've found today and there are a lot of settings adjustable and quite stable. For me perfect pictures....
Try and give feedback.
I've used Derpfest for a couple of days and was very happy with it. But I couldn't get Android Auto to work with my car - dark screen on the dashboard and phone would lock up. I've dirty flashed PE and there Android Auto works fine.
I understand Android Auto may be a very rare use case, so I certainly don't want to complain. What's more interesting is that you may apparently try dirty flashing between PE and Derpfest...at least at this moment.
Can confirm. Android auto not working. Black screen and phone restarts for me.
So i am going back to PE.
Laptapper said:
Battery tweak
I've tested magisk module "MOD optimal battery saving for Mi 9 v3. 7" in newest derpfest
and yesterday evening I was on 71% and today in the morning around 8 hours of sleep it was also 71%!
Never seen such a low battery consumption over night.
Click to expand...
Click to collapse
Hi, thanks. Can you share the mod?
Sent from my MI 9 using Tapatalk
GIPAQ said:
Hi, thanks. Can you share the mod?
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
Attached