yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 4] daniel_m:
Strange, I flashed this nightly without problems. So far it's working as expected ...

Edit: boot time is extremely long and I got stuck in a boot loop this evening ... good that the next nightly was already available then :)
[Motorola Droid 4] joefuf:
I did a completely clean install. I flashed the 5-29 nightly, which hasn't gotten any complaints from anyone else that I've seen. Everything else on the ROM works just fine, and oddly, I can receive MMS messages, but I cannot send. I've tried Handcent and Messaging.

Here is what I see under the selected APN Setting. I noted that in this thread, the OP had a link going into the MMSC line, but my setting is blank. Simply adding that didn't work for me though. Other posts to the same effect have different numbers for the ports and stuff. See anything relevant?
[Motorola Droid 4] joefuf:
Nevermind, I figured it out. Not sure if anyone else that has flashed a recently Nightly has come across this issue, but I found a guy on a Galaxy S III running a CM 10.1 ROM that encountered the same issue.

Further down the thread, some guy suggested that anyone with this problem "toggle the cdma subscription back and forth from RUIM/SIM to NV ultimately back to RUIM/SIM."

In my case, I was already on NV, and by making it RUIM/SIM and rebooting, I am now able to send/receive MMS messages.
[Motorola Droid 4] sydfab:
Hello! I've installed this ROM but notification led doesn't work, is it normal? Tnx in advance

Inviato dal mio XT894 utilizzando Tapatalk
[Motorola Droid 4] lucize:
I don't think that in current form it will get merged, because I made a test exclusion in framework_av and I think that hdmi hal needs to be fixed to report the correct sound format.

I submitted the changes but I got no input from no one

http://review.cyanogenmod.org/#/c/64711/

http://review.cyanogenmod.org/#/c/64710/

http://review.cyanogenmod.org/#/c/64607/

Do you have LFE inverted with center ?

Regards
[Motorola Droid 4] sharptv:
Bluetooth does not work with VOIP apps such as Viber and Fring. I am using m6, is it working on the later nightlies?
[Motorola Droid 4] rblanca:
Sorry lucize...i was unable to check that ...I tested playing a movie in my girlfriend's house but they have all speakers together in the same table...next time a will check that! Thanks again for everything you do!
[Motorola Droid 4] daniel_m:
The June nightlies seem to have shortened battery life again :(

The one from the 5th ofJune crashed on me and I could only revive my phone by plugging in the charger. Apparently the battery dropped from 60% to 0% within 1 second. BetterBatteryStats didn't reveal anything. Looks like Android crashed and sucked the battery empty without the system having a chance to even log this event...

Hope the next nightly with all its omap4 changes will be better.
[Motorola Droid 4] StevePritchard:
Bluetooth Auto-play

I've gone from the 1st Jun nightly to 7th Jun, and now when bluetooth auto-connects it auto-starts Spotify and starts playing. Is there a way to stop this behaviour, as I find it really annoying.
[Motorola Droid 4] sd_shadow:
try, menu>manage apps>all>spotify>clear defaults
[Motorola Droid 4] StevePritchard:
Thanks for the suggestion, but that was the first thing I tried, but it made no difference.
[Motorola Droid 4] stargo:
Hi,

Sorry, didn't find much spare time the last weeks and if I found a bit I just tried to fix major problems (like build-failures for 4.4.3).

Shouldn't there be a check for AudioSystem::PCM_16_BIT || AudioSystem::PCM_24_BIT in there? Or is there no AudioSystem::PCM_24_BIT? (I haven't looked)

As you write, the HDMI hal should be fixed. But I'm not exactly sure what it should return...

Cyanogen pushed it :)

I also have a problem testing your changes: I have only 2 speakers connected to my receiver...

Thanks for your continuing work on HDMI :)

Hmm, this is probably fixed by the audio-wrapper: http://review.cyanogenmod.org/#/c/63328/

This isn't included in M6 but is in M7.

The wrapper should also fix the cause for the sporadic audio-loss. Did anyone experience it again since about 2014-05-10?

I can't see what could have caused this.

And BBS is useless after a reboot :(

Hmm, it's probably the media-buttons which now happen to be recieved by Spotify. Try this:

Settings -> Privacy -> Privacy Guard -> Spotify (long click) -> Media buttons: Denied

The Spotify should not get notified when you connect to BT.

Regards,

Michael
[Motorola Droid 4] StevePritchard:
Thanks, but that didn't seem to make any difference.
[Motorola Droid 4] sharptv:
Looks like m7 is coming up. Does anyone here experienced a dead gps chip in the droid 4? I think the one in my is dead, can't detect any gps at all, be in in stock or custom.
[Motorola Droid 4] bofis:
Ugh, my CallUI and Phone keep crashing whenever I get or make phone calls. This is on the latest, 6.07 nightly right now...anyone else?
[Motorola Droid 4] daniel_m:
I am pretty sure that my GPS chip is working, but I cannot get GPS to work on my system. As usual, with XPrivacy and Disable Service, it is almost impossible to say where the problem is.

Are thre others with GPS problems? I disabled the same services that are disabled on my Droid 4 on another phone and GPS is still working there. I also allowed almost everything for Android system components in XPrivacy without getting GPS to work.

Also, the 050614 nigthly didn't crash again and the battery lasted pretty long the last two days :)
[Motorola Droid 4] lucize:
had this problem, I needed to fastboot the original sbf image re-root etc. there is no other fix

regards
[Motorola Droid 4] rblanca:
Some has the download link for m7? I look on https://download.cyanogenmod.org/?device=maserati&type=snapshot but it isn't there
[Motorola Droid 4] sd_shadow:
Then it isn't available yet
[Motorola Droid 4] noleng:
yes. I have also had this issue for the last 2 or 3 builds. I think it started with the builds that had the new contact list/favorites/dialer format.

sometimes i can get out of the crash and answer the call.. other times i can not.

Since this issue occurred. a couple other issues also occur. The wallpaper seems to keep resetting to the default cm image. as well, the ringtone for all incoming calls seems to reset to default also.

I will once or twice a day go and save my preferred wallpaper and ringtone.. but usually upon the CallUI crash. this is also when the wallpaper and sounds would reset.

I have installed every nightly build since this issue has started.. and all seem to do the same thing.

I have done wiped cache etc.. (never done a full system reset as of yet) but still same thing. I wasnt going to mention anything.. but now that someone else has. i figured i would add my info as well.
[Motorola Droid 4] rblanca:
HI! Someone knows if GSM is still needed to work with GSM networks outside US?. Thanks!
[Motorola Droid 4] tbv2005:
As long as you do the build.prop changes for GSM it's working perfectly. Using latest nightly from cm site in europe right now
[Motorola Droid 4] rblanca:
It's still needed tu do it in every CM (OTA) update?. Thanks!
[Motorola Droid 4] tbv2005:
Good question. I not using the OTA update. Still manually downloading --> going to safestrap --> make backup --> install rom --> make build.prop changes - and yes with manual installation it's needed for me to get it working.

Not sure if there are differences using OTA (as I never used OTA update for CM up to now). Easiest way to find out - go into your build.prop and check the relevant entries (ro.mot.phonemode.vzwglobalphone should be 1 for example)
[Motorola Droid 4] bofis:
Well you may be in luck! Today's M7 build is running great on my phone and the CallUI and Dialer crashes seem to be gone. My wallpaper and theme has stayed solid since I updated, and I tested out some calls to make sure. I'm not sure wtf happened on 6/06 and 6/07 nightlies, but the M7 is great, so whatever changes ruined our phone will hopefully not get merged or have been corrected ;)
[Motorola Droid 4] rblanca:
I have and endless incallui crash on m7...it's a pain in the nuts

Edit: It start to crash when you sync your google contacts using google accounts
[Motorola Droid 4] rblanca:
I think I found the problem...incallui crash if screen it's in landscape mode.

Edit: Seems to fixed on tomorrow nightly.....http://review.cyanogenmod.org/#/c/65501/ Can m7 be redone with that fix?
[Motorola Droid 4] Mentor.37:
Yes, you have to edit the build.prop to use the droid 4 on gsm but if you installed my patch you do not have to reinstall it at every update, If the patch is installed and you will update the rom without formatting /system the patch will automatically edit your build.prop at every update.
[Motorola Droid 4] daniel_m:
OMG! :eek:

Can I restore my nand backup afterwards or do I have to re-install CM?
[Motorola Droid 4] sd_shadow:
Yes you can restore nandroid after flashing XML/firmware.

Will need to reroot and reinstall safestrap first of course.
[Motorola Droid 4] noleng:
awesome.. and yes.. i actuallyu downloaded the M7 build last night.

If i am correct.. i think i ead in earlier posts in this thread that i should NOT update my nightly to a M7 correct?

So i didnt boot into the M7 just yet. but i did install it into a new slot. I recall that when i updated to a M release from a nightly a few months ago, it kept forcing close, errors, etc.. andf then someone wrote that a M release should not at all be updated from a nightly andf to install it fresh.

and yes. I noticed that the errors were only happening when i had it either docked (in landscape) and/or was rotating the phone when picking it up. so for now.. i turned auto rotation off. so that it will only rotate when i slide open the keyboard. i will see if that fixes my issue before loading the slot with the M7 release.

i would like to know if these M7 fixes will be in the next nightly.

update: using M7 on slot 2 - along with the mentor gsm patch, and all works perfect.. will go back to slot 1 (nightlies on this slot) once i hear back if anything is patched for this error.
[Motorola Droid 4] daniel_m:
Which tool did you use to root your phones?

Also, does anyone here have bootloops with XPosed? I have to disable the XPosed framework to successfully boot into CM M7 :(

Edit: I narrowed it down to XPrivacy! The XPosed framework itself does not cause any problems.
[Motorola Droid 4] rblanca:
If i undertund you right... you not have inuicall crash if you install it on slot 2...that is correct?
[Motorola Droid 4] noleng:
It doesnt matter where you install the M7 update. But if i am correct. If you have a nightly installed currently (we will say this is already in slot1) than do not simply update your nightly.. install a fresh M7 in any slot. but i chose to not want to delete my nightly rom, so i also created another slot for the M7.

the slot doesnt matter. But if you update a nightly to a M release. you will get errors and boot loops and crashes (i think this is correct)

the M7 release has to be installed to a fresh slot was all I did.. i chose slot2 because i did not want to lose everything on my slot1. this way slot1 with the nightly is still there for me to boot into which still has the errors.. but the M7 on a separate slot does not have any errors.

You can also just go into your display settings and turn auto rotate off (not needed to do in the M7 but do this in the nightly) because as long as it is in the standard portrait view, this crash will not happen
[Motorola Droid 4] StevePritchard:
FWIW I installed M7 over the previous nightly, and didn't have any issues, but I think the general advice is not to do it... http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items
[Motorola Droid 4] noleng:
So for people that were having issues with the latest few nightly builds in regards to having system crash events with the dialer while in landscape mode.. as well as having the ringtone and wallpaper selections reset to default, well here is a bit more info.

It was noted that these issues were to have been resolved within the latest M release (M7)

These issues seem to have been smoothed out in the M7 release.. but not corrected 100% as of yet.

Today i just (by mistake) so happened to leave my keyboard slider out after typing a message.. the screen was off. but keyboard slid out fully.

the phone rang.. and when i attempted to answer it, i had a few issues getting to the answer to start off with. I closed and opened the keyboard.. pressed the power button once or twice to toggle the screen on screen off setting. and then i had a black screen.

nevertheless. after i answered the call and hung up. i noticed later that the ringtone as well as the background wallpaper were reset once again.. just like the issues with the nightlies.

anyhow.. just wanted to let people know..

but it seems to be less system and inuicall crash's with the M7 .. way less.. i dont have to set the auto rotate setting to off with M7.. but with the keyboard out forcing the landscape mode at all times.. it seems to have brought back the issues. only difference was there was no pop up notification stating the inuicall crash with M7 though it did the same errors.
[Motorola Droid 4] bofis:
I have not had any Dialer or CallUI crashes, but I also have not left my keyboard out or used a dock, and lock my rotation to only rotate on keyboard out. However, just to throw this into the mix, I installed the M7 over the previous, super buggy, nightly, and have not had issues since. My phone does not bootloop and the call issues seem to have subsided. Now the question is, should I stick with this, or now upgrade it to the 6/11 nightly which seems to include 234234234234 fixes and changes?
[Motorola Droid 4] daniel_m:
How can you even ask that question?! UPDATE!!!11!!!!1!

.

.

.

PS: Don't listen to the addict :cool:

I have to re-install to get GPS and XPrivacy to work again. For some reason those June nightlies completely messed up my Droid. If you are happy with M7, stay with it.
[Motorola Droid 4] bofis:
Dirty flashed today's, 6/11, nightly over the M7 and so far so good. The Dialer isn't crashing anyway ;) I think it's more an issue of going from a newer nightly back down to the Milestone releases that causes issues. I've never really had any more problems going from a nightly to a Milestone or up to a nightly from a Milestone ::knock on wood::
[Motorola Droid 4] rblanca:
for me 06/11 works perfect!...good battery life, no crash...awesome work!
[Motorola Droid 4] bofis:
On the 6/11 nightly right now...haven't encountered any major issues besides apps refusing to update and claiming "insufficient storage" as usual...ugh.

However, I am noticing that the phone does not seem to be going into Deep Sleep very often. This CPU chart is from when I unplugged my phone at the end of the work day yesterday through this morning when I woke up. In that time it was in airplane mode while I was on the subway, and also was plugged in charging overnight while I slept. I would image that it should have been in Deep Sleep for both of those times, which should show up as more than 3 hours and 27 minutes...Also shouldn't it be at 1200mHz a little more than that...I totally used my phone actively for more than 12 minutes :-\

P.S. Using Interactive governor
[Motorola Droid 4] wilkster:
Phones don't generally sleep when charging. Try using better battery stats to troubleshoot problems.
[Motorola Droid 4] sharptv:
Ok guys, I finally figured out what's causing the gps issue. It is the case! You are reading it right, the case is blocking the gps signal. It really amazed me when I figured it out, 'cause everything else worked fine, wifi, celluar and bluetooth. Apparently others have also encountered this issue. I was using a plastic case, not even a metal one. I figured that the chip should be fine, since all other radios were working fine and there are within the same chip. With the case on, I can't get ANY gps singal at all, without the case, i can get a lock in under 30 secs even in 'device only' from a cold start.

This is simply unbeliable, but it is true, for me at least. So for those who are experiencing 'dead gps' or poor gps performance, try removing your case.
[Motorola Droid 4] daniel_m:
Thanks for reporting!

My case doesn't seem to block GPS and I got mine to work again by re-installing the stock ROM and CM ... turned out that I probably deleted an important apk ... just weird that my CM installation broke gradually ... well well, life would be boring without problems :laugh:
[Motorola Droid 4] rblanca:
I believe i found a bug...when screen is locked without a patron set and you long press button of your wired headset, google now pop ups but it freeze on loading screen.... this happennd to any one else? Thanks

Enviado desde mi XT894 mediante Tapatalk
[Motorola Droid 4] joefuf:
What's the difference between a nightly and the M7 ROM? I've seen M7 mentioned a few times.

I'm running the 5-29 nightly and I have no issues whatsoever. Tonight my phone got an update notification for the cm-11-20140609-Snapshot-M7. Is that a stable update?

EDIT: I just read this article and got a good idea what the M7 is. I guess I'll wait til July like it suggests.

http://tech.firstpost.com/news-anal...d-4-4-3-based-nightlies-available-225489.html
[Motorola Droid 4] rblanca:
Tried 06/13 nightly and this bug still present...can anyone please test it and me that it's not only me...steps are:

1) Connect your wired Head Set

2) Get your screen phone locked with deafult lock type (slide/swipe i don't how is called on english :P but it's not patron)

3) Long press Headset's main button like 3 segs.

4) you will hear a voice telling you to wait the app will get freezed on loading screen (I believe that the app is Google Now).

Thanks!....besides of that 06/13 seems to work fine like 06/11
[Motorola Droid 4] rblanca:
If anyone is interested the problem was it only work with English language....It's possible to change the voice dialer default language or import motorola's one?. Thanks
[Motorola Droid 4] daniel_m:
Did I mess something up, or do the notification panel buttons (or the quick panel) in 06/11 and 06/13 not show the correct mobile data state and mobile network? I can toggle mobile data and the network mode successfully and mobile data is indicated correctly in the status bar, but the notification panel and the quick panel always (wrongly) show that I am connected to mobile data and the wrong network type is indicated (e.g. 2G instead of 2G/3G).
[Motorola Droid 4] Sensonic:
My phone doesn't find the SIM card nor mobile network at all when I boot into CM11 :( When I boot into stock ROM it'll find the network almost instantly. I'm using Elisa network operator in Finland and the frequences are 900 /2100 MHz.
[Motorola Droid 4] daniel_m:
Did you install Mentors GSM patch?
[Motorola Droid 4] Sensonic:
No I didn't. Where to find that one???
[Motorola Droid 4] sd_shadow:
[PATCH][GUIDE] Patch to fully enable GSM on Verizon CDMA Android phones
[Motorola Droid 4] daniel_m:
Stargo (or someone else?), do you know how to report a bug in CM11 nightlies? Reporting bugs is only possible for stable releases and milestones :( And the CM forums are more or less deserted ...

The bug concerns the busybox binary and might have been introduced after the release of milestone 7 (busibox has a different MD5 in my 13/06 nightly than in M7). The stat command seems to produce segmentation faults that prevent oandbackup (issue on GitHub) from restoring permissions for app data files. A simple "busybox stat SOMEDIRECTORY" shows the properties of that directory, as expected, but is followed by a segmentation fault as well.

I didn't see any changes on the busybox binary on http://www.cmxlog.com/11/maserati/. Do they not list all changes?
[Motorola Droid 4] Sensonic:
OK, got it, thank you very much!

Could someone answer to these questions regarding this ROM:

1) how to make earpiece (of the phone) louder? It's quite quiet right now and I can barely hear what the people are saying when they call me / I call them?

2) how to get rid of the Google search bar on the main screen? I'd like to fill my screen with as much icons as possible and get rid of that search bar.

Thanks a lot in advance!
[Motorola Droid 4] michelsberg:
Wow, thanks for that!

My problem was that I blocked mtalk.google.com manually by sending it to localhost via /etc/hosts :laugh:

It was probably in an attempt to reduce "unnecessary" spy traffic, assuming it was only for hangouts or the like. I wasn't aware that GCM relies on that domain. Thank you for making me aware!
[Motorola Droid 4] bofis:
If you have your phone up to 100% call volume and it's not actually loud enough, it usually helps to step it down first, and then back up, to sorta make the phone realize it's all the way up to begin with. As in, while it reports 100% volume, it's really acting like it's low, so by going down and back up, it should get louder.

As for the search bar, that's a launcher setting. I'm not sure if you can disable it under Trebuchet or the GNL, but if you're using any 3rd party launcher (like ADW EX or Nova) you can typically just remove it like any other widget by long pressing on it. Also, 3rd party launchers let you adjust your grid/icon size so you could prolly make even more room on your screen for icons (as well as in the drawer if you like).
[Motorola Droid 4] Sensonic:
Stupid question (well maybe) but is it possible to remap the physical QWERTY keyboard when using this ROM?

I'd need Ä and Ö letters mapped to my physical QWERTY keyboard since they're needed in the Finnish language. I tried to modify omap4 files, put into their original folders, booted the phone but they don't seem to work :(
[Motorola Droid 4] sharptv:
Did you set the correct permission? If you are modifying the shift/alt characters, you'll need edit the omap4-keypad.kcm file, found inside usr/keychars

Make sure you set the correct permission though, is should look like this if you are using root explorer:

tick tick "no-tick"

tick "no-tick" "no-tick"

tick "no-tick" "no-tick"
[Motorola Droid 4] Sensonic:
Yep, I edited omap4-keypad.kcm file as well omap4-keypad.kl file, put them into their folders, rebooted phone but nothing happened. I just wonder whether it'd possible to change the characters behind "SYM" button? I could place Ä and Ö letters over there.

Edit: any chance to get some screenshots of those aforementioned "tick-no tick" settings since I'm quite a newbie with the android system???
[Motorola Droid 4] sharptv:
It should look like this:
[Motorola Droid 4] rblanca:
Hi people...days back i did got a problem and it was that in some games fps was a little low compared with stock rom...the reason was in Interactive's Governor..cpu waits a big time before increase freq if it's needed on heavy load ...if someone note this behavior change:

above_hispeed_delay = 100000

to

above_hispeed_delay = 20000

You can change it with SetCPU (Go to Governor's tab) or similar...games and overall performance will be better without any huge battery usage increment.

additionaly you can change:

target_loads = 90

to

target_loads = 95

it doesn't cause lag input, games/overall performance lost or similar, cpu freq stay almost time between 300 - 600 mhz (if are not running games or heavy apps) and that should save some battery but i'm still testing if the battery save it's noticiable.
[Motorola Droid 4] Sensonic:
I dunno whether I should write this here but I've tried to remap the physical keyboard and all I've done is to screw up the whole thing.

It seems that whenever I try to modify omap4 files I cannot revert them anymore and then all will get screwed up.

Any hints to get the job done? It seems that it's almost impossible to modify the physical keyboard in KitKat :(
[Motorola Droid 4] rblanca:
Hi stargos, it's possible to add smartassV2's governor support to kernel...or it's difficulty