Related
This is now considered a beta version of Ice Cream Sandwich for the HeroC. Please keep all comments/communication about this ROM in this thread, and keep the Development thread clean for people actively working on the ROM.
No guarantees that anything will work, or that your phone will not be turned into a brick or a toaster. Please backup if you value what is currently on your phone.
You can use this with or without gapps. If you load them both on the initial setup, be sure to select "Setup Wizard" when the system first comes up.
In its current state this ROM with GAPPS needs around 155M in /system. I am currently running firerats at 160/20 just to be safe for testing purposes. I would recommend at least 155 for system.
There are some obvious places where we can reduce the size, but that will come as we continue to refine and move forward. Performance in not great, but overall it is fairly functional. Gapps are just some a minimal version to get Market working.
THIS ROM TAKES A LONG TIME TO BOOT (ESPECIALLY FIRST BOOT).
Boot animation has been added in 26NOV version. Please be patient.
This is a work in progress and there remain many Opportunities for Improvement (the gentle euphemism for Defects).
Working (at least for me):
Touchscreen
Trackball
Phone
Data
WiFi
MMS
Audio
Bluetooth
SD Card
Market
GPS
Gallery
Boot Animation
LatinIME Keyboard
Prediction/Dictionary
Network Stats (Data Usage)
Headsets (Audio Jack & HTC 11 Pin)
Not Working:
Camera
Gallery2
Graphics Acceleration
TBD (Lots of other stuff)
25-NOV-2011 Initial Alpha release
TeamICS-4.0.1-25NOV-HeroC.zip
26-NOV-2011 Update with working GPS. Disabled broken qcom egl so that Google Maps works (slowly). FIXED LINK
TeamICS-4.0.1-26NOV-GPS-HeroC.zip
28-NOV-2011 Updated kernel for better alignment with ICS. Lots of additional updates. Updated to fix wifi issue (wlan.ko replacement)
TeamICS-4.0.1-28NOV-NEWKERN.zip
01-DEC-2011 Updated kernel to support network stats (Data usage). Modified LatinIME to show entire keyboard. Synced with CM/AOSP repos.
TeamICS-4.0.1-01DEC-HeroC.zip
06-DEC-2011 Updated with test fix for random app crashes (phone, exchange, popups, etc.)
TeamICS-4.0.1-01DEC-HeroC.zip
18-DEC-2011 Updated to latest AOSP/CM 4.0.3 source base. Fixed trackball. Replaced Gallery2 with older Gallery for the time being. This has major changes to the source base and limited testing, so backup is recommended.
TeamICS-4.0.3-18DEC-HeroC.zip - Currently offline while resolving some issues
18-DEC-2011 Updated to latest AOSP/CM 4.0.3 source base. Update from earlier post to add audio driver fixes, and su updates that restore Superuser functionality.
TeamICS-4.0.3-18DEC-HeroC-AUDIOFIX.zip - Currently offline while resolving some issues
20-DEC-2011 Back to 4.0.1 for the time being, until 4.0.3 issues can be resolved. This version has all of the standard fixes including radio/data, trackball, and audio. Also includes Gallery instead of Gallery2.
TeamICS-4.0.1-20DEC-HeroC.zip
22-DEC-2011 Minor update to include fixes for Headset (Audio Jack) and Dictionary/Prediction.
TeamICS-4.0.1-22DEC-HeroC.zip
25-DEC-2011 Add basic Bluetooth functionality. Additional testing in progress. Classification changed to Beta, as all major functionality is working except for Camera and Hardware Acceleration.
TeamICS-4.0.1-25DEC-HeroC.zip
01-MAR-2012 Integrating development with Evervolv team. Brings alignment with ICS 4.0.3 development.
Evervolv-ICS-2.1.0-01MAR-HeroC.zip
GAPPS
You can use the latest ICS Gapps from here. Or other Gapps of your choice.
FAQ / Fixes
DATA ISSUES
If you are having issues with Data try the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
If you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
KEYBOARD ISSUE
Attached below is a replacement keyboard that doesn't have the bottom row off-screen. This is just a quick hack to get a functional keyboard. After some clean up and testing, I will include it in the releases going forward. Just replace the existing /system/app/LatinIME.apk with this one for the time being.
Reserved 2
This is also reserved for later use.
Nice.
Sent from my HERO200 using XDA App
I've got work in an hour........ so here we go, I'll let you know what happens.
whoa man, already? YOU GUYS ARE AWESOME!!
p.s- happy thanksgiving btw!!
edit:btw downloading it right now,, going to give it a go
---------- Post added at 10:45 AM ---------- Previous post was at 10:03 AM ----------
hmmm after the HTC screen, i get a black screen showing nothing. Plugged the charger and shows charging light.. Still waiting for it, it's been like 3 minutes. im on 170 40 mtd settings. K nvm it setup just appeared. For those that are trying, wait for it.
EDIT: K been messing around with it (sorry for all these edit, just trying to prevent a lot of posts and I am awake this late so might as well show some heads up) but problems I found
1) Keyboard is half (missing space bar and the alt function)
2) Screen orientation is choppy
3) Im missing the actual market app, might be firerats issue
I found a pointless feature.. but using the trackball brings up a cursor lol didn't know it'd do that. Making it "click" u have to press the ball then scroll quickly rather than just keep clicking the ball.
Thank you ICS Team. Other than the items listed in the OP, I cannot get data to work. Phone is stuck on No Service and every few minutes will jump to roaming and then back to no service. If I try to call a number with the dial pad, the dial pad disappears after I press send, I assume this is because I have no cell signal. Could not test google apps due to no data. I was still able to play with the home screen, widgets, etc.
@ Majin101, my keyboad seems to be working ok, I do have the market app but haven't tried to use it yet. I am not using firerats mod. If anyone else tries to flash this, make sure you wait a few minutes for the rom to boot as mentioned in the above post. You will see a blank screen but it will eventually boot.
This is going to be a great rom. If you use a different keyboard you also get space and alt to show up.
Findings.
Okay, Seems nice. There is no bootscreen, so be patient, when setting up, choose "setup wizard"(this is kind of a no brainer, but you never know). Alright:
1. Data isn't working, I changed the roaming settings, but it didn't help.
2. As mentioned in an earlier post, the keyboard is missing some keys.
3. I do however have the market application. I used the gapps in the op and am using firerats 160 40
Really amazing work. The fact that this is even running on my hero amazes me. And they thought it would have trouble with eclair
Freeroot said:
Okay, Seems nice. There is no bootscreen, so be patient, when setting up, choose "setup wizard"(this is kind of a no brainer, but you never know). Alright:
1. Data isn't working, I changed the roaming settings, but it didn't help.
2. As mentioned in an earlier post, the keyboard is missing some keys.
3. I do however have the market application. I used the gapps in the op and am using firerats 160 40
Really amazing work. The fact that this is even running on my hero amazes me. And they thought it would have trouble with eclair
Click to expand...
Click to collapse
Data is working well for me with the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
Try that, and if you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
As i was installing in cwm i got an error stating "random offset: 0 x 150" yet the rom still installed. Any ideas as to what this was/is?
jaybob413 said:
Data is working well for me with the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
Try that, and if you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
Click to expand...
Click to collapse
Alright, that did the trick. Really nice work.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
rizdog23 said:
As i was installing in cwm i got an error stating "random offset: 0 x 150" yet the rom still installed. Any ideas as to what this was/is?
Click to expand...
Click to collapse
I got the same error. It booted just fine and I thus ignored it. Would be nice to know though.
For those that want to fix the keyboard, just download ics keyboard from market. For those that cannot download from market, use root explorer to go into "cache" and create a folder named "downloads", for those that want to increase scrolling speed etc., flash the TweakZ.zip found in the android general forum here at XDA. I would also recommend setCPU.
I also got Random Offset 0x1ba. Once rebooted, HTC screen showed up then black screen. I waited 10 min but it looked frozen. So I pulled the battery. Then I accidentally formatted my SD card and the fun was over.
Sent from my HERO200 using Tapatalk
The "random offset" comment has to do with the flashing of the kernel. I'm not entirely sure but I think it has to do with the way the boot.img is packed. Should be harmless though..
Good to see you'll got this thing running though.
Sent from my PG86100 using Tapatalk
Another feedback!
pros
1) Ive been texting sending and recieving just fine no problems (havent tried mms)
2) Made calls talked fine (although my face kept hitting the end button..)
3) Installed swype, texting is fine now and changed the dictionary too english to get rid of those red lines under the words
4) Also increased pointer speed to just use the trackball if needed
other bugs:
1) Noticed that some of my notification doesn't make a sound or plays
2) When I play music its coming through the ear piece speaker rather than the back speaker
3) google map fails to login
Darn looks like I have to go back to CM7.1. People try to call me but my won't won't tell me someone is calling and their isn't any sound either. Also the gallery app opens but doesn't show pictures and apps are missing from the market but thats probably a build.prop issue.
-------
Just flashed without mtd and it seems to be working better. I'm receiving calls and can hear my sound now.
Great job guys! Running for about an hour and besides the above mentioned bugs, I've noticed one more.
When I put the phone on the charger it becomes unresponsive and the screen goes dark. No way to wake the phone nor is the charging led on.
The only way I can charge the phone is to do a battery pull and boot the phone while on the charger.
mines charging and im still able to use it?
Very Impressive, to say the least!
*note for the development team - you are the F-ing man!!!!
Hi all,
First off, I tried posting this in the Q&A section but it said I did not have permission to do so (even though the rules prohibit you from posting in the developer threads and direct you to the Q&A forum )
I just upgraded my Samsung Infuse to the latest Jelly Bean 4.2 CyanogenMod10 ROM. Everything went smoothly, however, I am noticing a few issues, some of which are quite important:
1- The time is 5 hours ahead. I used network-provided time and the minute is correct, but it is +5 hours. So instead of 2:19PM right now, it's 7:19. If I set it to manual time, it seems to stay correct, but I would prefer to let the network handle it, and as soon as I turn it back on, it changes immediately. So...is it thinking my time zone is incorrect or something?
2- My device isn't syncing with the Google Play website. I access the app on my phone and even started downloading some apps, but when I go to the Play website it says I haven't accessed it from my device yet, and it also says "you have no devices".
3- I swear I am not going crazy, but the first time after upgrading I pulled down the status bar from the top and in the right hand corner there was a button which opened a screen full of widgets to toggle such as bluetooth, sleep, etc, yet now when I do that all I see is the date in the top left corner... where did that other button go?
4- Also not going crazy, but when I upgraded and saw the home screen, all I had was a screen for icons which is great. However, after a few minutes, a bar at the top appeared for Google search/voice. It appears on all of my home screens now, and it appears fixed. I cannot seem to remove it or adjust it at all. Where did this come from and can I remove it? I definitely do not want it there.
So far I am liking this modded ROM of JellyBean and I think everyone who helped make it possible, but if some of these things are in fact glitches, I may have to revert back to ICS (only upgraded to fix the Bluetooth anyway).
I am not sure if any of all of these issues are already known or not, but just looking for some general help.
Many thanks to anyone who can help!
I've finally decided to flip the switch, so the 14.1 nightly builds are running (though they are built only once a week, due to the current infrastructure limitations).
The official builds are signed with private keys (for good security reasons), so there's no plan to provide any unofficial builds by me, to avoid the hassle of switching between different keys.
I'd like to thank @Loader009 for the donation of his retired xt897 devices to me, it greatly helped to make the transition from 13.0 to 14.1 much less painful.
Please let me know about the issues you encounter when running 14.1. In the case of the device crashes, I need to see the output of "cat /proc/last_kmsg" from adb shell, captured after the device rebooted after the crash. Thanks in advance.
I've got it flashed on my RAZR HD XT925 JBBL with the DPI changed to 320. I bought it secondhand and it came with KKBL so I downgraded to JBBL. Most things run fine but some apps that render off the GPU like Temple Run 2 and Subway Surfs show artifacts (random black squares and multicoloured artifacts). This occurs both in Lineage OS 13.0 and 14.1, what's the cause of this to occur?
I've noticed only two problems:
1 - NFC doesn't work properly. I can't read any tag. Android Pay also says, that device is not supported to use NFC.
2 - I use 2 custom layouts for physical keyboard and hot-keys like CTRL+Space don't work. I tried to modify the layout to make it work, but it doesn't work while typing (since space key in use, maybe)
I just installed it yesterday after a complete wipe (and format data/cache f2fs), and think I've got it all set up the way I like except launcher, and didn't run into any real problems yet.
I can't figure out how to get the expected shift/capslock behaviour from hardware keyboard. Still playing with settings.
It didn't come with an APN for freedompop but I found that info on another thread here, before applying that I didn't get LTE, only 3G or no data at all (at the places I've been in last day or so).
I dunno anything about NFC, but Android Pay installed for me with Aroma Gapps, haven't tried using it, doubt it'll work for tap-to-pay tho, as it didn't work for the last few versions of CM either, something to do with PN544 driver or something.
Did LineageOS come with trebuchet? I ended up with only the google now launcher, but maybe my gapps install erased trebuchet, I used aroma for the first time and may have selected things wrong... this one seems I can't customize much, can't get rid of google search bar, can't set background as solid color, can't set background color of app drawer at all which is back to a grid like kitkat.
Play store says firefox not compatible... dunno why. Maybe something I didn't select right with Aroma gapps, although every other app installed fine. Totally unrelated to LineageOS or our phone, but I wish I could find an idiots guide for aroma app selection, explaining what each app is for, particularly system apps I'm not familiar with.
edit: had one reboot, also had errors about MTP host stopping pop up...
enigma9o7 said:
I just installed it yesterday after a complete wipe (and format data/cache f2fs), and think I've got it all set up the way I like except launcher, and didn't run into any real problems yet.
...
Did LineageOS come with trebuchet? I ended up with only the google now launcher, but maybe my gapps install erased trebuchet, I used aroma for the first time and may have selected things wrong... this one seems I can't customize much, can't get rid of google search bar, can't set background as solid color, can't set background color of app drawer at all which is back to a grid like kitkat.
Click to expand...
Click to collapse
Trebuchet is the default launcher for LineageOS. Your Gapps deleted it. Also, if you use a smaller GApps, there is no google search bar ie its not installed. I personally use OpenGapps Pico.
Nightly build from 2017-07-28. Wi-Fi not working. Is it just me?
//EDIT: Tried older builds, too. Wi-Fi did not work with any of them. Flashed back to CM 11.0 and it worked again. Tried LineageOS 13.0 and Wi-Fi worked, too.
//EDIT2: Okay, I think I've figured it out. When I flashed the LineageOS 14.1 after I flashed the phone with previous versions, the Wi-Fi worked alright. It stopped working after changing File system to f2fs.
//EDIT3: Fine, I actually don't know, what happened, but I just changed the File system to f2fs again, flashed the phone with LineageOS 14.1 one more time and the Wi-Fi surprisingly works. I have absolutely no clue, why it did not work after the first flashing.
Shift key not working as expected
I already posted this in a seperate thread a few days ago, but I've got no response and it's driving me crazy, and I assume anyone who is still using this device is because of the physical keyboard, so probably relevant to all.
How do restore traditional "shift" behavior? I want to be able to press then release shift, and the next key I press is shifted. Right now I have to hold shift and another key simultaneously if I want capital letters or symbols from the numbers. I think there even used to be an LED that light up when shift was pressed/released until the next keypress, although I'm more concerned about how it actually works than the led...
I've played with most of the settings on the attached screenshot, other settings only seem to make things worse, sometimes making nothing happen at all for shift, sometimes putting out garbage, sometimes messing with capslock behavior (which is working normally with these settings, although no LED either)... but I certainly haven't tried everything.
If this is standard behavior for everyone using L14.1 and not a setting, is there a file I can modify or a 3rd party app, or anything, to get behavior I want?
rootdefyxt320 said:
I've got it flashed on my RAZR HD XT925 JBBL with the DPI changed to 320. I bought it secondhand and it came with KKBL so I downgraded to JBBL. Most things run fine but some apps that render off the GPU like Temple Run 2 and Subway Surfs show artifacts (random black squares and multicoloured artifacts). This occurs both in Lineage OS 13.0 and 14.1, what's the cause of this to occur?
Click to expand...
Click to collapse
hi
the version that you flashed in your xt925 was the oficial one released by LOS?
did u do any kind of port or mod?
enigma9o7: I've had the same problem sometimes back with the older builds of LineageOS 14.1. Try to clean flash it with the newest build from yesterday. I just tried to type something with the physical keyboard and the Shift button just worked "correctly".
EDIT: Okay, I think I've figured out your problem. You probably use the Asanti v2 keyboard setting. Switch it to Asanti v1 and the Shift key should work as expected.
Krlos Eduardo said:
hi
the version that you flashed in your xt925 was the oficial one released by LOS?
did u do any kind of port or mod?
Click to expand...
Click to collapse
It's the official 14.1 one for XT897.
rootdefyxt320 said:
It's the official 14.1 one for XT897.
Click to expand...
Click to collapse
without doing any port?
Should updates work thru the updater?
I just tried doing it, it downloaded succesfully, then rebooted into TWRP, but didn't do anything. So I tried installing myself (took me a while to find the file btw) and it failed zip signature verification. So I downloaded it on my PC, copied it over via USB, then tried again, and still fails.
kabaldan said:
I've finally decided to flip the switch, so the 14.1
Click to expand...
Click to collapse
@kabaldan, I noticed that a number of device trees in LineageOS now have a new branch of "lineage-15.0", but the xt897 does not. Is this an ominous sign that the xt897 will not be built for Oreo?:crying: or is just a timing thing at this early stage:fingers-crossed:
any hope for running it on mb886?
mb886 - atrix HD - ...you can test it if is your bl unlocked and twrp installed.
Mainboard have same base - msm8960. But i am now 100% sure if your phone is bl free unlockable. if not, then you can test to unlock it via sunshine.
I have installed this and for a while all was fine. But I was browsing in chrome when all of a sudden it froze and the phone restarted and went into a boot loop just showing the bootloader unlocked screen. I cleared the cache and dalvik cache from TWRP, which makes it boot, but any attempt to uninstall or launch chrome makes it happen again. Now it just seems to be happening at random without even opening chrome.
How can I wipe my device completely and start again? I know I can do a factory reset, but is there a lower level way to wipe it? I also saw something about changing the filesystem, is that worth doing (can it make it a bit faster)?
I have ordered a gemini PDA that I hope will arrive by late january or sometime in february, but I need this phone to get me through a couple more months!
Installed this a couple weeks ago, upgrading from a 4.4.4 CM after a number of apps I run on this finally dropped support. I did a complete wipe including the f2fs formats as suggested and it installed without incident.
I cannot believe how well it runs: keyboard works and lights up on pull out, turns off on close, hdmi port works, gps, camera+flash works. It really didn't lose any speed from my older install. Really well done, I was afraid there would be bigger problems but only a couple small ones so far.
The couple things I noticed: slow to get carrier signal and voice is garbled when using freedompop's dialer or google hangouts on the bottom mic. Slow signal seems normal, even 4.4.4 had this issue, though it can sometimes take a few minutes. Using a sound recorder shows the bottom mic working, but using fpop/hangouts dialer makes it garbled. Top mic, speaker phone, always works though. I don't have regular service to see is default dialer has same issue though, just freedompop free service which is just voip.
Still, this is a pretty awesome breath of life on this old thing. Ram holds it back somewhat but it's still pretty useful.
So I just wiped everything, repaired filesystems, and reinstalled. Data and cache were already f2fs so nothing to do there. But I noticed that during install it says:
twrp patching system unconditionally
unknown command [log]
unknown command [log]
Do I need a newer version of TWRP? I have 2.8.6. I noticed that at least 3.0 is available: https://forum.xda-developers.com/showthread.php?t=1887070
Here is 3.1.1-0 for you
https://drive.google.com/file/d/1vO4_nq3FNquuO3neHrOzuIb5gnmN11AZ/view?usp=sharing
CornholioGSM said:
Here is 3.1.1-0 for you
https://drive.google.com/file/d/1vO4_nq3FNquuO3neHrOzuIb5gnmN11AZ/view?usp=sharing
Click to expand...
Click to collapse
Thanks!
I've now installed the latest TWRP and reinstalled Lineage, gapps and su, and I didn't get any errors this time
But I have a really odd problem which I was hoping this would fix and it hasn't - I can't download certain applications from the play store, they say "Downloading" but they never actually start to download. Eventually either it mysteriously stops trying to download or I get an error message with code 492. It seems to be applications that are over a certain size. I've been googling but can't find any solutions that work. I have a lot of free space in all partitions. Did something with the directory structure get screwed up maybe? Seems like some problem with the dalvik cache I think, but wiping doesn't seem to help. I have no idea at this point
I recently got myself the pixel 2 xl after Leaving my OnePlus 3T and I found myself really miss some of the features and I have also have some weird bugs
Features
Locking recent apps: for example I use Spotify and if I dismiss the app the music stops so in my OnePlus I could lock it and then when I clear all I would stay there.
Floating button or a way to clear the recent apps and notifications without scrolling to the top of list just to be able to clear them all
Gestures when screen is off like turning the flash on or changing songs
Bugs
The double tap to open screen almost never works
The swipe to open sometimes just almost not work and I have to try like 10 times until I just give up and use the fingerprint
And sometimes the phone could just freeze even when not a lot of apps are open until I close the screen for 20 seconds and then it's back to normal
So if anyone knows a way to help fix the bugs or get back those features I would so happy
Since this is the Pixel 2 forum, rather than 2XL, some of your bugs may be better addressed in the other forum. I've no problem double-tapping to wake the ambient display (I don't need "always on"), have never had a problem with swiping and have not had a hang in 6 months with the phone.
As for features, those are presumably One+ additions, so "getting them back" means "adding them". From your description they sound like things that would need root, and I don't know whether anyone has made such mods for rooted phones. But why are you clearing all apps anyway? I don't think I've done that since 2011 or so, and cannot think of any reason to do it.
Large Hadron said:
Since this is the Pixel 2 forum, rather than 2XL, some of your bugs may be better addressed in the other forum. I've no problem double-tapping to wake the ambient display (I don't need "always on"), have never had a problem with swiping and have not had a hang in 6 months with the phone.
As for features, those are presumably One+ additions, so "getting them back" means "adding them". From your description they sound like things that would need root, and I don't know whether anyone has made such mods for rooted phones. But why are you clearing all apps anyway? I don't think I've done that since 2011 or so, and cannot think of any reason to do it.
Click to expand...
Click to collapse
About the root I have hoped to avoid that but I'll see what I do. And the reason i clear the apps is because the phone just freeze when more then 3 apps are open and I don't have any app that should Fu*k up the system'
Something is wrong with your unit then, because I agree with previous poster, clearing apps is not really needed since old android times, and could arguably be even worst ..
But this is the wrong place to ask, should post in Pixel XL 2 QA section
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!