Hey all,
I've been trying to hit this hard today to get the 810 that fell in my lap updated to the 8.1 (and possibly eventually 10) dev previews. But the dev preview app keeps saying I'm not registered as a developer when I definitely am, Windows Phone Developer Registration keeps saying there's a time mismatch issue, Nokia care doesn't seem to work...are basically all my avenues leading to dead servers and there's no way for me to pull this off?
Related
Updated to the latest firmware and noticed that they dropped the Never option for screen timeout. I'm kinda pissed because I have been using that for the past week or so and my Live Tiles were doing a much better job with it set to never turn off.
I'm one of the few people around here lucky enough to have a problem free phone. I've never had any of the problems that this new firmware is supposed to fix, so I really don't need it. I am seriously considering rolling back to the old firmware to get the Never setting back. Before I go through all the trouble with that, I just wanted to double check that the the Never setting is gone for everyone with the new firmware.
Does anyone out there with the new firmware still have Never as an option for the screen time out?
Nope, gone for me too. But, I kept mine set to 1 minute anyway.
Oops I posted a new thread before I noticed this. I'm pissed too. I used it with my car stereo and Zune. I used to be able to control music easily at a glance while driving (using cradle). Now it's too much of a process and dangerous. I also liked keeping it on while charging (why do I need a locked phone at home, sitting right next to me, not drawing power from battery?) What genius made this decision!
I have yet to find a single benefit for the new firmware on my phone. Seems exactly the same to me but with the Never option removed. I think I may try rolling it back with the Zune backup.
The Dell tech I spoke with in India actually told me to re-sync the phone, factory reset it and sync it again (at least that's what I think he said, I had to ask him to repeat himself several times as I don't think our English dialects were compatible). I'm afraid to try this. He also offered to send me my third replacement phone if this was unsuccessful. I think I'll just live with it. I'm so tired of dealing with Dell. According to my logs I've clocked in well over 7 hours of phone time with them. I try to remain loyal to Microsoft, but I think it's Android time. I feel so embarrassed when my buddy uses his Evo in my presence.
Hello everyone, my Nexus 7 (32gb Wi-Fi Model) has been randomly rebooting itself. I have unlocked the boot loader on it, but I have not installed any custom ROMs yet. I've mainly noticed it rebooting when I'm watching YouTube or using Google Chrome. Any idea on how to fix it? Thanks.
Just a test.
same here...
you know...
i would watch youtube, then put it down to go somewhere, when i come back to turn on screen ,
Quick tap of power button, no response... well not reboot but, shut down,
Im guessing it takes time from going back from deep sleep and i have no patience, or when i turn off the screen i push it a little bit too long...
Yours reboot?, like just WOah , rebooting device kind of thing...
unstable? overclocked?
Best app to help figure this out. Go into the options and check the top 3.LINK
Might be a shot in the dark but I had experienced reboots that was caused by HD Widgets (was acknowledged by them) and possibly Beautiful Widgets. uninstalling them cured my nexus 7 rebooting syndrome.
gokart2 said:
Best app to help figure this out. Go into the options and check the top 3.LINK
Click to expand...
Click to collapse
Currently giving this app a try. Hopefully this will shed some light on the situation. Thanks.
Jomari29 said:
same here...
you know...
i would watch youtube, then put it down to go somewhere, when i come back to turn on screen ,
Quick tap of power button, no response... well not reboot but, shut down,
Im guessing it takes time from going back from deep sleep and i have no patience, or when i turn off the screen i push it a little bit too long...
Yours reboot?, like just WOah , rebooting device kind of thing...
unstable? overclocked?
Click to expand...
Click to collapse
On my new 1 week old stock Nexus 7 32GB I've had a few random reboots too. Been reading around and trouble-shooting diagnosing the cause for it the past few days and my findings after viewing my debug log traces shows that the OS will reboot when it encounters a null pointer or invalid argument to a function call (or method call for you java programmers). When this error happens due to what seems to be any old app that was not developed for the new Android v4.2.x OS then the system will reboot itself to clear itself up. Ideally the new OS should be catching (detecting) when this invalid null argument or pointer situation occurs and gracefully clean up and terminate the offending app and the OS should just continue staying alive going along its merry way. But Google's new OS methods are not catching these sorts of errors it seems and thus the error is passed all the way up the chain of command to the main OS critical error handler which forces a reset and reboot. That's what is causing it. The solution I believe for now is to find all the old apps that you loaded onto the new device and by process of elimination remove them all. They are not 100% compatible to run on the new OS as of yet. Also report it to the app developer so that they can update and recompile their apps to work with the new v4.2.x java libs. That's my take and fix for now until Google developers add the try{} catch{} blocks to the proper places in their new OS implementation and release a new firmware to users.
Infobits said:
On my new 1 week old stock Nexus 7 32GB I've had a few random reboots too. Been reading around and trouble-shooting diagnosing the cause for it the past few days and my findings after viewing my debug log traces shows that the OS will reboot when it encounters a null pointer or invalid argument to a function call (or method call for you java programmers). When this error happens due to what seems to be any old app that was not developed for the new Android v4.2.x OS then the system will reboot itself to clear itself up. Ideally the new OS should be catching (detecting) when this invalid null argument or pointer situation occurs and gracefully clean up and terminate the offending app and the OS should just continue staying alive going along its merry way. But Google's new OS methods are not catching these sorts of errors it seems and thus the error is passed all the way up the chain of command to the main OS critical error handler which forces a reset and reboot. That's what is causing it. The solution I believe for now is to find all the old apps that you loaded onto the new device and by process of elimination remove them all. They are not 100% compatible to run on the new OS as of yet. Also report it to the app developer so that they can update and recompile their apps to work with the new v4.2.x java libs. That's my take and fix for now until Google developers add the try{} catch{} blocks to the proper places in their new OS implementation and release a new firmware to users.
Click to expand...
Click to collapse
Awesome! Thanks for the tip! I spent the last week slowly removing apps and re-installing them and I think I've solved the problem.
Hello.
I enjoy my Nexus 7 2012 (Wi-Fi 32GB) tablet very much, when it is working properly and, unfortunately, that hasn't been often for some time. Android 5.02 helped a bit and the tablet is currently running 5.1 from a OTA update, which seemed to help a bit more. Android 5.1.1 has been mentioned however, I am not sure my issues will be helped by an update. For this reason, I am here to ask for advice or suggestions as to what I should do next (if anything!)
My first issue was the battery. The battery only lasts four hours per charge and since it is the original from 2012, I have ordered a new one and am awaiting its arrival. This tablet was a gift and whatever warranty it had has most likely expired so I am not concerned about invalidating a warranty. I hope that a new battery will make a big difference.
However, it is the second problem that is really annoying. The screen on my tablet freezes often, in any program and at any time. After charging the tablet, I've learned that it is best to restart the tablet to prolong the amount of time before the tablet freezes for the first time. Reading an article, for example, is a problem as I can read the first page but when it is time to slide the screen up to scroll to the next page, I am at risk of the screen freezing and it definitely freezes before page three. When typing a comment on Facebook or Twitter, etc. either they keyboard freezes while typing or if I can type the comment, the screen freezes before I can press the send key. I have other ways that are less portable to access these types of programs however, portability is the reason for a tablet. Using the tablet as a reader, I usually do not have any problems swiping page to page for usually as long as I'd like (although the swiping motion is a potential problem outside of the reading app.)
I backed up the tablet just prior to the 5.1 update and reset it to factory settings and for almost a week the difference was amazing. However, even with 5.1, the tablet is back to freezing again. Regarding the 32 GB internal storage; the actual available space after the OS is 28.17 GB and my available 23.90 GB. Due to the tablet's lack of response, I only reloaded a small number of apps and then, with the screen freezing multiple times in the four hours the battery allows, I uninstalled even more apps to get where I am now; I have never exceeded 50% at any time. In a browser, I often have more than one window open, yet it is the only program open. Sometimes, Facebook and Messenger are open at the same time but not always. If I get an incoming update, such as CNN, etc. if I open that for a few minutes, I'm risking another freeze. I am continuously aware of what programs are open and close them with the bottom square icon on my tablet. I have two frequent errors: SYSTEM UI is shutting down and the Process System is shutting down and they happen often. I am using Nova Launcher and the other Launcher on the tablet has been force stopped. I should probably note that I did the cache cleaning process two different times before I reset the tablet to factory settings.
Would going to something like the Cyanogen Mod be of assistance with this situation? There is an Official CM12 Mod available for this tablet however, the article I am referencing is from January 2015, written by Vinod Yalburgi titled, "Update Nexus 7 2012 (grouper) to Android 5.0.2 with CyanogenMod 12 official ROM." The tablet is already at 5.1 though and, as you have surmised correctly, I am not fluent in Mods of any type so I am unable to determine which mod is the best in this situation or if a mod is not going to be the right answer. I am open to rooting the tablet; the huge benefit I'd appreciate is the ease of creating a full back-up.
Is there another, more appropriate solution? My main concern is that if I wait for Lollipop 5.11, whenever that might be, it will not improve the issue with the screen freezing and I will have waited longer and ultimately gotten nowhere. Going back to KitKat 4.4 as I have read others have done is not appealing but if is the best solution . . .
Thank you for your patience with all of these details. I am hoping that with this info and all of the experience here, you can help me move in the right direction. Your time and any and all of your helpful suggestions are appreciated! This tablet can still work very well and as it was a gift, I want to make it work (on the days I do not want to hit it with a hammer!)
CShirey
I had the same freeze ups after the 5.1 update. I reset it 3 times to no avail! So I went back to KitKat 4.4.4. This lollipop is a big SUCKER, if you ask me... Google has screwed the pooch on this one.
? Take me to your Leader ?
Not the option I was hoping for but maybe the solution!
eLCruz said:
I had the same freeze ups after the 5.1 update. I reset it 3 times to no avail! So I went back to KitKat 4.4.4. This lollipop is a big SUCKER, if you ask me... Google has screwed the pooch on this one.
Take me to your Leader
Click to expand...
Click to collapse
Thank you for your suggestion! Does your tablet work well with KitKat 4.4.4? Any problems with freezing and battery drain? I have continued on with my research on this trying to determine what other owners have done in a similar situation. Lots of complaints but not a lot of answers, so far!
CShirey
General surprise at the lack of helpful replies!
I am grateful for the reply I received however, I am disappointed in the general lack of interest. Whenever I come to review posts here, I see that generally, most posts receive multiple answers. I am in the right forum . . . Is my question considered to be too simple . . . or did I miss an unwritten rule? Thanks.
CShirey
Sorry, had turned notifications off and forgot. It's working smoothly on 4.4.4! Should have never updated, IMO. I believe lollipop will be Google's windows vista... Hope every thing works out.
?Here, there be Whales...?
i've read similar problems with other users who sought help from the meizu-flyme websites but they won't respond with anything better than a canny reply that they will be looking into it. it's been months since this problem popped up and its amazing that nobody finds anything that specifically addresses this particular product. someone suggested that it is the manufacturer that can provide a valid and lasting solution to this by providing the source code of the os. but even so, i am just a curious cat daring to get killed or be delivered by its boldness. i just can't believe that it is so difficult to gain access to my m2 note again even as it keeps me from doing so and still receive phone calls from it and let me listen to my music with it. No modifications were made to it except perhaps getting root access but I am not sure if debugging was activated before i was shut out from getting in due to this flyme lockscreen pattern that id completely forgotten! i did try the new security flaw that's just been discovered wherein you try to put in a very long string when making an emergency call with it. But when i get to the next step in using the camera, it just won't show the notification shade where i can proceed with what is expected to be done to crash or hang the unit! there is a factory mode that i can boot into but i find no suggestions on what i can do from there. in fact i can even upgrade it successfully (i can watch it go through the process) and it would later inform me that it was successfully done but still the pattern lock would still be there! before it locked me out i managed to link it to my wifi so it is actually online but i don't know how good that is if it could solve my problem at all.
Whew, this is a large site! I believe I'm posting in the right area. If I'm not, would the moderators please move it?
As brief as I can: I have a Nexus 7 (2012) that I bought brand new because I never had an Android device. It was useful until I mistakenly upgraded from Jelly Bean to KitKat to Lollipop, at which point it stopped being useful (a known issue, I've since learned). For the last couple of years I've pretty much only used it for playing Candy Crush, and even that crashes and gets w_a_a_a_y slow. It has survived being thrown across the room!
Recently I read that upgrading to Marshmallow or even Nougat could breathe new life into the tablet. Problem is, I've never rooted a device, and all the instructions I've read have been frustrating, often leading to dead links for downloads, etc. I did manage to root the machine, although how I'm not sure. I have the TWRP recovery mode, which is well-designed, and I even managed to flash Nougat to the device.
However, when I boot the device, after an interminable long time, I get into the Lineage startup screen and have to go through the time set, network connect, language setup process. And then I have only the apps that have been pre-installed; none of my old apps (like Candy Crush) are available, although attempts to download and install them result in being informed that they are already installed.
I've done a recovery from the data partition, but nothing works. Google Play services reports it needs to be updated, but crashes when I try to do so. In effect, I have a working Nougat Nexus 7 -- as long as "working" is defined as using only the built-ins.
Could I be pointed to a soup-to-nuts, clearly written instruction set that walks one through the upgrade process? Not only the HOW but the WHY! I'm no stranger to computers, and have plugged the Nexus 7 into both Mac (preferable) and Windows 10 computers, and can evern use Linux if that's the best way. I'm not afraid of the command line, and have adb and fastboot on both workstations. I'm just stuck trying to figure how to put it all together. How can I get my Nexus 7 wi-fi running a modern OS with the apps I previously installed?
Thanks to all who read this entire post!
fpuhan said:
Whew, this is a large site! I believe I'm posting in the right area. If I'm not, would the moderators please move it?
As brief as I can: I have a Nexus 7 (2012) that I bought brand new because I never had an Android device. It was useful until I mistakenly upgraded from Jelly Bean to KitKat to Lollipop, at which point it stopped being useful (a known issue, I've since learned). For the last couple of years I've pretty much only used it for playing Candy Crush, and even that crashes and gets w_a_a_a_y slow. It has survived being thrown across the room!
Recently I read that upgrading to Marshmallow or even Nougat could breathe new life into the tablet. Problem is, I've never rooted a device, and all the instructions I've read have been frustrating, often leading to dead links for downloads, etc. I did manage to root the machine, although how I'm not sure. I have the TWRP recovery mode, which is well-designed, and I even managed to flash Nougat to the device.
However, when I boot the device, after an interminable long time, I get into the Lineage startup screen and have to go through the time set, network connect, language setup process. And then I have only the apps that have been pre-installed; none of my old apps (like Candy Crush) are available, although attempts to download and install them result in being informed that they are already installed.
I've done a recovery from the data partition, but nothing works. Google Play services reports it needs to be updated, but crashes when I try to do so. In effect, I have a working Nougat Nexus 7 -- as long as "working" is defined as using only the built-ins.
Could I be pointed to a soup-to-nuts, clearly written instruction set that walks one through the upgrade process? Not only the HOW but the WHY! I'm no stranger to computers, and have plugged the Nexus 7 into both Mac (preferable) and Windows 10 computers, and can evern use Linux if that's the best way. I'm not afraid of the command line, and have adb and fastboot on both workstations. I'm just stuck trying to figure how to put it all together. How can I get my Nexus 7 wi-fi running a modern OS with the apps I previously installed?
Thanks to all who read this entire post!
Click to expand...
Click to collapse
I'm not sure but it looks like you haven't installed Google apps.
Wysłane z mojego SAMSUNG-SM-G890A przy użyciu Tapatalka