yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] gumbi2647:
If it doesn't work then you have to uninstall contacts in tibu and download contacts from the play store. Reboot your phone before downloading. Then I had to go into dialer and try a favorite and then it asked for permissions and which contacts app to use. If you choose the wrong one then it will keep crashing. So go into settings apps and reset the open with permission.
[Moto Maxx Android Development] fgl27:
ROM no gapss Contacts 100%

ROM + open.pico 20160621 Contacts 100%

may have others old version of open that are 100%, old V of open...

https://github.com/opengapps/arm/releases?after=20160622

clean install advice.
[Moto Maxx Android Development] gangrenius:
Mine worked. But I had uninstalled previous and installed playstore and set it to system then upgraded rom and mine is fine.
[Moto Maxx Android Development] fgl27:
:confused:

upgrade of the ROM erase system so you have the contact from the ROM as you made that one part of system it was erased...

Clean install must resolve all of that, as I change contacts did a clean and my dialer integrates with contacts just fine no permission ask noting related to setting, works without any interaction...
[Moto Maxx Android Development] gumbi2647:
I dirty flashed and that is how I got mine to work. XT1254 is what I have. It works for me and that's all I care about. ROM is smooth and runs great!
[Moto Maxx Android Development] fgl27:
;)

uninstall the app removes any setting related attached to that app (default apps, data/cache, other app connection etc... that may be bug because of the old AOSP app), installing it from play will redo any need for that when you start to use the app and making new relation when using others apps.

the app on play is the one in the ROM, if you dirty flash and the app was on system you have the one form ROM but is all the same.

you just fake a clean install that only had affect on Contacts.apk and it relation to the rest... so yours workaround seems to resolve the problem without clean install with is good, but some point in the future may be need some real clean install...
[Moto Maxx Android Development] fgl27:
Can some XT1254 user do some test (simultaneous voice and data over LTE) using this test kernel.

BHB27-Kernel-V201-4-M_Teste.zip

Flash the kernel, try to use voice with data a download or webpage load over LTE during a phone call, if no good try to disable then enable data, disable then enable enhanced LTE... test again repeat some times 2 to 3...

Then after share some report how it was and logs here...

Logs:

kernel adiutor app > setting > click Logcat + Driver Message... files (dmesg.txt and logcat.txt) in internal storage, zip both in a single file to be easy to attach here...

that kernel is the same as released yesterday + some changes to VoLTE related services...

To restore the default ROM kernel is need to dirty flash the current ROM version...

:good:
[Moto Maxx Android Development] immadeofpixels27:
Would it not be simpler to make a backup of the current kernel in TWRP before flashing this test one? Or does the zip also modify something else that requires the entire ROM to be re-flashed?
[Moto Maxx Android Development] immadeofpixels27:
[MENTION=5747496]bhb27[/MENTION] I tried using VOLTE on the test kernel and it didn't work. Here are the logs:

Edit: if they're too cluttered with Xposed stuff, just ask and I'll do it again with Xposed disabled
[Moto Maxx Android Development] kitcostantino:
i didnt do all that (^3) and Contacts is perfect. i did do a clean, full install with no Twrp data restores. couple of TiBup restores (trans es file explorer, old version of Root Browser without annoying BusyBox [pro] advert, um recommendation....ultimately, zero issues with this ROM. I used Bluetooth and GPS for 3-4 hours today. Typical usual net activity otherwise. i ran Darkness under clocked and under volted. Somehow Mp Decision and Intelliplug were on. All is well. Many thanks [MENTION=5747496]bhb27[/MENTION] !!!!
[Moto Maxx Android Development] Henriqueceni:
[MENTION=5747496]bhb27[/MENTION] any way to instal this rr without bhb27 kernel? If i instal this kernel i cant use any mobile data :(
[Moto Maxx Android Development] Nitefire77:
Just use the stock kernel that installs with the rom
[Moto Maxx Android Development] Henriqueceni:
Oh ill try it ty man
[Moto Maxx Android Development] gangrenius:
That's nothing I got 6 hours sot with moderate to heavy use
[Moto Maxx Android Development] kitcostantino:
What settings do you run in bhb27 kernel aidutor?
[Moto Maxx Android Development] fgl27:
1. Not demanding installing any kernel with the ROM.

2. I don't release a damage kernel, data is just fine on my kernel.

Revise what you are doing besides the kernel change...
[Moto Maxx Android Development] Henriqueceni:
Everything going fine with any rom, when i try rr my mobile data gone, so i assume the problem is the bhb27 kernel, and if i try to instal this kernel on stock rom my mobile data gone too.
[Moto Maxx Android Development] gangrenius:
Just as it is. I don't change anything. Try running stock kernel too. I put my phone in deep doze in the rr settings and I use greenify paid also. I don't ever have GPS on though. Mainly YouTube and browsing and listening to music over Bluetooth.
[Moto Maxx Android Development] kitcostantino:
Xt1225 or xt1254? also, it never hurts to keep a fxz for your device around so you can do:

fastboot flash radio radio.img

i have to do that occasionally on cm based ROMS.

I assure you, its not the kernel.
[Moto Maxx Android Development] colthars:
just to say

the contacts problem

i solved it by uninstall it whit tibu

downloaded version 1.4.9 from apk mirror

copied it to system/app

reboot

also have to install again clock app
[Moto Maxx Android Development] SimpTheChimp:
Okay that seemed to work. Is there any reason why tibu worked better at uninstalling the contacts in system rather than other apps? I had tried that before with one of the freebie system uninstallers but it didn't work properly.

Anyway, contacts are now working as they should. [emoji4]
[Moto Maxx Android Development] quantum tao:
[MENTION=5747496]bhb27[/MENTION] volte test.

Tried multiple times. Even downloaded my Verizon app and toggled hdvoice off on account, rebooted, went to account and resubscribe to hdvoice, rebooted(had to do this to make it work in cf's ROM). Didn't work.
[Moto Maxx Android Development] gumbi2647:
Tibu is a root app and has the ability to uninstall system apps. I'm not 100% sure but that's my guess.
[Moto Maxx Android Development] drizzzzzz:
I have a bug that's been consistent over many flashes. I didn't report it earlier because I thought I just need to do a clean flash, which I finally did. I still have an issue when unlocking the screen. Occasionally, when I turn the screen on and go to swipe up, the clock moves a little like it's going to unlock, but it just bounces back down to the locked position. I can try this as many times as I want, but it won't unlock the phone. The only solution is to turn the screen off and on again. It's not a huge bug, or too frequent, but it happens enough to be an annoyance. I don't have Xposed or any other mods installed yet. Does anyone else have this issue/have a solution?
[Moto Maxx Android Development] immadeofpixels27:
Are you using the latest release version of his custom kernel or the VOLTE test kernel? I also had the the same problem after a while on the test kernel, but going back to the release version fixed it.
[Moto Maxx Android Development] Nitefire77:
Ive had it happen to me a couple times but It was never a big deal to me
[Moto Maxx Android Development] Henriqueceni:
I just give up, today in my first boot everything is fine even my mobile data "LTE" but when i restart my phone my data doesnt work anymore, dunno what to do anymore...
[Moto Maxx Android Development] gangrenius:
So this is your first time and your giving up? Try airplane mode on then off. Did u flash everything necessary? What's your radio image? Was this a clean flash? Your not giving very much info.
[Moto Maxx Android Development] fgl27:
Are you shore It was not the reboot that fix?

Network problem on the carrier side, maybe just the time it takes to reboot and network to reestablish on the carrier side...

I need data from those changes without those VoLTE will ever work. If data works for some time I doubt they can be damage after a while with those...

Those things I can't test I depend on users reports and logs, as I only have a XT1225...

That user is from Brazil, I doubt he is on XT1254 on VZW network if he used the test kernel he did not read right the purpose of the test V...

I never had any problem running my Kernel on Brazil carrier so he must have another problem or he doesn't know how to config the device in the data/apn configs... there is google to help on that, still I don't need to make any manually config to get any data to work it all works just fine no user interaction need...
[Moto Maxx Android Development] gumbi2647:
I have been on your volte test kernel since its release on my xt1254. I haven't had any problems with data connection. I don't have volte as expected but no problems with the kernel itself.
[Moto Maxx Android Development] mirdones:
Friends,

I know this post has no relation to the rom, But I'd like to say Thanks to [MENTION=5747496]bhb27[/MENTION] and to [MENTION=2228410]Skrilax_CZ[/MENTION] for the development of roms and kernels for the Moto Maxx.

Without you two we would have a much worse phone.

I just sold my XT1225 and bought a Galaxy S7 Edge so I won't participate anymore in this forum.

Any way, Thanks.
[Moto Maxx Android Development] Henriqueceni:
Already tried 30times, model xt1225, flashed all radio images from 5.0 to 6.1, tried dirt ant clean instal, dunno whats happening with this rom, any other rom instal perfectly, i can do a video of my issue and share if anyone as able to help.
[Moto Maxx Android Development] fgl27:
video show noting...

you need to provide logs after the problem:

Logs:

kernel adiutor app > setting > click Logcat + Driver Message... files (dmesg.txt and logcat.txt) in internal storage, zip both in a single file to be easy to attach here...

+ plug the device on computer in adb mode give adb permission in developer and post all the output of the below command

adb shell getprop

output of command is something like this but with more lines...

[sys.sysctl.extra_free_kbytes]: [43200]
[sys.sysctl.tcp_def_init_rwnd]: [60]
[sys.usb.config]: [mtp,adb]
[sys.usb.configfs]: [0]
[sys.usb.ffs.ready]: [1]
[sys.usb.state]: [mtp,adb]
[telephony.lteOnGsmDevice]: [1]
[usb.mtp.config]: [mtp,usbnet]
[usb.mtp.pid]: [2ea4]
[use.dedicated.device.for.voip]: [false]
[use.voice.path.for.pcm.voip]: [true]
[vold.has_adoptable]: [0]
[vold.post_fs_data_done]: [1]
[wifi.interface]: [wlan0]

+ device model, last stock ROM used and carrier.

:good:
[Moto Maxx Android Development] Henriqueceni:
well here we go
[Moto Maxx Android Development] NepoRood:
Connect USB to a running device, then open command window (terminal)
[Moto Maxx Android Development] fgl27:
ADB log of the ROM after the problem is display to you.

that is adb from TWRP.
[Moto Maxx Android Development] Henriqueceni:
Adb from twrp doesnt work here keeps loading for ever....
[Moto Maxx Android Development] fgl27:
you have just post a adb log from TWRP.

I need the ROM...

enable adb in developer

setting > developer > android debugging

then give permission on the screen after you give a command in terminal
[Moto Maxx Android Development] fgl27:
Good if that give problem let me know...

I doing some fix and improves, even if VoLTE doesn't work on the next version, there will be more log's about VoLTE and will be better to understand way...
[Moto Maxx Android Development] quantum tao:
does apn matter? sometimes i look and its set to vzwadmin, i normally set it to vzwinternet. is there a correct one to use for our device on verizon ?

thanks for all the work you are doing to make volte work.
[Moto Maxx Android Development] newbe1droidx:
Vzwadmin is the same, your good. Straight talk is the problem child
[Moto Maxx Android Development] quantum tao:
the settings are not the same
[Moto Maxx Android Development] neur0tk:
This is how I run my radio with WiFi and good results so far :)

I use this app to select the radio

https://play.google.com/store/apps/details?id=de.mangelow.network
[Moto Maxx Android Development] hpbrasil:
Sometimes the capacitive buttons slow to respond, does not happen only to me.
[Moto Maxx Android Development] paborges:
Reboot didnt work for me.

DPI change to 520 made the trick, surprisingly and unexplainably.

dont know for how long.
[Moto Maxx Android Development] immadeofpixels27:
Like the attached pictures. You could've just checked the other apps and folders in /system/private :p
[Moto Maxx Android Development] kitcostantino:
im guessing dialing *#*#4636#*#*

doesnt work anymore.
[Moto Maxx Android Development] neur0tk:
Idk didn't try it
[Moto Maxx Android Development] fgl27:
The fix is not a DPI change, but the force soft reboot that happens after, if you just soft reboot without change the dpi the result is the same flash/torch works...

Need to discovery way :eek:.... :good:
[Moto Maxx Android Development] iiWoodstocK:
Still works. That's how I get to the hidden menu
[Moto Maxx Android Development] gumbi2647:
Still works for me too
[Moto Maxx Android Development] Latiken:
Interesting; I'll try a soft reboot when my flashlight stops working.

Glad to know we came up with a temporary fix.

EDIT: I can confirm that a soft reboot fixes the flashlight.

If you're chop chop crashes CMActions, perform a soft reboot.
[Moto Maxx Android Development] GreaterLesser:
DPI seems to be the torch fix for me on my XT1254 - A SystemUI did nothing for me. Changed to 520 dpi and now torch survives a reboot and the icon stays in QS.

Update: Nvm it survives a manual reboot but doesn't survive a system crash - that is very weird...
[Moto Maxx Android Development] fgl27:
Do a "soft reboot" not a "systemui reboot"...

But never mind I find a perm fix...

@ all

It will be on the next ROM, but for now any one can use my kernel with the fix...

BHB27-Kernel-V126-CM-RR-Test-12-M

A update ROM with this fix + some improves in 24h... :good:
[Moto Maxx Android Development] Latiken:
Nice work.

I feel like I contributed to a fix :)
[Moto Maxx Android Development] RSDamasceno:
I managed to install this build and FINALLY my wifi works PERFECTLY!

THANKS!

--

Moto Maxx - XT1225

Xposed RR Rom 5.1.1
[Moto Maxx Android Development] fgl27:
Some other user with that bug, already reported that too. seems that all is working now...

I expect the fix to be on the kernel, if used my last test version on top o CM or RR it must work...

Have you tested my kernel a new version on top of a old RR before 02-27 or CM?

with ROM and version ? and what is the result?

if you did tell me... :good:
[Moto Maxx Android Development] Latiken:
I seem to be getting an odd bug where after a bit of watching a video or playing a game, it will freeze.

For example if I'm watching a video after like five minutes or so it will freeze or start jittering, but the sound will keep playing. If I swipe to bring up the status bar (and nav bar since I have those enabled) it will go back to normal.

Not sure if its an issue with the ROM or kernel.

Running latest ROM build and Test 11 kernel
[Moto Maxx Android Development] quangv:
[MENTION=5747496]baybutcher27[/MENTION]: weather is working right now. But i have wifi issue: when i chosen other network from quick setting panel it was turned off wifi immediately.
[Moto Maxx Android Development] colthars:
anyone can say if chromecast is working fine?
[Moto Maxx Android Development] immadeofpixels27:
That happens to me when I expand the QS tile. I don't even get a chance to attempt a network switch :silly:
[Moto Maxx Android Development] ceelos218:
just used it not too long ago.. so yes its working fine.
[Moto Maxx Android Development] newbe1droidx:
Hmm looked at mine and are the same, where are you

OK looked closer you are correct! I guess you could delete the higher ones so it becomes default. I tried that before and it screwed things up on my phone. Had to factory reset to get it to work again.
[Moto Maxx Android Development] iiWoodstocK:
The thing is that the APNs aren't limited to what you see in the settings menu. Within the config file itself, the Verizon APNs on RR are a mish-mosh of numerous Verizon APNs from what I've seen. IIRC, the Straight Talk one is actually the most accurate one (oddly enough). For the past couple days, I've been using the APN config file from SU4TL-49. So far, it's mostly fine. I've encountered some issues where my mobile data doesn't know what to do, however, I've been using a rather "dirty" setup that contains extras from a failed VoLTE test I did.
[Moto Maxx Android Development] quantum tao:
Figures, that's the only one I deleted.
[Moto Maxx Android Development] newbe1droidx:
Just go to 3 dots top right and restore defaults
[Moto Maxx Android Development] Nitefire77:
he wanted a log not your build prop
[Moto Maxx Android Development] Henriqueceni:
just did the comand

"+ plug the device on computer in adb mode give adb permission in developer and post all the output of the below command

Code:

adb shell getprop"
[Moto Maxx Android Development] fgl27:
That was what I need...

custom ROM is setting up your device as XT1254 verizon see

[ro.build.description]: [quark_verizon-user 5.1 SU4TL-44 44 release-keys]
[ro.build.display.id]: [rr_quark-userdebug 6.0.1 MOB30Z 6f969d92c7 test-keys]
[ro.build.fingerprint]: [motorola/quark_verizon/quark:5.1/SU4TL-44/44:user/relea
se-keys]
[ro.com.google.clientidbase.am]: [android-verizon]
[ro.com.google.clientidbase.gmm]: [android-motorola]
[ro.com.google.clientidbase.ms]: [android-verizon]
[ro.com.google.clientidbase.yt]: [android-verizon]
[ro.fsg-id]: [verizon]

your device has no idea what device it is, it is missing a prop line

this:

[ro.boot.hardware.sku]: [XT1225]

try this on CMD:

adb shell getprop | grep XT

and

adb shell getprop | grep sku

I'm not on widows this command may not work on windows CMD...

if error or no answer do

adb shell

enter

then just

getprop | grep XT

and

getprop | grep sku

Print the terminal screen if you can...

that missing line is the problem in custom ROM...

What device you have? how you get it? what carrier?

answer me all, so I can understand and solve this...

:good:
[Moto Maxx Android Development] Henriqueceni:
my device is moto maxx xt1225 from brazil no carrier, its a retail,

"adb shell getprop | grep XT" doesnt work on cmd anything wrong?

message is "grep" não é reconhecido como um comando interno.
[Moto Maxx Android Development] fgl27:
it works only on linux... try this for windows

adb shell

enter

then just

getprop | grep XT

and

getprop | grep sku

try those above for me please... they must out put empty, not a error...

the fix is on the bootloader

Do

this line

fastboot oem config fsg-id singlela

output is

...
(bootloader) <UTAG name="fsg-id" type="str" protected="false">
(bootloader) <value>
(bootloader) singlela
(bootloader) </value>
(bootloader) <description>
(bootloader) FSG IDs, see http://goo.gl/gPmhU
(bootloader) </description>
(bootloader) </UTAG>

OKAY [ 0.019s]
finished. total time: 0.019s

fastboot must be on the same folder as you ADB some times it is call mfastboot so change fastboot to mfastboot...

After the line run ok "OKAY" you can reboot...

fastboot reboot

theoretically it must work but is advised to do a clean install so all "verizon" config is erased...

Before clean install past here again all the output of

adb shell getprop

Of course after the fastboot command and a reboot
[Moto Maxx Android Development] fgl27:
all the configuration are OK now setup as XT1225, if it doesn't works try a clean install to clean remaining bad props

Report after. :good:
[Moto Maxx Android Development] Henriqueceni:
man... realy realy thanks all fine now *-* iv tried this for months and nothing.... but now its working fine *----*:laugh:
[Moto Maxx Android Development] pedrohxn:
Latest build + latest kernel + latest KA running faster and smoother than ever.

Thanks [MENTION=5747496]bhb27[/MENTION] !!
[Moto Maxx Android Development] fgl27:
Nice

your device came out of the factory without received a device prop... this

[ro.boot.hardware.sku]: [XT1225]

I don't know if it can be add/change by the user on this device, not need don't worry...

There is the chance that your fsg-id can change if you flash back stock... this is not normal this is the first time that I see a device "not knowing what it is"...

So if you notice a problem like that again check for fsg-id and remember on custom ROM it need to be singlela... the "Multi device support" use on custom ROM need to support XT1225, XT1250 and XT1254 depends on that "ro.boot.hardware.sku" with that missing the device is set as wrong device model and can cause those problem...

:good:
[Moto Maxx Android Development] fgl27:
Any one have the build.prop of SU49?

Please share, I'm on low internet speed land can't download those SU49 zip...
[Moto Maxx Android Development] Henriqueceni:
ok man ill save this post for any issues i can have on future, and as i tould my device where crazy and i did nothing wrong xD
[Moto Maxx Android Development] koftheworld:
It's from CF's latest so it's not pure SU49.
[Moto Maxx Android Development] iiWoodstocK:
I have CF 1.3.7 (SU4TL-49). Maybe [MENTION=7237874]NepoRood[/MENTION] has stock SU4TL-49.

disregard, [MENTION=2640499]koftheworld[/MENTION] beat me to it
[Moto Maxx Android Development] pedrohxn:
[MENTION=5747496]bhb27[/MENTION] I have the developer option for showing CPU info enabled to monitor CPU frequencies, and I noticed when the battery drops down under 30% no more than 2 cores goes online no matter what I do... Disabling hotplug drivers, forcing via command shell...

I believe this is a policy for battery saving, am I right?

Is there any way to disable it and have all 4 cores allowed to go online?

I already disabled the battery saving features under the battery settings menu.

Thanks!
[Moto Maxx Android Development] NepoRood:
SU49 Build prop. It's not actually "zipped", just rename and remove the zip extension.
[Moto Maxx Android Development] fgl27:
This is on the ROM kernel?

May it be the thermal-driver.

I never notice this, need to run below 30% to understand...
[Moto Maxx Android Development] pedrohxn:
I'm running your latest kernel release with Intellithermal driver.

Didn't test with Thermal Engine driver yet.

Thanks!
[Moto Maxx Android Development] jb14813:
Is it normal to have only about 1000mb RAM available now? Even with no apps open and recents clear?
[Moto Maxx Android Development] khangozzy:
[MENTION=5747496]bhb27[/MENTION] After many time dirty flash new build, today, I decided to clean install with all wiped even internal storage. I got this Privacy/Advanced Settings fc when slide to Bootup section.

One more issue is I couldn't delete content in otg sdcard, though I can copy from otg sdcard to internal.

Pls find screenshot and logs attached.

http://cloud.tapatalk.com/s/57d3c76c3aa87/logcat.txt

http://cloud.tapatalk.com/s/57d3c772b2f51/dmesg.txt
[Moto Maxx Android Development] gumbi2647:
Are you are talking about memory in settings running and it saying that 2.3gb is used of 2.7gb? If so then open and view what is using the memory. Some apps and system processes run from startup and continue to run in the background even when you think that you turned them off.
[Moto Maxx Android Development] fgl27:
Supersu was removed from the ROM because of that privacy guard problem maybe others, privacy guard controls root access, the ROM comes pre root there is no need to use Supersu or any other Su. To solve clean install or on Supersu app full unroot then dirty flash the ROM.

Your driver must have a problem or a full permission problem, or a permission problem to the file you wanna to deleted, that happens some times depend on how you add those files to the driver, try to search for permission problem and try to understand how you are adding those there. change the file browser use one with root privilege like ES file browser (root must be enable in the ES app).