Database Users

Mediaserver battery drain help

Been having horrible battery life lately and have been led to believe that the media server process is to blame. 8-12% battery usage on average and have searched and searched for a fix to no avail. Formatted SD twice, factory reset twice, and flashed back to Google's stock image to no avail. No idea what's causing it and it appears to randomly wake the device up from deep sleep every once in a while overnight. Any help would be appreciated thanks.
Sent from my Nexus 7 using xda app-developers app

Worst. Question. Ever.
Sent From My N7 via White Tapatalk

zZDave_Stud said:
Been having horrible battery life lately and have tried both paranoid and AOKP with the same results, 45 minutes of screen time on at 77 percent battery currently... I used to get 6+hours of screen time and now get about 3.5-4. This could be accountable to 'mediaserver'. No idea what it is or how to get rid of it but usually takes up 8-12% of battery. So far stock still produces the best battery life but it's still pretty bad. Any tablet ROMs that produce good battery life? Thanks for anyone's input!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Dude, it's pretty obvious that the problem lies not with your ROM, but with your 'media server' or any other processes that suck battery life. There are threads on the 'media server' battery issue that you might want to search for.
Sent from my Paranoid Nexus 7 with excellent battery life

ÜBER™ said:
Worst. Question. Ever.
Sent From My N7 via White Tapatalk
Click to expand...
Click to collapse
There, I re-phrased the question. No need to be a jackass on here.. If you don't have anything helpful to say, then don't say it. It's just a waste of space :laugh:

zZDave_Stud said:
There, I re-phrased the question. No need to be a jackass on here.. If you don't have anything helpful to say, then don't say it. It's just a waste of space :laugh:
Click to expand...
Click to collapse
I did help you. Helped you realize what your real question should have been
Sent From My N7 via White Tapatalk

ÜBER™ said:
I did help you. Helped you realize what your real question should have been
Sent From My N7 via White Tapatalk
Click to expand...
Click to collapse
Well thanks. I just wish I could fix my N7...:crying:

zZDave_Stud said:
There, I re-phrased the question. No need to be a jackass on here.. If you don't have anything helpful to say, then don't say it. It's just a waste of space :laugh:
Click to expand...
Click to collapse
I give you credit, sir. I expected an angry, hostile post from you after ÜBER was so blunt. That was not what you ended up posting.
Sent from my Paranoid Nexus 7

RockNrolling said:
I give you credit, sir. I expected an angry, hostile post from you after ÜBER was so blunt. That was not what you ended up posting.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
Well I don't really like flaming/raging at people because then this thread would just be pointless after that; ÜBER and I going at eachother aimlessly. I'm hoping someone more knowledgeable on the mediaserver issue can fix this problem because I'm quite certain that I'm not the only one with this problem.

It was recently introduced. I remember not too long ago this wasn't an issue. Then out ta nowhere flashing a nightly it appeared. However I'm told it is things polling the sdcard for images or as the title suggests media. There really isn't a fix, that I new of or come across.
Sent From My N7 via White Tapatalk

ÜBER™ said:
Worst. Question. Ever.
Sent From My N7 via White Tapatalk
Click to expand...
Click to collapse
Btw these kinds of posts do NOT HELP anything at all in anyway... If you feel the question is silly or even dumb....refrain from posts like this as they don't help and do nothing but lead to flamming typically. See if you posted ur last post first instead of this then the result might of been much better...
And OP no need for the name calling btw. We can all be civil here guys.

sgt. slaughter said:
Btw these kinds of posts do NOT HELP anything at all in anyway... If you feel the question is silly or even dumb....refrain from posts like this as they don't help and do nothing but lead to flamming typically. See if you posted ur last post first instead of this then the result might of been much better...
And OP no need for the name calling btw. We can all be civil here guys.
Click to expand...
Click to collapse
It wasn't serious... at least completely it was a Simpson reference if you didn't catch that. And also it turned out just fine... he reworded the question and we didn't get in an argument. :thumbup:
Sent From My N7 via White Tapatalk

ÜBER™ said:
It wasn't serious... at least completely it was a Simpson reference if you didn't catch that. And also it turned out just fine... he reworded the question and we didn't get in an argument. :thumbup:
Sent From My N7 via White Tapatalk
Click to expand...
Click to collapse
I hear ya but what things look like over text are not always taken the way the poster intended for it to mean...
Sent from my EVO using Tapatalk 2

zZDave_Stud said:
Well I don't really like flaming/raging at people because then this thread would just be pointless after that; ÜBER and I going at eachother aimlessly. I'm hoping someone more knowledgeable on the mediaserver issue can fix this problem because I'm quite certain that I'm not the only one with this problem.
Click to expand...
Click to collapse
I found this thread you might want to look through. It seems to be similar to the issue you're having.
http://forum.xda-developers.com/showthread.php?t=1801378
Sent from my Paranoid Nexus 7

RockNrolling said:
I found this thread you might want to look through. It seems to be similar to the issue you're having.
http://forum.xda-developers.com/showthread.php?t=1801378
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
Already saw that one and that guy's problem had to do with a navigation app issue where mediaserver was constantly scanning the map files, which isn't my case. Thanks though man I appreciate your help.

zZDave_Stud said:
Already saw that one and that guy's problem had to do with a navigation app issue where mediaserver was constantly scanning the map files, which isn't my case. Thanks though man I appreciate your help.
Click to expand...
Click to collapse
His bad is it? Is it the top thing eating battery or just under display?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent From My Toro+ via White Tapatalk

My Solution
I have the Galaxy Note 2. My battery used to be at 40% after 15 hours of continuous use because the battery is 3,100mAh. One day I started noticing "Media" consuming 30-50% of my battery drain and the phone was always getting hot. I thought I solved the problem a couple days ago, but it came back and I couldn't figure out how to delete this post, so here's an update lol.
Things I've tried
I tried using Titanium Backup and Freezing "Media," "Downloads," and a couple of other apps/services/processes, but that usually had no effect, or just crashed other apps.
I tried downloading F5 Media Scanner and freezing my media scanner, but I got impatient and just uninstalled it. My media never showed up, and I didn't know what I was doing.
Some people said Google Play Music was causing it, but that only seemed to run "Media Service," not "Media." I disabled "Automatically cache" just to be sure. I guess I can re-enable it and monitor now.
I found a couple corrupted video and image files on my SD card. They might have been the cause? I used ES Explorer and noticed some pics and videos didn't have thumbnails generated... that's how I spotted them.
I also deleted a couple of "temp.43223523" files. They were some things I was downloading from the Internet browser, but I must have lost connection or something... and the files were left behind.
I tried renaming some of my pics that had ridiculously long names like "e62352_3423525.23542.jpg" to "pic34.jpg."
I moved all my Titanium backup files (1,300) and ROM backups to my computer and deleted them off my phone.
My Solution?
I placed an empty ".nomedia" file in every folder on my SDcard and ExtSD (and reboot phone). That seemed to actually solve the problem. I've been gradually deleting the .nomedia files with ES File Explorer (and rebooting). You have to enable "Show Hidden Files." Any file starting with a period is hidden.
When you reboot your phone, I think "Media" scans your SD card automatically. So this is how I investigated: 1. Reboot, 2. Charge the phone to 100%, 3. Unplug charger and periodically check my battery status.
Conclusion
The .nomedia solution seems to work when you reboot your phone and maybe clear your "Media Storage 4.1.1..PALJ1 (PLAYLISTS)" with Titanium Backup by hitting "Wipe Data." I enjoy the piece of mind knowing I don't have all these random pics and **** from various apps being scanned continuously at all hours of the day or on each reboot, cluttering up my gallery/playlists. If you're not going to use this solution, I might suggest limiting the number of files on your phone. Making several Titanium Backups resulted in 1,300 files probably being scanned a few times a day. I have 900+ pics and videos I've taken and 10gigs of videos downloaded on my phone and I think I solved my problem. Now my phone is cool to the touch and after 4 hours of use has only dropped 20%.
Create the file with notepad -> save as ".nomedia" or find it somewhere else on your memory card and copy/paste it.

[Q] How's the Butter?—Android 4.3 vs 4.2.2

Hey all; I, along with many others, am still waiting on the Android 4.3 OTA update for the Nexus 10. For those that have it, or who have flashed it, I have a few questions that I'm sure we're all curious about.
First off, the butter. Of course, I'm talking smoothness. The Nexus 10 is obviously a powerful device, and it can power this display for sure. However, it does stutter and lag from time to time. The Google+ timeline stutters, scrolling through the comments stutters (only sometimes, strangely), and I see some general scrolling lag at times. The home screen does this too, but rarely. The gesture typing on the keyboard also drops frames at times, especially in some apps (Google Maps is the chief offender). It lags, drops behind, etc. Generally it works well, but as mentioned especially in Google Maps it drops frames and acts slowly. Are scrolling and similar tasks improved with 4.3?
Second, RAM usage. Currently, I'm sitting around ~560MB free After a couple hours of varied usage, as you can see in the screenshot attached. On average, the most I see is 600MB unless it's after a fresh reboot. I am one of the users who experiences the random reboots, also, so this drops eventually until the tablet crashes on me. Has average free RAM increased with the addition of the Surfaceflinger leak fix in the latest update?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thirdly, and finally: homescreen redraws. Whenever I press the home button after being in an app for a few minutes, the entire homescreen has to redraw. On a device like this, I expect that this shouldn't happen. It interrupts the experience. I love the Nexus 10, I just want it to be more perfect for me than it currently is!
Thanks for those who read, thanks! I look forward to the conversation.
~Walkop
Sent from my Nexus 10 using Tapatalk 4 Beta

I feel like this needs a bump. I'm still quite curious, and this page has a lot of views since I posted it.
Therefore: BUMP!
Sent from my Galaxy Nexus using Tapatalk 4 Beta

CWalkop said:
I feel like this needs a bump. I'm still quite curious, and this page has a lot of views since I posted it.
Therefore: BUMP!
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well the home screen redraws can easily be fixed by using apex or nova and choosing keep in memory. Also I'm quite happy with 4.3. It was more of a behind the scenes fix up stuff update which is a good thing. It's a lot smoother and the tablet just runs better overall. No major changes besides some small things like camera redesigned and miracast support added, etc.
Sent from my Xperia Play (r800x)

To answer your first question, the 4.3 rom is undoubtedly smoother than 4.2.2 was. In fact, 4.3 stock is smoother than 4.2.2 was with the tablet overclocked to 2.1ghz/720Mhz. Chrome is much more usable, and animations almost never stutter. I don't recall ever seeing the Maps app slow down either. I haven't really tried the play store or G+ apps too much, I'll give them a go tonight and let you know.
The homescreen redraws are still there. I haven't tried the fix suggested by abdel12345 as it doesn't really bother me much.
Free ram usually hovers somewhere between 200 and 400MB, but this is fine. It amazes me that despite so many explanations, people still don't understand how caching works in Linux!

stiggy2012 said:
To answer your first question, the 4.3 rom is undoubtedly smoother than 4.2.2 was. In fact, 4.3 stock is smoother than 4.2.2 was with the tablet overclocked to 2.1ghz/720Mhz. Chrome is much more usable, and animations almost never stutter. I don't recall ever seeing the Maps app slow down either. I haven't really tried the play store or G+ apps too much, I'll give them a go tonight and let you know.
The homescreen redraws are still there. I haven't tried the fix suggested by abdel12345 as it doesn't really bother me much.
Free ram usually hovers somewhere between 200 and 400MB, but this is fine. It amazes me that despite so many explanations, people still don't understand how caching works in Linux!
Click to expand...
Click to collapse
In fairness, although most modern operating systems now have this behavior (with regards to memory usage), none of them are designed to have a built-in process fail to free it until the system keels over. Personally though, I haven't had any SurfaceFlinger-related issues, so I can't say too much about it.

Rirere said:
In fairness, although most modern operating systems now have this behavior (with regards to memory usage), none of them are designed to have a built-in process fail to free it until the system keels over. Personally though, I haven't had any SurfaceFlinger-related issues, so I can't say too much about it.
Click to expand...
Click to collapse
Very true, though older versions of Windows do make me wonder! :laugh:
Point I'm making is that whether there is a memory leak in a process or not you, should not be seeing more than a few hundred MB of "free" ram, unless by free ram you mean free+cached.

stiggy2012 said:
Very true, though older versions of Windows do make me wonder! :laugh:
Point I'm making is that whether there is a memory leak in a process or not you, should not be seeing more than a few hundred MB of "free" ram, unless by free ram you mean free+cached.
Click to expand...
Click to collapse
Granted. But considering how much effort people pushed in peddling RAM-freeing solutions, it's not surprising that many people still want "free" RAM (which is ironic, because you're not getting any use out of that RAM you bought by keeping it free...).
Memory management took a huge leap with Windows 7, but much of the underlying improvements actually came from Windows Vista. That operating system is actually a lot better than people give it credit for. More than anything else though, Vista was shot in the foot by OEMs who needed to sell out their inventories of the "budget PCs" that were really in at the time-- machines with yesteryear's specs that could just about run Windows XP nicely, but that were forced to run Vista so as not to appear "dated." You know the end result of that.

Touch responsiveness is better.
Enviado desde mi Nexus 10 usando Tapatalk 2

stiggy2012 said:
To answer your first question, the 4.3 rom is undoubtedly smoother than 4.2.2 was. In fact, 4.3 stock is smoother than 4.2.2 was with the tablet overclocked to 2.1ghz/720Mhz. Chrome is much more usable, and animations almost never stutter. I don't recall ever seeing the Maps app slow down either. I haven't really tried the play store or G+ apps too much, I'll give them a go tonight and let you know.
The homescreen redraws are still there. I haven't tried the fix suggested by abdel12345 as it doesn't really bother me much.
Free ram usually hovers somewhere between 200 and 400MB, but this is fine. It amazes me that despite so many explanations, people still don't understand how caching works in Linux!
Click to expand...
Click to collapse
Thanks for the reply!
Glad to hear browsing and animations are much better. It sounds like a fantastic improvement (being relative, of course- the Nexus 10 is already the smoothest Android 10" tablet experience around). As for redraws - oh well. I may swap to Nova or Apex (I have full editions for both, IIRC). As for RAM, I actually agree with you there. I just didn't expect that they improved caching performance - on 4.2.2, I sometimes end up with 400MB for no reason whatsoever after clearing all recent apps, instead of 600MB-750MB that I get on a fresh boot with a couple recent apps. More used RAM, if there isn't a leak, is a GOOD thing!
Anyway, I'm still waiting on the OTA. A family member's Nexus 10 got it today, so I'm hopeful!
Sensamic said:
Touch responsiveness is better.
Click to expand...
Click to collapse
Interesting. Hopefully it will pick up those quick bezel-swipes more accurately from now on! Sometimes they don't register for me.
Rirere said:
Memory management took a huge leap with Windows 7, but much of the underlying improvements actually came from Windows Vista. That operating system is actually a lot better than people give it credit for. More than anything else though, Vista was shot in the foot by OEMs who needed to sell out their inventories of the "budget PCs" that were really in at the time-- machines with yesteryear's specs that could just about run Windows XP nicely, but that were forced to run Vista so as not to appear "dated." You know the end result of that.
Click to expand...
Click to collapse
Totally agreed. I had an old pre-fab Compaq with Vista before I got the custom build up and running that I use today (SSD+Windows 8 = WIN). It ran Vista - and it worked great for me! UAC was a pain, at times, but I never really noticed it until I saw complaints on forums. Either way, Vista was a relatively solid OS. I never ran into any bugs or issues, and it performed well.
8 is definitely a massive improvement over 7, though. Boot-up times are much faster, interacting with the entire OS is just a much more fluid experience. 8 isn't just about Metro (or whatever they call it now) - it brings a lot of behind-the-scenes improvements.

Not happy
Serious noob here, so, my thoughts:
Was trying to stay stock on the N10, so I upgraded to 4.3 OTA today. The screen times out in ~ 5 seconds now, and the only fix I've found is to factory reset. I called support, and the rep said I need to factory reset (surprise). I've done this twice now, and nothing's changed.
And I can't find a video player that doesn't crash. I used to use Dice, and it won't work. I made the mistake of uninstalling to see if a reinstall would fix, and now Play says it's incompatible and won't install. I tried a couple others, and they crash too.
I wished I didn't upgrade. It's not bricked, but it's not really usable either. I generally used it to take notes at work and play videos at home. I can't really do either at this point.
Any suggestions would be appreciated.

thehobster said:
...And I can't find a video player that doesn't crash. I used to use Dice, and it won't work. I made the mistake of uninstalling to see if a reinstall would fix, and now Play says it's incompatible and won't install. I tried a couple others, and they crash too...
Click to expand...
Click to collapse
Right now (Jul 30th) we are all in a hold pattern waiting for our favorite HW accelerated player to be updated. You are not alone.

thehobster said:
Serious noob here, so, my thoughts:
Was trying to stay stock on the N10, so I upgraded to 4.3 OTA today. The screen times out in ~ 5 seconds now, and the only fix I've found is to factory reset. I called support, and the rep said I need to factory reset (surprise). I've done this twice now, and nothing's changed.
Click to expand...
Click to collapse
I did say I was a N00b, right? I discovered the sleep setting which I thought I'd set had no value at all following the factory reset. So maybe the upgrade to 4.3 unset the value or there was really a screen timeout problem. But now that it's set to something the problem is gone. Sheesh I'm an idiot.

thehobster said:
Serious noob here, so, my thoughts:
Was trying to stay stock on the N10, so I upgraded to 4.3 OTA today. The screen times out in ~ 5 seconds now, and the only fix I've found is to factory reset. I called support, and the rep said I need to factory reset (surprise). I've done this twice now, and nothing's changed.
And I can't find a video player that doesn't crash. I used to use Dice, and it won't work. I made the mistake of uninstalling to see if a reinstall would fix, and now Play says it's incompatible and won't install. I tried a couple others, and they crash too.
I wished I didn't upgrade. It's not bricked, but it's not really usable either. I generally used it to take notes at work and play videos at home. I can't really do either at this point.
Any suggestions would be appreciated.
Click to expand...
Click to collapse
For video, try the VLC beta. MX Player doesn't work for me either, after the 4.3 update, but I watched a movie on VLC just fine last night. It will even play codecs that other players like MX Player won't play, like the dts audio codec.

DicePlayer has received two updates yesterday. Now its back in playstore for our n10. So far works fine for me.

nvertigo67 said:
DicePlayer has received two updates yesterday. Now its back in playstore for our n10. So far works fine for me.
Click to expand...
Click to collapse
Yep - installed and working fine. Whew.

DicePlayer working excellent!!

Amiga4ever123 said:
DicePlayer working excellent!!
Click to expand...
Click to collapse
Mx player updated and seems to be working on 4.3. Someone to confirm this?

Should work fine. It's official info about support android 4.3

c1oud said:
Mx player updated and seems to be working on 4.3. Someone to confirm this?
Click to expand...
Click to collapse
Yep. Just watched an video with hw+ decoder for half an hour after receiving the 1.7.16 ARMv7-neon update.

I always used Mxplayer, but I I noticed that diceplayer hiding status bar and bottom navbar. Display is on fullscreen Mxplayer has both black bar Diceplayer win in my eyes

[Official] Google Play Edition General Discussion

This thread is for any talk related to the Google Play Edition HTC One. If you have any questions on how to convert use the forum linked below.
How to convert: http://forum.xda-developers.com/showthread.php?t=2358781
The Google Play edition phones automatically receive updates of the latest Android software. Optimized for the latest apps, more storage for your content and a fast, clean user experience all come standard.
Click to expand...
Click to collapse
Related:
Android 4.4 update delivered to Google: http://gigaom.com/2013/11/18/htc-one-kitkat-update-ready-delivered-to-google/

Mines fine

What app could we download to see if the readings are correct? Mine is fine.
Sent from my HTC One using xda app-developers app

define "mine is fine"
because is common that the thing that uses more battery is the screen, but in android 4.3 is android system, but I think the battery is not bad at all...
In the other hand:
- super smoth
- ir enable
- better bluetooth
- sixasis support
the only fault that I see in 4.3 GPE (beside the battery report) is the camera app, it is just not good =/

SLver said:
define "mine is fine"
because is common that the thing that uses more battery is the screen, but in android 4.3 is android system, but I think the battery is not bad at all...
In the other hand:
- super smoth
- ir enable
- better bluetooth
- sixasis support
the only fault that I see in 4.3 GPE (beside the battery report) is the camera app, it is just not good =/
Click to expand...
Click to collapse
My definition just means i can use it all day without the bigbdrain sense 5 was giving me. (4.1.2). I guess I'll look more into it since I just flashed yesterday. Also for camera, at least for me, it works fine. Of all the phones I've owned I've never messed with the settings (filters, iso, etc) just because I've never needed to. Plus I have a DSLR camera to do that . but that's me.
Sent from my HTC One using xda app-developers app

I am thrilled with the 4.3 update. I have had zero issues and battery life is very solid. My wife finally took the plunge from her iPhone 4 and I picked her up a ONE yesterday. While settings hers up, I realized how much better Stock Android is just due to the smoothness and simplicity of it. In my opinion, Sense 5 is still the best manufacturer experience to date but it's still too cumbersome compared to plain ole Stock Android

My battery life seems to be decent. I don't notice much difference than when I was on sense. I do notice the high android usage but as gunny said, I think it's being misread as it doesn't seem to be having a negative impact.
Also I know some have mentioned low signal. Again its just the way its reported because last night I had two bars and I was pulling speeds in the 20,30,40mbps range. Which I think they must have upgraded some towers because here in NYC with all the network congestion I usually pull 9-15mbps on average(depending on location)
Sent from my HTC One using Tapatalk 4

My only issue on 4.3 is a lower LTE signal. I am only getting 1 bar now, and I used to get 3-4. The battery is good, even with that weird bug.

Does GPE 4.3 still has the 3 dot menu button?

proximity sensor bug is back,
pulling phone away from my face doesn't turn the screen back on.

gunnyman said:
proximity sensor bug is back,
pulling phone away from my face doesn't turn the screen back on.
Click to expand...
Click to collapse
How often does this happen? I was on a call yesterday and I was testing the sensor and it was super sensitive I thought. I barely put my hand over it about 2 inches and it shut off the screen .
Sent from my HTC One using xda app-developers app

GrimStranger said:
Does GPE 4.3 still has the 3 dot menu button?
Click to expand...
Click to collapse
with stock kernal yes

How do you receive the new 4.3 update.
I have been trying "System Update" under "About" for days now, and there are no update from Google.

gunnyman said:
proximity sensor bug is back,
pulling phone away from my face doesn't turn the screen back on.
Click to expand...
Click to collapse
True, I still have this bug.
Sent from my HTC One using xda premium

monkeypaws said:
How often does this happen? I was on a call yesterday and I was testing the sensor and it was super sensitive I thought. I barely put my hand over it about 2 inches and it shut off the screen .
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It seems random

Yeah, 4.3 is all sacked. LTE ping is slow as a turtle. 4.2.2 everything was snappy. ADB doesn't work, screen off proximity sensor, when phone is off the charge animation doesn't work when rooted. Its not the root process. My nexus 4 & 7 have stock ROM and supersu installed.. No problems. What has HTC done!? Back to 4.2.2 I go. This 4.3 blows.
Look at this junk! Wow.. Horrible Horrible update. 4.2.2 was at 20-30% system this is at 80%+!?!? Horrific.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One using Tapatalk 4

Don't hold back tell us how you really feel

gunnyman said:
It seems random
Click to expand...
Click to collapse
Regarding the proximity sensor bug, I briefly flirted with the complete Google Play edition conversion then decided to return to completely stock sense. I started blindly messing about with mids, cids , firmwares etc. I eventually managed to run RUU 1.28.401.7 successfully. :laugh:
I factory reset my device for good measure then proceeded to install every subsequent update and I am now on 2.24.401.1 and I factory reset my device after every update. Everything appeared good and I have set my device up again with what I would consider to be a very clean install of the stock sense rom.
......Then ring ring and there it is...the dreaded proximity sensor bug
How can this be??

bobsie41 said:
Regarding the proximity sensor bug, I briefly flirted with the complete Google Play edition conversion then decided to return to completely stock sense. I started blindly messing about with mids, cids , firmwares etc. I eventually managed to run RUU 1.28.401.7 successfully. :laugh:
I factory reset my device for good measure then proceeded to install every subsequent update and I am now on 2.24.401.1 and I factory reset my device after every update. Everything appeared good and I have set my device up again with what I would consider to be a very clean install of the stock sense rom.
......Then ring ring and there it is...the dreaded proximity sensor bug
How can this be??
Click to expand...
Click to collapse
My good buddy has the HTC One for AT&T. I rooted it for her and all was well. Next thing she finds out her proximity sensor borked. She called att and they went thru a process to see what the sensor was on.. The sensor should be at 50 and the reports came back that her sensor was at 0. Hearing more and more of this sensor bug, makes me think its more of a hardware fault. Its only a matter of time till the sensor completely flakes out and dies.
Sent from my HTC One using Tapatalk 2

luckylui said:
My good buddy has the HTC One for AT&T. I rooted it for her and all was well. Next thing she finds out her proximity sensor borked. She called att and they went thru a process to see what the sensor was on.. The sensor should be at 50 and the reports came back that her sensor was at 0. Hearing more and more of this sensor bug, makes me think its more of a hardware fault. Its only a matter of time till the sensor completely flakes out and dies.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Any idea how they found out what the sensor was at?

Official 4.3 Update - Report the Bugs which your Facing here

As of the Official Update of Jelly Bean 4.3 has been started to Rolling out, the users who have installed started using it. So if you find any bug pls report here so Others can be saved.
As far am using it more than 24 hrs,
- Touchwiz is still bit laggy
- Few app including XDA app is getting FC
- Ram usage is high
- Battery is same
- Opening and closing of app is taking bit more time
- Still Finding

Is it worth the update or should I wait?

Stock browser with quick controls and full screen enabled doesn't hide the nav bar properly... A bug since first leak.

4.3 Consumes 1.3gb to 1.7gb ram never lower than 1gb. Same in s4. I prefer 4.1.2 its faster
Sent from my GT-N7100 using xda app-developers app

torbjorne said:
Is it worth the update or should I wait?
Click to expand...
Click to collapse
Its better u can wait or Flash DN3 Rom.. but i can say this update is stable than S3 update.. less bugs..

The autobrightness is really bad
Even if I am setting it at +5 its really dim indoors as compared to 4.1.2
Really any idea how to fix it
Am I alone facing this issue

The "HealthService" starts, but I dont have the S Health app, and dont know why this service starts after reboot of the phone.
any one else with this?

akashsgpgi said:
The autobrightness is really bad
Even if I am setting it at +5 its really dim indoors as compared to 4.1.2
Really any idea how to fix it
Am I alone facing this issue
Click to expand...
Click to collapse
Am using in -2 , for me its gud in indoor and in sunlight also..

With about 90 apps installed, of which BBM, WhatsApp, Vonage, LBE Security Master, Greenify, CSipSimple, Google+ and KeepScreenOn run all the time in addition to the usual stuff like TW, Messaging, GMS that runs with Android, My RAM usage with MK4 is 784MB. I don't find any lag in TW or in any of the games I play (except Ingress, of course - but that is an app issue).
I of course have rooted, disabled a bunch of stuff from loading automatically at boot, and frozen Sammy crap that I don't want or use. And no Knox.
XDA App is working perfectly fine, deep sleep seems to pretty good - lost 1% overnight after 2 recharge cycles. Auto Brightness is cranky at times - sometime stuck at lowest or brightest - but returns back to sanity after a display off-on.
Overall there is nothing new or extraordinary in the MK4 version from what we have seen in the leaks - except of course the knox status in the bootloader (I didnt care about it as am out of warranty anyways).
Haven't tried the stock browser with quick controls+full screen though, I rely on Chrome...
Xposed Framework with Wanam's module, per app dpi setting, message notification to toast, and then some more - all works great.

ph03n!x said:
My RAM usage with MK4 is 784MB.... [and then some more] - all works great.
Click to expand...
Click to collapse
Can I ask, I just need some clarification: are you running a stock version or a custom ROM?
If it is the stock, which Open version are you using?

Static-Noise said:
Can I ask, I just need some clarification: are you running a stock version or a custom ROM?
If it is the stock, which Open version are you using?
Click to expand...
Click to collapse
This is a stock ROM, the only changes being removing the Knox related apk and rooting. I'm not sure what you mean by open, can you explain on it?

Any of you having issues with official rom should join me in using DN3 custom rom for note 2 with a bunch of note 3 features and very few bugs.
Sent from my Note 2 using DN3 V2.

grk007 said:
As far am using it more than 24 hrs,
- Touchwiz is still bit laggy
- Few app including XDA app is getting FC
- Ram usage is high
- Battery is same
- Opening and closing of app is taking bit more time
- Still Finding
Click to expand...
Click to collapse
- for me its a bit smoother than 4.1
- i haven't got any FC even on the leaked MI6
-not really
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
with many apps running
-yeah battery about the same as 4.1
-i think its about the same as 4.1

Many sincere thanks for taking the time to reply.
ph03n!x said:
This is a stock ROM, the only changes being removing the Knox related apk and rooting.
Click to expand...
Click to collapse
And, as much as this may seem like a stupid question, could you please show me which one you were using? I assume that you have upgraded and forfeited the "warranty void" issue for the new ROM?
ph03n!x said:
I'm not sure what you mean by open, can you explain on it?
Click to expand...
Click to collapse
I meant, for example, 'Open Asia', 'Open India', 'Open Europe', etc.
Henchman007 said:
...[You]... should join me in using [DN3 custom rom]... [with] very few bugs.
Click to expand...
Click to collapse
I am running that ROM at the moment, and to be honest, as much as I love it, there is still the issue with the screen off when the phone is in use, And the leg you get upon finishing the call itself.
Apart from that, is a fantastic update.

Major update but with few bugs.
When installing an app from play store, the downloading process is smooth but just when the installation is about to complete there are frame drops for a second or two and it really annoys me as a heavy play store user.
Frame drops and touchwiz!!! Brother's for life!!!
Sent from my GT-N7100 using xda app-developers app

I'm getting the odd FC, but it's very rare. I had to force a reboot twice since upgrading, but I've also been using my device like crazy and installing a lot of apps as i test this new firmware.
My only real gripe is that bringing up the multitasking list (long press home key)takes longer than before.
Sent from my GT-N7100 using Tapatalk

Static-Noise said:
Many sincere thanks for taking the time to reply.
And, as much as this may seem like a stupid question, could you please show me which one you were using? I assume that you have upgraded and forfeited the "warranty void" issue for the new ROM?
I meant, for example, 'Open Asia', 'Open India', 'Open Europe', etc.
Click to expand...
Click to collapse
I upgraded to the INU ROM that got released - http://www.sammobile.com/firmwares/3/?download=21880 - that is open India I guess (and there is no other 4.3 official ROM released yet? At least that's what Sammobile says...)
Code:
Model: GT-N7100
Country: India
Version: Android 4.3
Changelist: 2099172
Build date: Sun, 10 Nov 2013 06:00:26 +0000
Product Code: INU
PDA: N7100XXUEMK4
CSC: N7100ODDEMK1
MODEM: N7100DDEMJ9
And yes, I voided my Knox bootloader warranty - because I bought the phone from Singapore and didnt have India warranty anyway. And the phone is more than a year old too...
I see a delay in the caller number or name getting displayed when someone calls me (ringtone sounds, but screen is blank), but then that's nothing that can't be fixed with a build.prop edit.
I dont have a lag anywhere, at least nothing I can find - I have made a few tweaks to the PegasusQ parameters though (reduced freq_step from the default 37% to 5% so that all the frequencies of the CPU are used, Set the cpu_up_rate to 12 and cpu_down_rate to 16, set the hot plug frequencies to 600-400, 800-600, 1000-800 and hot plug run queues to 175-175, 275-275 and 375-375, down_differential to 10, sampling_down_factor to 1 nd sampling_rate to 30000) based on my experience with earlier stock and non-stock kernel performance.
I'm overall happy about the update, though we could have been shown some more love from the S4 / Note3 devices

Clipboard options have been removed and multiwindow isn't working.
Sent from my GT-N7100

are you refering to the n7105 Nordic 4.3 that release 2 days ago? can u put that in title or OP. n7100 users might get confused. (crazy cousins) think its about them......
finally LTE gets its rom date.

I had at beginning multi window issue where it was inactive but after full wipe it was fixes. Today I have an issue with keyboard as I can't switch to other languages rather than English anybody has this problem?
Sent from my GT-N7100 using xda app-developers app

Nexus 6P Gyro/Accelerometer issue?

Anyone have an issue with their accelerometer/gyro on their 6P? I'm thinking mines faulty, the first sign was Google Fit, telling me I've done 45,000 steps in a day (when Moto Body said I've done 5,000! which is realistic)...
Next I noticed that my Live Wallpaper Minima wasnt very smooth in its motions and kept on freaking out even when held as still as I could. It had always worked perfectly on the old Nexus 6.
The phone works fine in general & rotates fine etc. It just seems extremely jumpy. Anyone else having this same issue?

I spoke to Google and they're sending a replacement.
Heres a video of the issue:
I'll post a reply to confirm the replacement device has fixed the issue.

Hey Dyna. I'm Josh, the developer of Minima. I'm currently looking into what might be causing this issue, as I've received maybe ten complaints from various 6P and 5X users over the past couple weeks about the jumpy tilt effect. The fact that it's spread across both devices makes me think it has more to do with how the system handles sensor updates on Marshmellow, rather than a particular device flaw.
Either way, I should have an update out soon to deal with the issue. I hope it will be as simple as smoothing out the incoming raw sensor data. If you'd like to discuss further you can reach me at [email protected].

Hi Josh
I have a new 6P arriving tomorrow, but possibly not required if other people are having the same issue, unless its a more common hardware fault as not everyone will use similar wallpaper or Google Fit so may go unnoticed. I had a Nexus 6 prior to the 6P and it worked perfectly with Marshmellow and Minima.
I love Minima btw!

I had this problem as well, as Josh said it may be an app issue if we're all having the same problem.

Same problem as you but:
Having the same problem and noticed it the same way (Minima). I tried a random compass app and it was really finicky. At first I thought my gyroscope/accelerometer was defective but just now I tried Doodle Jump, which works fine. Now I'm just confused.

OkayDev said:
Having the same problem and noticed it the same way (Minima). I tried a random compass app and it was really finicky. At first I thought my gyroscope/accelerometer was defective but just now I tried Doodle Jump, which works fine. Now I'm just confused.
Click to expand...
Click to collapse
I can think of several reasons why some apps would work and others wouldn't. For one, the app can choose certain types of sensors for this info (gravity vs accelerometer) and certain delays (UI vs Game vs Fastest). It could also have to do with how the sensor registration process starts per app. I've tried different combos with no luck.
I really hope it's in my code, because then I can fix it and all's well. If it's a sensor problem though...:crying:

I published a fix for this last night, let me know if any of you are having a better experience now, and if so which device is working better or not.

JokoInteractive said:
I published a fix for this last night, let me know if any of you are having a better experience now, and if so which device is working better or not.
Click to expand...
Click to collapse
Yeah I got it this morning, it's working much better. I still get the odd jolt, not a full glitch where it would freak out but a small jolt where it will stop for a fraction then catch up again. To be honest it may had done it on the Nexus 6, but I just never paid that much attention to it.
This is on both my 6P's, the original one that made me start this thread & my new RMA. It works perfectly on both, so maybe it was a software issue all along. I havent it long enough to see how Google Fit behaves, I wouldnt had thought your app would have had any impact on Google Fit?

DynaMight said:
Yeah I got it this morning, it's working much better. I still get the odd jolt, not a full glitch where it would freak out but a small jolt where it will stop for a fraction then catch up again. To be honest it may had done it on the Nexus 6, but I just never paid that much attention to it.
This is on both my 6P's, the original one that made me start this thread & my new RMA. It works perfectly on both, so maybe it was a software issue all along. I havent it long enough to see how Google Fit behaves, I wouldnt had thought your app would have had any impact on Google Fit?
Click to expand...
Click to collapse
It wasn't really a problem with Minima. Minima has been using the Gravity Sensor since last year, which is a combination of accelerometer and gravity data on the device. It's more accurate than just accel usually, which is why I used it. It looks like the gravity data can get buggy on the 6p and 5x, so I reverted to just using the accelerometer and things seem to have smoothed out.
So apps using gravity may get whacked out, while apps using only accel (like Doodle Jump) might be just fine. I can't say for sure, all I know is the switch seems to have worked well enough. I'm still continuing research in hopes that I'll find something more concrete.

JokoInteractive said:
I published a fix for this last night, let me know if any of you are having a better experience now, and if so which device is working better or not.
Click to expand...
Click to collapse
What kind of fix? For what? For a app?
Send with the App Tapatalk

I think I have also worked out why my Google Fit registers a stupid amount of steps. I dont fully understand why as none of my previous phones have done this...
I use Daydream mode as a bedside clock, which I've done for years, but for some reason on the 6P, if I do this it'll clock up as much as 40,000 steps overnight!
Heres this morning so far... I've been up about 2hrs and not even left the house:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Heres when the steps were made... when I was asleep!

I have the same issue with my 6P, you can clearly see that accelerometer is weird by using apps like star chart, or try viewing photospheres in a VR mode, you'll see that it just randomly like crazy

aygul12345 said:
What kind of fix? For what? For a app?
Click to expand...
Click to collapse
Minima Live Wallpaper. I'm using a different sensor configuration on Android 6.0 to work around the faulty gravity sensor data the 5x and 6p are generating.
---------- Post added at 09:32 AM ---------- Previous post was at 09:31 AM ----------
DynaMight said:
I think I have also worked out why my Google Fit registers a stupid amount of steps. I dont fully understand why as none of my previous phones have done this...
I use Daydream mode as a bedside clock, which I've done for years, but for some reason on the 6P, if I do this it'll clock up as much as 40,000 steps overnight!
Heres this morning so far... I've been up about 2hrs and not even left the house:
Heres when the steps were made... when I was asleep!
Click to expand...
Click to collapse
Yeah, just sitting idle the 5x shows a lot of jumpiness. I can see how it's logging that as steps.

So I was having the same issues with my Nexus 6P, spoke with Google Support and ended up getting my device replaced. I just received my new replacement device today and this one is still having the same exact issues.
On further testing using the Street View app, I've noticed that when I switch to Cardboard View it tracks perfectly, it's only the photo-sphere view that will not track my movements; it either won't spin at all or spins wildly by itself. Anyone have technical data on what the Cardboard viewer uses to track movement versus standard photo-sphere?

My phone started messing up also after I updated to MDB08L on Nov 11. I got my phone November 9th and the step counts were normal until then. My UP app has me walking over 200,000 steps yesterday and 75000 today when I normally average 12000. This is using the phone sensors. My android wear watch has normal counts. I also use the daydream app at night but the trends graph in the UP app have me doing 30 - 70000 steps in a 5 to 10 minute span while my phone is not Daydreaming. I'll be waiting to see if your RMA'd phone has the same problem.
OP: Which build are you on?
---------- Post added at 10:11 PM ---------- Previous post was at 10:05 PM ----------
Also the Google Sky app is very jittery as compared to my 2013 Moto X. But photosphere is relatively smooth.

I just installed and so experiencing issues... any fix yet?

HartgE46 said:
So I was having the same issues with my Nexus 6P, spoke with Google Support and ended up getting my device replaced. I just received my new replacement device today and this one is still having the same exact issues.
On further testing using the Street View app, I've noticed that when I switch to Cardboard View it tracks perfectly, it's only the photo-sphere view that will not track my movements; it either won't spin at all or spins wildly by itself. Anyone have technical data on what the Cardboard viewer uses to track movement versus standard photo-sphere?
Click to expand...
Click to collapse
I just tried photosphere on streetmaps and although it doesn't spin on its own or anything and tracks my angular shifts as I do them, it does seem to consistently show 'micro jitter' like it has parkinsons. I'm just gonna check my Z3 and see if it has the same jitteriness there and update this post. And as a side note, if this pans out to be true, then at risk of sounding retarded, I wonder if this same issue has been why electronic stabilisation is not at optimum on the 6P.

I got a replacement and it also has the same issues... I wonder if it's a software problem
too bad I updated android as soon as I turned it on, so I can't verify if it was working before MDB08L... any easy way to rollback to verify it?

waldo447 said:
My phone started messing up also after I updated to MDB08L on Nov 11. I got my phone November 9th and the step counts were normal until then. My UP app has me walking over 200,000 steps yesterday and 75000 today when I normally average 12000. This is using the phone sensors. My android wear watch has normal counts. I also use the daydream app at night but the trends graph in the UP app have me doing 30 - 70000 steps in a 5 to 10 minute span while my phone is not Daydreaming. I'll be waiting to see if your RMA'd phone has the same problem.
OP: Which build are you on?.
Click to expand...
Click to collapse
I got mine just over 2 weeks ago now, I accepted an OTA straight away. I think it was from MDA89D to MDB08K & I noticed the issue straight away. I'm now on MDB08M and its still got the same issue.
I have raised the issue with Google support and the guy I spoke to said he'd raise it for me. Hopefully its just a software issue that'll be fixed in the next OTA update.
If anyone wants to roll back to the original image, you can flash the factory images here: https://developers.google.com/android/nexus/images?hl=en as standard it'll wipe everything inc your pics etc, you can get around this by not flashing userdata.img.