I've been following this forum re 32.3.A.0.376. There are many users commenting on sound issues, etc. However, many have rooted their phones and done modifications. I use my phone unmodified and would like to know if the various issues exist on the standard phone. Thanks.
rebecker said:
I've been following this forum re 32.3.A.0.376. There are many users commenting on sound issues, etc. However, many have rooted their phones and done modifications. I use my phone unmodified and would like to know if the various issues exist on the standard phone. Thanks.
Click to expand...
Click to collapse
I haven't tried re-locking my bootloader so I do not know whether a locked bootloader would yield higher external sound volume. My *guess* is it won't.
I have however tried both with unmodified kernel and modified (RootKernel 5.20 with DRM fix) kernel and in both cases I experience a significantly lower volume from both Spotify and YouTube compared to Marshmallow.
I have been running unmodified stock since launch for the first time on an android, and flashed AU .376 this weekend, with thoughts that if it did not fix this sluggish poor-batteried clump, I would switch to something else like Huaweii.
So far on day 2.5 I experience a much more smooth phone with prolonged battery life, albeit not as much as it had on MM. I've not experienced the sound bugs with low volume, although when I sitting down to switch the various notification sounds while wearing earplugs, it suddenly started playing from the phone speaker.
So far I am happy enough that I will keep the phone for now, with no plans of rooting or unlocking it as of now.
Is the AU .376 legit to donwload? I mean, would my warranty be void if i download it before the official release?
non-root user
AndreasElia said:
Is the AU .376 legit to donwload? I mean, would my warranty be void if i download it before the official release?
non-root user
Click to expand...
Click to collapse
It might void the warranty, ref http://talk.sonymobile.com/t5/Android-development/using-flashtool-void-warranty/td-p/924234. Although for me in Norway this might fall in a gray zone as we have some good consumer protection laws in norway.
I might reflash it without any wipe when the proper release is out just in case I am to sell it at any point.
Been using the new build stock since yesterday and noticed better battery life. I'm using a US stock E5803 on 32.3.A.0.376 Malaysia and I've disabled a bunch of extra apps. Here are a few pros/cons that I've seen so far.
Pros: Better battery life, improved camera post processing (white/colour balancing, sharpening), improved camera speed with video recording/photos, Improved ram management, LTE does not drop anymore, phone heats up a tiny bit less than before, fingerprint scanner works with no issues, better stamina mode options, and phone sleeps like a baby with no noticeable battery drain.
Cons: Lower volume on 3rd party apps using phone speaker (spotify, etc) and no issues so far with Anker bluetooth speaker.
Untested: Bluetooth with car stereo, call quality.
Im using Nougat since last week and im downloading MM back again. Im not satisfied with nougat. In my opinion the performance is worse than on previous release.
I installed the previous release (.372) via OTA, so far it's good but battery is a bit less.
My question here is, if .376 will be pushed to my phone via OTA or I will have to flash it manually.
Currently I'm waiting for OTA update and checking daily, so fsr no luck :/
Sent from my E5803 using Tapatalk
Way better than any Marshmallow firmware I ever used on my phone. ZERO PROBLEMS! No sound issues, no notification issues. I'm using .376 w/o root to test if battery life is longer than when using root. Anybody noticed differences in battery life between root and non-root?
Cerhio said:
Way better than any Marshmallow firmware I ever used on my phone. ZERO PROBLEMS! No sound issues, no notification issues. I'm using .376 w/o root to test if battery life is longer than when using root. Anybody noticed differences in battery life between root and non-root?
Click to expand...
Click to collapse
How did you install it without root? Tried to do it with Xperia Flash and it give me a locked phone notification.
Also, is there a way to back up the current firmware before installing .376?
Thanks
AndreasElia said:
How did you install it without root? Tried to do it with Xperia Flash and it give me a locked phone notification.
Also, is there a way to back up the current firmware before installing .376?
Thanks
Click to expand...
Click to collapse
Install the same way like with root. Use latest version of Flashtool to download and install new firmware.
I assume you have a locked bootloader which means no nandroid backup via TWRP, right?
You could try to backup via adb. Google for adb backup. You can also use a GUI called Holo for it if you not familiar with command prompts.
However from what i heard it's not as good as a nandroid backup and a few things can be missed in the backup.
But if you don't like nougat, you can also just flash back an old firmware via flashtool.
So, I woke up today to see OTA notification for .376 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"
}
It was only 85mb download, so I downloaded it via mobile data and installed it. I took screenshots of before and after update, take a look.
Currently running with no issues, and will post update for battery time and performance.
Sent from my E5803 using Tapatalk
Just updated it to Nougat, no root, no unlocked bootloader. Everything is fine, volume is ok I guess (seems high both with music and with ringtones) very fluid. Camera is maybe a bit improved (quality is almost the same) but apart from the countdown before the selfie shooting, there is the possibility to set the Iso up to 3200 when using 20/23 mpx in manual mode (don't remember if it was in MM too); seems a little faster when taking the picture. Still no control over shutter speed in the stock camera, STILL limited to 1/10 in the manual camera app (damn), S T I L L no capability to shoot Raw. Overheating is still there, but not much a problem (at least in winter )
Good update, not really different after all but little improvements are there (damn Sony is too lazy on the camera though)
Gewiz said:
Install the same way like with root. Use latest version of Flashtool to download and install new firmware.
I assume you have a locked bootloader which means no nandroid backup via TWRP, right?
You could try to backup via adb. Google for adb backup. You can also use a GUI called Holo for it if you not familiar with command prompts.
However from what i heard it's not as good as a nandroid backup and a few things can be missed in the backup.
But if you don't like nougat, you can also just flash back an old firmware via flashtool.
Click to expand...
Click to collapse
Good morning
Did everything you suggested without any trouble - used Android Studio for the back up and then download Xperia flashtool (Emma).
Unfortunately when reaching the point that i had to flash my mob with the new system, 'Emma' cannot proceed due to my phone been locked. Knew that it was too easy to finish everything fast and successfully Guess i ll have to wait
Anyone here with a nougat update in UK?
AndreasElia said:
Good morning
Did everything you suggested without any trouble - used Android Studio for the back up and then download Xperia flashtool (Emma).
Unfortunately when reaching the point that i had to flash my mob with the new system, 'Emma' cannot proceed due to my phone been locked. Knew that it was too easy to finish everything fast and successfully Guess i ll have to wait
Click to expand...
Click to collapse
Nearly pal, i don't know if it should work with latest version of emma to. Never used before. Usually if flashtool is mentioned here, we mean another tool. Try it with this one(latest version):
http://www.flashtool.net/downloads.php
I updated to the Vodafone UK firmware through Flashtool (I live in Norway) and I noticed they've fixed the white noise issues with sound through mini jack, which is amazing
However, it seems that my unlocked bootloader is causing some issues with the fingerprint scanner, Youtube, mobile connections etc. Think I'm gonna root, as the thermal engine still seems to be kind of meh :/. Also, no stutters so far, even when using Chrome and Word at the same time plus Messenger bubbles
It's been about 27 hours since the update and I'm loving it. No volume issues at all and battery life seems at least comparable to MM (my use was abnormal for the past day, so I'll report back if I notice drastically different battery life over time). Only thing I did after updating was cleared the cache. One small warning, though: my update took a LONG time... nearly an hour. I didn't expect that, and it had me worried that something went wrong, but it was fine.
jackpotbox said:
Anyone here with a nougat update in UK?
Click to expand...
Click to collapse
Yes, got mine on O2. Not convinced on battery life is better but overall looking it
Sent from my E5823 using Tapatalk
Gewiz said:
Nearly pal, i don't know if it should work with latest version of emma to. Never used before. Usually if flashtool is mentioned here, we mean another tool. Try it with this one(latest version):
http://www.flashtool.net/downloads.php
Click to expand...
Click to collapse
Tried again last night, installing eveything right from the beginning. this time is seemed to be much easier and faster and at last updated to Nougat successfully! Only thing noticed until now is the smoother fingerprint sensor and i really enjoy the clear all and window switch commands.
Thanks for all the help, have a nice day
Andreas
Related
I'm trying to get to the bottom of this freezing issue affecting many users where the NS will not wake up from standby and requires a battery pull to rectify. As samsung or Google seem reluctant to do anything about this (or even acknowledge the problem) I wonder if we can narrow it down to what is causing the issue? If you are affected by this you will know what I am referring to without the need for further explanation.
If your NS is freezing, please copy and paste the following with your answers:
Length of ownership:
How long ago did freezing start:
Current software version:
Did you notice freezing before update:
Update method (Manual / OTA):
i9020 (SAMOLED) or i9023 (SCLCD):
Hopefully a colleciton of responses to the above might start to show a pattern so if as many of you can replay with your answers as possible we stand a better chance of narrowing this down.
note to mods: please don't move this to Q&A as with my other thread on the matter as this is not a question, more an attempt to gain more info. Thanks
stock ROM
ownership: since it came out in december
freezing: what freeze?
Did not notice any freeze, not before, not after
method OTA
i9020
same answer for custom ROMs, except for the OTA part
Length of Ownership: Since Feb 25, 2011
Freezing: yes, at random times have not pinpointed what/why (necessitating a battery pull every single time )
Version: 2.3.1 OTA
Noticed it shortly after the update (at least twice a week) but NOT before (the OTA update)
Edit: Stock
SAMOLED
Sent from either my Nexus S, N1 or telepathically using two tin cans and some string.
AllGamer are you on 2.3.3 or something else?
I'm hearing the issue effects all 2.3.x versions ... was there anything before this or is that what the NS released with - I can't recall from when I had mine at launch?
Hi,
My responses inline.
Length of ownership: 2 months
How long ago did freezing start: 1hr
Current software version: 233
Did you notice freezing before update: no
Update method (Manual / OTA): manual, on custom rom now
i9020 (SAMOLED) or i9023 (SCLCD): i9020
1 thing I noticed is that my freezing was not rectified even after puling the battery out, the only thing it responded was changing the sim card, then it took me phone registration screen and phone was fine after this even with old sim. Never encountered this problem after that.
Sent from my Nexus S using XDA App
Length of ownership: Jan 2011
How long ago did freezing start: Since Jan 2011 randomly
Current software version: 2.3.3 Cyanogen 7.0 RC4 with netarchy 1.3.0.1 CFS
Did you notice freezing before update: Yes
Update method (Manual / OTA): Manual , using custom roms
i9020 (SAMOLED) or i9023 (SCLCD): i9020
Additional comments : Personally, I think it has to do with both BLN and noLED apps and how the kernels are responding to them. BLN pro caused me more problems with the freezing as opposed to noLED so i moved back to noLED.
For me, the freezing is about once every 2-3 days and usually if i flash a non-netarchy CFS kernel. Once i'm on netarchy, it freezes less frequently. Maybe once a week and only if i overclock to 1.3 and charging at the same time. (Possible overheating problem?)
Hope my comments helps in your research. Thanks for doing this
xspyda said:
AllGamer are you on 2.3.3 or something else?
I'm hearing the issue effects all 2.3.x versions ... was there anything before this or is that what the NS released with - I can't recall from when I had mine at launch?
Click to expand...
Click to collapse
yes 2.3.3
have you guys tried wipe data + wipe cache?
AllGamer said:
yes 2.3.3
have you guys tried wipe data + wipe cache?
Click to expand...
Click to collapse
I'm pretty sure that has been tried by many experiencing the problem to no avail. Seems that whatever causes the issue results in a hardware fault that neither Google or Samsung are willing to acknowledge.
I'd LOVE to hear of someone having actually fixed this problem.
Length of ownership: 4 months
How long ago did freezing start: after 6 weeks
Current software version: 2.3|2.3.1|2.3.2|
Did you notice freezing before update: not sure
Update method (Manual / OTA): OTA
i9020 (SAMOLED) or i9023 (SCLCD): i9020
I bought my phone on 12/31/2010 with FW 2.3. The phone worked fine for about 6 weeks, maybe a bit less. At first I've noticed random reboot or freeze, but very very few of them. then it gradually escalated to unusable phone.
Quick summary of Samsung's service.
1.) I've send the phone for the 1st time - Samsung claims no issues found, restores phone to FW 2.3 and mails the phone back. I open a package a week later and cannot boot up the phone, the phone only displayed the while "Google" writing and a lock-pad on the bottom of the screen. After many and many retries I was able to boot up the phone but then it froze again.
2.) I've send the phone for the 2nd time - Samsung keeps the phone for a week and claims no issues found, restores phone to FW 2.3 and mails the phone back. I pick up my phone, put in my battery and the phone freezes within 5-10 minutes. So I mail it back again.
3.) I've send the phone for the 3rd time - They are evaluating I guess. I've called and some woman picked up (2nd level support here in US as i requested) very unfriendly and basically said to my face "we're evaluating your phone and you'll get your phone when you'll get it" and that she cannot do anything about this.
i will never buy a Samsung phone again.
They always reset to FW 2.3 which the phone still freezes on. Some Google guy claimed for a while that they are working on this but it seems doubtful.
here is the link:
http://www.google.com/support/forum/p/Google+Mobile/thread?hl=en&tid=44db6d8e31129d4c
Wow, nasty experience with Samsung by the sound of it and from what. I've read this is all too common.
I'd personally be quite satisfied with the Nexus S but I don't think I could use one daily knowing that I could run into this problem at any time with no way to resolve and be at the mercy of Samsung who seemingly don't give a damn.
From the content of this thread I'm not seeeing any pattern as I'd hoped to. Shame, I really thought we might just learn something from this and sadly the only thing I am learning is to steer clear of Samsung.
Of course this issue doesn't affect every NS owner out there but is seems those tthat are unlucky enough to experience issues are left out in the cold.
Still interested to hear of other users' experiences. Thanks to all that have contributed so far, keep your reports coming guys.
Length of ownership: Since the week of the US release
How long ago did freezing start: Roughly 2-3 weeks ago.
Current software version: 2.3.3
Did you notice freezing before update: No
Update method (Manual / OTA): OTA
i9020 (SAMOLED) or i9023 (SCLCD): i9020
I first noticed my phone randomly crash, reboot and then go to the recovery screen with the exclamation mark in the triangle. It was just sitting there when I saw it happen. Pulled the battery and booted fine.
The next day it crashed, rebooted and went into safe mode... which I had never even seen or used before. In safe mode it crashed again and rebooted and went into a crash > safe mode boot loop until I pulled the battery. Worked fine for a while and then the freezes started happening. I would go to power on the screen and nothing would happen. Pulled the batter and then it worked.
Sometimes it would freeze and the screen was just very dimly lit... sometimes I would see just the menu "buttons" lit. either way a battery pull was the only solution. Started happening more frequently... though again not if I was plugged in.
Tried full wipes a couple times including storage... even with just the standard apps installed it still would eventually freeze.
So using my Nexus One for now... I'm really not in a hurry to deal with Samsung so I've been putting off calling them. But I miss my NS in my hands...
bought in USA Bestbuy
Length of ownership: since January 2011, 4 months
How long ago did freezing start: since end of February after OTA update
Current software version: 2.3.1
Did you notice freezing before update: NO, Nexus S was working for 2 months without freezing
Update method (Manual / OTA): OTA from 2.3 to 2.3.1
i9020 (SAMOLED) or i9023 (SCLCD): i9020
My phone randomly crashed, reboot and then went to the recovery screen with the exclamation mark in the triangle.
I've tried factory reset, clear cache, format SDcard,
I've tried flash 2.3.1, 2.3.3 with Odin
I've tried nandroid recovery 2.3.3 , 2.3.1
no idea why and how to solve it
----
I just want to add that I didn't install any software and I didn't change any settings. I've just let the phone in default setting after flashing or recovering (nandroid recovery). I didn't set any google account or set wifi. And also I didn't insert any SIM card and and bootloader is locked. Still is freezing.
xspyda: yes, I tested without SIM card. Right now I haven't been using Nexus S for 2 months it is not possible to use him.
-----
edit2:
I played with this phone again, I did nandroid recovery 2.3.1 ( It is pity that we don't have nandroid backup of 2.3 ) maybe could help.
And after 3-6 restarts he got stuck in this screen and only remove battery helped.
{
"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"
}
Maybe it helps to move forward this issue.
pphmmr said:
I've tried factory reset, clear cache, format SDcard,
I've tried flash 2.3.1, 2.3.3 with Odin
I've tried nandroid recovery 2.3.3 , 2.3.1
no idea why and how to solve it
Click to expand...
Click to collapse
This may be clutching at straws but have you tried remving the sim card also? In fact, does the freezing still occur without a sim card inserted - anyone?
I could be wrong but it appears to me that the majority of people experiencing freezing issues are doing so only after performing an update, whether that be manual or OTA. Could there be something wrong with the way Google are pushing out these updates I wonder?
I think we need more reports like these already collected and then we need to look at the possibility of passing this information on to the relevant area for investigation (I know, it's a long shot).
Thanks for all reports so far, would be great if we can keep this thead going / updated and gather as many instances of this as possible.
Mods: Any chance of making this a sticky so as to collect as much info as possible?
Please keep your reports coming!
Length of ownership: since january
How long ago did freezing start: about a month or so ago
Current software version: 2.3.2 with voodoo kernel stock rom
Did you notice freezing before update: nope
Update method (Manual / OTA): manual
i9020 (SAMOLED) or i9023 (SCLCD): i9020
Sent from my Nexus S using XDA App
Lately my phone freezes randomly. Yesterday I got a phone call, went to plug in the head set and the phone wouldn't wake up for me to turn off speaker phone, and then it just rebooted. I'm considering just wiping my phone and starting fresh. I'm starting to lose my patience with this crap
Sent from my Nexus S using XDA App
Thanks for the edit / update pphmmr. From what have learned so far there is no way for us to fix this when the freezing occurs.
mylexon20s - are you talking about the same freezing issue that is described in this thread, the known issue affecting many? If so, can you please fill in the template at the beginning as other users have so we can continue to seek a pattern to this fault please?
There is new update 2.3.4 out. Does it help to solve our problem? Has anyone tried?
pphmmr said:
There is new update 2.3.4 out. Does it help to solve our problem? Has anyone tried?
Click to expand...
Click to collapse
Interested to know this too. Anyone with the problem tried the update yet?
Perfect. Done. Now it is my nexus s OK. finally.
I've just updated to 2.3.4.
I was testing it for 3 hours and still ok.
edit1:
still I can wake SNS up after 8 hours and also after 24 hrs. still OK.
How to solve the problem:
I upgraded to GRI49 ver. 2.3.3 by this zip
I copied zip file into SNS sdcard and follow next steps:
1. turn off
1. turn on + hold volume up
3. select RECOVERY
4. if you see exclamation mark in the triangle press and hold power button and after 2 sec. press volume up as well
5, choose update from sdcard
6. find zip file
then I updated again but to ver. 2.3.4 by this zip with same procedure
And then I did factory reset and I wiped cache as well.
If you have 2.3.3 GrI40 you can skip 1st procedure and just update to 2.3.4 directly.
Great, keep us posted please...
So I installed one of the 4.2.2 ROMs on one of my N7s and had noticed a very slight screen flicker that occurs once in a while like the brightness is trying to adjust up and down quickly. It is very slight and hard to notice unless your using something with a light colored background. Out of curiousity I installed a few different 4.2.2 ROMs and a variety of kernels and the issue is always present. To test this further I tried the same things on my other N7 and end up with the same results. To test it even more and eliminate the possibility of it being something related to the devices being 3-5 months old I picked up a brand new 32gb N7 this morning, unlocked it, rooted it and installed some 4.2.2 ROMs and a bunch of different kernels and the same thing happens regardless of the combination of ROM and/or kernel. Has anyone else noticed this at all?
airmaxx23 said:
So I installed one of the 4.2.2 ROMs on one of my N7s and had noticed a very slight screen flicker that occurs once in a while like the brightness is trying to adjust up and down quickly. It is very slight and hard to notice unless your using something with a light colored background. Out of curiousity I installed a few different 4.2.2 ROMs and a variety of kernels and the issue is always present. To test this further I tried the same things on my other N7 and end up with the same results. To test it even more and eliminate the possibility of it being something related to the devices being 3-5 months old I picked up a brand new 32gb N7 this morning, unlocked it, rooted it and installed some 4.2.2 ROMs and a bunch of different kernels and the same thing happens regardless of the combination of ROM and/or kernel. Has anyone else noticed this at all?
Click to expand...
Click to collapse
Yes... long since known and extensively reported on...
http://forum.xda-developers.com/showthread.php?t=1740385
I use this solution...
http://forum.xda-developers.com/showthread.php?p=38207942#post38207942
----
There is an ad nauseum sequence of reports here, to Google, on this tiresome issue...
http://code.google.com/p/android/issues/detail?id=39841
Rgrds,
Ged.
GedBlake said:
Yes... long since known and extensively reported on...
http://forum.xda-developers.com/showthread.php?t=1740385
I use this solution...
http://forum.xda-developers.com/showthread.php?p=38207942#post38207942
----
There is an ad nauseum sequence of reports here, to Google, on this tiresome issue...
http://code.google.com/p/android/issues/detail?id=39841
Rgrds,
Ged.
Click to expand...
Click to collapse
I forgot to mention that this is with the auto brightness turned off.
airmaxx23 said:
I forgot to mention that this is with the auto brightness turned off.
Click to expand...
Click to collapse
Yes... I know...
I am alluding to PRISM/SmartDimmer AS WELL as auto-brightness.
Read my second link in detail.
Rgrds,
Ged.
GedBlake said:
Yes... I know...
I am alluding to PRISM/SmartDimmer AS WELL as auto-brightness.
Read my second link in detail.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks, this has been driving me crazy for 3 days. I searched for 4.2.2 flicker but there wasn't much for results.
airmaxx23 said:
So I installed one of the 4.2.2 ROMs on one of my N7s and had noticed a very slight screen flicker that occurs once in a while like the brightness is trying to adjust up and down quickly. It is very slight and hard to notice unless your using something with a light colored background. Out of curiousity I installed a few different 4.2.2 ROMs and a variety of kernels and the issue is always present. To test this further I tried the same things on my other N7 and end up with the same results. To test it even more and eliminate the possibility of it being something related to the devices being 3-5 months old I picked up a brand new 32gb N7 this morning, unlocked it, rooted it and installed some 4.2.2 ROMs and a bunch of different kernels and the same thing happens regardless of the combination of ROM and/or kernel. Has anyone else noticed this at all?
Click to expand...
Click to collapse
I have noticed this issue as well. I didnt see it before 4.2.2 (im reading books on the tablet so I should have seen it before I think). The flicker is both with and without auto-brightness turned on but it is only noticeable on low brightness level. And because I havent seen it before 4.2.2 and you have tried it on three different devices it feels like it is software and not hardware related, at least we can hope so! Have you tried the suggested solution above and did it help you?
GedBlake said:
Yes... long since known and extensively reported on...
http://forum.xda-developers.com/showthread.php?t=1740385
I use this solution...
http://forum.xda-developers.com/showthread.php?p=38207942#post38207942
----
There is an ad nauseum sequence of reports here, to Google, on this tiresome issue...
http://code.google.com/p/android/issues/detail?id=39841
Rgrds,
Ged.
Click to expand...
Click to collapse
Does your suggestion work the same way as the app "NVidia Tegra PRISM Toggle" from playstore?
jocke_lulle said:
I have noticed this issue as well. I didnt see it before 4.2.2 (im reading books on the tablet so I should have seen it before I think). The flicker is both with and without auto-brightness turned on but it is only noticeable on low brightness level. And because I havent seen it before 4.2.2 and you have tried it on three different devices it feels like it is software and not hardware related, at least we can hope so! Have you tried the suggested solution above and did it help you?
Does your suggestion work the same way as the app "NVidia Tegra PRISM Toggle" from playstore?
Click to expand...
Click to collapse
As I understand it... Yes, that is correct... and the same setting can also be accomplished via TricksterMod (although it never seems to survive a reboot).
Trickster MOD Kernel Settings - http://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en
Rgrds,
Ged.
jocke_lulle said:
I have noticed this issue as well. I didnt see it before 4.2.2 (im reading books on the tablet so I should have seen it before I think). The flicker is both with and without auto-brightness turned on but it is only noticeable on low brightness level. And because I havent seen it before 4.2.2 and you have tried it on three different devices it feels like it is software and not hardware related, at least we can hope so! Have you tried the suggested solution above and did it help you?
Does your suggestion work the same way as the app "NVidia Tegra PRISM Toggle" from playstore?
Click to expand...
Click to collapse
The fix posted above seemed to take care of the problem on all of the devices. I use S Manager for a few other scripts and just made a new one for this and have it set on boot. I actually placed a small widget on one of my home screens so I can just press if after boot up to make sure it is activated.
airmaxx23 said:
The fix posted above seemed to take care of the problem on all of the devices. I use S Manager for a few other scripts and just made a new one for this and have it set on boot. I actually placed a small widget on one of my home screens so I can just press if after boot up to make sure it is activated.
Click to expand...
Click to collapse
Does this mean that something did change in 4.2.2 compared to 4.2.1 since neither one of us had the problem before the update?
airmaxx23 said:
The fix posted above seemed to take care of the problem on all of the devices. I use S Manager for a few other scripts and just made a new one for this and have it set on boot. I actually placed a small widget on one of my home screens so I can just press if after boot up to make sure it is activated.
Click to expand...
Click to collapse
That's an interesting way of doing it.... it never occurred to me to set up a widget.
I just rely on the 'toast' message at boot, Smanager has been granted superuser permissions for an interactive shell... I know the script has been executed then.
Occasionally, I might use a filemanager with root access to examine...
Code:
/sys/devices/tegradc.0/smartdimmer/enable
...to ensure the value is indeed null (ie, 0, disabled and not 1, enabled)
Your widget idea guarantees the execution of the script... just by touching on it.
-----
And I always know when it hasn't worked... the screen brightness fluctuates like a cheap 40 watt lightbulb! (maybe I'm just sensitive to such things - my friends don't seem to see it).
Rgrds,
Ged.
---------- Post added at 03:19 PM ---------- Previous post was at 02:48 PM ----------
jocke_lulle said:
Does this mean that something did change in 4.2.2 compared to 4.2.1 since neither one of us had the problem before the update?
Click to expand...
Click to collapse
Hi, jocke_lulle...
Well, I can't speak for others, but this issue has been a constant bugbear of mine, ever since 4.2 was rolled out in October/November of last year. I never had this problem with 4.1.x
...probably because 4.1 doesn't employ SmartDimmer... It just used AutoBrightness.
Why Google/Asus/Nvidia (SmartDimmer is their pet project) or which ever overpaid CEO thought implementing two wholly distinct and disparate battery saving schemes was a good idea, I'll never know.
Quite frankly, it's a dog's breakfast... and even a hungry dog would be loathe to eat it!
Rgrds,
Ged.
That's an interesting way of doing it.... it never occurred to me to set up a widget.
I just rely on the 'toast' message at boot, Smanager has been granted superuser permissions for an interactive shell... I know the script has been executed then.
[/QUOTE]
I use a couple different widgets for GPU OCing as well, it's quick and that way I know it's actually being executed. I also have the toast notifications for SuperSU turned off, here is my left home screen with the few script widgets.
{
"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"
}
I did root and install trickstermod. Even if i disable smartdimmer i can see that the screenlight is fluctuating. It does it even with autobrightness off. I also tried the script posted here but same thing.
Gf noticed it on her new n7. I didn't notice it on mine until I installed today's cm nightly. Reverted back to previous nightly and I still noticed it. After reading these threads, ill always notice it if I don't fix it.
It's just an annoyance, right? If gf (her n7 isn't rooted yet) doesn't mind it, it should be fine to leave it?
Sent from my LG-VM670 using Tapatalk 2
{
"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"
}
https://plus.google.com/+DavidSchuster/posts/6h8ahhkY9GQ
https://motorola-global-portal.cust...prod_answer_detail/a_id/105508/p/30,6720,9277
Now that motorola dropped the bomb and even the update page it's public, I want to know how you guys feel with the update, please don't ask for off topic matters, like unrooting or going back to stock.
What do you think of lollipop?
What do you think about motorola?
Are you getting better battery life?
For me I had better battery on lollipop than kitkat
Did you get the update to 5.1 on your turbo as well? How is the camera shutter speed after the update?
Can one of you who has the update please extract the system.img so we can get to work on trying to create a rooted build? This is being requested by http://forum.xda-developers.com/showthread.php?t=3147455
If you don't know how to do so I'm sure Computerfreek can assist. Some of us are unable (such as myself) to take the update so please help. That is what this community is all about.
JakeDHS07 said:
Can one of you who has the update please extract the system.img so we can get to work on trying to create a rooted build? This is being requested by http://forum.xda-developers.com/showthread.php?t=3147455
If you don't know how to do so I'm sure Computerfreek can assist. Some of us are unable (such as myself) to take the update so please help. That is what this community is all about.
Click to expand...
Click to collapse
Pm'd you the link from root junky with the ota. I'm not sure if I'm allowed to post it here so I'll just keep the mess in pm.
No big reason to hate it much at all. Loving the pull-down menu! Too much white, though.
Sent from my XT1254 using XDA Free mobile app
I updated with the rootjunky soak after checking its md5. Had the phone plugged in for the duration and let it update as I was going to bed. Woke up to a fully functional Lollipop, and haven't had any of the issues others are mentioning. Never rooted.
I didn't remember they stopped letting you change mobile data on/off automatically. I have horrible reception at work and like to turn off mobile data to save battery, and now I'll have to remember to manually change it. Luckily it's only four steps -_- (two-finger swipe down to get to quick settings, click on the cell icon, click the toggle on the top right, accept the confirmation dialog box). Three steps to turn it on - there's no confirmation.
Similar issue with location services: if you turn it off/on through the quick settings, it automatically changes it to High Accuracy instead of the previous setting (like Battery Saving). Luckily, Google changed the way locations are handled last year and this shouldn't be as big of an impact on battery as it had been previously.
The volume modes are going to be a headache to explain to my parents who also have Turbos. Glad I updated before they do...
JakeDHS07 said:
Can one of you who has the update please extract the system.img so we can get to work on trying to create a rooted build? This is being requested by http://forum.xda-developers.com/showthread.php?t=3147455
If you don't know how to do so I'm sure Computerfreek can assist. Some of us are unable (such as myself) to take the update so please help. That is what this community is all about.
Click to expand...
Click to collapse
We have to wait for Verizon or Moto release the full firmware and then you can patch it, I'm waiting for that too, for the firmware list
I absolutely love the new 5.1 Lolipop. Seems much smoother, faster, better overall appearance. Can't wait to really dig into this and see how the battery life is compared to stock 4.4.4
Overall: huge fan and love it!!
I've been very happy with 5.1 on the Turbo. Honestly, the Turbo seems to run 5.1 much better than my Nexus 9. I haven't had any major problems. I did, however, run into one odd issue that might just be a coincidence. I noticed after updating that I wasn't able to connect to my Verizon Network Extender, even though I still had Advanced Calling disabled (if Advanced Calling is on, and you have an LTE connection, you'll use that over a Network Extender). The Network Extender worked fine with other VZW devices. This went on for about a day, and then it magically started working again.
Forgive me if I over looked it, but I noticed now when I turn my phone volume down to silence it it just goes on vibrate rather than just silent with no vibrate. Did that feature disappear? I hate to be picky but I like to have it on silent while at work and I can't stand having it on vibrate.
Sent from my Droid Turbo using XDA
Did an OTA update a few hours ago. Didn't bother with a factory reset and so far no issues that I am aware of. Silky smooth.
streebs87 said:
Forgive me if I over looked it, but I noticed now when I turn my phone volume down to silence it it just goes on vibrate rather than just silent with no vibrate. Did that feature disappear? I hate to be picky but I like to have it on silent while at work and I can't stand having it on vibrate.
Sent from my Droid Turbo using XDA
Click to expand...
Click to collapse
press the volume key and click on the bell on the left, now you are on vibrate
I took the OTA, did a factory reset, and set it up as a new phone; not restoring any backups. It's installing lots of app updates right now, so I haven't done much with it, but I haven't noticed any new bugs. Unfortunately, Lollipop hasn't fixed the wi-fi bug where my phone continually disconnects and reconnects to my wi-fi. It may just be a problem with certain routers (mine is a Belkin N750 DB), but I've got the latest available firmware on my router, too, and everything else works fine with it. I think it's time to see if I can get a warranty replacement.
I'm liking the karate chop light feature!
RichSPK said:
I took the OTA, did a factory reset, and set it up as a new phone; not restoring any backups. It's installing lots of app updates right now, so I haven't done much with it, but I haven't noticed any new bugs. Unfortunately, Lollipop hasn't fixed the wi-fi bug where my phone continually disconnects and reconnects to my wi-fi. It may just be a problem with certain routers (mine is a Belkin N750 DB), but I've got the latest available firmware on my router, too, and everything else works fine with it. I think it's time to see if I can get a warranty replacement.
Click to expand...
Click to collapse
I had that router for 7 or 8 years. towards the 6 year mark - it started dropping all my devices randomly so I bought a Cisco AC router and nothing has dropped off once unless I rebooted it or someone "accidently" unplugs it. In my case it was my router that was dropping my client devices off and this was before I bought my DT.
Jaocagomez said:
press the volume key and click on the bell on the left, now you are on vibrate
Click to expand...
Click to collapse
Thank you, but I just want a silence feature without the vibration. Any way to do that?
Sent from my Droid Turbo using XDA
streebs87 said:
Thank you, but I just want a silence feature without the vibration. Any way to do that?
Sent from my Droid Turbo using XDA
Click to expand...
Click to collapse
pull all the lever volume down
The update fixed the main problem I had with the phone. I play music from my phone to my car's system (Ford Sync) through bluetooth, and it used to not be able to start playback again after returning to my car without me having to manually toggle bluetooth off & on to reconnect it. Now it starts up right where it left off without me having to mess with it, like my old HTC phone did.
I haven't had much time to explore the update yet, but so far so good. I did OTA with no factory reset and everything seems fine.
streebs87 said:
Thank you, but I just want a silence feature without the vibration. Any way to do that?
Sent from my Droid Turbo using XDA
Click to expand...
Click to collapse
Try the app "SoundHUD" (haven't myself, but supposedly gives a silent mode).
GeodudeFFP said:
Try the app "SoundHUD" (haven't myself, but supposedly gives a silent mode).
Click to expand...
Click to collapse
Thanks, I'll give that a try.
Sent from my Droid Turbo using XDA
Hi Guys, here are the Download Link for official Lineage OS for m7_u, m7_ul and m7_vzw
have fun regards, and Thanks to the Guys from Lineage.
Edit:
Now there is no official Update for two weeks because they have no Maintainer for the device so they dropped support for our m7. As long as there is no friendly guy who starts maintaining a 4 Year old device it looks bad for official updates. And that propably will make some problems for other Custom Roms or Kernels which are based on LineageOS in the future. But no matter we have great devs here on XDA and out there, they work hard to bring the latest Software to our m7 (SlimRoms, XenonHD, RR, AICP all those still official support the m7). And we have some other great devs here which bring us other unofficial Roms with very good results regarding to Android N.
end of edit
Website: https://www.lineageos.org/
Wiki: https://wiki.lineageos.org/devices/m7
Downloads: (m7_u, m7_ul) https://download.lineageos.org/m7
(m7_vzw) https://download.lineageos.org/m7vzw
FTP: (m7_u, m7_ul) https://lineageos.mirrorhub.io/full/m7/
(m7_vzw) https://lineageos.mirrorhub.io/full/m7vzw/
Or here: https://download.lineageos.org/m7
Is more user friendly...
oh nice
Is the GSM version UL compatible? I'd like to retain LTE on my 801s
warnabrotha said:
Is the GSM version UL compatible? I'd like to retain LTE on my 801s
Click to expand...
Click to collapse
LTE/4G should work with the GSM Version.
What about issues?
Here is my experience with 14.1.20170130 nightly. I have been using it since yesterday morning and I am astonished by how well it works. LTE, GPS, WiFi... everything works. Since yesterday, I made a few phone calls, used GPS navigation, browsed the web, installed a few apps and even played Ingress (which is kinda resource hungry) for a couple of hours. The system is rock solid (could not say that about CM 13) and even with storage encryption enabled the phone seems to run even faster than with the stock HTC ROM.
Great job! How can I buy you guys at LineageOS a beer?
{
"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"
}
Hydracio said:
Here is my experience with 14.1.20170130 nightly. I have been using it since yesterday morning and I am astonished by how well it works. LTE, GPS, WiFi... everything works. Since yesterday, I made a few phone calls, used GPS navigation, browsed the web, installed a few apps and even played Ingress (which is kinda resource hungry) for a couple of hours. The system is rock solid (could not say that about CM 13) and even with storage encryption enabled the phone seems to run even faster than with the stock HTC ROM.
Great job! How can I buy you guys at LineageOS a beer?
Click to expand...
Click to collapse
This is what they write about that "We are currently not accepting monetary donations. This message will be removed when there is an official method to help fund the project. "
So, I've been out of the CM game for a while, and I'm a little curious as to how the Lineage OS update revision continues on from CM. I have an HTC One m7 (GSM), and I have CM12.1 installed (Android 5.1.1). So, is it safe to assume that LOS 14 would have been CM14, or Android 7.xx? I'm just trying to get my bearings on the update nomenclature, because I seem to remember that CM13 (Android 6) was not very stable on HTC One m7 (GSM), so I'm nervous to try LOS14.
Thanks!
waleismer said:
So, I've been out of the CM game for a while, and I'm a little curious as to how the Lineage OS update revision continues on from CM. I have an HTC One m7 (GSM), and I have CM12.1 installed (Android 5.1.1). So, is it safe to assume that LOS 14 would have been CM14, or Android 7.xx? I'm just trying to get my bearings on the update nomenclature, because I seem to remember that CM13 (Android 6) was not very stable on HTC One m7 (GSM), so I'm nervous to try LOS14.
Thanks!
Click to expand...
Click to collapse
CM = LOS. No difference at all (expect the name). You can try it as it's really stable. Just remember to full wipe before flashing
Sent from my One using XDA Labs
Awesome! I'm gonna have to try this out sometime! Are there any problems with calls, like the bug where the microphone is really quiet, and you can't hear the other person? Also, how stable is it, and which is the most stable version, experimental or nightly?
ZentixZaneic said:
Awesome! I'm gonna have to try this out sometime! Are there any problems with calls, like the bug where the microphone is really quiet, and you can't hear the other person? Also, how stable is it, and which is the most stable version, experimental or nightly?
Click to expand...
Click to collapse
Carefully read this site
Hydracio said:
Here is my experience with 14.1.20170130 nightly. I have been using it since yesterday morning and I am astonished by how well it works. LTE, GPS, WiFi... everything works. Since yesterday, I made a few phone calls, used GPS navigation, browsed the web, installed a few apps and even played Ingress (which is kinda resource hungry) for a couple of hours. The system is rock solid (could not say that about CM 13) and even with storage encryption enabled the phone seems to run even faster than with the stock HTC ROM.
Click to expand...
Click to collapse
Are you still satisfied? I am thinking of switching
bliblablub said:
Are you still satisfied? I am thinking of switching
Click to expand...
Click to collapse
I am satisfied, very stable and good performance. I use it as daily driver.
I started with lineage-14.1-20170131-nightly-m7-signed.zip, and currently I have flashed lineage-14.1-20170207-nightly-m7-signed.zip.
Everything works for me: Phone calls, SMS, GPS, BT, Wi-Fi, WhatsApp, Mail, Camera...
No major bugs observed so far - only one app is crashing compared to stock rom, but did not test everything till now...
Anybody flashed Blinkfeed? I use it, can someone try downloading it please?
Paul_Days said:
Anybody flashed Blinkfeed? I use it, can someone try downloading it please?
Click to expand...
Click to collapse
Yes, I have flashed sense home 8.51 by ckpv5 with more sense apps like weather, clock camera etc. Everything works fine for now.
Hey there .. I have flashed this rom yesterday, which one would be the supporting thread?
I have a problem with the alarm clock, I cannot set it up it crashes when I try to open it. Same deal with the gboard from openapps.
Any ideas how to solve it? The alarm is pretty damn important!
oicirbaf said:
Hey there .. I have flashed this rom yesterday, which one would be the supporting thread?
I have a problem with the alarm clock, I cannot set it up it crashes when I try to open it. Same deal with the gboard from openapps.
Any ideas how to solve it? The alarm is pretty damn important!
Click to expand...
Click to collapse
I had that problem too a while ago. Try to reflash your gapps or flash older version of gapps. If everything fails do a full wipe and flash rom and gapps.
BlueTooth problems
I've been running the 20170207 build for two days now and mostly it is working fine (even felt confident enough to encrypt the phone). Two (or three, depending on how you see it) annoying bugs are there though:
the "portrait" setting doesn't work, the phone remains in "auto orientation" mode
when bluetooth headphones are attached, phone calls won't work anymore (no audio is picked up or output by either the phone or the headphones)
even with BT turned off that problem persists until you remove all BT audio devices and reboot the phone
It'd be lovely to properly report these bugs. Unfortunately, the LineageOS people don't seem to be using GitHub issues?
Not really BT after all...
The real problem seems to be that any outgoing phone call has both microphone and speaker disabled. By hitting the "mute" button twice and the (enabled? why?) speakerphone button thrice, the phone call works then normally. Incoming calls are fine. If anybody from the Lineage OS team reads this, please help, it's a really annoying bug!
Also unfortunately the USB connection gets disconnected immediately after plugging in. In TWRP it works just fine, so it's not a hardware problem.
Was not doing much with my G6 today except webbrowsing and I walked over to my phone to find this error
{
"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"
}
Links to this page: https://support.google.com/nexus/an...6698467256067-2151825810&p=verified_boot&rd=1
Eventually it said the system was corrupt and could not be started. Contact customer service.
I managed to get the phone to reboot and it started up fine. Have never seen this error so wondering if someone could explain?
Is it related to Secure start-up? Or maybe malware? There's not really anything installed on my phone that I wouldn't trust.
Will call T-mobile today.
Well this is unnerving to see....
this is the screen you see after you unlock the bootloader... shows on my phone as well and everytime you boot the phone. on my ZTE 7 it's slightly different, but message is the same. did your phone reboot on it's on? maybe after installing the latest update?
cortez.i said:
this is the screen you see after you unlock the bootloader... shows on my phone as well and everytime you boot the phone. on my ZTE 7 it's slightly different, but message is the same. Did your phone reboot on it's on? maybe after installing the latest update?
Click to expand...
Click to collapse
I'm assuming it restarted itself since I was out of the room when it happened. It looked like it tried restarting a few times. It refreshed that screen a few times, then it said that the system is corrupt and it could not be started, etc and to call customer service... then it turned off.
I did read about software modifications from that help link but haven't installed anything questionable. Pretty much only big apps like Twitter, Instagram. No games, no utilities since I am just testing what came with the phone. I haven't touched the bootloader since I'm still technically testing the phone. The most I've done is enable Developer mode but I haven't tweaked any settings.
I didn't accept any software updates and I didn't see any notifications. Unless it updates itself?
I attached the screen that the phone gives using Power + Vol Dwn
Again, it's still working. It just had to be rebooted. Just not sure what triggered the message... unless enabling Developer Options is all that it takes.
I'm trying to find the screen it gave me after the one I posted above. It didn't stay on long enough for me to take a picture.
Same thing happened to me just a little while ago - it's been running fine since I received it otherwise. It eventually restarts itself and seems ok, but then I got that error a second time within about 15 minutes.
The only change I had made today was installing the XDA Labs app. It seems shortly after that is when this started. I've since removed that app to see if the error returns.
bren924 said:
Same thing happened to me just a little while ago - it's been running fine since I received it otherwise. It eventually restarts itself and seems ok, but then I got that error a second time within about 15 minutes.
The only change I had made today was installing the XDA Labs app. It seems shortly after that is when this started. I've since removed that app to see if the error returns.
Click to expand...
Click to collapse
Uh oh. Keeping an eye on this
Sent from my Nexus 6P using Tapatalk
bren924 said:
Same thing happened to me just a little while ago - it's been running fine since I received it otherwise. It eventually restarts itself and seems ok, but then I got that error a second time within about 15 minutes.
The only change I had made today was installing the XDA Labs app. It seems shortly after that is when this started. I've since removed that app to see if the error returns.
Click to expand...
Click to collapse
FWIW I installed the app yesterday and haven't seen this crash.
bren924 said:
Same thing happened to me just a little while ago - it's been running fine since I received it otherwise. It eventually restarts itself and seems ok, but then I got that error a second time within about 15 minutes.
The only change I had made today was installing the XDA Labs app. It seems shortly after that is when this started. I've since removed that app to see if the error returns.
Click to expand...
Click to collapse
Try factory resetting my phone. I did it to mine with Power Btn + Volume Down when starting. You gave to take finger off power button when LG logo comes up and then holding power btn down again quickly. It flashes it incredibly quick.
When I googled the issue, I read it has something to do with "verified boot". So far the only phones I've read that have it are Nexus, but the text on the LG is a little bit different. There is a second screen that says something about customer support... if you see this screen, if possible have a camera on hand to screen shot it. It looks like some kind of bug with the OS. Doesn't look like it will effect the function of the phone. But the message is frightening...
This is the Google official page about it:
Understand warning about operating system safety
https://support.google.com/nexus/an...6698467256067-2151825810&p=verified_boot&rd=1
What is Strictly Enforced Verified Boot in Android 7.0 Nougat?
http://thehackernews.com/2016/07/android-verified-boot.html
Pasted above from the second link in the above post. Seems like it could possibly apply to this issue...
What is Strictly Enforced Verified Boot in Android 7.0 Nougat?
http://thehackernews.com/2016/07/android-verified-boot.html
As far as security is concerned, Google is going very strict with the newest version of its mobile operating system.
Until now, Google has not done more than just alerting you of the potential threats when your Android device runs the check as part of the boot process.
Android Marshmallow 6.0 does nothing more than just warning you that your device has been compromised, though it continues to let your device boot up.
1. Android Nougat 7.0 Getting Strictly Enforced 'Verified Boot'
In
Android Nougat, Google has taken the security of its Android operating system to the next level by strictly enforcing verified boot on devices.
Among multiple layers of security protection, Android uses verified boot - since Android version 4.4 KitKat - that improves its device's security by using cryptographic integrity checking to detect if your device has been tampered with.
Now, Android Nougat will strictly enforce the boot check, giving you far more than just a warning.
2. Android 7.0 Verified Boot Protects Device from Rootkits and Malware
Enforcing verified boot on a device is a good idea.
If any Android malware or rootkit made its way onto your Android device and made deep system changes to critical kernel files, your device will either start in a limited-use mode (presumably similar to safe mode) or refuse to start at all, protecting your data.
In addition to strict verified boot, Android Nougat also features forward error correction that is capable of repairing some errors on devices without any user input.
And, of course, Nexus devices will be the first to get these features.
This will prevent your Android device from becoming a playground for malware and viruses, at least after you restart it.
That sounds really great. Right?
3. If Modified, Corrupt or Tampered, It won't let your phone Boot
For most users the strict verified boot would be helpful, however, for some, it's bad news. According to Google, some non-malicious corruption of data could cause Android devices to fail to boot up because verified boot process runs into issues that it can not correct.
This data corruption could be the result of some software flaws or hardware issues.
Here's what the Android Developer blog explains: "This means that a device with a corrupt boot image or verified partition will not boot or will boot in a limited capacity with user consent. Such strict checking, though, means that non-malicious data corruption, which previously would be less visible, could now start affecting process functionality more."Since corrupted data may not always be malicious, even a single-byte error could prevent the device from booting.
However, Android Nougat brings additional code designed to protect against data corruption.
"In the changes we made to dm-verity for Android 7.0, we used a technique called interleaving to allow us to recover not only from a loss of an entire 4 KiB source block, reads the blog, "but several consecutive blocks, while significantly reducing the space overhead required to achieve usable error correction capabilities compared to the naive implementation." 4. Verified Boot Has Made It Harder to Root Android 7.0 Nougat
Like I said, data corruption could not always be due to malicious reasons.
Strictly enforcing verified boot could also make it tougher for you to tweak your Android Operating System (especially with locked bootloader) using custom ROMs, mods, and kernels.
Since this involves circumventing the locked bootloader, verified boot process will detect any changes, making it harder for users to play with their devices when Nougat rolls around.
The bottom line:
Enforcing strict verified boot in Android Nougat is a good idea, because most users root their devices with custom firmware but forget to take important security measures, which leaves their devices open to malicious software and rootkits.
What do you think of the additional security Google provides to the boot process in Android Nougat?
Let us know your views in the comments below!
Click to expand...
Click to collapse
Interesting it mentions it tries to fix the error. I noticed this when mine was "crashing". Flashed the first screen a few times before it "failed". Unfortunately can't find an example of this screen anywhere.
Man. This happened to me on LG v20. No explanation since I didn't root my phone. Lucky T-Mobile sent me replacement .
Sent from my LG-H872 using Tapatalk
Is this limited to t mobile devices so far? Sounds like they have an app Google sides not like.
This has happened to me twice about 4 days apart. I have AT&T LG G6 US variant. I have also seen on Reddit this happened to Verizon customers.
I don't root/unlock and I only install well known apps from the playstore.
I did find one thing in common was that both times it happened relatively soon after turning OFF the always on display. Was this the same for anyone else?
for those affected by this "issue", have you reported this to T-Mobile/ATT? if yes, what was their respective response(s)? thanks.
cortez.i said:
for those affected by this "issue", have you reported this to T-Mobile/ATT? if yes, what was their respective response(s)? thanks.
Click to expand...
Click to collapse
They were more interested in talking about malware tbh. Thinking of reporting it to LG. Especially if I get a shot of the second screen... that one reads like it's bricked.
For what it's worth, this hasn't happened again since I removed the XDA Labs app. May just be coincidence. I'm planning on putting that app back on to see if the issue resumes.
cortez.i said:
for those affected by this "issue", have you reported this to T-Mobile/ATT? if yes, what was their respective response(s)? thanks.
Click to expand...
Click to collapse
The ATT rep said looks like a software bug and reset the phone and said if it happens again to go through the exchange/return process.
It has happened a second time already I just really don't want to return this phone if it's a software issue that could be fixed with an update. But I'm starting to think maybe I should.
Dcpeiffer said:
The ATT rep said looks like a software bug and reset the phone and said if it happens again to go through the exchange/return process.
It has happened a second time already I just really don't want to return this phone if it's a software issue that could be fixed with an update. But I'm starting to think maybe I should.
Click to expand...
Click to collapse
UPDATE: I talked with AT&T and they said that a phone update that went live is actually what's causing the faulty bootloader message. Apparently a factory reset is fixing the issue most of the time but I can exchange the phone for up to a year if the issue persists.
Glad to say since I've factory reset my phone, I've had 0 issues. I'm thinking it is a bug tbh and not something to be too concerned with.
Dcpeiffer said:
UPDATE: I talked with AT&T and they said that a phone update that went live is actually what's causing the faulty bootloader message. Apparently a factory reset is fixing the issue most of the time but I can exchange the phone for up to a year if the issue persists.
Click to expand...
Click to collapse
Glad AT&T is taking responsibility and giving you a nice window for exchange. All T-mobile was willing to give me was the normal 20 days, then it would have to be within the warranty period...