Database Develop

Google Dialer Port (w/Incoming Caller ID Lookup)

After lots of frustration and hours to make this work, It's done.
This Google Dialer works just like the one in the Nexus 5 stock.
What's the difference between this dialer and the CM11 dialer?
1.) On the dial screen, it allows you to type a name of a business or "place" and the dialer will show you the closest numbers to you for fast dialing
2.) Incoming Caller ID Lookup, This compares your incoming call to the same database for any name lookup and/or picture lookup, in January or soon after, it will show contacts for Google+ on the caller ID screen. As far as I know, you do not have to have this person in your circles to have the caller id show.
How do you install it?
1.) First and very formost. This is for Cyanogenmod 11 with 4.4.1+. If you try to do it on any earlier Android version, you'll most likely get lots of force closes and your phone will stop functioning altogether... You've been warned...
2.) Boot into recovery
3.) Backup
4.) Flash this file: http://www.tinozplace.com/moto-kitkat/12-10_GoogleDialer_4.4.1_signed.zip or for 4.4.2,
http://www.tinozplace.com/moto-kitkat/12-12_GoogleDialer_4.4.2_signed.zip
5.) Reboot
6.) Profit???
I edited the installer file to delete dialer.apk, so you no longer have to do that.
Enjoy!
If you'd like, I have built the dialer into my gapps. This way you don't need to flash several zips each time you upgrade to a new nightly.
http://www.tinozplace.com/moto-kitkat/12-17-gapps-wDialer.zip
NOTE:
You can link to this post, however mirroring and posting the link to my site on any other forums is strictly prohibited. I worked for weeks doing research and was finally completed yesterday.
Tested to be working on:
HTC One
Motorola xt926
Motorola xt925
Motorola mb886
Sprint Galaxy S4 (Verizon)
If you have confirmed this zip is working on any other roms or phones, please post here
EDIT: Gapps fixed to allow use on other phones. Someone was complaining that Wifi was being interfered with, along my travels, I found that certain versions of CloudPrint was getting in the way. Updated to 4.4.1 CloudPrint2.apk.
EDIT: Works with 4.4.2
EDIT: Reports of the LTE toggle (in the quick settings panel) being broken have come to my attention. There isn't much I can do about this. It's google's code, not "backwards-compatible" with AOSP. You'll have to choose the dialer or the LTE toggle, sorry.
EDIT: If you downloaded 12/10gappswDialer, redownload the latest. Somehow, I forgot to put the APK's in the zip. Very sorry about this.

Did you test this on aosp roms base on android 4.4.1?

Just CM..

Wow fantastic work. I'm assume this would work on SlimKat. I just have to find the balls.

Reach down in your pocket, you'll find them
Let me know if it does work, my guess is it will as long as you are on 4.4.1

Reach down in your pocket, you'll find them
Heck, if you do a backup, there should be nothing to worry about.
Let me know if it does work, my guess is it will as long as you are on 4.4.1

Congrats man. I've been watching your progress on this and can't wait to give it a try next time I flash a kitkat rom

Heck yeah man!!! Nice work. I know you had your doubt's about this one so its nice to see that you figured it out.
Sent from my Nexus 7 using Tapatalk

Great job. I think I'll finally jump to CM11 tonight and give this a spin. :good:

If you are on a different device, use the dialer without the gapps. I'll fix the gapps tomorrow
Sent from my XT926 using Tapatalk

Works on ose rom xt925
Envoyé depuis mon XT925 avec Tapatalk

spart'84120 said:
Works on ose rom xt925
Envoyé depuis mon XT925 avec Tapatalk
Click to expand...
Click to collapse
Gapps Fixed for other devices (See OP)

Working on mb886!!!
Sent from my MB886 using Tapatalk

Thanks. OP updated
Sent from my Nexus 7 using Tapatalk

This dialer works, but after i flash it, i got FC in settings/interface/quick settings panel, allso /quick settings panel/tiles and layout.
I use CM11 today build, also on yesterday build was the same.
If i flash a clean build those settings works fine, after i flash this google dialer i got the problems.
XT925

darktyroll said:
This dialer works, but after i flash it, i got FC in settings/interface/quick settings panel, allso /quick settings panel/tiles and layout.
I use CM11 today build, also on yesterday build was the same.
If i flash a clean build those settings works fine, after i flash this google dialer i got the problems.
XT925
Click to expand...
Click to collapse
Are you flashing the Gapps with the dialer or just the dialer?
I do not have that problem, my guess is that you have the LTE toggle? That probably won't work because this dialer is Google source and CM is AOSP.
Did you have this problem in previous nightlies? or did you just start using this dialer?

Would this gapps are propper for ART?
Sent from my XT925 using Tapatalk

motopuk said:
Would this gapps are propper for ART?
Sent from my XT925 using Tapatalk
Click to expand...
Click to collapse
Yes. It's all I will ever release

abuttino said:
Are you flashing the Gapps with the dialer or just the dialer?
I do not have that problem, my guess is that you have the LTE toggle? That probably won't work because this dialer is Google source and CM is AOSP.
Did you have this problem in previous nightlies? or did you just start using this dialer?
Click to expand...
Click to collapse
Well i flash both. Simple dialer and gapps with dialer. Same problem. It makes FC when i press on those settings but after that i can use the settings.
Sent from my Motorola Razr HD XT925 using Tapatalk 2

I updated the OP to explain this.

[Q&A] [KERNEL] ElementalX-m7-Sprint-13.1

Q&A for [KERNEL] ElementalX-m7-Sprint-13.1
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

smokin901 said:
Time for New build.
Added ultrasound_a and ultrasound_b with the help of @poondog
Fixed BT.Calls issue. (thank you brymaster for tip)
Added confirmation screen to avoid flashing screw-up
Click to expand...
Click to collapse
why this kernel on my phone no DT2W with ARTMOD V5.2 VERIZON ROM ?

wangxiantaoye said:
why this kernel on my phone no DT2W with ARTMOD V5.2 VERIZON ROM ?
Click to expand...
Click to collapse
it is not kernel fault works perfect for me. check what option did you select during installation. make sure you select D2TW Fullscreen during installation

smokin901 said:
it is not kernel fault works perfect for me. check what option did you select during installation. make sure you select D2TW Fullscreen during installation
Click to expand...
Click to collapse
i m sure i select DT2W FULLSCREEM

wangxiantaoye said:
i m sure i select DT2W FULLSCREEM
Click to expand...
Click to collapse
Well you are the only one complaining about Double Tap to wake not working. in 1000 of people using it. check your phone settings. double tap is configured by init script so check if it exists.

I'm on ViperOne 7.0.1 and.v18 is disabling NFC. It will not turn on in settings.
Sent from my HTC One using XDA Free mobile app

OneHitWonder said:
I'm on ViperOne 7.0.1 and.v18 is disabling NFC. It will not turn on in settings.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Make sure nfc.default.so file is there in /system/lib/hw

I have nfc.m7wls.so. Is this the right file or do I need nfc.default.so also ?
Sent from my HTC One using XDA Free mobile app
---------- Post added at 08:29 AM ---------- Previous post was at 08:23 AM ----------
I grabbed the nfc file from the Rom and swapped them and it works . Thanks for pointing me in the right direction.
Sent from my HTC One using XDA Free mobile app

OneHitWonder said:
I have nfc.m7wls.so. Is this the right file or do I need nfc.default.so also ?
Sent from my HTC One using XDA Free mobile app
---------- Post added at 08:29 AM ---------- Previous post was at 08:23 AM ----------
I grabbed the nfc file from the Rom and swapped them and it works . Thanks for pointing me in the right direction.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
I just renamed nfc.m7wls.so to nfc.defaulf.so and NFC started working immediately. I rebooted anyway just to make sure but it works.
Smokin901 posted this same fix back around version 6, it worked then and still works now. I wonder how come it can't be incorporated into the kernel installer.

dgl6y7 said:
I just renamed nfc.m7wls.so to nfc.defaulf.so and NFC started working immediately. I rebooted anyway just to make sure but it works.
Smokin901 posted this same fix back around version 6, it worked then and still works now. I wonder how come it can't be incorporated into the kernel installer.
Click to expand...
Click to collapse
I choose not to and suggest to have two files nfc.default.so and nfc.m7wls.so because if you switch to different kernel nfc will be be broken again.

Hey guys. Can anyone confirm that this is working with Viper 7.0.1?
I tried flashing it, I had a bunch of graphics problems like screen tearing, no wallpaper, reboot menu not appearing, screen shots not working.
Should I try with a fresh flash?
Thanks in advance.

sauprankul said:
Hey guys. Can anyone confirm that this is working with Viper 7.0.1?
I tried flashing it, I had a bunch of graphics problems like screen tearing, no wallpaper, reboot menu not appearing, screen shots not working.
Should I try with a fresh flash?
Thanks in advance.
Click to expand...
Click to collapse
You need to install version 17 or 18

smokin901 said:
You need to install version 17 or 18
Click to expand...
Click to collapse
Real quick;
I've noticed that with power saver off, the phone hits max freq (1.84 GHz for me) pretty often. Should I be concerned? Does this affect the longevity of the phone?

sauprankul said:
Real quick;
I've noticed that with power saver off, the phone hits max freq (1.84 GHz for me) pretty often. Should I be concerned? Does this affect the longevity of the phone?
Click to expand...
Click to collapse
Did you select higher frequency during install Max by default is 1.7
If cpu is on max frequency very often then something is keeping it busy check your apps.

Bluetooth headset
I read that Bluetooth is supposed to be working on this kernel. I have had no issues with anything other than no call audio with the bluetooth. Medias works fine. Love the kernel other than that. Is there a fix i am not aware of for this? Would be great to use my headset.
Htc m7 running Skydrasgon 9 4.4.3
Elementalx 18

donnykerr said:
I read that Bluetooth is supposed to be working on this kernel. I have had no issues with anything other than no call audio with the bluetooth. Medias works fine. Love the kernel other than that. Is there a fix i am not aware of for this? Would be great to use my headset.
Htc m7 running Skydrasgon 9 4.4.3
Elementalx 18
Click to expand...
Click to collapse
BT should work with 17.2-3

Thank you for the suggestion, tried it. Same issues, im going to try a different rom later to see if that has something to do with it. Although it workedfine on this rom until i used the kenel. Love it so far minus this one hiccup.
James
UPDATE:
I tried using the newest version of the SkyDragon Rom and the BT worked fine. Then I went ahead and added the Elementalx 17.2.3 Kernel, and right back to no call audio. But the kernel did fix a few other issues including the WIFI Tether app not working properly, minus the fact that it wont shut down the HostAPD. I have to manully shut that down to get it to restart, but works fine. And I really like the wake gestures. I am not sure why the BT wont work on my device but I thought I would share what I know so far. Thanks for the great work so far, I see it just keeps getting tweaked and made better. Keep it up.

dgl6y7 said:
I just renamed nfc.m7wls.so to nfc.defaulf.so and NFC started working immediately. I rebooted anyway just to make sure but it works.
Smokin901 posted this same fix back around version 6, it worked then and still works now. I wonder how come it can't be incorporated into the kernel installer.
Click to expand...
Click to collapse
Edit: after a lengthy cycle of trying to fix my call audio problem it seems that the nfc fix is breaking it. I dont make calls often so when i notice the problem i have been reflashing rom then kernel to fix it. I check the call audio and it works. Then i do the nfc fix and reboot. Then call audio is broken again.
Any ideas?
Also reflashing the radio didn't help
Viperone 7.0.1
Elementalx 18

dgl6y7 said:
Edit: after a lengthy cycle of trying to fix my call audio problem it seems that the nfc fix is breaking it. I dont make calls often so when i notice the problem i have been reflashing rom then kernel to fix it. I check the call audio and it works. Then i do the nfc fix and reboot. Then call audio is broken again.
Any ideas?
Also reflashing the radio didn't help
Viperone 7.0.1
Elementalx 18
Click to expand...
Click to collapse
Edit2: it now looks like the NFC fix is just a coincidence. After reflashing the ROM and the kernel I have call audio on first boot. As soon as I restart call audio is broken again. Am i screwing up something with the double restart after flashing this kernel? I know the instructions say wait for it to fully boot before restarting. I was considering the phone fully booted when the c1, c2, and c3 went to idle. Should I wait longer?

dgl6y7 said:
Edit: after a lengthy cycle of trying to fix my call audio problem it seems that the nfc fix is breaking it. I dont make calls often so when i notice the problem i have been reflashing rom then kernel to fix it. I check the call audio and it works. Then i do the nfc fix and reboot. Then call audio is broken again.
Any ideas?
Also reflashing the radio didn't help
Viperone 7.0.1
Elementalx 18
Click to expand...
Click to collapse
dgl6y7 said:
Edit2: it now looks like the NFC fix is just a coincidence. After reflashing the ROM and the kernel I have call audio on first boot. As soon as I restart call audio is broken again. Am i screwing up something with the double restart after flashing this kernel? I know the instructions say wait for it to fully boot before restarting. I was considering the phone fully booted when the c1, c2, and c3 went to idle. Should I wait longer?
Click to expand...
Click to collapse
I found your solution by simply searching for 'call audio' in the Viperone thread, a simple search and you would have found the solution that somebody already posted...
http://forum.xda-developers.com/showpost.php?p=57482456&postcount=5647
Even the Developer posted how to see a fix within the ViperHub...
http://forum.xda-developers.com/showpost.php?p=57570782&postcount=5665

ABANDONED!!! [ROM][HYDROGEN/HELIUM][FIXED]CM13 Unoficial 2016-06-14 UNIVERSAL-FIXED

The base rom turned out to be full of small bugs and just not worth it any future work on it. Sorry...
After two days of digging around finally managed to fix the only CM13 release that doesn't have the nasty and so far impossible to fix 3G bug some of us experience with all other CM based releases to date.
I think this ROM by itself deserves a new thread despite the many we have already... Don't you agree?
Fixed Video Playback, Video Recording, Network Location, Speaker Low Volume Level... Those were the major known issues with this version...
Will get us by till 3G bug is fixed(I hope) in later ROMs.
Credits and thank you to:
@ffboy2009[/MENTION] for his 2nd CM13 release this ROM is based on;
@ajsmsg78[/MENTION] for the helium video recording fix;
This is all-in-one Mi Max UNIVERSAL CM13 ROM for both hydrogen and helium devices. It will check an install the proper version for your device.
BUT MAKE SURE YOU ARE RUNNING THE CORRECT TWRP FOR YOUR DEVICE CODE!!! HELIUM WITH OLD TWRP FOR HYDROGEN WILL BRICK!!!
If you are coming from any CM13 rom you can dirty flash. From anything else including RR clean flash is recommended! Backup device before install etc but you know what to do if reading this...
As usual install gapps etc...
Report bugs and I will try fixing them but I am very time/resources limited during the week.
Download: cm-13.0-20160614-UNOFFICIAL-hydrogen+helium-fixed_nijel8.zip
PS. Will appreciate if you guys don't link the ROM download directly anywhere else... Refer to this thread instead... Let's keep it all in one place for better feedback. Thank you!

Just did a clean install. Video recording doesnt work. Tried adding the fix line in build.prop but didn't help.

n1tro said:
Just did a clean install. Video recording doesnt work. Tried adding the fix line in build.prop but didn't help.
Click to expand...
Click to collapse
It's not the build.prop...
What exactly is doing? No sound or else... Need to know to fix it for helium I can't test...

nijel8 said:
What exactly is doing? No sound or else... Need to know to fix it for helium I can't test...
Click to expand...
Click to collapse
After pressing record, it just starts and stops. I took the fix file that asjmsg78 created and flashed it and also left the fix line in the build.prop and it works with sound. I let the phone sleep for a bit and seems to be still working.

Same here in another helium, just start to records and stop suddenly :crying:

n1tro said:
After pressing record, it just starts and stops. I took the fix file that asjmsg78 created and flashed it and also left the fix line in the build.prop and it works. I am letting the phone sleep and will test again.
Click to expand...
Click to collapse
Ok... I'll fix it... Just to be clear you are talking about this file for helium, right? Because it is not needed for hydrogen...
[FIX] [HELIUM] [HYDROGEN] Video Recording Fix by ajsmsg78

nijel8 said:
Ok... I'll fix it... Just to be clear you talking about this file for helium, right?
[FIX] [HELIUM] [HYDROGEN] Video Recording Fix by ajsmsg78
Click to expand...
Click to collapse
Yes, that is the file I used to flash after installing this rom.

n1tro said:
Yes, that is the file I used to flash after installing this rom.
Click to expand...
Click to collapse
Ok, thank you for the quick reply... We'll get it fixed right away...:good: Fixed... Uploading... Done...
Glad no flashing problems on helium. Took a slim chance by not having you or @ajsmsg78 test it on your heliums before publish it.

Skalexs said:
Same here in another helium, just start to records and stop suddenly :crying:
Click to expand...
Click to collapse
Please redownload... Just fixed it...

I just got home and saw this. Great news. I'm glad you were able to fix everything. All we need now is to figure out the data bug and most of our roms should be perfect

ajsmsg78 said:
I just got home and saw this. Great news. I'm glad you were able to fix everything. All we need now is to figure out the data bug and most of our roms should be perfect
Click to expand...
Click to collapse
Yeah... data bug is going to be difficult without proper debugging and taking logcat/dmesg logs. We both can't do that...
Let me know if you want to fix RR5.7.0 and I will give you details...

nijel8 said:
Please redownload... Just fixed it...
Click to expand...
Click to collapse
Great
I've made a clean install and video recording works :good:
Thanks for the time you've wasted here :victory:
PD: I had data bug in RR, but with this rom it seems to work perfectly

nijel8
Thank you!:good:

Skalexs said:
Great
I've made a clean install and video recording works :good:
Thanks for the time you've wasted here :victory:
PD: I had data bug in RR, but with this rom it seems to work perfectly
Click to expand...
Click to collapse
That's why I fixed exactly this one...

Awesome work dude!!!
In general, how does the battery life compare on cyanogenmod ROMs compared to miui?
What about reception/signal compared to miui?
Also, I assume we don't need a locked bootloader for this
I can't wait to try it:victory::victory:

Great job bro..3g working here..Greeting from Malaysia...
Helium 64gb
Sent from my MI MAX using XDA-Developers mobile app

Great Job!
Thanks for the effort, video recorder has become useful again
Just one request, add the Enhanced LTE mode in the sim network options section. Annabathina build has the same issue of no selection/activation menu.
Wish you get a fix really soon. And thanks again.

techy97 said:
Thanks for the effort, video recorder has become useful again
Just one request, add the Enhanced LTE mode in the sim network options section. Annabathina build has the same issue of no selection/activation menu.
Wish you get a fix really soon. And thanks again.
Click to expand...
Click to collapse
Ii didn't build this rom... I am just the fixer... Adding things is not that easy in prebuilt roms.
Even if I can add it I can't test LTE at all and I hate doing things I can't test... So probably not gonna happen, sorry...

panyan said:
Awesome work dude!!!
In general, how does the battery life compare on cyanogenmod ROMs compared to miui?
What about reception/signal compared to miui?
Also, I assume we don't need a locked bootloader for this
I can't wait to try it:victory::victory:
Click to expand...
Click to collapse
for me: normal use on Miui--> 1,5 days, normal use on CM-->3,5 days

This ROM should tie people over until xiaomi releases the kernel for our devices and some developers come into the picture. Amazing how much was accomplished by nijel8 and asjmsg78, both who aren't developers but had enough curiosity about our devices to tinker with it to make it a better device for all. Show some appreciation by making a donation to these guys or we all be stuck with the crappy miui ROM with no android auto and delayed notifications!

[DISCUSSION] Cyanogenmod 13 for the Huawei P9 Lite

This thread was made to keep the development thread of Cyanogenmod 13 clean.
If you have any question related to this rom,feel free to ask here!
EDIT
Due to certain circumstances and requests by several people to share my link of the CM build I produced,here is the link to the folder:
DOWNLOAD
NOTE
The source code is by Meticulus.
This is also for those who installed the CM build on the Honor 5C,please do give feedback so a Working/Not Working list can be assembled.

Used cyanogenmod 13 for a while on this phone but decided to revert back to stock because of the camera. now when i try to install it and do a factory reset from twrp i cant!
on twrp boot it gives me an error that it cant mount /data (no such file or destination) thus not wiping it, thus not being able to install cm13. any help?
EDIT: seems that twrp doesnt detect internal storage at all. shows 0mb available , but i can browse it on the stock file manager just fine. ideas?

slumpijs said:
Used cyanogenmod 13 for a while on this phone but decided to revert back to stock because of the camera. now when i try to install it and do a factory reset from twrp i cant!
on twrp boot it gives me an error that it cant mount /data (no such file or destination) thus not wiping it, thus not being able to install cm13. any help?
EDIT: seems that twrp doesnt detect internal storage at all. shows 0mb available , but i can browse it on the stock file manager just fine. ideas?
Click to expand...
Click to collapse
try to flash custom rom based on stock
and then flash stock recovery and then do a factory reset from stock recovery
try it and tell me what happened
sorry for my poor English

hey can I flash the new update without formatting the system?

Double touch to unlock and swipe to lock are working?

Claleale said:
Double touch to unlock and swipe to lock are working?
Click to expand...
Click to collapse
I don't think so,but you can unlock the phone instantly with your fingerprint,so I personally see no reason to use DT2W on this device.

I have a question,
if only LTE is availeble, what happen when you are in a place where the reception isn't good? Does the network stop working?

Potato997 said:
I have a question,
if only LTE is availeble, what happen when you are in a place where the reception isn't good? Does the network stop working?
Click to expand...
Click to collapse
When i have no LTE coverage, i have 3G network, so no

Everytime i want to pair my LG G Watch bluetooth turns off... And new on again...
Somebody the same Problem?

StefanSpiegel said:
Everytime i want to pair my LG G Watch bluetooth turns off... And new on again...
Somebody the same Problem?
Click to expand...
Click to collapse
I had this problem with my bluetooth headset, but after trying and trying it worked

enzo24754 said:
I had this problem with my bluetooth headset, but after trying and trying it worked
Click to expand...
Click to collapse
did you try something spezial?

StefanSpiegel said:
did you try something spezial?
Click to expand...
Click to collapse
Nope, just trying

How difficult will it be to get a CM 14 build up and running once we have a working CM 13 build (using CM13 as template)?
Just wondering because first CM 14 builds are out for other devices.

Schlengge said:
How difficult will it be to get a CM 14 build up and running once we have a working CM 13 build (using CM13 as template)?
Just wondering because first CM 14 builds are out for other devices.
Click to expand...
Click to collapse
CM13 can't be used as a template.
Other devices got CM14 because:
a)their stock rom stopped at MM,but their developers made the blobs open source,so they can easily go to CM14
b)they already have stock N,so they simply use the blobs from it.
Our device doesn't meet none of the provided scenarios,we will probably get stock N on December,and only then will we be able to start working on it.
Sent from my P9-Lite using Tapatalk

HassanMirza01 said:
@Meticulus if possible, upgrade the camera to 13mp first,,, we all are just waiting for original camera to install CM13 ❤ love your work in quick time :thumbsup
Click to expand...
Click to collapse
But... 13MP camera works on Google Camera...

enzo24754 said:
But... 13MP camera works on Google Camera...
Click to expand...
Click to collapse
Yah,but that pearl even had the audacity to order a developer what to work on,I doubt logic would work on him. :silly:
Sent from my P9-Lite using Tapatalk

I don't understand why people don't respect developers will.. They can work on whatever they want, if you have these kind of request just build your own ROM.

Potato997 said:
I don't understand why people don't respect developers will.. They can work on whatever they want, if you have these kind of request just build your own ROM.
Click to expand...
Click to collapse
Suggestions are okay, but not orders

Did the CM13 development stop?

I don't hope so..

Delete

:good:Thank you for the hard work

vlad3647 said:
:good:Thank you for the hard work
Click to expand...
Click to collapse
Naaaa...Tanks to @pduper:silly:

Many thanks to you @luisgonzales1977 for your work.
sm-g900i
Formatted and advanced cleaned
Installed Bliss-v12.2-klte-UNOFFICIAL-20200128 and open_gapps-arm-10.0-pico-20200124 together
Rom is very nice.
I have noticed that audio levels are low and device lags while in settings menu.
Anyone else experiencing this?

pmduper said:
Many thanks to you @luisgonzales1977 for your work.
sm-g900i
Formatted and advanced cleaned
Installed Bliss-v12.2-klte-UNOFFICIAL-20200128 and open_gapps-arm-10.0-pico-20200124 together
Rom is very nice.
I have noticed that audio levels are low and device lags while in settings menu.
Anyone else experiencing this?
Click to expand...
Click to collapse
yes...I installed earlier and I think its the best of the new Android 10 Roms for our device....I installed the Intelli Kernel and raised the volume levels....the lag in settings is a pain... I noticed the gear on the footer of quick settings wont work unless you bring the pull down all the way out....My guess is an overlay is probably in conflict with the system ui

Test Build Upload ...
Download.

luisgonzales1977 said:
Test Build Upload ...
Download.
Click to expand...
Click to collapse
Would love to test this but very happy with your other test build MSM Xtended that I have been using it all day with no problems..thanks again for the work you are putting into these roms

Fonts not working correctly...not all the phone and all the apps are fonted with my selected font in settings..sound to low..i cant hear anything when call or when receive some notification...and why no one cant fix connect headsets?...all android 10 mods have same problems..like copy pasted and changed ui only

Skerleton said:
Fonts not working correctly...not all the phone and all the apps are fonted with my selected font in settings..sound to low..i cant hear anything when call or when receive some notification...and why no one cant fix connect headsets?...all android 10 mods have same problems..like copy pasted and changed ui only
Click to expand...
Click to collapse
You have to know that android 10 is Beta Stage. If you don't want to face these bugs, you can simply go back to LOS 16, which is stable.
Bluetooth problem is always issue since LOS 15.1, so you'd better not expect to fix it in few days only.
See curiousrom's post that says you should don't press devs to fix these issues since they do volunteering. Therefore, if you keep this attitude, you will be sad because no one will develop any roms then.

SmgKhOaRn said:
You have to know that android 10 is Beta Stage. If you don't want to face these bugs, you can simply go back to LOS 16, which is stable.
Bluetooth problem is always issue since LOS 15.1, so you'd better not expect to fix it in few days only.
See curiousrom's post that says you should don't press devs to fix these issues since they do volunteering. Therefore, if you keep this attitude, you will be sad because no one will develop any roms then.
Click to expand...
Click to collapse
Lineage os is ****..best pie os is DOT OS 3.1

Skerleton said:
Lineage os is ****..best pie os is DOT OS 3.1
Click to expand...
Click to collapse
Wrong thread mate. Take your disrespectful comments elsewhere!!

Skerleton said:
Fonts not working correctly...not all the phone and all the apps are fonted with my selected font in settings..sound to low..i cant hear anything when call or when receive some notification...and why no one cant fix connect headsets?...all android 10 mods have same problems..like copy pasted and changed ui only
Click to expand...
Click to collapse
Oh no!! And on top of all that mummy didn't give you any lunch money! I feel for you my friend, I really do. It must be so tough going through life with no respect for anyone, especially when they are working hard and free of charge to bring your aging device up to date, God that sucks doesn't it.l?! Tell you what, you go and enjoy your pie and the grown ups will come and let you know when all these iddy biddy widdle bugs have gone.

I can't download the link, because the file was deleted.
Who can give me a download link?
Thanks!

Access denied where can I download the rom?

n_boy86 said:
Access denied where can I download the rom?
Click to expand...
Click to collapse
Try this link ?
https://qc5.androidfilehost.com/dl/...3197/Bliss-v12.2-klte-UNOFFICIAL-20200130.zip

I expected many Problems when migrating to a q Rom. Waited until today and started with Bliss.
And all i can say is that this Rom is awesome in responsiveness and Options. Everything is working so far. Only Thing is that there is no selinux set for now.
But that is okay. Everything else just works amazingly good!
Phone (with Recorder outofthebox), Camera, all Google Apps, WiFi, Mobile Data, Magisk
Also my 128g sd was set up as adopted storage and uses f2fs by Default. Nice!
Not a single glitch or freeze.
Will consider using this as my daily Driver.
Coming from LineageOS16
Big thanks to the devs from bliss project and OP of this Thread!!!!

Thinking about formating my DATA and CACHE also as F2FS. Would that Work and is that a good Idea? What do you think? More over is it possible to use also System as F2FS with Bliss?
Would really appreciate it.
And i found a little bug with gboard. There is a little unused space between my navbuttons and the bottom of my gboard. Is there an Option to Change that?
Thanks

ajox said:
Thinking about formating my DATA and CACHE also as F2FS. Would that Work and is that a good Idea? What do you think? More over is it possible to use also System as F2FS with Bliss?
Would really appreciate it.
And i found a little bug with gboard. There is a little unused space between my navbuttons and the bottom of my gboard. Is there an Option to Change that?
Thanks
Click to expand...
Click to collapse
I think its better to change only cache partition because f2fs is unstable due to our kernel version.
when I used this rom with tuned kernel, f2fs all, apps stopped frequently so I had to reboot a lot of time. This is just my opinion.
You have to disable gesture navigation bar to remove that blank.

SmgKhOaRn said:
I think its better to change only cache partition because f2fs is unstable due to our kernel version.
when I used this rom with tuned kernel, f2fs all, apps stopped frequently so I had to reboot a lot of time. This is just my opinion.
Click to expand...
Click to collapse
Did You try that with intelli Kernel, too? But as you said the rom is generally capable to usw F2FS formated system Partition right?
Think i will give it a chance this weekend.
SmgKhOaRn said:
You have to disable gesture navigation bar to remove that blank.
Click to expand...
Click to collapse
Thought about something like that. Anyway i dont find such setting... Maybe iam blind?

ajox said:
Did You try that with intelli Kernel, too? But as you said the rom is generally capable to use F2FS formated system Partition right?
Think i will give it a chance this weekend.
Thought about something like that. Anyway i dont find such setting... Maybe iam blind?
Click to expand...
Click to collapse
IDK since I don't like that kernel...
I didn't tested on this rom (using other Q rom now) so You can try and tell about the results... (Backup data first, don't need it on cache if you want...)
Just search it in setting's search section (type gesture if you can't find)...
Or remove qemu.hw.mainkeys=0 in build prop...
Can't use f2fs in System partition lol...
It will force to install as ext4 even you format it to f2fs...
This is all same in other roms...