Develop Bugs

[FD24] Changes made in FD24 (OTA)

It seems like there are many things changed and/or fixed in FD24 build [rom/kernel/modem]
FD24 ICS OTA is now availabe and you can download it from http://forum.xda-developers.com/showthread.php?t=1619474
Big thanks to kc_exactly for his post and ACS team for providing the download link.
Update: I just updated another phone from Stock Rooted EL29 to Stock rooted FD24.
I tried to update one of my stock rooted EL29 phone following the QBKing's guide but no success for rooted phone (downloaded OTA version). So, used sfhub's no data FD24 one-click odin method. No wipe at all and just flashed over EL29.
Before: EL29 modem/EL29 Rom/Rogue EL29 recovery Kernel/rooted.
After: FD24 modem/FD24 Rom/Stock Kernel/rooted.
There was nothing special and just used sfhub's one-click odin. Everything worked like a charm.
Please post your findings in here.
First Noticeable change made - notification bug fixed (sfhub reported).
Menu -> Settings - items rearranged. System updates separated from About phone
'Activate this device' menu added to settings (with improved options. You can update the profile and prl from here also)
For me, I'm getting one or two more voice signal bar after flashing it. I need some people confirms that - if this is true, the battery life would be great in this rom!
*3G*
So far, battery life is not bad at all. - 1 hour 50 minutes - 4% used (mine only and based on my usage)
update:
3 hours - 6% drop with 3G.
3 and half - 7%. About 1% drop in every 30 minutes so far.
9 hours - 20% with 3G. This is real big improvement and my test was focus on the battery savings during the idle time (only with my tweaks and not using any battery saving apps). Now I'm planing to test about battery consumption only using wifi.
*Wifi*
With same condition, I've tested wifi battery consumption and it was not good when it's compared with 3g battery consumption.
6 hours - 20% used with wifi turned on all the time.
*4G*
*Turn Off everything - Voice Signal Only*
Update: To extend your battery life even more, check this thread out - http://forum.xda-developers.com/showthread.php?t=1610741

Collections of changes - FD24
Reserved for collections of changes.
Some update related screenshots added.
*What's working or not *
.flac format music not supported (jerrypp)
wifi icon changed. It used to have the up and down arrows showing the traffic - moved back to previous version - weboide
Chrome is fixed? (satur9ine) - Nope. Bad scroll stutter, some locking up (kingdazy)
bluetooth devices wouldn't autoreconnect/autoconnect - fixed (Compusmurf)
bluetooth "bug" that's still there (Compusmurf, Dchibro)
JabraClip still isn't able to pair with my device (beast4romtheeast)
when screen is off bluetooth voice activation does not function at all (grncherry)
getting force closes of the email app in combined view only (Kamrondroid, sqb33, jamesey) - replace the emial app with previous version (workaround)
Battery timing is much improved then previous leaks but wifi reception has suffered ([email protected])
* still big discussion is going on in everywhere about the scrolling, camera and bluetooth devices. Many users reported that scrolling is not smooth but more people reported that it's better than previous build.
*battery life*
Battery life is really great for me. I tested the battery life during the phone is in sleep or idle mode. So far, this one is the best rom I've ever been used. Battery life could be different based on the signal strength and phone usage. So this result is only based on my usage and limited in my location. But generally speaking, this would be the same trend in your situation also.
(screenshot attached)

I can not play .flac format music

Wow..the font has changed to roboto on fd24?
Sent from my SPH-D710 using Tapatalk 2

bubur_bewok said:
Wow..the font has changed to roboto on fd24?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Nope. Screenshots were taken after my tweaks. I'm using flip font as default.

The wifi icon changed. It used to have the up and down arrows showing the traffic.
The scroll seems faster.
It also seems like the fading (when it goes to sleep or wakes up) is slower, more noticeable than FD19.
Signal seems weaker at first glance, but haven't really looked into it yet.

Can anyone check if Chrome is fixed? That is the first thing I check with every kernel update...

satur9ine said:
Can anyone check if Chrome is fixed? That is the first thing I check with every kernel update...
Click to expand...
Click to collapse
Nope. Bad scroll stutter, some locking up.
Sent from my calculator watch.

On top of other things folks mentioned, an odd bug I was having (but not now) was that bluetooth devices wouldn't autoreconnect/autoconnect.
Seems to be working in this one.
And I do NOT like that new WIFI icon. I miss the pretty little arrows. LOL

A whole lot of fugly, IMHO.. theming, we must do...

strongsteve said:
A whole lot of fugly, IMHO.. theming, we must do...
Click to expand...
Click to collapse
Do you mean after flashing or in those screenshots posted above? I think the ones in this thread are after the user's personal theming/tweaks. I can't imagine even Sprint would do that to us

neodorian said:
Do you mean after flashing or in those screenshots posted above? I think the ones in this thread are after the user's personal theming/tweaks. I can't imagine even Sprint would do that to us
Click to expand...
Click to collapse
Theme didn't changed at all. Only density is 200 from 240. And my tweaks do not change anything on appearance.

Those screen shots are Sprint specific stuff. Not ICS stuff.

Bielinsk said:
Those screen shots are Sprint specific stuff. Not ICS stuff.
Click to expand...
Click to collapse
I would consider it's a part of ICS because it's there in this build.
My interpretation of Steve's words is, there could be lots of things that we need to touch up and/or un-necessary based on FD24.

strongsteve said:
A whole lot of fugly, IMHO.. theming, we must do...
Click to expand...
Click to collapse
Very very nice to hear from you steady in here. Does this mean you are doing something, right? Was waiting for your rom long long time.

Wonder if the Wi-Fi may be related to a change in other Wi-Fi settings... I don't get my E4GT back full-time for another 12 days but I'll definitely have to test my particular issue once I can get it to the office. I'm optimistic this meant they stuck with what worked on GB and just recompiled the driver for ICS.
8 days without a fix hopefully means they squashed a lot of bugs. May also (hopefully!) mean we're getting another step closer to OTA.
If anyone has a peek at the official changelog can you please see a PM? Have a few ??s to see if maybe it will hint if the issues were addressed or not.

A bluetooth "bug" that's still there:
On headsets that had BT audio AND phone, you used to be able to unselect the BT audio profile and it would stick. This no longer works. On reconnect, the "disabled" profile will start back up each time.
Ah well, not a big issue, I can force it off in my headset. LOL

Anyone getting good battery so far?
Posted from my Epic 4G Touch on EL29

batting1000 said:
Anyone getting good battery so far?
Posted from my Epic 4G Touch on EL29
Click to expand...
Click to collapse
Not bad so far after I plugged out. 1 and half hour - 5% used (Actually measuring started from 98, was not fully charged).
Actually this is great for me based on in my reception area and my experience with other roms.
So far, there's no one else talking about the battery life yet. It's too early to say something.

Compusmurf said:
A bluetooth "bug" that's still there:
On headsets that had BT audio AND phone, you used to be able to unselect the BT audio profile and it would stick. This no longer works. On reconnect, the "disabled" profile will start back up each time.
Ah well, not a big issue, I can force it off in my headset. LOL
Click to expand...
Click to collapse
Mine was already doing this on previous builds. It's annoying because having media audio connected to my Sony car stereo causes my phone to randomly reboot. Then again, that's a symptom of bigger problems with Bluetooth ... for me anyways.

WIP - lightflow setting

hi all
im having issues with light flow as im sure some others are... i know the dev is working on it as i have been in constant contact with him regarding it
but for now i was hoping people can post their settings so others can set it up and know it works
example... do you have the root option selected? do you not? does it work without the root selection on?
etc etc
one of the main issues i am having is that my light doesnt turn off every once and a while
ex: i get a sms, it flash blue, i got read, light stays on solid blue until i go into lightflow app and it clears itself... debug is showing that the notification is cleared... odd i know...
so lets see it people... what do you have for your settings that are working
or do you have an alternate app you use? if so, what is it and how is it set up for you for it to work...
thanks all!

I have similar problems. The led won't actually work correctly unless you open the app. But I also know that poses a problem. In order for the app to work properly, it will have to constantly poll the notification pool. Which will create wakelocks. Which then turns into battery complaints. Finding a happy median will prove to be very difficult.
Sent from my SAMSUNG-SGH-I747 using xda premium

c_86 said:
hi all
im having issues with light flow as im sure some others are... i know the dev is working on it as i have been in constant contact with him regarding it
but for now i was hoping people can post their settings so others can set it up and know it works
example... do you have the root option selected? do you not? does it work without the root selection on?
etc etc
one of the main issues i am having is that my light doesnt turn off every once and a while
ex: i get a sms, it flash blue, i got read, light stays on solid blue until i go into lightflow app and it clears itself... debug is showing that the notification is cleared... odd i know...
so lets see it people... what do you have for your settings that are working
or do you have an alternate app you use? if so, what is it and how is it set up for you for it to work...
thanks all!
Click to expand...
Click to collapse
Not trying to Hijack your post but there are a few other items I think will be valuable:
Version you are using:
ROM you are using or Stock:
Kernel you are using:
Confirmation of the model (ATT/Bell etc...)
Are you having excessive battery drain by monitoring Partial WakeLocks:
LED Color Using:
LED Flash Rate:
Clear Notification Style setting:
I know you are focused on some usability issues with the LED being left on but I think these items above are related as well.
I know Andrew is hard at work on the issue work. I by no means am speaking for Lightflow I just happen to have been using his app since its inception and have seen these issues resolved many times. Each model phone I have had over the years has need tweaking for proper support.
---------- Post added at 11:16 AM ---------- Previous post was at 11:00 AM ----------
Here are my details:
Hardware:
ATT
Rooted
Version 4.0.4
Kernel Faux123 version 13
Based Band UCLI5
Version 3.2
No issues at all with the following settings
Samsung S3 root mode checked
Notifications Red Blinking, Very Slow flash rate, Blue, Very Slow flash rate
Clear Notifications on Screen On
Version 3.3
No issues at all with the following settings
Samsung S3 root mode checked
Notifications Red Blinking, Very Slow flash rate, Blue, Very Slow flash rate
Clear Notifications on Screen On
This version had excessive WakeLocks as a result battery drain was increased by 20%.
My daily volume is 100 texts and 200 emails I only monitor my emails and sms.

sgs3 (i747M)
Rooted Stock 4.0.4 Telus Sammy Rom and Kernel
V3.3
A few different LED colours all at fast flashing rate for 10 min
Direct mode, S3 root mode, and USA/Canada s3 mode all UNCHECKED
Run in Foreground CHECKED
I have 'Viewed' to clear notification (Note: LED will continue to flash even if you swipe to clear notification [not the clear button] until you actually open app and view the notification)
- NO deep sleep issues/wake locks
*Definitely had deep sleep/wakelock problems prior to v3.2

Earthdog said:
Version 3.3
No issues at all with the following settings
Samsung S3 root mode checked
Notifications Red Blinking, Very Slow flash rate, Blue, Very Slow flash rate
Clear Notifications on Screen On
This version had excessive WakeLocks as a result battery drain was increased by 20%.
My daily volume is 100 texts and 200 emails I only monitor my emails and sms.
Click to expand...
Click to collapse
these settings worked perfect for me... no lingering LED anymore, no wake locks, no battery brain. perfect! just like it was on the gnexus

Jellybean Roms and litekernel: Bug Reports

Well being I can't post on the development board I guess I will have to post my rom bugs here.
So I hope that thegreatergood will see it here.

RootBox-JB-i927-Nightly-20130212
BUGS
1) Either the new hardware keyboard lights fix by scottbot95 doesn't work or it wasn't included in this rom. I can see the hardware keyboard lights still come on while the keyboard is closed when the capacitive buttons are used. This leads me to believe that the new patch wasn't applied to rom.
2) Bluetooth still not working in regards to audio in, but audio out works and voice dialer no longer screams in your ear.
Confirmed Fixes

LiteKernel-4.2-20130212
1) Battery life... I have no app but the default battery app.
If the use by the kernel would be measured under Android System, then I think there is an issue.
Android System is at 27% after 45 minutes of use while screen is only at 23%.
This correlates unscientifically to what I witnessed in CM10.1 with LiteKernel-4.2-20130211 after 5 hours of pretty regular use playing games, backing up, downloading, and etc. Android System was almost equal with screen on battery usage.
I believe this to be a bug because before I upgraded while using LiteKernel-4.2-20130120, the screen usage was easily double the usage of Android System, under similar use patterns.
I am flashing back to CM10.1 and will test this more under daily driver.
2) The WIFI power manager, am I just missing where to turn it off? I am sorry and the work you do is amazing thegreatergood but it has to be one of the most annoying things I have ever encountered.

Neuntoter said:
LiteKernel-4.2-20130212
1) Battery life... I have no app but the default battery app.
If the use by the kernel would be measured under Android System, then I think there is an issue.
Android System is at 27% after 45 minutes of use while screen is only at 23%.
This correlates unscientifically to what I witnessed in CM10.1 with LiteKernel-4.2-20130211 after 5 hours of pretty regular use playing games, backing up, downloading, and etc. Android System was almost equal with screen on battery usage.
I believe this to be a bug because before I upgraded while using LiteKernel-4.2-20130120, the screen usage was easily double the usage of Android System, under similar use patterns.
I am flashing back to CM10.1 and will test this more under daily driver.
2) The WIFI power manager, am I just missing where to turn it off? I am sorry and the work you do is amazing thegreatergood but it has to be one of the most annoying things I have ever encountered.
Click to expand...
Click to collapse
1) I had the same issue... But i checked and some times there is a process that tries to turn on the screen, and keeps doing it forever, until you reboot the phone... I use pop up notifications from whatsapp and this happens alot... but sometimes you realize to late.. and the battery is already gone....
2) The same with you... It is really annoying... I already read in a post from dmans.. that he will put an option to disable that...

List of changes/enhancements/problems in the KitKat OTA

In the interest of making things easy for those who are holding off on the KitKat OTA, I thought it might be a good idea to consolidate all of our experiences into one thread. This is intended to cover mainly the changes specific to this OTA over Razr M-flavored Jellybean.
I'll start with my experience/thoughts and edit in additional findings. (Note: I'm bootloader locked, and now unrooted.)
The Good
The UI is definitely smoother. It doesn't jitter or stall under heavy usage anywhere near as much as it did in Jellybean.
Battery life when the phone is asleep seems to have been improved a little.
USB audio out is now supported.
The occasional "screen jitter" that plagued the Jellybean build is gone.
KitKat's Quick Settings panel is quite handy.
The native lock screen now supports adding, removing, and rearranging widgets.
Although it can't be installed from the Play Store, the Google Experience Launcher can be sideloaded and works just fine.
The Neutral / Very Subjective
The AOSP keyboard has changed; the keys are smaller and, in landscape, very squashed. You may need to adjust to it (I'm trying, but it's a struggle) or find a replacement.
Battery life when the phone is actively in use has not been noticeably improved in my experience; but it hasn't been noticeably worsened, either.
There's now a shortcut to the camera from the lock screen, which can be used even if the phone is locked by a pattern/PIN/etc. (Great if you're a shutterbug; not so great if someone else decides to troll your Dropbox/Drive account.)
The Google Camera app works - but Photosphere can't be used, as the Razr M doesn't have a gyroscope.
The Bad
No more root, for those with locked BLs (me). (Saferoot fails, and many users are reporting losing root even when they try survival methods.)
Wi-Fi tethering via most apps (e.g., FoxFi) has been blocked, so now you must pay your carrier for the feature unless a new workaround is discovered.
All notifications I've seen so far now flash the notification light white, instead of unique colors. This may be frustrating for some who used the colors to decide whether to check the phone immediately or later. (Luckily, there are ways to address this.)
The Blur launcher is same 'ol, same 'ol. It uses a solid black background for the soft keys and notifications bar (rather than taking advantage of KitKat's transparency support), and it still has that Quick Settings menu on the left (which is redundant now). In addition, Holo Launcher (which I was using) doesn't account for the space used by the softkeys at all, making it difficult to use. (I've switched to Nova Launcher, which is working fine.)
I've experienced some weirdness with the application switcher. Sometimes it drops me to the launcher right after displaying the list, and sometimes apps will overwrite another's position on the list, or be dropped from the list entirely without reason (this is always temporary, however - just bring up the switcher again).
Some apps can no longer write to the SD card - or at least not wherever they please. We still have the Files browser, mercifully (but I favor Total Commander anyway, which seems to work perfectly).
The audio quick switch on the lock screen has been removed. Also, the buttons for entering a PIN are smaller.
(Leraeniesh) Under heavy usage, the Razr M may get hotter under KitKat than it did under Jellybean, and may drain the battery more.
(GPIX) Some users have noticed decreased network performance in some apps, such as Chrome or YouTube, while on Wi-Fi and with Wi-Fi power-saving enabled.
(GPIX) Several users have reported popping noises - when a sound begins to play, or in the middle of playback. (I haven't experienced it, however.)
Swype is no longer included. If you used it in Jellybean, you will need to purchase it on the Play Store after taking the OTA.
(ls3c6) Some have encountered problems with sharing the address book to paired devices over Bluetooth.

My opinion, overall:
It's a nice upgrade, but all of little problems I've encountered (bugs, Verizon blockades, the works) make this feel like a bit of a letdown after the 6-month wait. In the end, after just three days, I find myself wishing I could take the phone back to Jellybean.
Here's hoping for either some exploitable holes or maintenance updates.

My opinion
Leraeniesh said:
So I popped my sim back into the XT907 for the weekend, and heres what I've noticed (when compared to 4.1.2).
Higher temps - previously, my XT907 hovered around 85F-100F, but with 4.4.2, I've noticed it drift toward 110F with 5+ minutes of active use.
Worse battery life - On 4.1.2 I averaged around 20% after 16 hours moderate use. With 4.4.2, I'm averaging around 5% in the same span.
Lesser LTE coverage - This may be something with my area, but I can usually get 2-3 bars of LTE in the Livingston County area on 4.1.2 (I've noticed the XT907 accel in this category). While on 4.4.2, I could not get any LTE coverage in the same area, and could only find it within more populated areas.
Slower performance - I'll always be amazed by how quick the XT907 was on 4.1.2, beating out devices with similar specs in the same price category. With 4.4.2, I've noticed frame drops, stutters, and random reboots be a common occurrence over the last few days of usage.
Overall, I'm satisfied with 4.4.2, but I still prefer the overall usability with 4.1.2.
Click to expand...
Click to collapse
Worth noting that I am using an unlocked bootloader, with CWM and SuperSU (only really did this to remove VZW bloat and install Xposed)

Leraeniesh said:
So I popped my sim back into the XT907 for the weekend, and heres what I've noticed (when compared to 4.1.2).
Higher temps - previously, my XT907 hovered around 85F-100F, but with 4.4.2, I've noticed it drift toward 110F with 5+ minutes of active use.
Worse battery life - On 4.1.2 I averaged around 20% after 16 hours moderate use. With 4.4.2, I'm averaging around 5% in the same span.
Lesser LTE coverage - This may be something with my area, but I can usually get 2-3 bars of LTE in the Livingston County area on 4.1.2 (I've noticed the XT907 accel in this category). While on 4.4.2, I could not get any LTE coverage in the same area, and could only find it within more populated areas.
Slower performance - I'll always be amazed by how quick the XT907 was on 4.1.2, beating out devices with similar specs in the same price category. With 4.4.2, I've noticed frame drops, stutters, and random reboots be a common occurrence over the last few days of usage.
Overall, I'm satisfied with 4.4.2, but I still prefer the overall usability with 4.1.2.
Click to expand...
Click to collapse
On 4.1.2 the "signal bars" were calculated by a xml in, I believe, SystemUI.apk. You could simply adjust the figures to show more or less bars, which Moto adjusted to show more. But having no LTE maybe a bad radio or a problem stemming from a bad flash. My Razr M doesn't get hot, no random reboots, and battery life seems to be the same. I haven't had any problems on KitKat.

ATTACK said:
On 4.1.2 the "signal bars" were calculated by a xml in, I believe, SystemUI.apk. You could simply adjust the figures to show more or less bars, which Moto adjusted to so more. But having no LTE maybe a bad radio or a problem stemming from a bad flash. My Razr M doesn't get hot, no random reboots, and battery life seems to be the same. I haven't had any problems on KitKat.
Click to expand...
Click to collapse
Gonna be doing some more testing in that regard. Even my M7 with its garbage radios gets LTE just about everywhere in the Metro Detroit area.

So far my experience with 4.4.2 has been positive. I agree with OP's list and would like to add these under the issue category.
ISSUE:
Decreased WiFi effectiveness/throughput - There is a noticeable decrease in performance on apps like Youtube and Chrome web browser.
Audio Popping noises - Some experience a popping noise when the sound driver starts up while others experience it during playback.

I have had the KitKat OTA now for 2 days and haven't found anything major wrong. The changes to the keyboard bugged me but I use swiftkey so that was moot. I also have an issue I haven't seen listed yet. The new sound for screen taps....it seems to give that "popping" feedback (that ive seen listed as an issue on driver start-up) ALL the time. I maybe get 1 clear sound out of every 5-6 screen taps. That is the only real "problem" I can find as of this point though. Does anyone have any insight on that?
Also activated Dev Mode and changed to ART runtime. Might be placebo but app response seems to be noticeably better! Not groundbreaking by any means but better than 4.1.2 for sure. Overall I am happy with the upgrade. Rather, will be happy once a root exploit comes up (I miss my debloating! On that note though, disabling apps never seemed to work right with 4.1.2....after hitting disable the app would show back up in active processes after a short time. Now I've gone 24 hours and 3 phone reboots and that damn NFL app is STILL disabled and NOT running as a background process. Might just have been an issue with my phone in particular before, but its fixed now!)

I am generally happy.
It fixed all the issues I had with Dhackers KitKat.
and feels about the same once you have rid of all the Bloat.
I like and I am happy that we still surprisingly got the update unlike the Galaxy S3
Happy =)

Just wanted to comment on the heat issue mentioned above:
I have only had KitKat for 2 days but I have definitely noticed a difference in heat after extended use compared to JB. One of the things I really liked about my Razr M was lack of heat so hopefully this is a fluke and I wont notice it too much in the future.
---
With that said, no big issues.
I don't like the keyboard -seems smaller, or something, The heptic feedback seems to be different too (for the worse IMO).
The lockscreen number pad seems smaller - definitely liked the number pad from JB.
I had to change the messaging app (hated the all white/lack of contrast). Using "8sms" if anyone is curious.
I also changed launchers to use the google-now launcher so the "okay google" thing would work on the homescreen and also get the transparency notification bar. But, in doing that I did lose the circle widgets which I liked. Can't win for losing sometimes...
---
On a positive note, Chrome/google searches seem to be much faster. The UI seems about the same (no complaints with JB).
If battery life can increase then I'll be satisfied with update (so far, no difference).

My experience has been very positive. My phone was bootloader locked and not rooted before (and, of course, after) the OTA. I cleared the cache partition from the recovery menu post-install but have not done a FDR. General impressions:
-- UI is overall much snappier/quicker. Extremely noticeable.
-- Love the new quick settings panel that you can get to after pulling down the notifications shade.
-- KK's changes to how the SDcard works have not been a big deal at all for me. The native "Files" app seems to have complete read/write access, as does ES File Explorer.
-- Like the new clock feature to automatically add a "home" display when traveling outside a pre-defined timezone.
-- Hate the new way you set the alarm on the clock. (Really, whoever came up with that input method should be transferred to a department where s/he can never affect design decisions again.)
-- I miss the audio silencer/mute on the lockscreen.
-- Battery life has been interesting. When I first installed the update (morning of 05/15), battery life was definitely worse, probably by about 50%. It has gradually been getting better, however, and now is probably only about 20%-25% worse than JB. Why it would change I have no idea, but it definitely is (I've been keeping notes, and am sure it is actually happening). I have noticed, using the Battery History details screen, that there are a LOT less wakelocks in KK than JB. In JB, I used to see tons of "Awake" indicators on that screen that did not pair with "Screen On" indicators. In KK, there are very few incidences of "Awake" that are not paired with "Screen On." Someone smarter than me will have to explain how that translates into worse battery life.
-- It may be my imagination, but it seems like the battery charges faster w/ KK. If it's not my imagination, I wonder if that means that the apparent decrease in battery life is really an issue of improper calibration/accuracy.
I have not experienced some of the things others have reported:
-- No random reboots.
-- No changes to WiFi or 4G signals. I don't use Bluetooth so can't comment on that.
-- No popping noise when using audio. (Note: I have seen some reports in other forums that a FDR fixes this issue for those who have it.)

I'm on locked BL, definitly non root, and I happen to installed MotoCam from a store n IT DID INSTALLED. .
Opens up, takes pictures beautifully. .
Only problems are the slide in menu is glitchy AND after taking HDR pic, cam UI is not there. Only live cam feed.
Other than these issues, it's playing nicely ESPECIALLY auto HDR does work, surprisingly!
How can I make those problems go away??
Sent from my XT907 using XDA Premium 4 mobile app

4039995825
GPlX said:
So far my experience with 4.4.2 has been positive. I agree with OP's list and would like to add these under the issue category.
ISSUE:
Decreased WiFi effectiveness/throughput - There is a noticeable decrease in performance on apps like Youtube and Chrome web browser.
Audio Popping noises - Some experience a popping noise when the sound driver starts up while others experience it during playback.
Click to expand...
Click to collapse
go into wifi settings...in the setting "uncheck" the box "wi-fi optimization" it made my WiFi significantly better..

Nidstang said:
-- No popping noise when using audio. (Note: I have seen some reports in other forums that a FDR fixes this issue for those who have it.)
Click to expand...
Click to collapse
Attempted a FDR on my phone, unfortunately it did not work for me. I will attempt to clear the cache partition to see if that may help the issue if
possible. So far i can only get the boot menu for a couple seconds and im lucky to get a selection in time.
EDIT: I cleared the cache partition, no effect. (NOTE: it seems to get into the recovery menu after selecting it at boot menu, you have to hold power & vol UP for a couple seconds)
crazy4android said:
go into wifi settings...in the setting "uncheck" the box "wi-fi optimization" it made my WiFi significantly better..
Click to expand...
Click to collapse
That is an excellent point. I'll shut off the optimization and will edit my results in after tinkering with it for a while.
EDIT2: Without doing speedtests etc. It is very noticable that the wifi has improved. Youtube & other apps load as fast as they did on 4.1.2

Haven't looked into it so this MIGHT be a feature of the Google Now Launcher I installed, but I JUST noticed if you swipe down from the clock area of the new lock screen, you can add widgets! Am I crazy or is this a new feature on our phones? If so, LOVE it! Helps mitigate the loss of the quicklinks from our old 4.1.2 lock screen.

kashif87 said:
I'm on locked BL, definitly non root, and I happen to installed MotoCam from a store n IT DID INSTALLED. .
Opens up, takes pictures beautifully. .
Only problems are the slide in menu is glitchy AND after taking HDR pic, cam UI is not there. Only live cam feed.
Other than these issues, it's playing nicely ESPECIALLY auto HDR does work, surprisingly!
How can I make those problems go away??
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
maybe you can uninstall updates to the cam in apps

bwer1233 said:
Haven't looked into it so this MIGHT be a feature of the Google Now Launcher I installed, but I JUST noticed if you swipe down from the clock area of the new lock screen, you can add widgets! Am I crazy or is this a new feature on our phones? If so, LOVE it! Helps mitigate the loss of the quicklinks from our old 4.1.2 lock screen.
Click to expand...
Click to collapse
Lockscreen widgets were introduced in Android 4.2.2.

Just want to let people know that the Google Now Launcher is working great on 4.4.2 including the "ok Google" functionality.
You can't download it from the play store. I just grabbed the apk from this thread.
http://www.xda-developers.com/andro...-and-gpe-devices-apk-mirrored-for-all-others/
Sent from my XT907 using Tapatalk

rooted + cwm
can't use "memory" feature under settings, while calculating settings app would crash

how can I go to hiddent menu? *#*#4636#*#* is failed until my M get kk updrade...

tieuvienson2005 said:
how can I go to hiddent menu? *#*#4636#*#* is failed until my M get kk updrade...
Click to expand...
Click to collapse
There are many "phone info" apps in the Market. Or create the short cut with Activity Launcher.
Also the Cam sucks on my Wife's m so get the Lenovo from my Moto x signature link.

[SUGGESTION] Update LiveDisplay

I noticed that the LiveDisplay setting is not turning on by itself if set to automatic. At first I thought it was a bug in the ROM, but after searching around a bit, I found out it requires location to work. It uses our location to determine sunset and sunrise times, and activate/deactivate LiveDisplay accordingly. Correct me if Im wrong here.
My suggestion would be to make this setting user configurable in a way that we can manually set start/stop times of night mode. First of all because we might want to turn if on/off at different times, secondly because having GPS turned on drains battery. Or give an option to use either user set hours or GPS.
Considering the magic the guys usually do, this could be implemented in a matter of hours, and would benefit the users and battery life.
Note: Before some smart ass gets to say "its open source, download and do it yourself" - I do want to do that, I am a developer, but currently I have limited hardware to build LOS and will get to it after I upgrade it.

I second this as in the UK the sun doesn't set till really late.

I found a workaround for this issue as there is still no option to set sunset and sunrise time manually. The workaround is the automation app Automagic . It supports setting of LineageOS System Settings since version v1.36. Root is requiered. In the app you have to look for Lineage OS System Setting "display_temperature_mode" (Value 4- Auto, Value 2 - day).