Related
Hello!
After updating from ICS to JB 2 months ago I constantly facing with different problems with. I was enjoying ICS and expected best experience from JB.
First of all I missed all of my media files from SD. I searched xda for answer and discovered same issues. All answers was, like, "delete .nomedia and/or wipe your device". I didn't have ANY .nomedia file on my SD. So, I forced to wipe all of my data, app settings, etc. and recover it again. F*ck, why I must format my phone to make it work properly? Sometimes I have known bug with stock launcher when it doesn't show any icons or render one icon to whole screen. Sometimes my device freezes and I only can reset it by ejecting battery. Very poor battery life. Several days ago my battery suddenly dropped to 0% from 60%! Look at pic in attachment.
But main problem with JB is performance. With ICS I hadn't any lags in simple games such as Cut the Rope, but in JB I often facing small freezes and lags that highly annoying. Sometimes one game running OK, but next time it very sluggish. I can't understand why. I constantly have ram issues. In ICS I saw stock launcher crash very rarely. But in JB after every Internet surfing or gaming I must wait to stock launcher load. More frequent is widget issues. When I press Home button I see that stock calendar widget blinking. That seems like it loading or reloading.
So, the main question is: what can I do with this? Is there any custom rom that hasn't this issues? Can I cut some JB features to increase it performance? Is there anyone that have same problems?
schroding3rscat said:
First of all I missed all of my media files from SD. I searched xda for answer and discovered same issues. All answers was, like, "delete .nomedia and/or wipe your device". I didn't have ANY .nomedia file on my SD.
Click to expand...
Click to collapse
look here http://forum.xda-developers.com/showthread.php?t=1913629
by the way I have no lag at all and a very good experience with JB
lostman.it said:
look here http://forum.xda-developers.com/showthread.php?t=1913629
by the way I have no lag at all and a very good experience with JB
Click to expand...
Click to collapse
I'd already solve this problem with wiping, but I didn't touch any of my media files. I don't think this was caused by corrupted file.
Wipe is necessary when you flash a brand new rom. I've experienced the same issue upgrading to jb from ics, solved by doing a full wipe!
Crucio32000 said:
Wipe is necessary when you flash a brand new rom. I've experienced the same issue upgrading to jb from ics, solved by doing a full wipe!
Click to expand...
Click to collapse
Of course I did this.
Also, sometimes I stuck with (bug?) android.server process consuming all CPU. Only phone restart helps.
I don't have a lot of complaints, and haven't had the same performance issues, though I don't do a lot of gaming. That's what the Nexus 7 is for.
The media scanner in Android sucks in my opinion, so if your files aren't showing up you may want to try running something like SDRescan. My music files (in Music directory on SD card) will show up as soon as I re-open Play Music.
You could try turning off Google Now if you haven't already. I did that and the battery seems to be a little better.
OP, I used to have the same problem and I could never find the .nomedia file. I had to delete ROM manager and its folder. After a full wipe and many tries, I got it to work. As for the launcher crashes, you might want to download an alternative from the play store. One that keeps it "in memory", that way it hardly crashes. I have Nova launcher and it happens frequently to where I switched to Apex haha.
This helped me and hoping it helps you. Good luck!
Sent from my Nexus S using xda premium
I've been running stock 4.1.2 (rooted) for a while now, and after really slow performance, steadily worsening battery life, and general annoyances like random reboots, Blue Screens, and other annoyances like duplicated incoming SMSs, I figure it's time to take the plunge and install a custom ROM and maybe even a fresh kernel.
Unfortunately, I don't have the time to devote to experimenting with all the different ROMs out there for this phone, and was wondering if I were to list out what I usually use the phone for and what apps I run most of the time if it would be possible for people to recommend which one would be a good fit to try as my first.
(I know this'll mean missing out on all the fun of having so many choices, and when I have more time later, I'll see what I can do about exploring the other options.)
I make heavy use of SMS, although often times my messages are laggy to send and receive (I don't know if this is a problem with my phone or T-Mobile). Incoming messages sometimes get repeated multiple times for no apparent reason. My current SMS default is EvolveSMS, but I had similar issues with GOSMS.
I also play Ingress, so any bugginess in the GPS would be a deal breaker.
Voice calling is sometimes problematic as well. When I make outgoing calls, it sometimes take 30 seconds for the phone app to load., With incoming calls, I may get the ringtone, but no screen to accept or reject the call.
I run the xposed framework for a handful of modules (All Notifications Expanded, and Buttered Toast)
I'm using Nova Launcher for my homescreen, because of the ability to set a grid size, use custom icons, overlap icons on top of widgets, and lock the homescreen configuration from accidental changes. A ROM that would do the same things natively without having to run a homescreen replacer would be welcome.
I'm also interested in running on my external SD, Is that something I should set up prior to flashing the new ROM, or can that only be done after the ROM is installed?
Team Apex have done some great work. By now they know the hardware very well, having done the initial dev work back on CM9, all the way up to the current CM11 and now Omnirom systems. Their current efforts are focused on the Omnirom-based Omnitoad project. It's at a point where it works very well. I suggest starting there.
The stock roms and the earlier CM roms all have a bug where the compass reads totally wrong after a reboot until you recalibrate it. This was finally fixed in the CM11-based ROMs. That should help Ingress.
radwolf76 said:
I've been running stock 4.1.2 (rooted) for a while now, and after really slow performance, steadily worsening battery life, and general annoyances like random reboots, Blue Screens, and other annoyances like duplicated incoming SMSs, I figure it's time to take the plunge and install a custom ROM and maybe even a fresh kernel.
Unfortunately, I don't have the time to devote to experimenting with all the different ROMs out there for this phone, and was wondering if I were to list out what I usually use the phone for and what apps I run most of the time if it would be possible for people to recommend which one would be a good fit to try as my first.
(I know this'll mean missing out on all the fun of having so many choices, and when I have more time later, I'll see what I can do about exploring the other options.)
I make heavy use of SMS, although often times my messages are laggy to send and receive (I don't know if this is a problem with my phone or T-Mobile). Incoming messages sometimes get repeated multiple times for no apparent reason. My current SMS default is EvolveSMS, but I had similar issues with GOSMS.
I also play Ingress, so any bugginess in the GPS would be a deal breaker.
Voice calling is sometimes problematic as well. When I make outgoing calls, it sometimes take 30 seconds for the phone app to load., With incoming calls, I may get the ringtone, but no screen to accept or reject the call.
I run the xposed framework for a handful of modules (All Notifications Expanded, and Buttered Toast)
I'm using Nova Launcher for my homescreen, because of the ability to set a grid size, use custom icons, overlap icons on top of widgets, and lock the homescreen configuration from accidental changes. A ROM that would do the same things natively without having to run a homescreen replacer would be welcome.
I'm also interested in running on my external SD, Is that something I should set up prior to flashing the new ROM, or can that only be done after the ROM is installed?
Click to expand...
Click to collapse
to be fully honest though...i do highly recommend flashing my B14CKB1RD kernel on whatever 4.4 kit kat rom you use if you want best stability and battery life...its been proven that at the end of the day your rom will have alot of batterly life remaining compared to stock....whats good about my kernel is that you control how you want the phone to work...where as with TeamApexQ stock kernels you are locked to that one state and also has an mpdec touchboost enabled that boosts your cpu core to 1134mhz minimum speed when you touch the screen thus rapidly draining your battery... I'm in no way saying the work they have done isnt great....theyve done a hell of a job bringing the device to the stability its at today... it just brings that much more stability outta any rom you use
REV3NT3CH said:
to be fully honest though...i do highly recommend flashing my B14CKB1RD kernel on whatever 4.4 kit kat rom you use if you want best stability and battery life...its been proven that at the end of the day your rom will have alot of batterly life remaining compared to stock....whats good about my kernel is that you control how you want the phone to work...where as with TeamApexQ stock kernels you are locked to that one state and also has an mpdec touchboost enabled that boosts your cpu core to 1134mhz minimum speed when you touch the screen thus rapidly draining your battery... I'm in no way saying the work they have done isnt great....theyve done a hell of a job bringing the device to the stability its at today... it just brings that much more stability outta any rom you use
Click to expand...
Click to collapse
mpdec and touchboost are two separate concepts. Touchboost boosts the second core to 1134 Mhz when you are using the display in order to make the phone more responsive. Mpdec turns off the second core when not in use and conserves a huge amount of battery. On OmniToad, with the standard kernel on it, I usually get 60 hours + per charge of medium use. I've been using OmniToad continuously, and since the beginning of it, I have not personally had any reboot that was not initiated by myself.
Um dude you do know your touchboost is mpdecision based right?....look at the defconfig...and to be honest my kernel works just as smooth if not smoother than the stock kernel of omni without it...using omni on stock kernel I wald have 40% battery come 11pm my time when unplugged at 7am...on my kernel I'll have anywhere between 65% and 70% with same usage and hours
Sent from my L1QU1D R3L4Y using xda-developers app
One other thing about touchboost, which will hopefully bring us all out of ignorance of it as I am tired of the constant FUD about it. It is the 'touch responsiveness' portion of Google's "Project Butter" initiative. It is a standard Android/AOSP feature enjoyed by Nexus owners since Android 4.1.x.
One more thing. It is a UI deficiency that the performance settings apps show 1134Mhz as min cpu when using touchboost. In kernel mpdec will run the cpus at 384mhz unless something needs more, or the cores will sleep. Now you know the facts. Let's stop spreading misinformation. Thanks.
Not spreading misinformation...my builds and the community have even spoken of the better battery my kernel and ROMs have with it disabled and removed....even flashing my kernel over omni the phone instantly stopped overheating and lost maybe a percent in 2 hours with moderate use.... I just love how as soon as I came to the relay you guys judged me as a noob and all the name calling and what not....it's your teams loss...all my gain...good luck
Sent from my L1QU1D R3L4Y using xda-developers app
In my opinion, I try all the roms available for relay right now, the better performance I have was with liquid ROM and blackbird kernel. Omni is smooth but the battery its not the best for my phone with my personal use, and with GPS and plugged to the car charger i got overheating. Carbon got better battery than omni and better customization options but not smoother. Liquid have all you need in a ROM, personalization, full control and with the kernel blackbird and Wheatley and sio configuration have the better performance and battery at all ROM I try
Sent from my SGH-T699 using XDA Premium 4 mobile app
So, I tried OmniToad for a bit. Wasn't really impressed with the compass fix mentioned above, because even after flashing it was still quite ill-behaved in Ingress.
I also couldn't get the External 2 Internal SD Card swap to work -- the storage tab kept reporting my internal as 5 gig and the external as 64gig. This was after trying two different microSDs.
So, because of those two issues, and being not too far along in re installing everything, I decided to flash again, with the Blackbird Kernel and Liquid Smooth.
Now, when I try to boot. it hangs on the screen with the ApexQ green penguin. If I try for recovery mode I'll get the blue text that says booting into recovery, and then it goes to the penguin again. Trying to boot to download mode also just gives me the penguin.
Troubleshooting suggestions? Because right now, I'm without any clue as to what to do next, and without a phone for that matter.
[Edit: Just got into recovery, so going to try flashing back to OmniToad]
[Edit 2, Electric Boogaloo: Back on the Toad for now, Seems to be working. Thoughts on how to get things running on my external SD? Is it maybe an issue with KitKat based roms?]
I'll guide you through it...my roms shouldn't show anything teamapexq related ...what recovery were you using...and have you tried heimdall or ODIN
Sent from my L1QU1D R3L4Y using xda-developers app
REV3NT3CH said:
I'll guide you through it...my roms shouldn't show anything teamapexq related ...what recovery were you using...and have you tried heimdall or ODIN
Sent from my L1QU1D R3L4Y using xda-developers app
Click to expand...
Click to collapse
Recovery is TeamWin, and I was finally able to get back into it. Put OmniToad back on it for the time being. If you wanted to put up a step by step for going from Omni to Liquid, I can give it a try, because at this point, I'm pretty sure it was a "ID Ten T "error.
Magamo said:
mpdec and touchboost are two separate concepts. Touchboost boosts the second core to 1134 Mhz when you are using the display in order to make the phone more responsive. Mpdec turns off the second core when not in use and conserves a huge amount of battery. On OmniToad, with the standard kernel on it, I usually get 60 hours + per charge of medium use. I've been using OmniToad continuously, and since the beginning of it, I have not personally had any reboot that was not initiated by myself.
Click to expand...
Click to collapse
Did u just say 60+ hours of use??
How?? What do u mean by medium use?? Are you using the stock battery??
That's only possible with screen off with no use in that 60 hours and the phone going into deepsleep...either that or he's using an extended battery....with very minimal use....also proof or it didn't happen
Sent from my L1QU1D R3L4Y using xda-developers app
@radwolf76 I sent you a pm
Sent from my L1QU1D R3L4Y using xda-developers app
I ended up partitioning my external SD card so I could use Mounts2SD. Seems to be working so far.
Now I just have to get all my stuff put back on this thing and figure out how the extra features of LiquidSmooth are going to fit into my workflows.
One thing that seems to be a minor annoyance, probably because I just haven't found the toggle for it yet: on stock, I used to be able to wake the phone from the home button and the screen would pop on instantly. Under both custom ROMs I've tried, it seems a lot harder to wake the phone. The power button seems to be the only thing that works, and I have to stab at it repeatedly. I almost suspect that I'm waking it up and puttting it back to sleep before the screen comes on, but I can't seem to find anything that consistently works. Like I said, it's probably something I just need to toggle under settings.
The home button's actual switch is in the center of the button, while the design allows the button to tip sideways. So if you press it on a corner instead of the middle, the phone sometimes won't recognize it.
radwolf76 said:
I ended up partitioning my external SD card so I could use Mounts2SD. Seems to be working so far.
Click to expand...
Click to collapse
I may have spoken too soon. Getting all sorts of apps stopping on me now. Launcher3, Hangouts, Ingress, Settings...
Also, Launcher3 seems to 'forget' homescreen layouts every so often... some times I'll be going back to blank homescreens, and then after poking around in other apps, the homescreen will be back to the original configuration.
Ingress also acts like it can't see Location Services most of the time.
Also, sometimes when I reboot, it takes up to 20 minutes before the phone's back up and running.
While I can't discount that it was any of the number of apps I've put back on the thing, I'm pretty sure that Mounts2SD is the smoking gun here. these problems didn't start until after I had started using it. The symptoms seem about right.
I'm wondering if there's a conflict between Mounts2SD and the governor/scheduler I'm running (Wheatley/SIO).
I'd rather not have to troubleshoot this, but one of my main goals with starting fresh on this was to be able to store and run apps on my External SD, preferably without having to fuss with it on a per-folder basis. So if anyone has had any success in that department, I'd love to hear some tips that point me in the right direction.
[Edit: Turns out Mounts2SD overrides the governor/scheduler choices anyway. I think, that when I get off work I'm going to start fresh again over my next few days off, and try using Link2SD instead.]
radwolf76 said:
I may have spoken too soon. Getting all sorts of apps stopping on me now. Launcher3, Hangouts, Ingress, Settings...
Also, Launcher3 seems to 'forget' homescreen layouts every so often... some times I'll be going back to blank homescreens, and then after poking around in other apps, the homescreen will be back to the original configuration.
Ingress also acts like it can't see Location Services most of the time.
Also, sometimes when I reboot, it takes up to 20 minutes before the phone's back up and running.
While I can't discount that it was any of the number of apps I've put back on the thing, I'm pretty sure that Mounts2SD is the smoking gun here. these problems didn't start until after I had started using it. The symptoms seem about right.
I'm wondering if there's a conflict between Mounts2SD and the governor/scheduler I'm running (Wheatley/SIO).
I'd rather not have to troubleshoot this, but one of my main goals with starting fresh on this was to be able to store and run apps on my External SD, preferably without having to fuss with it on a per-folder basis. So if anyone has had any success in that department, I'd love to hear some tips that point me in the right direction.
[Edit: Turns out Mounts2SD overrides the governor/scheduler choices anyway. I think, that when I get off work I'm going to start fresh again over my next few days off, and try using Link2SD instead.]
Click to expand...
Click to collapse
well i use nova launcher.....launcher 3 and google launcher in my opinion isnt the best of launchers...there is other options i mentioned in a pm before to storing apps on sd and is alot easier than fiddling looking for the right app ....what also gives you the assumption it messes with governer or scheduler....i know by default there is settings for sd read ahead write ahead scheduling but that app shouldnt have control in changing any of this
REV3NT3CH said:
what also gives you the assumption it messes with governer or scheduler....i know by default there is settings for sd read ahead write ahead scheduling but that app shouldnt have control in changing any of this
Click to expand...
Click to collapse
This post from another user in the Mounts2SD thread. They might be mistaken, but either way, my problems started cropping up after I installed that app, and if there's a chance that poster is right about it setting those things, that's just another reason for me to uninstall it.
right now Carbon wins
I've tried them all, Liquid smooth is awesome but the latest built gave me some blackscreen issues until the next built go with carbon if you want some nice features or slim for a nice overall rom.
Don't forget to install the Blackbird kernel for a even better result.
Peace!
Every test build, including the final release of lollipop had plagued me with a bug where it continuously oom kills apps, including the bluetooth service, music running in the nackground, navigation while im driving, or even my keyboard while im typing. It doesnt matter if its a background process or in the foreground, it will get killed eventually without any force prompt. I've tried lowering my oom values in 3c toolbox but that hasn't done anything. Anyone else having this problem or have a solution?
Well, I know that feel bro. LOL.
Check my post here for my experience.
b00bs said:
Well, I know that feel bro. LOL.
Check my post here for my experience.
Click to expand...
Click to collapse
I'm getting the exact same issue here. after using it for awhile (about 40 hours), i was getting launcher redraws constantly. I checked memory usage and system was hogging somewhere between 800MB to 1GB. I was reading on a reddit forum that this is due to a memory leak and that it could be a google play services issue and not a lollipop issue? I'm not a developer so really no basis for comment, but i feel you in that the phone definitely does start to get laggy. I'm really hoping google will address this, but in the meantime the fix has been to reboot.
I have the same problem. N5 is almost unusable on Lollipop. I will admit I have a lot of apps but not that many that are always running in the background.
The big annoyances are what OP said: Navigation getting cut off in the background, Music getting killed. I've noticed these two problems being more prominent when BlueTooth is turned on/connected.
makapav said:
I have the same problem. N5 is almost unusable on Lollipop. I will admit I have a lot of apps but not that many that are always running in the background.
The big annoyances are what OP said: Navigation getting cut off in the background, Music getting killed. I've noticed these two problems being more prominent when BlueTooth is turned on/connected.
Click to expand...
Click to collapse
Seriously, music getting killed with device like Nexus 5 is blow my mind.
Yup. Had Power Amp get killed today. Literally the first time I have EVER seen Power Amp killed. Thanks Lolliflop!
Yeah, this is extremely annoying! Have to restart the phone every 12-24h if I want some decent multitasking!
Please star this issue:
https://code.google.com/p/android/issues/detail?id=79729
My Nexus 5 has now become unusable. I can't figure out if it's because of encryption or just shiate multitasking in Lollipop.
<rant> Screw you Google for not having developers that actually use beyond 10 standard apps on their phones in your test group. </rant>
This has nothing to do with encryption .. I don't use this this feature.
I've been trying to diagnose this issue for a long time now, but haven't got any closer to a conclusion.
As the title says, my problem is that the phone is a lot of the time very slow in simple tasks like launching an app or performing a certain activity. I also find it freezing a lot, and it's really annoying, almost unusable.
Sometimes, the UI is very responsive and smooth, but most of the time it's the complete opposite. I started to notice this with Facebook's Messenger app, but I found that it's not the actual cause.
So I analyzed the CPU and RAM, both of which seem to not be the issue. And then I decided to test the Disk R/W speeds, and found that doing even very simple tasks or even not doing anything at all gets the disk read speeds to 100%. That's the most logical explanation to this that I could get to.
I did factory reset, clean flashed a new ROM, and all that aswell.
Does anyone have this problem and is there a solution?
Theres really not much to do. The phone is getting older and 2gb of ram(assuming you have 2gb model) is not the best in 2017. The real problem is unoptimized apps like facebook,mesenger,snapchat... The fix would be to go back to miui because it never keeps apps running in the background. I do to myself encounter this problem with any AOSP based rom. You can try clearing cache and dalvik.
timipisoboy said:
Theres really not much to do. The phone is getting older and 2gb of ram(assuming you have 2gb model) is not the best in 2017. The real problem is unoptimized apps like facebook,mesenger,snapchat... The fix would be to go back to miui because it never keeps apps running in the background. I do to myself encounter this problem with any AOSP based rom. You can try clearing cache and dalvik.
Click to expand...
Click to collapse
Does LOS' option in developer options to not keep any app running in background work in the same way? Do push notifications function then?
n3onis said:
Does LOS' option in developer options to not keep any app running in background work in the same way? Do push notifications function then?
Click to expand...
Click to collapse
You can try, never tried it myself. Probably same as miui and you probably will lose notifications, thats whats good about miui, it starts app every so to get notifications.
Since we've been talking about Pie in at least four different threads, I thought I'd create a single one to address, list and possibly fix all the issues that are being experienced with the gradual release of Android 9 on Nokia 7 Plus. Mods: I'm assuming this is helpful, but if you think this thread is redundant feel free to delete it.
IMPORTANT: Before you do anything or think something is broken, make sure you restart the phone twice once you've installed the update. If issues are still there, you might go for a hard reset which is always helpful for creating a clean system environment.
In any case, you're welcome to add to this list and help others find solutions. This is what I found so far:
Battery draining
Most users noticed a decrease in SOT, for some this is even 2-3 hours less than on Oreo. While it might be peculiar to Pie itself, it is worth noticing that the new Adaptive Battery feature takes some time to adjust according to how you use your phone and learn what apps to handle and how. You should also check that no app permissions have changed since the update, or that no unwanted processes are misbehaving because of it (see below).
@trveller72 points out a neat trick: deactivating the automatic Battery Saver (Settings > Battery > Battery Saver > UNCHECK "Turn on automatically") seems to extend battery life a lot.
Heating issues
Regardless of the SOT, these should not be there. I experienced the thing myself and in deep October no phone should burn into one's pocket, whether idle or when doing some light browsing. If you're having heating issues, this is most likely related to processes misbehaving and abusing your CPU when they shouldn't (either because of an application bug, or because of something gone wrong after the update). In this case you should launch the ADB command
Code:
adb shell top
which returns the CPU usage of your phone (make sure, of course, the phone is connected to your computer and has USB debugging enabled). This might give you an idea of anything strange going on and allow you to act accordingly. Or you could go for a hard reset like I did, which is a nice overkill solution and grants that you carry over no unwanted issues from Oreo - and it also recovered some SOT for me.
No adaptive brightness fade effect
I experienced this myself: the screen goes from 0 to 100 brightness in a millisecond and you're blinded forever, never to see your loved ones' faces again. This might possibly be an issue with the personal settings brought over from Oreo. In my case, I solved it to a degree by playing with the bar a bit, and it was solved completely with a hard reset. I think the fade effect is a bit faster in Pie anyway, so there is a degree of difference you should not worry about.
App notifications not disappearing
Notifications for some apps tend not to disappear when you swipe over them. For instance, this is true with the "HDR processing" progress bar of the PixelCamera mod (or better yet, in some versions of it). No fix for now, you just have to force quit the app and hope it is made compatible soon.
UI and Animation glitches
As with all first releases, this one is not perfect yet. I've personally encountered some animation glitches with the reception of nested notifications (especially in the lock screen), non-standard DPI settings, app-switch animations, volume control when writing on your keyboard, and minor stuff of the sort. While most of these are system-related and will have to be fixed in next releases, for in-app glitches make sure they are correctly updated and compatible with Pie; you could also try deleting cache/data, uninstalling and reinstalling them.
In particular, some report an issue where the bottom part of the touchscreen stops working after prolonged inactivity, regardless of the navbar settings. @k3dar7 suggests using XDA Navigation Gestures (no root).
Digital Wellbeing
Yes, this is not compatible with Nokia 7 Plus yet, despite it being in DP4 (iirc), the feature is still unavailable although installed on the phone and already collecting data, and can be enabled by subscribing to the beta program (thank you @divvykev). Downloading it as an app from Play Store won't be possible, but @Redcap56 kindly points out that a working version is available for download at APKMirror.
"Non-issues"
(i.e. things you're probably complaining about but are actually feature-dependant)
- The new gesture-based navigation is not available. It's there, but you have to turn it on under Settings > System > Gestures > Swipe up on Home button
- Mobile data is always active even when on a Wi-Fi. Yes, unlike before it is, but you can turn this feature off in Developer Settings.
- There is a maximum number of possible notification icons before the dreaded "etc. dot" appears. Nothing that can be done, unfortunately. This was decided by Google regardless of not all phones having a notch.
- File Manager is gone. And FilesGo is now there, like the child you never wanted. And most likely you never wanted it because it doesn't allow you to browse folders. The old file manager can still be accessed through the Download app or in System > Storage > Files. If you can't see the internal memory, make sure the option is ticked in the three-dot dropdown menu.
Digital Wellbeing does work!
Installing from apkmirror worked for me: apk/google-inc/digital-wellbeing (I am still not allowed to post url)
Redcap56 said:
Installing from apkmirror worked for me: apk/google-inc/digital-wellbeing (I am still not allowed to post url)
Click to expand...
Click to collapse
Thanks for the heads-up, it works indeed.
By the way, before getting the APKMirror version I had just found out that Digital Wellbeing is actually installed on the phone, just inactive.
https://drive.google.com/file/d/1vYzZE5zB3LNLAckAUlRMkWoXPMjkD42M/view?usp=sharing
When I updated it with the APKMirror one it could show me statistics from all the past day, which means two things: one, it's already collecting data and it's creepy. Two, it's in a working state as it was in DP, so shall we expect that it becomes activated with the next OTA? (or when marketing-wise it's no longer important to make it Pixel-exclusive?)
If I search on internet, Digital Wellbeing is only available on beta version for Pixel phones on Android Pie only.
I think, when the beta is finished, we have all access to this functionality
Wellbeing is available. I found it be looking for the app in the store but found that it was installed. Signed up for the beta and hey presto....there it is. Can't see it being of any use to man or beast but hey ho.
Am on Pie stable btw.
divvykev said:
Wellbeing is available. I found it be looking for the app in the store but found that it was installed. Signed up for the beta and hey presto....there it is. Can't see it being of any use to man or beast but hey ho.
Am on Pie stable btw.
Click to expand...
Click to collapse
Thank you.
I checked yesterday and was saying that you need a Pixel phone to install it. Today I just had to join the beta program and voilla!
divvykev said:
Wellbeing is available. I found it be looking for the app in the store but found that it was installed. Signed up for the beta and hey presto....there it is. Can't see it being of any use to man or beast but hey ho.
Am on Pie stable btw.
Click to expand...
Click to collapse
Thank you, I don't find it useful either but this is good information indeed! Post updated.
I don't see any difference between latest beta and this so called stable one, all the issues persists.
Phone heating is really pain in the a$$, especially while charging (most of the time, not always though). I have seen "Temp High, Stop Charging" notification 3 times in a row now.
I have some issues with displaying apps since Pie. For example, when I'm playing music with Youtube Music and Maps has a picture-in-picture overlay the YouTube music app will flicker heavily and the album art won't be visible anymore.
Same for the normal YouTube app and SwiftKey.
Anyone else experiences this?
PiotrekV said:
I have some issues with displaying apps since Pie. For example, when I'm playing music with Youtube Music and Maps has a picture-in-picture overlay the YouTube music app will flicker heavily and the album art won't be visible anymore.
Same for the normal YouTube app and SwiftKey.
Anyone else experiences this?
Click to expand...
Click to collapse
In Snapchat messages, the screen can flicker so much it's unusable. It's usually cause by putting the cursor before an already typed word.
shailendra1993 said:
I don't see any difference between latest beta and this so called stable one, all the issues persists.
Phone heating is really pain in the a$$, especially while charging (most of the time, not always though). I have seen "Temp High, Stop Charging" notification 3 times in a row now.
Click to expand...
Click to collapse
High temperature while charging is very, very bad. If you can't solve this, I'd suggest you go back to Oreo before the battery is ruined.
In any case: did you update directly from DP? Did you check for strange processes via ADB? If you haven't done it, a hard reset can be very helpful as well.
PiotrekV said:
I have some issues with displaying apps since Pie. For example, when I'm playing music with Youtube Music and Maps has a picture-in-picture overlay the YouTube music app will flicker heavily and the album art won't be visible anymore.
Same for the normal YouTube app and SwiftKey.
Anyone else experiences this?
Click to expand...
Click to collapse
RancidPenguins said:
In Snapchat messages, the screen can flicker so much it's unusable. It's usually cause by putting the cursor before an already typed word.
Click to expand...
Click to collapse
Not with the same apps, but I experience this as well. Only advice I can give is to try what you can for single apps (i.e. clear cache/data, uninstall, reinstall) but you probably did that already. If it isn't solved this way, only the next OTA (and/or the next app update) will solve it.
But yeah, this is definitely a thing. I have heavy flicker in some setup wizards for Google apps (most notably Lens) and the volume control will flicker at all times if shown while typing on the keyboard.
valexbast said:
High temperature while charging is very, very bad. If you can't solve this, I'd suggest you go back to Oreo before the battery is ruined.
In any case: did you update directly from DP? Did you check for strange processes via ADB? If you haven't done it, a hard reset can be very helpful as well.
Click to expand...
Click to collapse
Yes, updated directly from DP. I have done factory reset, Hard reset is necessary?
shailendra1993 said:
Yes, updated directly from DP. I have done factory reset, Hard reset is necessary?
Click to expand...
Click to collapse
Actually that should suffice AFAIK. If I were you, I'd try downgrading to a stable Oreo and updating from there. I'm really not sure about it, but probably some bad code is brought over from the beta? But that temperature is definitely not normal, especially if you already did a factory reset.
valexbast said:
Actually that should suffice AFAIK. If I were you, I'd try downgrading to a stable Oreo and updating from there. I'm really not sure about it, but probably some bad code is brought over from the beta? But that temperature is definitely not normal, especially if you already did a factory reset.
Click to expand...
Click to collapse
Maybe some app is behaving inapppropriately. I have done Hard Reset and will see if the problem still persists, else I will degrade.
shailendra1993 said:
Maybe some app is behaving inapppropriately. I have done Hard Reset and will see if the problem still persists, else I will degrade.
Click to expand...
Click to collapse
Not sure if you did that already, but the adb command I wrote in the first post can be useful to check that. Good luck anyway!
The stable pie update is a full rom, not an incremental update, so it doesn't matter from which version you are upgrading, after a reset, no trace of the old operating system remains
I might be wrong but I think the issue with the screen on time not lasting as long as it did in oreo in one of the updates they decreased the speed the battery charges or the curve it charges at, I can't remember where it was mentioned but there were issues and they said it will be addressed in pie, this could be related to the battery getting hot while charging as mentioned by @valexbast .I personally haven't had this issue with screen on time being less but I use my old Samsung charger 2Amp 5V most of the time.
I am having (albiet minor) bugs when adjusting the display density and font size both to their smallest. The lock screen pin entry sticks to the left side of the screen, and notifications & quick settings change themselves randomly to the wrong density and back again. Nokia support refuses to acknowledge these bugs exist but I have seen a few people around the web with similar issues. I did not have any of these issues on DP4 which is interesting!
occasionallyhavingeyes said:
I am having (albiet minor) bugs when adjusting the display density and font size both to their smallest. The lock screen pin entry sticks to the left side of the screen, and notifications & quick settings change themselves randomly to the wrong density and back again. Nokia support refuses to acknowledge these bugs exist but I have seen a few people around the web with similar issues. I did not have any of these issues on DP4 which is interesting!
Click to expand...
Click to collapse
While helpful, I noticed that Nokia support is often instructed to "pacify" the user and assure them everything is normal. But I guess they're taking notes. I haven't tried changing display/font size but the bugs you describe should be easy enough to fix in the next update.
I don't think any of this is app-related anyway, even when we're talking notifications from certain apps. So here's to waiting.
Edit: by the way, I'm a long-time lurker and only newish user so I'm really not a veteran, but hey... welcome to XDA!