Related
Every time I've turned on my phone for a while, it's gotten through the startup screens (Welcome to NOW etc) and then the desktop background and phone button shows up (no icons) and there's a little window in the middle of the screen that says "loading.." with the spinning dotted circle. That goes on forever it seems like.
About a week and a half ago, it came up to the desktop and my icons were rearranged and some were missing. I moved them around and put the folder that was deleted back on the desktop and put my regularly used apps into it. Then another time, all the icons were gone completely and I had to go to Personalize settings and restore my last used (unsaved) theme (not sure if that's the right word).
Now whenever I reboot, it just goes to the "loading..." thing as mentioned above forever and it's kind of a surprise what the desktop will look like.
I'm not sure when this started happening but it seems like some time after the Sprint voicemail app automatically updated itself a few weeks ago.
I'm gonna go out on a limb here and assume you're still running stock. Why don't you flash one of the lovely roms we have here? That'll fix that problem. You may end up with other problems, but that'll fix your original problem.
Or... try wiping some caches and dalvik and see if it'll clean up some and load better?
Sent from my HERO200 using XDA App
I'm actually running Nfinite's rom from about a year ago. I see that there's an updated version of it but with the mediafire links broken I can't get it. I'm also a newbie so I'm not sure how to wipe caches and dalvik. Will do some (re)reading and see if I can get back to speed enough to do that. Thanks.
A weird thing has been happening to my S5 since I got it, both before and after rooting. For some reason, not all widgets want to stick to my homescreen in the stock Samsung launcher. When I first got the phone, they all worked, as far as I could tell (I didn't investigate fully at the time, since I had no reason to suspect that they wouldn't work). After a little while, though, I found that I couldn't make Beautiful Widgets widgets stick. I long-pressed the homescreen, chose BW, selected a widget style/size, and customized it in the BW menu, just like it's supposed to work. But no widget appeared on the homescreen. What was weirder was that in the BW app itself, it listed my widget as working, even though it obviously wasn't. Uninstalling/reinstalling the app did nothing but clear the "existing" widget I had created from the list within the app interface.
At first, I thought this problem was limited to BW, so I just got rid of it and decided to jump to another app, but then I found that HD widgets didn't work, and another similar clock/weather-style widget group wouldn't work. Thinking maybe I had created some sort of data corruption, I did a factory reset, which worked for a while, but eventually the widgets stopped working again. After rooting, and finding that the problem still existed, I factory reset again, and started putting my apps back on one at a time, testing to see if it was a conflicting app causing the problem. No luck. The widgets worked until some random time when they simply no longer would.
I finally resolved to go without this kind of widget, since it wasn't a necessity, just a convenience. The problem is that I've now noticed that other kinds of widgets aren't working, either, including some that I'd really like to have work, like the Tasker timer widget.
Has anyone else noticed this problem occurring on their Verizon S5s? I'm going to look into which widgets actually still work (because some do), and which don't, and compile a spreadsheet, see if I can come up with a reason. I doubt I'll be successful, but it might be useful for other people who actually know how to fix things.
PS. Another weird thing is that the widgets stick to Nova Launcher homescreens just fine. Now, that would be okay, except that I want to do some theming now that we can flash some ROMs, and I thought that theming only applies to the stock launcher. Plus, I'm guessing that this isn't normal behavior and I do want to find out why it's happening, not just use a workaround.
After some more digging, I've found that, with only a few exceptions, the widgets that require some sort of customization before placement on the homescreen are the ones that don't work. All widgets that are simply "click-and-drop" work fine. But, if I click a widget and it opens up a configuration page, 9 times out 10 no widget will appear on the homescreen after the configuration.
It doesn't seem to matter what size the widget is, whether the widget's app is stock or third-party, or if it is solo on the widget page or part of a group of widgets from the same app.
Plus, there are some exceptions to this, such as Google Play widgets, Mint, and Email Me Pro. Others work sometimes, depending on what configuration you apply to the widget. For example, the stock Picture Frame widget works when you shuffle the pictures, and doesn't when you choose where to draw pictures from.
Very strange. I'm thinking my only course of action might be to go nuclear and flash a completely different stock image onto my phone through Odin. I downloaded one from this post: http://forum.xda-developers.com/showpost.php?p=53437805&postcount=1289. If I'm correct, this tar image should be exactly the same as the one that was on my phone from the factory, presumably minus whatever problem mine currently has. We'll see how it goes, I guess.
Okay, so flashed the tar image through Odin, reloaded some stuff without rooting (yet), and everything seems to be going fine so far. I'm pretty sure that by this point in my previous experiment, the widgets had stopped working. I think it must have been some sort of corrupted file deep inside my system that isn't there now.
Hello good Samaritans,
So my issue is that since I tried moving via SmartSwitch my conversation history from my iphone 4s back up to my new Samsung Galaxy s5, there are issues with the stock messaging app. At first it would not let me scroll properly the list of conversations (jumping back up), and the history of those conversations (jumping back down). I don't know if it's because I already had new messages on that phone beforehand. Rebooting would make the problem go away temporarily, but then it'd be back. After I deleted the "SmartSwitch" folder from the phone manually, the jumping hasn't happened again (so far) but I think the stock messaging app is still much more laggy than it was before I started using that infernal NotSoSmartSwitch. Also, strangely, most of the conversation history I transferred from the old phone disappeared, but not all.
Has anyone had similar experience? How can I restore my phone's lost innocence (that is, how do I get rid of any leftover harmful effect of PrettyDumbSwitch, such as the lagging), preferably without resetting the whole phone?
Thanks!!
- Jenny
Jenny666 said:
Hello good Samaritans,
So my issue is that since I tried moving via SmartSwitch my conversation history from my iphone 4s back up to my new Samsung Galaxy s5, there are issues with the stock messaging app. At first it would not let me scroll properly the list of conversations (jumping back up), and the history of those conversations (jumping back down). I don't know if it's because I already had new messages on that phone beforehand. Rebooting would make the problem go away temporarily, but then it'd be back. After I deleted the "SmartSwitch" folder from the phone manually, the jumping hasn't happened again (so far) but I think the stock messaging app is still much more laggy than it was before I started using that infernal NotSoSmartSwitch. Also, strangely, most of the conversation history I transferred from the old phone disappeared, but not all.
Has anyone had similar experience? How can I restore my phone's lost innocence (that is, how do I get rid of any leftover harmful effect of PrettyDumbSwitch, such as the lagging), preferably without resetting the whole phone?
Thanks!!
- Jenny
Click to expand...
Click to collapse
Well, I didn't read everything that you wrote because you're not using paragrahs for some reason. Which made your post too hard to read. But if I got the gist of it, you don't like the effect of smart switch on your SMS app. And you want to know if you can completely revert the smart switch settings.
The best way to revert settings is to restore a backup. If you didn't make a backup, that is something that you should take time to organize.
Simply turning off smart switch should stop it. But some apps also require that you clear the app and system caches. So go to Settings > Applications > Application manager > all > smart switch. Assuming that you can find it (sometimes apps show up under somewhat different names), choose clear cache. Then clear data. The latter step is basically setting the app's user settings back to default.
Then go to recovery mode (ensure that your phone is powered off, then press and hold volume up + home + power) and choose wipe (system) cache from the on screen menu.
Should you have ongoing problems and no backup to restore.. then the last resort would be to do a factory reset and /or reinstall the stock firmware with Odin or Kies. The former erases user files and defaults settings. And the latter will replace all system files.
.
That was bloody difficult to read
Sent from my SM-G900F using XDA Free mobile app
Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
DrPhant0m said:
Seeing as though there's no more BajaROM thread, I'll post this is in the general Q&A section. Of course, while I am running BajaROM, I can't be sure that the ROM had anything to do with it.
Something weird definitely happened to my phone last night... at exactly 2:28am, it would seem.
When I woke up this morning, my live background changed to a different static background, my normal keyboard (thumb keyboard) was replaced by the samsung one, my clock widget was frozen at 2:28, the battery level read 87% (after charging all night), and hasn't changed all morning, even after an hour commute of phone calls and media play... tasker had inexplicably turned off... and I'm still finding odd things.
I restarted my phone, and my clock is more current now, but my clock widget and the statusbar clock are a minute apart for a portion of every minute (like they're offset by <60sec) Tasker still didn't turn on like it should have, until I started the app to spark it... as if it was the first time I installed it. (It does the same thing when I restore the app through Titanium Backup on a new ROM install)
I checked to make sure I still have root by starting Titanium Backup... I have root, but titanium backup says it's the free version now... when I normally have the Donate (Pro) version. I had to reinstall it from the Google Play store
I have a few nightly backup/refresh items scheduled in Titanium Backup at 2am and 2:30am... so I wonder if something went wrong.
If anyone has experienced similar issues, leave a comment.
Thanks!
Click to expand...
Click to collapse
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
TheAfroSamurai said:
This won't help you understand what's going on but for what it's worth I'm running Baja 16.1 and it's just fine. I don't use any exposed or wanam modules. Think that might be the culprit? That is if you run any..
Click to expand...
Click to collapse
I do run some (several) xposed mods and wanam/gravity box mods, and have been for quite some time on several devices. A string of bizarre events like that hasn't happened though.
It is strange, though, that I did install XToast just last night. This is an xposed mod that gives you more control over the toast messages received under different circumstances. Could be the culprit... not sure. I think I'll disable it and go back to BurntToast, a mod that does similar stuff.
Maybe switching from one to the other borked something?
Thanks for the input.
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
armadiljo said:
I also experienced some weird behaviour. I do suspect Titanium tp cause the problems, but I'm not yet 100% sure...
Not all of my issues are completely the same as yours, but still similar.
First of all, my device is a Galaxy S3 mini, CM11 installed, rooted, XPosed installed with several modules (but no Gravity or Wanam). All partitions are in ext4, external SDcard is in exFAT.
(1) root: During startup, Titanium asks an awful lot of times for boot access. Sometimes it does for 50-100 times. In the end, devices will still be rooted but startup takes a long time.
(2) startup: As mentioned: takes really long. With EVERY reboot, I get the "Android is upgrading..." message for about a minute.
This issue is solved by clearing all .odex-files with Lucky Patcher.
(3) Keyboard. I used Google Keyboard as my standard keyboard, but a while after installing/flashing (10 minutes to an hour) Google Keyboard uninstalls spontaneously (without interaction). This happened with all Keyboard versions I tried, in system and in data. And with or without it checked as primary keyboard in language & input settings. (because of those issues I switch to SwiftKey)
(4) Background: Background (custom wallpaper) disappears after a crash, and instead I get a static generic Android wallpaper. Also, every time I try to set my wallpaper back, device instantly reboots. (soft reboot which crashes and goes into a full reboot)
(5) Clock freeze: I've had those clock freezes a few times, but months ago. I think in my case it was due to some bad code in the ROM, not Titanium.
(6) Root: Even though in SuperSU settings I asked to remember autorisation, and automatically grant access, but after every boot, I had to grant permission to all apps using root access over and over again.
In order to try to solve my problems, I changed a few things.
- Google Now Launcher + XGelSettings instead of Nova Launcher. This didn't solve any of these problems, but I do like GNL more now
- I'm using Titanium Backup 6.1.5.4 stead of latest version, installed as a data app.
- I'm using SuperSU 1.98 instead of latest version, flashed as a system app.
- I'm using an older ROM version (CM M5 instead of CM M9/latest)
Most of my issues are gone now. I didn't check for (3) anymore.
Click to expand...
Click to collapse
Thank you for the information. I kind of suspect that Titanium Backup had something to do with my problems, as well, since it happened right around the time that a scheduled action was to take place. I think that TB was still in the middle of the previous operation at 2am when it tried to start the next one at 2:30. This has never caused a problem before, but maybe it was at the wrong place at the wrong time, as odd as that may sound.
Your problems seem to be a more constant hassle. Especially the parts about granting SU access several times. I'm leaning toward the fact that your external SD card might interfere a little. External memory is handled a lot differently in kitkat builds, which CM11 is. In newer custom ROMs, there are attempts made to "fix" it... but in your case, maybe it was counter-intuitive.
The issue is that, to paraphrase... Kit-Kat imposes a lot of data access restrictions on external media. So... if you create a file in one app... you can't modify that file in another. That's a bastardization of the whole thing, I'm sure... so look up the particulars from someone more qualified than I. haha
If I were you (and I had a few hours to burn)... I'd back up everything on your external card and your internal memory (a good idea in any case),
clear EVERYTHING and reinstall the latest versions of everything without the external card in your phone. See if you still have issues. If you don't, then the card might be a problem. Then, wipe the card and put it back in your phone, and let your phone reformat it. At that point, copy your backed-up card data to your external card in whatever way is best to keep KitKat from messing it all up again.
Luckily, I don't have issues with my external card, except for the fact that, say, if I want to put a picture of my son as my wallpaper or notification shade background... if I pick a file from the card, it won't load after I restart my phone. For stuff like this... make sure that you put the pic ON YOUR PHONE STORAGE. Consider it like this... you wouldn't have a lot of luck if your PC's desktop background or screensaver ran from the CD drive, as opposed to your hard drive.
@DrPhant0m
I already went to that process of backing up, wiping and so on. Actually, I already did it twice.
The first time, I cleaned my device, installed latest versions of everything, went through the restoring process. But most of my mentioned issues still existed.
The second time, I cleaned my device again, did about exactly what you mentioned, but I restored some older versions of the ROM, SuperSU and Titanium Backup Pro. And right now, my issues are gone!
Actually, I didn't realise there are so many KitKat-related issues with SD. Maybe my pictures indeed are/where stored on a faulty SD. But it's reformatted now, and it works. And I actually don't know if that picture is stored internally or externally, I selected the picture with/by Google Photo. No idea how it handles is
I'm not saying Titanium certainly will be the bad guy, but I'm quite sure it plays it's part in it. Other issues are caused by the custom ROM. In the last few months, developers of that ROM don't give a **** about solving issues, and introduce one new feature after the other, most of them still highly experimental. Maybe that's another problem I can't control at all
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Michele31415 said:
I have found that Titanium always deletes my custom wallpaper and replaces it with the Samsung default every time I do a backup. It also changes my keyboard (normally Hacker's Keyboard) back to Samsung keyboard. It started doing this several updates ago.
Verizon Note 3, 4.4.2, NC4, stock rooted
Titanium Free 6.1.5.6
Click to expand...
Click to collapse
Every time you do a backup it does this? That's bizarre. Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund.
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
DrPhant0m said:
Every time you do a backup it does this? That's bizarre.
Click to expand...
Click to collapse
Yes. It is.
DrPhant0m said:
Or, do you mean when you restore a backup? I want to say to update to the paid version and see if it fixes it, and if not... request a refund..
Click to expand...
Click to collapse
No, I don't mean upon restoration. I mean I take a full backup (user apps + system apps), go off for a cup of coffee, come back, see that it completed OK, exit TI, and then I see that my background is back to the Samsung default and it I open something that needs keyboard, the keyboard is also back to Samsung default. I guess it was never enough of a bother for me to go to the trouble of buying it and then complaining. I figure that for free, I can put up with a minor annoyance.
DrPhant0m said:
What info do you back up when this happens? I could see restoring a backup working against you. For instance, if you restore your keyboard and maybe even some language/input system files... it might default back to the standard keyboard because your confirmation to use a 3rd party keyboard (which could theoretically log all of your keystrokes) is no longer valid.
Click to expand...
Click to collapse
I can see where you're thinking, but it happens right after *doing* the backup. I haven't even had the need to do a full restore yet, so I don't know what that would do.
DrPhant0m said:
The background thing is a different story. When Titanium Backup works well... when I restore all of my "MUST HAVE" stuff after a new ROM install... it will restore my live wallpaper, too. There are often times that TB will NOT "work well" and the widgets and wallpaper (among other things) aren't restored properly... not to mention the fact that I can not get my bluetooth pairings and known wifi networks to restore, whether I use snapshot or XML.
Click to expand...
Click to collapse
It's very odd, that's for sure.
It's here! Downloading it now and I'll flash it ASAP. Download link here, for those who want to give it a try:
http://developer.android.com/preview/download.html
I'm also gonna throw it out there: if you don't know how to flash this image you probably shouldn't. This is a developer preview and you are likely to run into far more problems than you would with the current official release.
I don't think it works with Nexus 9 LTE though
Edit: So you can flash the system, boot, cache and vendor img files using fastboot and get it working with just wifi. Just tried and successfully booted.
shenye said:
I don't think it works with Nexus 9 LTE though
Click to expand...
Click to collapse
no, probably not. it'll be no different from trying to flash the normal nexus 9 image with the LTE model. that image probably won't come out until the final release - this is just a developer preview after all.
Flashed (did a dirty flash, without performing a factory reset), but back to 5.1.1 now. At least in my case I found it impossible to use as a daily driver.
Issues discovered:
1. Settings panel (in notifications) had an extra white pane underneath. Once swiped away / clicked, the settings panel was not available anymore when dragging down from the notification area.
2. Home button not working
3. Unlock screen missing, on wake up the desktop is displayed, however swiping occasionally produces an unlock effect.
4. Facebook app crashes when trying to open it.
5. Holding and swiping up on the home button did nothing (instead of opening Google Now)
Other discoveries:
1. The application drawer now scrolls vertically. It has a search bar and the last apps (or maybe most used?) at the top, separated by a horizontal line from the rest of the drawer. When scrolling, only the search bar remains pinned at the top.
2. Profile icons on the right side, (only) the first time the notification panel is pulled down.
3. The notification panel opens wherever you swipe your finger from the top (not centered anymore).
4. The volume pane now has a drop down button on the right that reveals the other volume channels.
Warning: for me flashing back (again dirty flash) to 5.1.1 leads to a boot loop, where it boots, optimizes the apps, then throws a short Google Play Services has stopped and then black screen and reboots. Then does it again.
adancau said:
Flashed (did a dirty flash, without performing a factory reset),
Click to expand...
Click to collapse
I have no clue why you would do that then complain about what doesn't work.
JeeperDon said:
I have no clue why you would do that then complain about what doesn't work.
Click to expand...
Click to collapse
I was not complaining (I take full responsibility for flashing a preview edition). I was just describing my experience.
JeeperDon said:
I have no clue why you would do that then complain about what doesn't work.
Click to expand...
Click to collapse
So, to do this properly, do I have to unroot and go back to stock recovery? Or what's the best process when I'm unlocked, rooted, and with customer recovery already?
generosity21 said:
So, to do this properly, do I have to unroot and go back to stock recovery? Or what's the best process when I'm unlocked, rooted, and with customer recovery already?
Click to expand...
Click to collapse
You don't have to unroot and go back to stock (as this is not an update). If you go into the bootloader (adb reboot bootloader) and flash all the img files in the factory image (fastboot flash * *.img, where * is bootloader, boot, system, cache etc.) it will give you stock Android M. I'm saying flash the img files, as for me the flash-all thing didn't work (it complained about the system partition, apparently a common issue).
adancau said:
You don't have to unroot and go back to stock (as this is not an update). If you go into the bootloader (adb reboot bootloader) and flash all the img files in the factory image (fastboot flash * *.img, where * is bootloader, boot, system, cache etc.) it will give you stock Android M. I'm saying flash the img files, as for me the flash-all thing didn't work (it complained about the system partition, apparently a common issue).
Click to expand...
Click to collapse
Thanks! Can I skip the recovery.img and keep my custom recovery, or is that likely to cause problems?
generosity21 said:
Thanks! Can I skip the recovery.img and keep my custom recovery, or is that likely to cause problems?
Click to expand...
Click to collapse
I wouldn't. But you could experiment I guess (no guarantees though). Before you proceed make sure OEM unlocking is still on in Developer options, just in case.
Can someone who flashed it say some words about the the first impressions regarding performance ?
so after over an hour of trying to get it to work, i've finally got it to boot into the OS. i ended up having to force reboot it a bunch of times during the initial loading animation. interestingly, it showed a small warning for 5 seconds saying something like "your device has failed verification and may not work properly" with a red warning symbol on top, right after the bootloader splash screen.
before i force reset it (and reflashed the system image twice) it would get stuck at the loading screen for a very long time, much longer than what is normal for an initial boot on an encrypted device, and the top right corner of the tablet was getting very warm, meaning it was clearly working on something - maybe stuck in an infinite loop? anyway, installing my applications from a backup now and i'll get back about the performance and how it works.
something interesting i noticed right away is that when swiping down to show the notification shade, instead of always coming down right in the center it'll slide out from either the left, right or center of the status bar depending on where you swiped down. cool trick for making one-handed use easier i guess. i'll see if i can take a few screenshots once everything's set up.
oh, something else - there are a bunch of new neat animations everywhere. everything's a bit more fluid and there are some nice touches in a few places. not really something that can be explained without experiencing it though.
aside from the issues with booting up i haven't run into any other problems yet.
Flashed manually partition by partition, and erased user data before booting.
Absolutely no issues during flash and it booted on the first attempt.
It's currently restoring from my last Google backup, but so far a pretty easy experience (beyond flash-all being broken).
ooh there are a bunch of new battery optimization and battery usage tracking features, as well as a utility which tracks memory usage of various apps, and how often an app is running - and lets you choose whether to look at the past 3 hours, 6 hours, 12 hours and day.
foxmeister said:
Flashed manually partition by partition, and erased user data before booting.
Absolutely no issues during flash and it booted on the first attempt.
It's currently restoring from my last Google backup, but so far a pretty easy experience (beyond flash-all being broken).
Click to expand...
Click to collapse
I've noticed that the audio doesn't keep up with the keyboard if you type in any way reasonably quickly. Definitely seems slower to me so far compared with 5.1.1. I did a full clean wipe. I'm gonna do a restart once i install some stuff again and see if it clears it up. Noticed that the theme option under 'developer options' has an 'automatic' option, itd be pretty cool if it turned on at night for instance but its 10:24pm here in N.Ireland and it didnt go to dark mode when i chose automatic so who knows. Also see an option to enable/disable tap-to-wake, not something I want to disable but handy enough for those who do and maybe even potentially a small battery saving.
Jumpy audio through google play music, presumably related to the keyboard issue I was talking about. Still haven't restarted yet though.
EDIT: dark theme has enabled itself after i set the theme option to 'automatic', presumably because it's night time
seanashmore said:
I've noticed that the audio doesn't keep up with the keyboard if you type in any way reasonably quickly. Definitely seems slower to me so far compared with 5.1.1. I did a full clean wipe. I'm gonna do a restart once i install some stuff again and see if it clears it up. Noticed that the theme option under 'developer options' has an 'automatic' option, itd be pretty cool if it turned on at night for instance but its 10:24pm here in N.Ireland and it didnt go to dark mode when i chose automatic so who knows. Also see an option to enable/disable tap-to-wake, not something I want to disable but handy enough for those who do and maybe even potentially a small battery saving.
Jumpy audio through google play music, presumably related to the keyboard issue I was talking about. Still haven't restarted yet though.
Click to expand...
Click to collapse
Oddly, mine did go dark when I set the theme to automatic - I'm in England, so same time zone as you.
Can't say much else yet - still downloading my apps.
Quite a few force close pretty much immediately when I try to run them, but I'll let the restore take its course and reboot before making any firm judgements.
Given how generally poor my experience with my N9 has been to date, I'm prepared to put up with a few warts and teething issues.
adancau said:
I was not complaining (I take full responsibility for flashing a preview edition). I was just describing my experience.
Click to expand...
Click to collapse
I dont think its the fact that its dev preview that messed you up. By dirty flashing and then claiming it is not stable enough for a DD is stupid tho. If you want to truly experience it and not going around telling people you cant use it, then you should probably clean flash.
addicted1900 said:
Can someone who flashed it say some words about the the first impressions regarding performance ?
Click to expand...
Click to collapse
Its running great so far. Seem smooth for a dev preview. No FCs or other problems so far.
ilatimer1 said:
Its running great so far. Seem smooth for a dev preview. No FCs or other problems so far.
Click to expand...
Click to collapse
thanks. Then i will make the step tomorrow.
Does it still heats up like crazy when using Chrome?