Related
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
uncledavek said:
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
Click to expand...
Click to collapse
If you can get to the factory reset in the settings menu that would the first thing to do. And then check for an update. Make sure you set the wifi to not turn off and I would keep the screen from shutting off while downloading the update. Check in settings "about Device". If your not 3389 or higher then you need to update
I had this problem back in November when I first got my tab. Even though nothing seemed to work right, I was able to connect it to my desktop and push across clockworkmod v .08 and a custom rom. So, I never used the original rom more than 10 minutes.
If you can't get it connected while booted in original rom, then Bekit's NVFLash full restore procedure works really well. Just follow the steps carefully and it's a quick and painless factory reset to a known working rom.
These things are virtually unbrickable (is that a word?).
uncledavek said:
Just picked up the Viewsonic G Tablet. Got it back to my office, charged it, powered it on and the first thing i see is force close...wtf!
I am new to all of this so any suggestions need to be rather detailed.
Thanks
Click to expand...
Click to collapse
badfrog is correct. If you factory reset the device it should be fine from there - then you set up your wifi and get the update.
Go into your app drawer and choose Settings. I don't remember if you can do it from the menu button as I'm on a different launcher.
Inside Settings go to Security and select Factory Data Reset. Do this, the unit will reboot and come back up at which point you'll be asked to set it up. It may take some time. Set your Date and Time correctly and set up your Wifi and such.
Once that's done you'll likely get a prompt to update very soon after Wifi connects. DO NOT DO IT, yet.
Within Settings, go into Display and set the Display Timeout to Never.
This ensures that the tablet doesn't sleep or turn off your wifi while it's downloading the update. It's not likely to happen but if your connection is on the slow side and the timeout is set too low, it can mess things up.
Once you've done that, proceed to let the tablet update itself. Again, it may take a bit of time.
Once it's done, make sure you take not of what you have. You'll find this information under Settings in the About section. The last version I got was 3389 - but something newer MAY be there for you. If you get anything less than 3389 then you will have to wait until you get another notification for an update. I don't remember how they work - but I THINK you should get the newest one there.
Once you've confirmed you're on the most current build, It may not be absolutely necessary to do it, but I would factory reset again just to clear the 'gunk' of the older TnT out in case there is actually any.
When I got mine and powered it on the 1st time, I got a bunch of FCs. I powered off and then on, and no more FCs, and it was fine after that. I think I posted asking about that, and someone (roebeet, I think) said it was a known problem. I don't remember the TNT version, but it was the one before 3389, or one before the one before 3389.
Jim
It is a known problem, especially with the older firmware. Sometimes the FC's are so bad that you can't even get into the settings to do a data wipe.
I've actually called CS about this, as an example of why they need an offline updater of some kind to get around issues like these. Suggestion: if you don't want to install clockworkmod, at least try to update the firmware to the latest and greatest, via one of the newer stock ROMs we're retrieved:
http://forum.xda-developers.com/showthread.php?t=842000
That might get you enough access to get into the Settings menu and do the factory restore.
Now, from what I can gather, this problem stems from a faulty or dirty Micro-USB port. I tried compressed air, but it did nothing for me.
I decided to do a complete unroot, S-ON, factory restore and call HTC to see if I could get it fixed. To my surprise, the problem vanished. Thinking I had lucked out and that fixed it, I re-rooted the phone and the problem still didn't reappear.
Then, thinking I would start small, I flashed a Sense kernel. As soon as I rebooted it went straight to Car Home and began answering in speakerphone. For laughs I went ahead and flashed MIUI then CM7, both of which exhibited the same behavior.
After all of this, I got to wondering just why the stock ROM and kernel worked but nothing third party would. Then it hit me that all the 3rd party stuff I had been using were DHD ports, and not based off the Inspire. I downloaded and flashed ClearDroid, which has an Inspire base, and the problem is once again dormant.
The only sense I can make from it is that HTC has implemented some kind of fix for shoddy USB ports in the Inspire kernel.
So now here's the question: Does anybody know anything about this, and would it be possible to implement said fix in, say, and AOSP kernel?
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Also Im pretty sure when your rooted this setting will take effect as to where a nonrooted phone doesn't allow the permission to execute the command.
Gizmoe said:
When you flash a Rom there is a folder created called data on the root of your phone. This contains many files that control various settings on your phone. There is a file in particular where cardock settings get synced in data/data/Com.android.providers.settings/databases/settings.db. When you sign in with your google account some of these settings get restored to the mode in which you had it in when you wiped your phone. This is what causes some people to think that parts of their old Rom are bugging out their phone, I guess in a way it is, but its googles fault. The car dock is getting resynced to being on even though you haven't done anything. In order to fix it you must use SQL editor to open the database and look for the carmode or dock settings and set them back to 0. Once you do this it the next time the phone autosyncs it will save your newer settings.
Click to expand...
Click to collapse
I'll try that, but I can completely wipe my phone (cache, system, data, d-cache), flash CM 7.1.0, and without even logging into my Google account it happens.
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Agoattamer said:
Backing up to the beginning.....Are you flashing ROMs or kernels? Seems to me you are flashing ROMs but keep using the word kernel.
Why not just remove the car dock app from the ROM or use Titanium Backup to freeze it?
Click to expand...
Click to collapse
Both.
With the stock ROM and kernel, everything is fine. With the stock ROM and a DHD-based kernel it happens. With any AOSP ROM it happens.
Removing the Car Dock app keeps it from launching, but the phone still defaults to speakerphone for all calls (incoming and outgoing).
Gizmoe said:
After searching it seems this is a common problem with the phone. Some people where able to fix it and some where not. Even when it does go away for a while it will re emerge and get worse.
Some of the fixes are
1. turning airplane mode on for 10 min and then shutting it off
2. Changing chargers(dont ask me)
3. Blowing out port which you said you tried.
I am still not 100% its not some internal issue but why even bother if the hardware is malfunctioning.
I would start the warranty process and get it replaced.
Click to expand...
Click to collapse
The problem about warrantying it is when it's in a stock state, it works fine.
I've never dealt with HTC, but I can't exactly see it going over well if I call up and say "My phone acts funky when I run CyanogenMod".
The airplane mode fix is something I haven't heard before. I guess I'll give it a go.
I finally convinced my wife to join the Android ranks when the One X was released on AT&T earlier this year. She used an iPhone 4 before that; had an iPhone 3G before that. There's were growing pains in the first 48 hours, but she's really pretty comfortable with ICS and Sense now. (And she loves the hardware.)
That said, there's one thing that drives her absolutely nuts: She constantly receives notifications reporting that open wi-fi networks are nearby. (She leaves wi-fi on at all times, but the option to notify when open networks are detected is disabled.)
(She pulled down AT&T's latest update last week. This problem started then.)
A few others reported the same issue in this thread, but I couldn't find any mentionings of it anywhere else. I decided to create a new thread, here, rather than derail the one I found.
In that thread, a nerk69 says "Factory Reset... will clear up the problems that start happening right after an update" (but doesn't outright say that it will fix this issue, which wasn't listed in the OP's post).
I'll give the Factory Reset (sans-data-wipe) a shot tonight and report back with our findings. Anyone know of any alternative, more-convenient fixes?
Wait if you want to remove the notification for open networks all you have to do is go into settings>touch WiFi>touch menu located at the top right >touch advanced > and uncheck the first option that says network notification. You should be good to go.
Sent from my HTC One X using xda app-developers app
Nabeel Kiani said:
uncheck the first option that says network notification.
Click to expand...
Click to collapse
colbymulkey said:
... but the option to notify when open networks are detected is disabled.
Click to expand...
Click to collapse
Our problem isn't that we don't know how to disable the feature -- it's that we continue to get notifications, even when the feature is disabled. She's toggled it dozens of times and tried numerous reboots. The only way to prevent the notifications, that we've found so far -- save for a Factory Reset, maybe -- is to totally disable the wi-fi adapter. That isn't a "fix" though, for understandable reasons...
Nabeel Kiani said:
Wait if you want to remove the notification for open networks all you have to do is go into settings>touch WiFi>touch menu located at the top right >touch advanced > and uncheck the first option that says network notification. You should be good to go.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Edit: Deleted...too slow on my reponse and it ended up being redundant
Sorry about that other than that I personally have no idea.
Sent from my HTC One X using xda app-developers app
same problem here. drives me crazy.
Nabeel Kiani said:
Sorry about that other than that I personally have no idea.
Click to expand...
Click to collapse
No problem; just wish the toggle worked like it was supposed to.
ul49 said:
same problem here. drives me crazy.
Click to expand...
Click to collapse
It's easy for me to say it doesn't bother me, but I'm also not having to deal with it. (That's one of the first things I disabled on my Android phones too; just isn't necessary, especially when you're utilizing something like Tasker.)
I just ran the Factory Reset idea by her; probably won't be doing that after all. She hates the constant wi-fi notifications, but the idea of the Factory Reset makes her uneasy; doesn't want to have to recreate each of her apps' settings, and she's a little scared of losing other data. (She's also totally opposed to rooting and using custom ROMs -- she's seen me learn with trial-by-fire too many times on too many devices to believe that can be a hitch-free process.)
There's probably plenty of backup options that'll work within those parameters, but I'm out of my comfort zone.
If I find another solution, I'll definitely let you guys know!
I too am seeing this issue. I've tried restarting and killing the settings process numerous times with no luck. I sent an email to HTC support so we'll see what they come back with. Hopefully they don't suggest a factory reset but if they do then I guess I'll be the guinea pig.
Spacebob11 said:
I sent an email to HTC support so we'll see what they come back with.
Click to expand...
Click to collapse
I suspect the Factory Reset will work, and if it were my device, I'd do it in half-a-heartbeat. But if HTC or AT&T suggest that as the fix... well, let's just hope they don't. (Or, at the very least, let's hope they'll address this in the next update.)
Let us know what you find! :good:
colbymulkey said:
(She pulled down AT&T's latest update last week. This problem started then.)
Click to expand...
Click to collapse
I too have seen the issue where the setting doesn't work. I didnt pay too much close attention to which ROM's I saw it in, but out of about 30 ROM's I have tried maybe 2 have done it.
Its a bug in the ROM you are running, perhaps it is AT&T 2.20 that has the bug and it's likely ROM's based on 2.20 that also have the bug.
Live with it until AT&T release another update, or work to move to custom ROMs?
twistedddx said:
... or work to move to custom ROMs?
Click to expand...
Click to collapse
That's going to take a lot of work! :laugh: I've taken early builds of custom ROMs on my Android hardware long enough to grab a few buggy ROMs in the process, and she's witness the frustration it can lead to. (I wasn't always very good about taking nandroid backups before trying a new ROM, and that's backfired more times than I'd like to admit.) This is her first Android device, and while she's ahead of the curve, she's not interested enough to take the plunge into that world yet.
Besides, based on the other thread, it sounds like this might be fixable via Factory Reset.
Hopefully Spacebob11 can vouch for the Factory Reset after he gives it a shot. And hopefully he gets a positive response from HTC.
Got a response from HTC. Not the response I was looking for
Their are a couple options I can give you to rectify this issue. One is to add the Power Control Widget to your homescreen which will allow you to turn WiFi on when you want to connect to WiFi. You can add this Widget simply by pressing and holding on an empty area of your homescreen and then selecting Power Control. This allow quick access to a few different things to turn on/off.
The other option would be to do a Factory Data Reset to your device. This will reset your phone to its factory settings so before doing this, make sure you back up your personal data as it will reset the device to its factory settings. You can back up to Google, Outlook, or the SD card. If you need assistance doing this you can reply back to me or call our Technical Support at 1-866-449-8358 between 6 AM - 1 AM EST, 7 days a week.
Performing a factory reset from settings
1. Slide the Notifications panel open, and then tap Settings.
2. Tap Storage > Factory data reset.
3. Tap Reset phone, and then tap Erase everything
Click to expand...
Click to collapse
Spacebob11 said:
Got a response from HTC. Not the response I was looking for
Click to expand...
Click to collapse
Gotta love when the very first word from HTC is a typo.
You could try to use this backup method before using the factory reset.
http://forum.xda-developers.com/showthread.php?t=1420351
Going to try it tonight.
I also have this problem and am not wild about doing a factory reset. Subscribed for eventual solution (maybe 4.1, maybe workaround).
Yo-yo~
I want to do a factory reset inside of Bliss so that I can try to recover some backups that I had on an android device that bricked itself a couple of days ago. Issue is that once I get into Bliss live mode I cannot make it factory reset. I get to the option to do so, but I cannot select it, any time I click the button I hear the sound trigger that a button has been pressed but there is no reaction on my device.
If you know that this wont work, maybe you can give me some ideas on where to go next with my full story. Basically my pixel started acting up a few days ago, while trying to resolve that I made sure that I had everything backed up really well. Well, soon after the whole phone started refusing to charge and I found myself buying a new one. I decided to swap back to apple and got one of the iphones. While turning it on I saw that it has the option to restore from android devices! Only problem is that you have to be able to sign into some website on that android device to do it.
So my full plan is to do the factory reset on the Bliss OS Live in my laptop, recover my information through backups saved to the cloud, sign into this apple website, then use the Bliss Live to push whatever data it can to my new iPhone. Can anyone help me get this process started? Or maybe point me in the direction of a better way to accomplish this?
Thanks <3
So I know there's a method for pairing Wear OS watches running 2.0 through ADB with the Google Wear OS app.
Does the same apply for Galaxy Watch 4 and the Galaxy Wearable App? I really don't want to go through the configuration and sideloading of all these apps again ... That's what I get for trying to do too much with ADB and experimenting .
Not that ive found.....its annoying as hell, i have a ticket in with Samsung over it, Lots of shouting at them for selling me a $500 watch that they then seem to think they can tell me how to use. I havent finished shouting at them by a long shot. Because i test ROM's you can imagine how many hours their bs costs me....
My previous watch the Active 2 was simplish, you just set the Android ID to the same as previous install...
Niether that or the ADB method posted for earlier Wear OS works...
Do you mean this method?
Because if this doesn't work, I have a major problem, since I'm replacing roms quite often.
How to Pair Android Wear Watches to New Phones without Factory Resetting
A tutorial on how to pair Android Wear smartwatches to a new phone without factory resetting. Also useful if you flash a custom ROM and don't want to reset!
www.xda-developers.com
munky-head said:
Do you mean this method?
Because if this doesn't work, I have a major problem, since I'm replacing roms quite often.
How to Pair Android Wear Watches to New Phones without Factory Resetting
A tutorial on how to pair Android Wear smartwatches to a new phone without factory resetting. Also useful if you flash a custom ROM and don't want to reset!
www.xda-developers.com
Click to expand...
Click to collapse
it dosent work ;P
So this is the thing you were referring to. Good to know. I was planning on switching roms over the weekend, but I think I'll wait for a bit now.
munky-head said:
So this is the thing you were referring to. Good to know. I was planning on switching roms over the weekend, but I think I'll wait for a bit now.
Click to expand...
Click to collapse
I doubt Samsung will do something about it ; ) they are out of their mind! For example they block blood pressure on non samsung phone so good that on some samsung phones it doesn't work too and they region lock the watch so when you have a phone from different region you can't connect the watch at least easily
Maybe they think if they block everything on everything they will sell some more blocked **** you know because security!
Yesterday I tried pulling an adb backup (adb backup -all or something) and ended up with a ~60MB file.
Has any of you tried this method for backing up and restoring a backup? Might not save the need to reset and pair again, but can save some time when reinstalling.
Haven't tried it myself, just throwing it out there.
munky-head said:
Yesterday I tried pulling an adb backup (adb backup -all or something) and ended up with a ~60MB file.
Has any of you tried this method for backing up and restoring a backup? Might not save the need to reset and pair again, but can save some time when reinstalling.
Haven't tried it myself, just throwing it out there.
Click to expand...
Click to collapse
How it went in the end? If successfully, can you briefly describe the steps? I'll do my own research based on those, thanks
BigRulaZ said:
How it went in the end? If successfully, can you briefly describe the steps? I'll do my own research based on those, thanks
Click to expand...
Click to collapse
In a nutshell, it didn't work.
I pulled a backup, but no command would restore the apps.
This is so frustrating! I experiment with ROMs and the fact that that I have to start out fresh each time really makes me think of switching back to TicWatch.
munky-head said:
In a nutshell, it didn't work.
I pulled a backup, but no command would restore the apps.
This is so frustrating! I experiment with ROMs and the fact that that I have to start out fresh each time really makes me think of switching back to TicWatch.
Click to expand...
Click to collapse
Speaking of switching back to TicWatch, you're not wrong. The only feature that I will miss would be the ECG capability (which also is broken, no QTc value calculation, etc)
berni502 said:
I doubt Samsung will do something about it ; ) they are out of their mind! For example they block blood pressure on non samsung phone so good that on some samsung phones it doesn't work too and they region lock the watch so when you have a phone from different region you can't connect the watch at least easily
Maybe they think if they block everything on everything they will sell some more blocked **** you know because security!
Click to expand...
Click to collapse
Part of this is that blood pressure has to be approved by different authorities in different places. In the US, the FDA has not approved it.
Also, the stupid resetting thing appears to be a Wear OS 3 issue. Samsung never did that with Tizen. Google seems to have screwed the pooch on this one.
The thing about being unable to pair them once they lose connection is quite a big issue.
My watch and phone has just unpaired a few days ago, and I didn't do any system mods or anything for that to happens. If I try manual pairing with bluetooth it does not work.
I'm not friend of backups, since sometimes that process import some errors among system updates. So I normally do clean installings.
I tried that procedure removing google services via adb and wifi connection but de watch didn't connect in the end. And even if it connected it seems that some apps such as google Pay etc would give problems and would require to be reinstalled again.
On top of that I'm not quite sure but as I have the LTE version I think I will have to ask to my carrier to send me a new e-sim in order to connect the watch again, since I guess they are just one use.
So quite a big problem.
The really crummy part of it all, 1) the annoying tutorial EVERY DAMN TIME. although, as of the latest update (besides a reset a few days ago, oddly enough) it hasn't made me go through it. 2) the wearable app REQUIRING samsung internet (not beta) to be installed and default as browser while signing in and through the entire setup process. these are just to name a few things.