Htc m7 camera focusing problems.

Hi, got my m7 for two two years now. A few months ago the camera seems to have some problems in focusing. Very often, half of the picture seems blur. I'm made sure the lens is clean. Anyone got the same problem?

camera problems with apps

the camera display is upside down for apps in the playstore like photomath, camera-fv, etc.

ChromeCast 2015 & UnBlock-US Problems

Hi Folks,



I'm running into an annoying problem with my new ChromeCast 2015. I've got an Asus AC68U router which I created static routes for Google's DNS (8.8.8.8 / 8.8.4.4) that direct to unused IP addresses on my local network and set the routers DNS to point to UnBlock-US DNS (208.122.23.23 / 208.122.23.22). However, I seem to be getting a lot of "video is not available in your region" and "video is unable to play" errors from Netflix's.



Now I also have an old ChromeCast (dongle style) which I rooted (Team-Eureka's rom) in order to be able to set the DNS servers on it directly to UnBlock-US and it works flawlessly (abeit slower than the ChromeCast 2015 version). A video that generates an error (above) on the ChromeCast 2015, will play properly on the older ChromeCast.



I've changed the DNS entries to Google's DNS on my older ChromeCast to test the static routing is working (which it seems to). So the question is why is the New ChromeCast being such a pain in the butt, where as the older one works flawlessly? Am I missing something in my static routing?



Thanks for any thoughts or suggestions


(Xposted to Reddit /r/Chromecast)

Sent from my Nexus 6 using Tapatalk

OVERHEATING PROBLEMS? Let's try to use a better THERMAL PASTE!

As you may know, our beloved smartphone suffers from some overheating problem, due to the powerful Snapdragon 810 that use.
Its cores are the real "cores" of the problem: Qualcomm has adopted pure ARM reference design instead their revised versions, that creates more trouble than it should;
No custom kernel or other things really solve the problem and the results are bad performances in heavy load scenario (multitasking or gaming) and more heat than usual.
To be honest, I never had any particular problems with my M9, but wanted to try something that I also done on my old M7: disassemble the phone and apply a serious-level thermal grease to make sure to put processor die in contact with the metal body!

Well, let's start!
Here's what I am faced: a carefully disassembled One M9 (iFixit exhaustively explains how to do that) and, at my discretion, the best thermal paste on the market, the Artic MX-4.



Now i gently opened the metal coverage of components and ... There is our processor!



At this point, i have to remove the old (and inefficient) thermal pad applied by the factory.
-In the photo i've already partially removed it.



The instant after the compound application.
Pressure will definitely flatten it; it's also a large surplus but in that way i'm sure that it will cover the entire surface of the processor and also the surroundings. (no problem, it does not conduct electricity)



After closing the coverage, I applied a dose of thermal paste also on it, to bring together the processor with the outside of the smartphone, according to the scheme below.





Now we're ready to clo...HEY! wait, wait, wait, is a missing screw what I just saw?
YES! and also explains my perception of the slightly lower volume from the bottom speaker!
Fortunately, M7 screw are compatible... screwed and fixed!
... is not an oversight that I would expect from this flagship device...



...as I was saying, I reassembled the smartphone.
No one will notice anything, like new!




And now, you will expect results ... here they are!
I made this improvement more than one month ago, at the time I done many many tests, i also take screenshots, but they're totally useless at the moment, because what you should know is the following;
In addition to the significant drop in temperature outside of the phone, as I noticed with my old M7, I have seen an unexpected increase in battery life of 10% of the daily average, really not bad!
And the temperature of the processor? It's now under control! Even under full load, the temperature increases gradually and slowly, without peaks and never exceed 45 degrees on the cores, even after several minutes of use.
In normal use, temperature is a few degrees above the ambient one.
To ensure that my system works well I did a little test... I launched a benchmark app (viewing onscreen temp) and after a few minutes I put an ice cube on the back of the phone, just above the processor position: I assisted to an insane temperature drop, from 45 to 7 degrees Celsius within 8-10 seconds!

What to say, I am pleased of the change I made to my M9, now the problem is not completely resolved but it is dammed.

Remember, I shared with you my experience for information, I do not assume liability for damage to your smartphone!

[Q&A]N9005 CM12.1 Keyboard problems.

Hello xda users!
I came here cause i couldnt manage to find any answer elsewhere.

Since I don't like the stock CM12.1 keyboard i tried to flash a samsung stock keyboard with cwm but the system ignores it

I've tried many keyboards apk but the only ones i like are the stock ones... is there any way to use stock samsung keyboard on Cyanogenmod 12.1 :confused:

Bluetooth contacts synch problems

Hi everyone!

I just bought the Redmi Note 2 phone and the Zeblaze Crystal watch and after connecting the watch to the phone I found out that the contacts can not be synchronized. I have my contacts synched with Google and Mi accounts and also on both SIM cards but for some reason the watch can not see them. Everything else is working - I can read my SMS, call cogs etc, but the contacts can not be seen by the watch.

Later on I tried to connect the phone to my car and it connects and works fine - I make and accept calls but again the contacts can not be synched. The car has a very good Bluetooth settings menu and a specific function for contacts downloading but when I try to download the contacts after a few seconds it stops and gives a "not possible" message. I can only download the call log... Just like with the watch...
So I am starting to believe that it is a problem with the phone - maybe something with the MIUI settings (MIUI ver. 66.77.33.00).
With my wife's Samsung phone everything connects just fine and the contacts are synchronized immediately to the car or the watch so its really a problem with the phone.
Any ideas what the problem could be? :(

Boot problems after stock flash

A friend of mine was running CM on her L720 and asked me to re-image it. I'm not sure what version of CM it was but it was definitely a 4.4.2 build. I tried to flash back to stock using Odin and FNG2 img. Odin reported that it passed but the phone won't boot. It displays the Galaxy logo for 5-6 seconds then goes black and nothing else happens. I can boot into download mode and recovery (CWM). I've tried reflashing and factory reset, but no luck. I have not flashed stock recovery back yet...could this be the issue? It seems like a logical next step but since I know little about troubleshooting these issues, I thought I'd better ask before I screw things up further. Any help would be greatly appreciated. TIA!

(E5823) Problems with camera...

My Problem is, when i start the camera ive get a black screen.

If i make a hard reset, and after i make all settings, the camera ist working fine!
After some minutes, i dont know why, the phone is making an automatical restart. Then the camera dosnt work anymore. If i use apps like instagram or else, the camera works.
I have the problem with the firmware 32.0.A.4.11 and now with 32.0.A.5.32

It sucks. :)
Can someone help me? Any solutions?

I have problems to S-OFF my M7

Hi everyone,

I need to S-OFF my M7 otherwise I'll have to buy a new phone, but I love it so I don't want to change it.

I'm on Android 5.0.2 so maybe I'm a bit too updated for most of the procedures to correctly work, maybe?
I tried RumRunner but it tells me to try another kernel or rom, since it will not work with my current setup.
I wanted to try MoonShine but I'm on 7.19.401.30, but only 1.29.401.16 and 1.29.401.13 are available.

What should I do in your opinion?

[solved] Bluetooth pairing problems

I'm running the N9005XXUGPOI2_DevBase_alexndr 5.0 ROM on my N9005. Bluetooth pairs OK with my car and bluetooth headphones but it refuses to see my Bose Soundlink II speaker. Other devices pair OK with the Bose speaker. Does anyone have any ideas? Thanks.

problems with rooting LG G4 h815 v10d

Hi everybody,

in the last days i had some problems with my LG G4 with wifi and i read that the only way to fix the problem was to root the phone and delete some dhcp files .
So this afternoon i started the root following this guide : http://forum.xda-developers.com/g4/o...ot-lg-t3164765
I followed all the points (the only thing i couldn't do is to copy the file system.rooted.H81510c-EU in the root folder in SD card just because i don't have sd external card, so i copied it in the general storage folder.
It all went well til the firmware update. I turned off the phone and restarded in download mode. Now it's about 30 min that it's stuck in the firmware update at 0%... :( what could i do? do i have to wait or there is some problem?? help pls

Problems with 2G/3G Signal Reception. Antenna issues?

Folks.

I dropped my phone once and since then, it has very bad connectivity. Flashed all sorts of ROMs and radios but nothing would work. I am afraid this is a physical damage/dislocation to either antenna or the 2G/3G GSM Radio Chip, since 4G/LTE works mostly fine.

Any idea what might have gone wrong?

Anyone had GPS fix problems?

Has anyone had problems with GPS fix at all? I was using my Z1 in the car today with TomTom Go and I was getting problems with it losing GPS positioning. The app would just stop updating location. At first I put it down to it being just another bug in the app - it seems pretty buggy. But after giving up on TomTom and using Google Maps that app also reported loss of GPS fix, even though it had a good clear view of the sky. So I suspected a hardware fault. But at a traffic light I managed to pull up the app GPS Test and it showed good reception with 25 satellites in view and 13 in use - yet no fix. Which suggests to me there is some error in the GPS software handling. This is the one problem I have had with the phone so far, anyone else?

Z5 Display problems brightness/illumination

Hi all,

i got a problem with my display.

The brightness/illumination on display when displaying content with white background is from what I see not correct.

A certain part in the middle of my display is clearly more illuminated then the rest. But only when showing the color white.

I did the diagnosis test in the menus and here it occurred again.

Does anybody have the same issue?

Is this a display problem so I have to change my phone? Or is this just a calibration problem?

Thanks in advance:)

Galaxy s3 SHG-1747 with 4.4.2 rooting problems

Ive been up all night long on this site looking for a way to root my galaxy s3 i have tried almost everything and still cant find a way to root it, i dont care if it voids the warranty because there is no warranty. please can someone help me or atleast tell me that it is unrootable.

10 OF The Nexus Android 6.0 Problems & How to Fix Them.

This list of common Nexus Android 6.0 problems comes with some fixes that have been passed down over the years. All of them are proven fixes and there’s a good chance that you’ll find the fix that you’ve been looking for here. If you don’t, there are a number of other resources that could come in handy. We outline those below.


How to Fix Android 6.0 Installation Problems

Google’s Nexus Android 6.0 Marshmallow OTA roll out is moving slowly but that’s not a problem. That’s by design. If you’re unable to install the update, manually or Over-the-Air, that’s a problem. And a common one at that.

If you’re having trouble sideloading the software on your Nexus phone or tablet, take a look at our in-depth guide. It will take you through the process and show you how to install the software without any trouble.

There are a few things you can try if your Android 6.0 Marshmallow installation gets stuck during the download or the installation.One thing that’s worked for us is to let the device’s battery die, recharge it to 100%, and then try the update again.

If that doesn’t work, you can try clearing your device’s cache partition to try and jumpstart the installation. Here is how to do that:

Press and hold Power and Volume Down buttons simultaneously until you see something other than Google on the screen.

At this point, you should see a large arrow at the top of the screen.

Tap Volume Down repeatedly until you see Recovery in the arrow.

Then tap the Power button.

You should see an android on his back with its chest open showing red triangle and exclamation mark.

While holding the Power button, tap Volume Up once then release the Power button.

You should now see a list of items at top of screen.

Tap Volume Down until the item to erase or wipe the cache partition is highlighted.

Then tap Power button to initiate the process.
A status messages will appear at the bottom of the screen.

Be patient because this can take 10-15 minutes to complete.

When done restart the Nexus.

If none of that works, and you can’t find a fix anywhere else, you might want to factory reset your device.

Obviously, that’s not ideal but it’s an option if you can’t dislodge the problem.


How to Fix Android 6.0 Battery Life Problems.

Battery life issues are extremely common after major Android updates so it hasn’t been surprising to see Nexus users complain about abnormal battery drain this week. Nexus Android 6.0 battery issues are isolated but we could see the number of complaints grow as the OTAs pick up speed.

If your Nexus Android 6.0 battery life isn’t what you think it should be after installing Google’s new operating system, you’ll first want to wait a couple of days for the software to settle. Battery life can take a few days to settle down. Wait two days. If nothing changes, it’s time to take action.

We’ve put together a guide that will take you through some steps to take if you notice something wrong with your Nexus’ battery. Take a look at that before you factory reset your phone or try and get a new device from Google.


How to Fix Android 6.0 Charging Problems.

For one reason or another, charging problems always seem to plague Nexus users after new Android updates. Android 6.0 Marshmallow is no different and we expect to see more charging issues emerge in the days, weeks and months to come. Fortunately, there are some potential fixes for these Android 6.0 Marshmallow charging problems.

First try this. If you can, charge your Nexus up to 100%. Once it’s there (this could take awhile), let the charge start to fall. Before it gets down to 0%, right around the 5% mark, charge it up to 100% again. Repeat this three to four times and it could return to normal.

If that doesn’t work, and it may not, there are a few other possible remedies to try. Make sure that the Nexus is being charged with the cable that it came with. If you’re using the original charger, and it still doesn’t work, try using another charger with the same voltage rating as the one that came with your device.

You can also try swapping out the wall charger for a USB cable. Plug your Nexus device into a computer and charge it that way to see if it helps.

Google’s fixes in the video above might work as well. Take a look at them because they include one quick fix that might jumpstart your Nexus.


How to Fix Android 6.0 Data Problems

Some Nexus users are saying that Android Marshmallow fixed their data issues but others are saying that Android 6.0 is causing issues with cellular data. Issues with these connections are common right after a major update but they can be tricky to fix.

If you’re confident that these issues don’t have anything to do with an outage at Google or your service provider, you’ll want to restart your Nexus device. Power it down and reboot it. This has worked for some Nexus users in the past. that doesn’t work, it’s time to head into your phone or tablet. First, try forgetting your Wi-Fi connection. Go into your Wi-Fi settings, either in the Settings menu or via the Quick Settings drop down, and select the connection. Choose Forget and then reconnect.

You can also try changing the frequency. To do that, click the vertical dots in the top right corner to bring up the Advanced menu. Go to Wi-Fi frequency band and test the different options. It should be set to Automatic by default.

If none of these fixes squash your Android 6.0 Wi-Fi problems, we recommend updating your applications.
If that doesn’t help, boot your device into Safe Mode to try and single out problem apps. Apps have been known to cause issues with connectivity.


Android 6.0 Bluetooth Problems

Bluetooth problems are also extremely common after Android updates and we’re starting to see Nexus users complain about Android Marshmallow Bluetooth problems. These can be a little tricky to fix due to the number of third-party Bluetooth devices out there but here are some fixes for the most common issues.

First, try flipping it off then back on again. If that doesn’t jumpstart your connection, you can try forgetting the connection to see if that helps. Head into your Bluetooth connections in Settings, select the one causing you problems, and then select Forget. Reconnect and see if that helps. This has worked for us with speakers, headphones and watches in the past.

If you’re having problems with Bluetooth in your car, you’ll want to try and reset its Bluetooth connection if you can. Consult the car’s manual or take it into a dealer if you can’t figure it out on your own. Reset it, forget the connection on your device and then try to connect again.

If forgetting your connections fails to solve the issue, you will want to try booting into Safe Mode. Again, to do this, follow Google’s instructions. Safe Mode will disable third-party apps and help you track down culprits.

You can also try wiping the cache partition (instructions above) or factory resetting the phone or tablet to see if that corrects the issue.


How to Fix Android 6.0 Data Problems

Some Nexus users are saying that Android Marshmallow fixed their data issues but others are saying that Android 6.0 is causing issues with cellular data. Issues with these connections are common right after a major update but they can be tricky to fix.

If you’re confident that these issues don’t have anything to do with an outage at Google or your service provider, you’ll want to restart your Nexus device. Power it down and reboot it. This has worked for some Nexus users in the past.

We’ve also had success putting our device into Airplane Mode. Switch on Airplane Mode and then switch it off. Airplane Mode will kill of your connections. Once you turn it off, your connections will be restored.

You can also try taking out the SIM card from the side of your Nexus device (if you have one). This has been known to restore broken data connections but it’s not a guaranteed fix.

If that doesn’t work, and you’re positive that should be getting service, you should try and contact your service provider.


How to Fix Android 6.0 Performance Problems

If your device starts exhibiting lag or random stuttering after the Android 6.0 Marshmallow update, there are a few things you can try.

The first thing to try is a clearing of your cache partition. (Instructions near the top of this page.) This is a proven fix for lag issues and it could come in handy if your Nexus 7 2013, Nexus 5 or another device starts underperforming with Android 6.0 on board.

If that doesn’t work, you can try using an application like Qualcomm’s Trenpn Profiler to monitor your CPU activity.

If you don’t want to download another app, Android 6.0 Marshmallow also comes with a new RAM Manager tool (it can be found inside of the apps menu).

The RAM Manager allows you to see what’s slowing your device down, what’s using the maximum or minimum amount of RAM, and more. Keep an eye out for troublemakers.

You can also try deleting files that you no longer need, cut back on the amount of widgets that you’re using, and cut back on animations and transitions. If you want excellent performance on your device, you’ll want to be lean.


How to Fix Android 6.0 App Problems.

We’re seeing complaints about various app problems after the Android 6.0 Marshmallow update. This isn’t surprising because apps always tend to act up after Android updates.

First, try installing the latest bug fix update to see if that helps stabilize the application. We’ve seen tons of applications get updated in the past week and these should help to cut down on issues.
Try downloading the latest update, assuming it has good reviews.


Random Reboots

We’re already hearing about random reboots in the aftermath of the Android 6.0 Marshmallow update. This doesn’t come as a surprise. Random reboots (memory leaks) have plagued Nexus devices since the beginning.

First, try restarting your phone or tablet. If that doesn’t help, try updating your applications. Old apps that haven’t been updated in awhile can cause issues. You might also want to clear App data and cache. To do that, go into Apps in Settings, click your apps, and the clear data and cache.

If none of that works, you can try a downgrade (with the appropriate files, of course) or a factory reset. of your device.


How to Fix Android 6.0 Problems If Nothing Else Works

If none of these fixes work, there are several other resources to take a look at before contacting Google.

First, we recommend looking at Google’s Nexus Help Forum. There are tons of people on there that are willing to help with issues big and small.

If you can’t find anything, we recommend performing a factory reset on the device to bring everything back to the way it was when the device was first bought. Make sure all of your files are backed up before you do this. :victory:

Nexus 5X reboot problems

If you're having reboot problems please post here - if there are problem apps or bad devices out there it would be good to know!

Got a new Nexus 5X yesterday for my partner. Plugged it in and charged all day (oh what patience). 10pm started setup and added account to it. Phone immediately did an update which succeeded. Then it started to install the saved apps from the Google account, about 50 in all. After all the apps were installed I handed it over to her to play and log into all those apps with logins. Tedious.

Within about 30 minutes she tried to take a photo and it rebooted. Then a bit later she was using it and it rebooted again. Before going to be it rebooted a few more times. Then again this morning. There wasn't one particular app or other that was in use when these crashes happened. During the day she saw a message about "Google needs to restart". Also the camera often comes up with an all black screen and can't be used.

I called Google tech support and they wanted to do a factory reset and maybe a cache partition wipe. They would also like to investigate if a rogue app is causing the crashes by using it without any apps installed. Because reinstalling apps is so tedious I decided to have her do a cache partition reset I'm awaiting news. I'm hoping we don't have to do the other... I can't imagine how a bad app could be causing such repeated crashes (well I can, but it just shouldn't happen). That's lame...

It would really help if it was easy to get a crash log and find out the cause - unfortunately unless you're rooted this doesn't seem to be easy, and may well be impossible.

Duplicate contacts and BT problems SOLVED

Quote:

I have 3 problems that are really annoying me in G4. 1- can't find an option to save new contacts in Google contacts by default. 2- whenever I install WhatsApp I have duplicated numbers not in phone app but I do have them in SMS app (stock/yataa/handcent). 3- some contacts refuse to sync over bluetooth to my car. I tried to figure what's different between them and the ones who sync and can't find any common denominator.

For future reference to anyone with same problem, how I managed to solve them:

1-To use google contacts as default for new contacts you have to select to show only google contacts in the setting of contacts app.

2- This one took a bit of time but after using this app to delete duplicated numbers within same name it was solved. You need the pro version. https://play.google.com/store/apps/d...ector&hl=pt_PT

3- Found this one in a French forum. It seems like this is been an issue when using some roms with Renault and Mazda systems. You also need this pro version. https://play.google.com/store/apps/d....irmc&hl=pt_PT

Hope it helps some one... Was getting desperate!

problems with Elephone S2 Plus

Hello! Please help! There is a produced phone in use 1,5 MTH. Approximately in a kickoff of October there was a misfortune, sensor control buttons have refused and began not to work correctly тачскрин. There was it after I wished to deliver mt manager, have decided to clone приложуху. It was gained, but W / O optimisation. For this purpose it was necessary to change toolbox W appropriate permissions. Began to change and root explorer has given out an error. Has folded. All subsequent startings up were W the same error, and the earphone particularly hung before abandonment. Has decided to reboot. After has gained cyclical reboot. Has come in in recovery, has made wipe. reboot. Both AGN reboot. And AGN. And AGN.... Has downloaded wearing, it was broached flashtool. But wearing has fixed by error from Elephone s2. The phone was started up, but W a black screen. Began to dig further and has discovered on s2 plus wearing. But after push button starting up do not work, the shield W it is left overshoots capitally. Multiple rewearings have not helped. In some applications spontaneous horizontal attitude, and furthermore in horizon the shield on a broader scale is stacked impression does not work. Suggest, where the dog is inearthed? THX! Answers or here on e-mail prihodkods@gmail.com

Here a broad gull from AIDA64, on it it can is possible to ascertain something

<<< System >>>

Manufacturer: Elephone
Model: Elephone S2 Plus
Brand: Elephone
Board: Android
Device: Android
Hardware: mt6735
Product: Elephone S2 Plus
Serial: 0123456789ABCDEF
Installed RAM: 2 GB
Total Memory: 1944 MB
Available Memory: 671 MB
Internal Storage Total Space: 12.16 GB
Internal Storage Free Space: 8286 MB
Device Features: android.hardware.audio.output
android.hardware.bluetooth
android.hardware.bluetooth_le
android.hardware.camera
android.hardware.camera.any
android.hardware.camera.autofocus
android.hardware.camera.flash
android.hardware.camera.front
android.hardware.faketouch
android.hardware.location
android.hardware.location.gps
android.hardware.location.network
android.hardware.microphone
android.hardware.screen.landscape
android.hardware.screen.portrait
android.hardware.sensor.accelerometer
android.hardware.sensor.compass
android.hardware.sensor.gyroscope
android.hardware.sensor.light
android.hardware.sensor.proximity
android.hardware.telephony
android.hardware.telephony.gsm
android.hardware.touchscreen
android.hardware.touchscreen.multitouch
android.hardware.touchscreen.multitouch.distinct
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.usb.accessory
android.hardware.usb.host
android.hardware.wifi
android.hardware.wifi.direct
android.software.app_widgets
android.software.backup
android.software.connectionservice
android.software.device_admin
android.software.home_screen
android.software.input_methods
android.software.live_wallpaper
android.software.print
android.software.voice_recognizers
android.software.webview

<<< CPU >>>

SoC Model: MediaTek MT6735
Core Architecture: 4x ARM Cortex-A53 @ 988 MHz
Manufacturing Process: 28 nm
Instruction Set: 32-bit ARMv7
CPU Revision: r0p4
CPU Cores: 4
CPU Clock Range: 221 - 988 MHz
Core 1 Clock: 988 MHz
Core 2 Clock: 988 MHz
Core 3 Clock: 988 MHz
Core 4 Clock: 988 MHz
CPU Utilization: 24 %
Scaling Governor: interactive
Supported ABIs: armeabi-v7a, armeabi
Supported 32-bit ABIs: armeabi-v7a, armeabi

<<< Display >>>

Screen Resolution: 720 × 1280
xdpi / ydpi: 320 / 320 dpi
GPU Vendor: ARM
GPU Renderer: Mali-T720
GPU Cores: 1
Refresh Rate: 56 Hz
Default Orientation: Portrait
OpenGL ES Version: 3.0
GPU Version: OpenGL ES 3.1
OpenGL ES Extensions: GL_EXT_debug_marker
GL_ARM_rgba8
GL_ARM_mali_shader_binary
GL_OES_depth24
GL_OES_depth_texture
GL_OES_depth_texture_cube_map
GL_OES_packed_depth_stencil
GL_OES_rgb8_rgba8
GL_EXT_read_format_bgra
GL_OES_compressed_paletted_texture
GL_OES_compressed_ETC1_RGB8_texture
GL_OES_standard_derivatives
GL_OES_EGL_image
GL_OES_EGL_image_external
GL_OES_EGL_sync
GL_OES_texture_npot
GL_OES_vertex_half_float
GL_OES_required_internalformat
GL_OES_vertex_array_object
GL_OES_mapbuffer
GL_EXT_texture_format_BGRA8888
GL_EXT_texture_rg
GL_EXT_texture_type_2_10_10_10_REV
GL_OES_fbo_render_mipmap
GL_OES_element_index_uint
GL_EXT_shadow_samplers
GL_OES_texture_compression_astc
GL_KHR_texture_compression_astc_ldr
GL_KHR_texture_compression_astc_hdr
GL_KHR_debug
GL_EXT_occlusion_query_boolean
GL_EXT_disjoint_timer_query
GL_EXT_blend_minmax
GL_EXT_discard_framebuffer
GL_OES_get_program_binary
GL_OES_texture_3D
GL_EXT_texture_storage
GL_EXT_multisampled_render_to_texture
GL_OES_surfaceless_context
GL_OES_texture_stencil8
GL_EXT_shader_pixel_local_storage
GL_ARM_shader_framebuffer_fetch
GL_ARM_shader_framebuffer_fetch_depth_stencil
GL_ARM_mali_program_binary
GL_EXT_sRGB
GL_EXT_sRGB_write_control
GL_EXT_texture_sRGB_decode
GL_KHR_blend_equation_advanced
GL_OES_texture_storage_multisample_2d_array
GL_OES_shader_image_atomic

<<< Network >>>

<< Telephony - SIM1 >>
Phone Type: GSM
Network Operator Name: MTS RUS
Network Operator Code: 25001
Network Operator Country: Russia
SIM Provider Name: MTS RUS
SIM Provider Code: 25001
SIM Provider Country: Russia
SIM State: Ready
Network Type: EDGE
Data Connection State: Disconnected
Data Activity: None
Device Is Roaming: No
ICC Card: Present

<< Telephony - SIM2 >>
Phone Type: GSM
Network Operator Name: Beeline
Network Operator Code: 25099
Network Operator Country: Russia
SIM Provider Name: Beeline
SIM Provider Code: 25099
SIM Provider Country: Russia
SIM State: Ready
Network Type: EDGE
Data Connection State: Unknown
Data Activity: Unknown
Device Is Roaming: No
ICC Card: Present

<< Wi-Fi >>
State: Enabled
SSID: "@RtemNet"
BSSID: 48:ee:0c:c7:36:e2
Hidden SSID: No
IP Address: 192.168.0.45
MAC Address: 00:0c:e7:a2:2e:90
Signal Strength: -51 dBm (Excellent)
Link Speed: 135 Mbps
Frequency: 2472 MHz
Network ID: 0
Gateway: 192.168.0.1
DNS1: 192.168.0.1
DHCP Lease Duration: 24 hours
5 GHz Band: Supported
Wi-Fi Direct: Supported

<<< Battery >>>

Power Source: Battery
Level: 88 %
Status: Not Charging
Health: Good
Technology: Li-ion
Temperature: 26.0°C
Voltage: 4.122 V

<<< Android >>>

Android Version: 5.1 (Lollipop)
API Level: 22
Rooted Device: Yes
Android ID: aaf65a649b1586b9
Build ID: Elephone_S2_Plus_20150619
Codename: REL
Fingerprint: alps/full_bird6735m_35gu_a_l/bird6735m_35gu_a_l:5.1/LMY47D/1434632411:user/dev-keys
ID: LMY47D
Incremental: 1434632411
Java Runtime Version: Android Runtime 0.9
Java VM Version: ART 2.1.0
Java VM Heap Size: 128 MB
Kernel Architecture: armv7l
Kernel Version: 3.10.65 (wtl@wtl) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Jun 18 09:28:42 EDT 2015
Tags: dev-keys
Type: user
OpenSSL Version: OpenSSL 1.0.1j 15 Oct 2014
ZLib Version: 1.2.8
ICU CLDR Version: 25.0
ICU Library Version: 53.1.0.1
ICU Unicode Version: 6.3
Android Language: Russian (Russia)
Configured Time Zone: Vostok Time (UTC+06:00)
UpTime: 2 days, 10:34:11

<<< Devices >>>

<< Rear-Facing Camera >>
Resolution: 13.3 MP (4864 × 2736)
Video Resolution: 2.1 MP (1920 × 1088)
Video Snapshot: Supported
Video Stabilization: Supported
Zoom: Supported
Smooth Zoom: Supported
Auto Exposure Locking: Supported
Auto White Balance Locking: Supported
Flash: Supported

<< Front-Facing Camera >>
Resolution: 1.9 MP (1600 × 1200)
Video Resolution: 0.9 MP (1280 × 736)
Video Snapshot: Not Supported
Video Stabilization: Supported
Zoom: Supported
Smooth Zoom: Supported
Auto Exposure Locking: Supported
Auto White Balance Locking: Supported
Flash: Not Supported

<< USB Device - Linux 3.10.65 musb-hcd MUSB HDRC host driver >>
Manufacturer: Linux 3.10.65 musb-hcd
Product: MUSB HDRC host driver
Serial: musb-hdrc.0.auto
Device ID: 1D6B-0002
Device Class: 09 / 00 (Hi-Speed Hub with single TT)
Device Protocol: 01
Supported USB Version: 2.00
Current Speed: 480 Mbps

<< OpenCL Device - Mali-T720 >>
Device Name: Mali-T720
Device Type: GPU
Device Vendor: ARM
Device Vendor ID: 0x07201000
Device Version: OpenCL 1.1
Device Profile: Full
Driver Version: 1.1
OpenCL C Version: OpenCL C 1.1
Clock Rate: 5 MHz
Compute Units: 1
Address Space Size: 64-bit
Max 2D Image Size: 65536 × 65536
Max 3D Image Size: 65536 × 65536 × 65536
Max Samplers: 16
Max Work-Item Size: 256 × 256 × 256
Max Work-Group Size: 128
Max Argument Size: 1 KB
Max Constant Buffer Size: 64 KB
Max Constant Arguments: 8
Native ISA Vector Widths: char16, short8, int4, long2, half8, float4, double2
Preferred Native Vector Widths: char16, short8, int4, long2, half8, float4, double2
Profiling Timer Resolution: 1000 ns
OpenCL Library: /system/vendor/lib/egl/libGLES_mali.so
Global Memory: 1990692 KB
Global Memory Cache: 64 KB (Read/Write, 64-byte line)
Local Memory: 32 KB
Max Memory Object Allocation Size: 497673 KB
Memory Base Address Alignment: 1024-bit
Min Data Type Alignment: 128 bytes
Command-Queue Out Of Order Execution: Enabled
Command-Queue Profiling: Enabled
Compiler Available: Yes
Error Correction: Not Supported
Images: Supported
Kernel Execution: Supported
Linker Available: No
Little-Endian Device: Yes
Native Kernel Execution: Not Supported
SVM Atomics: Not Supported
SVM Coarse Grain Buffer: Not Supported
SVM Fine Grain Buffer: Not Supported
SVM Fine Grain System: Not Supported
Unified Memory: Yes
OpenCL Extensions: cl_khr_global_int32_base_atomics
cl_khr_global_int32_extended_atomics
cl_khr_local_int32_base_atomics
cl_khr_local_int32_extended_atomics
cl_khr_byte_addressable_store
cl_khr_fp64
cl_khr_int64_base_atomics
cl_khr_int64_extended_atomics
cl_khr_fp16
cl_khr_gl_sharing
cl_khr_icd
cl_khr_egl_event
cl_khr_egl_image
cl_arm_core_id
cl_arm_printf

No CUDA devices found.
No PCI devices found.

<<< Thermal >>>

mtktswmt: 27.0°C
mtktspmic: 30.8°C
mtkts1: 32.5°C
mtkts2: 32.3°C
mtkts3: 31.9°C
mtktsbattery: 26.0°C
mtktscpu: 32.5°C
mtktsAP: 23.0°C
mtktsbtsmdpa: 25.0°C
Battery: 26.0°C

<<< Sensors >>>

ACCELEROMETER:
PROXIMITY: 1.0 cm
LIGHT:

<<< Apps >>>

2ГИС: ru.dublgis.dgismobile(v3.19.5)
4PDA: mike.flameclient(v2.1.2)
ACR: com.nll.acr(v14.9)
AdAway: org.adaway(v3.0.2)
AIDA64: com.finalwire.aida64(v1.29)
AK Notepad: com.akproduction.notepad(v2.4.6)
B612: com.linecorp.b612.android(v4.0.1)
BSPlayer FREE: com.bsplayer.bspandroid.free(v1.24.183)
Button Savior: com.smart.swkey(v2.1.8)
CandyCamera: com.joeware.android.gpulumera(v2.24)
Chrome: com.android.chrome(v46.0.2490.76)
Compass: com.apksoftware.compass(v3.2.2)
Cool Reader: org.coolreader(v3.1.2-102)
DU Cleaner: com.duapps.cleaner(v1.0)
DU Speed Booster: com.dianxinos.optimizer.duplay(v2.6.7)
Durak++: tm.durak(v15.10.16)
ES Проводник: com.estrongs.android.pop(v4.0.2.3)
Evernote: com.evernote(v7.3)
Firefox: org.mozilla.firefox(v41.0.2)
FTP (Передача файлов): com.ghisler.tcplugins.FTP(v2.06)
Gmail: com.google.android.gm(v5.6.103338659.release)
Hangouts: com.google.android.talk(v5.0.104885319)
Helper(Smart App Protector): com.sp.protector.helper(v2.0)
Hola Launcher: com.hola.launcher(v2.0.3)
LINE Launcher: com.campmobile.launcher(v2.0.95)
Mobileuncle Tools: com.mobileuncle.toolbox(v20140111v2.9.9)
MyScore: eu.livesport.MyScore_ru(v2.1.0)
Navitel: com.navitel(v9.5.0)
OfficeSuite: com.mobisystems.office(v8.4.4317)
QIWI: ru.mw(v2.18.1.2)
QuickPic: com.alensw.PicFolder(v4.6.2.1180)
Root Browser: com.jrummy.root.browserfree(v2.2.3)
Root Checker Basic: com.joeykrim.rootcheck(v5.6.1)
Root Explorer: com.speedsoftware.rootexplorer(v3.3.5)
Rutaxi: com.its.rto(v3.6.1)
Skype: com.skype.raider(v6.6.0.333)
Smart AppLock: com.sp.protector.free(v6.6.3)
Taxi: com.its.taxi(v1.21.2)
Taxsee Driver: com.taxsee.driver(v3.2.6)
Telegram: org.telegram.messenger(v3.2.4)
Titanium Backup: com.keramidas.TitaniumBackup(v6.2.0)
Total Commander: com.ghisler.android.TotalCommander(v2.62)
TrackID™: com.sonyericsson.trackid(v4.3.B.1.3)
Viber: com.viber.voip(v5.6.0.2413)
Weather & Clock Widget: com.devexpert.weather(v5.5.0.1)
WhatsApp: com.whatsapp(v2.12.317)
YouTube: com.google.android.youtube(v10.37.58)
Zedge: net.zedge.android(v4.18.3)
Zello: com.loudtalks(v3.03)
Борьба Умов ПРЕМИУМ: se.feomedia.quizkampen.ru.premium(v2.1.8)
ВКонтакте: com.vkontakte.android(v3.15.2)
Все коды регионов: com.region(v3.19)
Грузик: com.fordarian.gruzik(v0.3)
Календарь: com.google.android.calendar(v5.2.4-102744861-release)
Клавиатура SwiftKey: com.touchtype.swiftkey(v5.3.4.70)
ОК: ru.ok.android(v4.5.2)
Операторы России: org.nkuznetsov.def(v1.7.6)
Почта Mail.Ru: ru.mail.mailapp(v3.1.3.12222)
Почта России: com.octopod.russianpost.client.android(v3.2)
Приложение Google: com.google.android.googlequicksearchbox(v5.4.25.19 .arm)
Российская газета: com.rg.android.newspaper.main(v1.0.7)
Советские военные карты: com.atlogis.sovietmaps.free(v4.0.7 free)
Чемпионат: ru.ideast.championat(v3.2)
Чёрный список блокировки: com.appall.CallBlockingBlacklist(v1.2.0)
Штрафы ГИБДД FREE: org.policefines.finesNotCommercial(v4.2.6)
Яндекс.Почта: ru.yandex.mail(v2.16)

<<< Codecs >>>

OMX.MTK.AUDIO.DECODER.MP3: audio/mpeg
OMX.google.opus.decoder: audio/opus
OMX.MTK.AUDIO.DECODER.ADPCM.MS: audio/x-adpcm-ms
OMX.MTK.AUDIO.DECODER.ADPCM.DVI: audio/x-adpcm-dvi-ima
OMX.MTK.AUDIO.DECODER.GSM: audio/gsm
OMX.MTK.AUDIO.DECODER.RAW: audio/raw
OMX.MTK.AUDIO.DECODER.G711.ALAW: audio/g711-alaw
OMX.MTK.AUDIO.DECODER.G711.MLAW: audio/g711-mlaw
OMX.MTK.AUDIO.DECODER.FLAC: audio/flac
OMX.MTK.AUDIO.DECODER.APE: audio/ape
OMX.google.amrnb.decoder: audio/3gpp
OMX.google.amrwb.decoder: audio/amr-wb
OMX.google.aac.decoder: audio/mp4a-latm
OMX.google.vorbis.decoder: audio/vorbis
OMX.MTK.VIDEO.DECODER.MPEG2: video/mpeg2
OMX.MTK.VIDEO.DECODER.HEVC: video/hevc
OMX.MTK.VIDEO.DECODER.MPEG4: video/mp4v-es
OMX.MTK.VIDEO.DECODER.H263: video/3gpp
OMX.MTK.VIDEO.DECODER.AVC: video/avc
OMX.MTK.VIDEO.DECODER.VPX: video/x-vnd.on2.vp8
OMX.MTK.VIDEO.DECODER.VP9: video/x-vnd.on2.vp9
OMX.MTK.VIDEO.DECODER.VC1: video/x-ms-wmv
OMX.MTK.VIDEO.DECODER.DIVX: video/divx
OMX.MTK.VIDEO.DECODER.DIVX3: video/divx3
OMX.MTK.VIDEO.DECODER.XVID: video/xvid
OMX.MTK.VIDEO.DECODER.S263: video/flv1
OMX.google.vp8.decoder: video/x-vnd.on2.vp8
OMX.google.h264.decoder: video/avc
OMX.MTK.VIDEO.ENCODER.MPEG4: video/mp4v-es
OMX.MTK.VIDEO.ENCODER.H263: video/3gpp
OMX.MTK.VIDEO.ENCODER.AVC: video/avc
OMX.MTK.AUDIO.ENCODER.VORBIS: audio/vorbis
OMX.MTK.AUDIO.ENCODER.ADPCM.MS: audio/x-adpcm-ms
OMX.MTK.AUDIO.ENCODER.ADPCM.DVI: audio/x-adpcm-dvi-ima
OMX.google.aac.encoder: audio/mp4a-latm
OMX.google.amrnb.encoder: audio/3gpp
OMX.google.amrwb.encoder: audio/amr-wb
OMX.google.flac.encoder: audio/flac
OMX.google.vp8.encoder: video/x-vnd.on2.vp8

<<< Directories >>>

Data: /data
Root: /system
Java Home: /system
Download/Cache Content: /cache

<< External Storage >>
Primary External Storage: /storage/emulated/0
External Files #1: /storage/emulated/0/Android/data/com.finalwire.aida64/files
Alarms: /storage/emulated/0/Alarms
DCIM: /storage/emulated/0/DCIM
Downloads: /storage/emulated/0/Download
Movies: /storage/emulated/0/Movies
Music: /storage/emulated/0/Music
Notifications: /storage/emulated/0/Notifications
Pictures: /storage/emulated/0/Pictures
Podcasts: /storage/emulated/0/Podcasts
Ringtones: /storage/emulated/0/Ringtones

<< Mount Points >>
/: Device: rootfs
File System: rootfs
Read-Only
/dev: Device: tmpfs
File System: tmpfs
Read-Write
/dev/pts: Device: devpts
File System: devpts
Read-Write
/dev/cpuctl: Device: none
File System: cgroup
Read-Write
/dev/usb-ffs/adb: Device: adb
File System: functionfs
Read-Write
/proc: Device: proc
File System: proc
Read-Write
/sys: Device: sysfs
File System: sysfs
Read-Write
/sys/fs/selinux: Device: selinuxfs
File System: selinuxfs
Read-Write
/sys/fs/cgroup: Device: none
File System: tmpfs
Read-Write
/sys/kernel/debug: Device: debugfs
File System: debugfs
Read-Write
/acct: Device: none
File System: cgroup
Read-Write
/mnt/asec: Device: tmpfs
File System: tmpfs
Read-Write
/mnt/obb: Device: tmpfs
File System: tmpfs
Read-Write
/mnt/media_rw: Device: tmpfs
File System: tmpfs
Read-Write
/mnt/media_rw/sdcard1: Device: /dev/block/vold/179:129
File System: vfat
Read-Write
/storage/usbotg: Device: tmpfs
File System: tmpfs
Read-Write
/storage/emulated: Device: tmpfs
File System: tmpfs
Read-Write
/storage/emulated: Device: tmpfs
File System: tmpfs
Read-Write
/system: Device: /dev/block/platform/mtk-msdc.0/by-name/system
File System: ext4
Read-Only
/data: Device: /dev/block/platform/mtk-msdc.0/by-name/userdata
File System: ext4
Read-Write
/cache: Device: /dev/block/platform/mtk-msdc.0/by-name/cache
File System: ext4
Read-Write
/protect_f: Device: /dev/block/platform/mtk-msdc.0/by-name/protect1
File System: ext4
Read-Write
/protect_s: Device: /dev/block/platform/mtk-msdc.0/by-name/protect2
File System: ext4
Read-Write
/nvdata: Device: /dev/block/platform/mtk-msdc.0/by-name/nvdata
File System: ext4
Read-Write
/mnt/cd-rom: Device: /dev/block/loop0
File System: iso9660
Read-Only
/mnt/shell/emulated: Device: /dev/fuse
File System: fuse
Read-Write
/storage/sdcard1: Device: /dev/fuse
File System: fuse
Read-Write
/storage/emulated/0: Device: /dev/fuse
File System: fuse
Read-Write
/storage/emulated/legacy: Device: /dev/fuse
File System: fuse
Read-Write
/mnt/shell/emulated: Device: tmpfs
File System: tmpfs
Read-Write

<<< System Files >>>

Buddy Info: /proc/buddyinfo
Build Properties: /system/build.prop
Character & Block Devices: /proc/devices
Command Line: /proc/cmdline
CPU Information: /proc/cpuinfo
Execution Domains: /proc/execdomains
File Systems: /proc/filesystems
Frame Buffer Devices: /proc/fb
GPS Config: /system/etc/gps.conf
Hosts: /system/etc/hosts
Interrupts: /proc/interrupts
Input Devices: /proc/bus/input/devices
I/O Ports: /proc/ioports
Kernel Version: /proc/version
Load Average: /proc/loadavg
Locked Files: /proc/locks
Memory Information: /proc/meminfo
Memory Map: /proc/iomem
Misc Drivers: /proc/misc
Partitions: /proc/partitions
Statistics: /proc/stat
Swap Spaces: /proc/swaps

Will Marshmallow and Doze Mode fix the battery problems Lollipop brought to the M8?

My HTC One M8 was running fine before the Lollipop update back in January. KitKat had great battery life (I had at least 30% when I got to bed) and never had lag. Since then I have to charge it a bit during the afternoon if I dont want to risk running out of battery and I have occacional lag which goes away when I clean the recent apps. Tried cache cleaning, did 2 factory resets, a couple of custom roms 5.1 based and even flashed the RUU file to bring it back to pristine state, to no avail since Android OS and Android Kernel are to 2 most battery draining app I have (checked on Gsam battery monitor). SOT is much worse also, I only get 3 - 3,5h maximum.
Do you guys believe Google and HTC are able to bring the battery life of this otherwise great smartphone to how it was before LolliFLOP?

Cheers