I know what forum I am using mods. This is a major ONLINE development that is crucial to get development work to users, and we need to fix it. Move if you need to, but I think it will be more useful in the development thread. also if this is fixed soon, developers reupload, or something similar, please move it to general then, or delete it. im trying to help all rom flashers on our device.
okay for those of you who dont know, goo.im has been constantly going down lately. that means no file downloads. This happened because they are upgrading their servers, and this has been causing problems. heres the biggest problem (taken from their blog, would link, but it might be down any minute):
The Ugly:
We had an issue with our Lustre cluster. Ours is laid out with a metadata server, and two object storage targets/servers (OSTs, or basically, file servers). You can think of the metadata server (MDS) as like the MBR or index of a hard drive; the MDS lists where every file is on the OSTs and contains metadata and if it gets wiped out, recovery of data is nigh-impossible. As it turns out, when the new OST was brought online, it caused a race in the MDS, where it thought the new OST was the old, and that all data was missing... And started wiping out the data. By the time everything was over, the cluster was up and running normally, but all the metadata was gone. Because of that, all of the files were inaccessible.
To give you an idea, imagine trying to find a specific quote from a certain page in a particular book inside all of the libraries of the world, but with no librarians, no index cards, no computer index, nothing. Just you and endless rows of books. That's what it would be like to try and pull out a ZIP from almost a dozen terabytes of storage space. On top of that, we did not have the means nor budget to have a backup system for all of the data that was hosted. Don't worry, we have already budgeted for a backup system, and will be implementing it likely in the next round of upgrades or sooner to prevent just such an issue in the future. Unlike some folks, we learn from our mistakes.
We were able to restore a backup of the site itself, as well as all developer and sponsor accounts, as well as the GApps. We're working with developers to help them get their data re-uploaded from mirrors, and all developers can now resume uploading and restoring their data. However, some folders such as /stock we do not have any backups for. We will try and find as many files as we can and restore them from around the web, but it will take a while and it's likely that we will not be able to restore all of them.
The buildbox at the very least was untouched, so no data is missing from it, and developers can continue to use it normally. On top of that, this has given us a chance for a clean start, wiping out old, unused files and letting us completely reorganize with all developers located under the /devs folder and all of them having full compatibility with GooManager from now on so long as they make their ROM compatible.
We apologize for the disruption this data loss has caused. We had picked lustre specifically because it was designed to be very reliable and provide high throughput to all of our distribution servers. Despite this setback, Goo.im will continue to operate, and we will work to restore what we can.
in summary for those who dont want to read it: THE SERVER GLITCHED UP AND DELETED ALL FILES ON IT. that means all the roms hosted only on goo are now inaccessible, which is at least all CM9 and CM10 builds for our beloved nook tablet, and millions of others. that means unless a user uploads it, or the developer reuploads it, we cannot get roms!
so lets get a fix out for us nook tablet users: lets share the files, and get them back online. The problem is some developers don't allow mirrors. so lets figure out which devs will let us mirror, and then mirror (with credits). I have the latest CM9, and CM10 builds, and the Jandycane rom. I will upload as soon I found out I wont make any devs angry, but some people dont like parts of the latest versions, and use an older version I dont have. So this development is to get all versions of all goo only based roms into one place so we can mirror them all. I can put them on dropbox, dev-host, and goo (while its up), so if you have the file, and know if we can mirror it, comment below, and lets fix this.
Related
Is there a way or is there a backup program to restore only the data wich is installed and with registery information for the programs and NOT the rom image "OS files etc..."?
Couse everytime I flash my device with a latest rom, I have to install and register 250 programs again
Think if there was a program which restored only the registeration informations and only installed programs :twisted:
Are you using the official ROM's?
Try to use a kitchen and make a rom where many programas can be placed on rom, so you don't need to install all the programs.
http://xda.weblink.net/
In this site you have the possibility to send snapshots of programs that you want to install in way to make it available later!
It's an ideia...
pardon me for sticking my nose in here, but this sounds dangerous or at least irresponsible to do.
For the referenced web site to advise persons to download a program onto a device, then have it make two files that the user has to send to a person owning the website that the user does not know and wait for instructions....
...plus told "IMPORTANT, do not remove the program"
is truly suspect.
Any hacker with half a brain could then own your passwords to your server, thus your whole login info to your corporate network. The person could "own everything about you" through your device.
THIS IS A SECURITY NIGHTMARE AND I ADVISE EVERYONE NOT TO FOLLOW THESE INSTRUCTIONS ON THE WEBSITE.
Sorry if there are truly good intentions with the web site, but what they want violates every good security practice surrounding computers.
Hi all,
I am new to android. First time using it and really know nothing about it.
Bought the G tab at woot. I am knowledgeable with computers, so I hope that helps. Over 50, so need your help here.
I have spent a decent amount of time looking through these forums and there is so much information here, it is hard to discerne what is relevant for me.
I did the OTA update. I do not have an sd card, so all will be through the usb to my home computer.
I have played with the gtab a bit, but I figure, before I go and do a bunch of setup for the family and download apps that if I am going to root it, I may as well do it now. Those of you with experience using it don't like viewsonics version, so I assume that these ROM's must be so much better.
From this thread http://forum.xda-developers.com/showthread.php?t=842004
it reads that if I have stock gtab, I can simply install TnTLite 4.4 without clockworkmod. I assume then that without colckworkmod, I can't clear the cache or datafiles. Do I really need nvfLASH? I read it and it sounds a bit confusing.
I read that you should repartition the gtab. I looked and can't find out how to do this. Is this before or after you run the mod?
For the market fix, http://forum.xda-developers.com/showthread.php?t=845175
I follow the link to download the zip file. When I download apps from the computer, where on the gtab do they go to unzip them?
What does sideload mean? What do you mean when you say make sure that market is working with your google id? do i need a gmail account?
On a side note, the gtab will not load up my yahoo mail account? hmmm, is that correct? My wife has an old aol account that she uses and she said she can't respond to emails, that is true also?
Thanks in advance,
Kozmokrmr
Lots of questions... let's see what we can do here...
Yes, You can setup TnTLite 4.4 without ClockworkMod. However, CWM is included in the install as part of the 3588 Recovery Pack. You can actually switch it in and out as needed for the purposes of clearing caches and wiping data.
Repartitioning is one of the advanced functions of ClockworkMod. You will not likely find it necessary unless you're doing lots of modding (or are particularly anal about procedure, like I am...).
It doesn't really matter where you download or unzip files to as long as you know where they are. I leave them in the default download folder or create a folder for the particular project on one of the sdcards. Sideloading consists of downloading an app's .apk file to the tablet then installing it without using the market. Most file managers (including the one included on the gtab) do this with a click or two.
Yes you will need a gmail account to make the market work. When you start it the first time it will ask for your gmail credentials to log in.
There is a Yahoo mail (and IM) client/app. Not sure about AOL. But either can be accessed through the web browser.
All that being said... if you are planning on using the "Family" accounts setup that comes stock on the G Tablet you'll want to try that before loading any custom ROM. They all replace the contacts app which is required for that to work. I'm not sure if any of the custom ROM's supports any kind of multi user setup.
Thank you K J Rad
To enter clockworkmod, then just use the power and volume up to access clockworkmod from 3588 update? Then do the data and cache clearing? Is clockworkmod, just a tool to do a few system functions?
Ok, then I won't worry about repartitioning.
Hmm, alright, I guess I'll just give the sideloading a go and see what happens.
About NVFlash, should I worry about it or is it only for the guys who switch out roms and play around with it? I figure, once I install a mod, other than maybe updating the rom, I won't be yanking around with it like this anymore.
Ok, then we'll get a few gmail accounts. Thanks.
The internet on the gtab wouldn't access my yahoo. Possibly I need to upgrade yahoo to the paid version to get the pop account.
The AOL account could be read, but she couldn't reply to any emails. Possibly the same problem there.
No big deal about the family accounts, we don't need them. Its not an issue.
The people here I read that have issues (not booting up, stuck in a loop, etc.) have what? done a step wrong, played around a bit too much or just one of those odd software flukes that catches some guys?
So there really is a BIG difference in the stock rom and the modded roms's, yes?
Thanks again.
Power and Volume Up enter "Recovery Mode." If ClockworkMod is installed then that is what you will get. Otherwise you'll get the stock recovery. 3588 does not install CWM. There is a very good thread "Stickied" in the development section about installing Clockwork, ROMs, etc. Once you've got that installed the instructions for installing TnTLite 4.4 and switching between the two types of recovery are in the stickied TnTLite thread. I usually do a data wipe before and after installing a ROM (it works for me... YMMV).
Knowing how to nvflash could be the difference between nirvana and complete disgust. It may never come up but if it does then you will be thrilled that you know how.
Once you have the market installed and working download a better browser. I use Dolphin HD and it works with my Yahoo account just fine (after you tinker with it's settings a bit...). Probably work fine for AOL also. If not, try Opera Mobile.
Any number of things can cause the issues you'll see posted about here. I've suffered magic number mismatch, boot loop, FC's... the whole gamut. If you get comfortable with the tools then you'll be able to recover from anything. Good practices will also lead to greater success. For example, when I'm flashing to a new ROM I do the following:
1) Cache and Data wipe.
2) nvflash to Factory install.
3) Update to 1.1-3588 build.
4) Data wipe (probably not necessary but wth...)
5) Proceed with update.
For experimental builds I modify that to include repartitioning.
Following this procedure has reduced my occurances of unexpected issues to near zero (I don't always remember to do every step...).
Yes... the custom ROMs are "Better" but better is subjective. I like TwoTapsX for its speed and stability though it does suffer from a few video artifacts from time to time. TnTLite is a good solid daily driver for the average user. VEGAn is popular with a lot of power users. Each has its tradeoffs and even the stock ROM has some advantages (easy to use custom interface, decent basic set of integrated apps, settings optimized to reduce confusing options).
Welcome and enjoy.
So, everything was fine as I shut down last night after reading a few pages from a book. Tried to power up this evening and it just won't cooperate. It won't turn on unless I hold the power button down for nine seconds. It starts up "with tap n tap" screen, then the n logo shows, then the "with tap n tap" flashes and returns to black screen then shows the "with tap n tap" for a total of eight times then stays black. No rooting, totally stock, used very little, few apps, added some reader stuff, tried a barcode thing to no avail - nothing more. Please advise. Take pity on someone like your mother! Any ideas on how to fix this? Should I contact Viewsonic or Woot? (yes, it's fully charged - first thing I tried). I'm so disappointed : (
Thank you
I've seen this happen a few times with both stock and modded devices. I think it's caused by corruption in data files that are used by some of the system firmware but I'm not 100% certain of that. A data wipe could very well get you going again. Without being able to boot all the way you're options for doing that are somewhat limited. One would be to install and use ClockworkMod, a very minor and extremely common modification to the firmware. The other option that I have used successfully is a script I've written that will delete those system prefence files and clear the machines cache without modifying your firmware. Neither is terribly complicated to implement.
All that being said... it is really up to you as to how comfortable you would feel performing those options. I can say that you will find plenty of people here that will be willing to stay right with you until it's fixed and we have a very high success rate when it comes to recovering from this kind of issue. On the other hand, Woot has been very responsive to customers with problems so it's really your call.
This thread: http://forum.xda-developers.com/showthread.php?t=865245 has instructions for installing ClockworkMod. It has a lot of other information in it also but the important part would be installing CWM. It also has download links to the files. Once it is installed it is a fairly simple matter of booting the machine up while holding down the volume up key and you'll be presented with a menu of options that will include wiping data. Selecting that will clear out any apps you've downloaded and associated data along with the system data. Once done you simply reboot the machine from another menu option and you should be off and running.
My script is run very much like installing ClockworkMod but will simply do the deletion without any user intervention. When done it reboots automatically and in two or three minutes you should be back to the initial setup screen for the tablet.
All of this probably sounds a lot more difficult than it really is but I think if you take a look at that thread I listed above and do a little searching on terms like "ClockworkMod Data Wipe" you'll find there are lots of folks who have done this and plenty of help if you need it.
KJ and LynnyW,
Since he can't boot, he will either have to make a microSD with a CWM update.zip and recovery folder (with command file edited to point to SDCARD2 instead of SDCARD) and boot that into recovery with power/volume + .
Or, he will have to NVFlash the CWM by itself.
http://forum.xda-developers.com/showthread.php?t=1020747
http://forum.xda-developers.com/showthread.php?t=1030042
The two links above have most of the info.
If he can get CWM up by one method or the other, need to go to Advanced Menu and tell it to Partition (2048 and 0), Fix Permissions and Wipe Dalvik Cache -- and then return to Main Menu and Wipe Cache and Wipe/Reset Factory Data. Then reboot.
If the tablet comes up fine we're good to go. Otherwise may need to talk about a
stock rom flash.
Hope this helps.
Rev
I am running a stock system. Amazon market and a couple bird games are all that's really on it as I use it mostly to browse the web with. No flash no email, it's stock. So far I've limped through how to recover from the acore.process problem, then ended up learning how to use nvflash after what this user described happened twice so far. I am debating updating to a Dev rom if they are more stable as otherwise this is just a fragile toy that I can't take out of the house on trips.
wetzk said:
I am debating updating to a Dev rom if they are more stable as otherwise this is just a fragile toy that I can't take out of the house on trips.
Click to expand...
Click to collapse
Update. So much better it's unreal. Go with something stable like Caulkin, Vegantab, or TnT lite. Not only will you get the real Market, you'll be much happier all around. It can be much more than a fragile little toy.
butchconner said:
KJ and LynnyW,
Since he can boot, he will either have to make a microSD with a CWM update.zip and recovery folder (with command file edited to point to SDCARD2 instead of SDCARD) and boot that into recovery with power/volume + .
Or, he will have to NVFlash the CWM by itself.
http://forum.xda-developers.com/showthread.php?t=1020747
http://forum.xda-developers.com/showthread.php?t=1030042
The two links above have most of the info.
If he can get CWM up by one method or the other, need to go to Advanced Menu and tell it to Partition (2048 and 0), Fix Permissions and Wipe Dalvik Cache -- and then return to Main Menu and Wipe Cache and Wipe/Reset Factory Data. Then reboot.
If the tablet comes up fine we're good to go. Otherwise may need to talk about a
stock rom flash.
Hope this helps.
Rev
Click to expand...
Click to collapse
I think the decision needs to be made as to whether LynnyW actually wants to start mucking about before we go suggesting modifying the recovery and repartitioning the tablet. In this case I think all that's necessary is a data wipe and that can be done without starting down a path that LynnyW may not care to follow. I certainly wouldn't recommend anything as extreme as repartitioning when the question asked is whether or not a call should be made to the manufacturer and vendor.
KJ,
Take him where you want to go -- but if he can't boot up he's going to have to
get inside somehow. That's why I said I thought he would have to install CWM.
If you know some way to wipe or reset without CWM, go for it.
Rev
P. S. -- And I assume anyone that posts here wants to fix it unless that is not
possible -- and then they want us to tell them to go to VS or Woot or
whatever.
I meant no offense, Rev. She asked whether she should call woot or Viewsonic. I was just pointing that out. Not everyone is ready to jump into modding when they have the option of warranty return/replacement.
waiting for Viewsonic call
Thanks folks. I don't want to go mucking about until necessary. I guess I was hoping for an easy fix/reset. I prefer not to send the tab for repair unless replacement is necessary. Not yet willing to put my toe in water of this vast new world of acronyms I know nothing about. My brother's voice echos in my head "you know just enough to be dangerous" (re windows). I don't want to void the warranty. I called Viewsonic and had to leave my telephone number for a return call. I'm hoping they can e-mail a file which I can copy to a microSD, pop in, turn on, and resume - until I have the nerve to install something more stable. I will let you know what Viewsonic has to say. They no longer operate at the toll free number listed on the website. Directed to another number where they answer the phone "can I help you?". I wonder what service they are using for tech support.
Lynny
I have just such a file that might get you going. Posted it this morning here:
http://forum.xda-developers.com/showthread.php?t=1030915
Feel free to look that over and let me know if you have any questions. The main caveat is that it will delete any user apps that have been installed. That may include factory installed apps that are stored in the user app area. If that is a problem I can modify the script to preserve them but then we might not be clearing the problem file.
Viewsonic should hire you!
Well, I received a call from Viewsonic tech support. The moment I finished explaining what happens on the screen, the tech said "I never heard of this. Ship it back." Whoa, no attempt to troubleshoot? I asked was there not a bootable file I could be e-mailed? After rephrasing and getting nowhere, I was not happy to be told to send this to LA for an unknown amount of time at my expense. I was told I could call back later when the manager was back from lunch. This is a far cry from the claim on the Viewsonic website:
"Got a question? We have the answers right here: documentation, downloads, tech support, software updates, product warranty and registration. Get the assistance you need, when you need it – right now. Find out how we stand behind our product, all the way."
The lack of speculation regarding what the problem might be makes me feel that Viewsonic farmed this out to a fly-by-night call center and the folks there were told to have callers just send in the hardware.
Sorry, I had to rant.
KJ, Viewsonic should hire you and your xda brethren. The files to clear the data worked. Yes, it did wipe out factory and user apps, but it got the tab working in five minutes. It also gave me a little courage. I will, after all, start reading about modifying this thing. I don't want to set it all up only to have it faint on me again.
If you have any recommendations for the least-likely-to-brick-it route, please advise. I have read a number of threads but there is so much information, and although there are numerous step-by-step instructions, I have no idea what the different roms do. I don't know where to start reading and I don't want to become an annoyance here. I will do my homework before I ask too many newbie questions.
THANK YOU!
Lynny
We understand the need to rant from time to time. No problem ;-)
Glad it got you going. I do want to recommend that you do a factory reset from the system settings also just to make absolutely sure everything was cleaned properly. It's under "Security" in the System Settings.
As for modding... read, read read. Start with the "Stickied" items in the General and Developer sections. You'll find references to basic procedures and cautions but always make sure to follow the developers instructions attached to the specific ROM you choose. As for the "Least likely to brick it..." I may not be the best person to ask since I routinely run experimental ROMs. I do like the TnTLite path for its stability, reasonable speed and close association to the stock ROM. Read as much of the threads attached to each one and ask questions if you need to. That's why we're here.
Intro
I don't mean this to be a thread for any specific ROM or problem, but rather a general guide that essentially eliminates all doubt of machine or user error (we all make mistakes). This is generally geared towards the issues users are experiencing when flashing an AOSP ROM, but can also apply to Sense, and even other devices. This covers from downloading a ROM forward, and also making sure that everything gets properly installed with no corners cut, so that everybody can be on the same page when a problem arises. I'm not trying to say anybody's way of doing things is wrong, but I've see a lot of people asking different questions that end up getting solved with the same few answers. This isn't a "how to flash" thread, but rather how to ensure you're getting your device in a clean, fresh state so that everybody can be on the same page when it comes to bugs, otherwise nobody is going to want to help you if you don't try to help yourself first.
I know this is on the longer side, so key points are underlined, with a TL;DR at the bottom
Downloading
Checksums or hashes are a great way to make sure that the *.zip or any other file you're downloading is not only the right one, but that it hasn't been corrupted or tampered in transfer (uploads or downloads). You'll probably need to install something to work with chescksums- personally I like the open-source HashCheck for Windows. It adds a "Checksums" tab to the right-click > Properties dialog that automatically calculates MD5 (most common) and SHA-1 (more advanced) hashes. I encourage anyone posting a file to also post the MD5 with it, for everybody's sake, since it only takes a few extra seconds to eliminate all doubt of a bad upload or download. HashCheck even gives an option to create a *.MD5 file, just like the ones you might get from goo.im. If you're on Linux, Android, or presumably Mac you can check a file's md5 by opening terminal and simply typing "md5sum <filename>" without the quotes. If a file is posted without an MD5, you can download it twice and check it against itself, but just keep in mind you're going to be hitting somebody's server twice as hard, so only do it if necessary. Now that you're sure you have the right files...
Wiping/Flashing
Most people know dirty flashing is at your own risk, and if you have a problem, the first thing anybody's going to tell you is to do a clean flash. No really, just clean flash- that's what backups are for, but that's a whole different topic. Unfortunately, most people consider a clean flash to be just a factory reset, but that only wipes dalvik, cache, and data (except your sdcard), while leaving the system partition intact. To do a proper clean flash you want to go into advanced and make sure that system gets wiped in addition to dalvik, cache, and data. I can't say exactly what (sorry), but there's lots of miscellaneous things that can persist between flashes, especially when you're going to a different ROM. For us DNA owners, there's still a lot of activity in our CM device tree, meaning that even on the same ROM, some of our device files may change between versions which will necessitate a wipe of system. Maybe it's just me, but it seems things go out of line more often on 4.3 so I just always wipe system now.
If you're here, you probably know how to flash a ROM, but always double check the OP or first few posts and see what gapps/settings/etc are recommended. I'm also going to remind you that it takes just a few extra seconds to create a *.md5 file with HashCheck that you can push to your device along with the *.zip and TWRP (probably CWM too) will check the file against it's MD5 before flashing it. After using the Setup Wizard to log in to your Google account, make sure that you uncheck the box to restore settings and data to your phone, otherwise those can cause problems. Now you can be sure that whatever is on your device is clean as can be and as the developer intended, otherwise you're probably not going to get much help.
Narrowing down the problem
Now that you've got a brand spanking new and clean ROM is the best time to try and narrow down a problem, but before you post anything, try the golden rule of IT- "Have you tried rebooting it yet?" Also, you can try booting to recovery to clear just dalvik and cache and/or repair permissions. This is the first time you should consider making a post about your problem, but please, please, please don't make a post that just says something like "Settings FCs." Posts like that don't tell anybody anything- the best thing you can do is pull a log (more on that in a second), and create a post in the appropriate thread which you can determine as follows: Start by seeing if the problem occurs with nothing installed besides the ROM and recommended gapps- do not restore any backups, install any apps, or flash any kernels, even if the OP recommends it. If you're having problems with Settings or any Google app, there's likely a conflict with the gapps package that should go away if you reflash only the ROM, otherwise it's a bug in the ROM itself. Either way, if you can reproduce a problem at this point you should post in the ROM thread. If you want to flash a custom kernel, only do so after you've verified the problem isn't with the ROM or gapps. Flash only the kernel, and if there's any problems after that, post them in thread you got the kernel from, not the ROM thread.
If you're having a problem with an app, once you've completed the above steps, install only that app without restoring any data. If you can't replicate the problem, there's likely an incompatibility any corresponding data you may have restored, and sorry, but there's not really anything you can do about that. If the problem occurs with a freshly installed app, first check the Play Store to see if other users are experiencing the same problem- there may just be something wrong with the app. If it only seems to be you having this problem with a clean install, the ROM thread is the best place to post, although keep in mind other users may not be familiar with app.
Pulling and posting logs
Even now, nobody is obligated to help you (you flashed that ROM at your own risk, remember?), but once you're at this point, you'll have a better chance at getting help. Try to include as much information as possible like what else you were doing, what screen you were on, what button you tried to press, etc. and if you can, try to see if you can replicate it. Like I mentioned above, posting a log is the best way to get help, and they're really easy to get. Not everybody is going to understand every line, but if you know what you're looking for, occasionally the log can tell the developer exactly what the problem is, and bam- easy fix.
First make sure USB Debugging is enabled in Developer Options (if you don't see Developer Options, go into About Phone and tap on the Build Number line 7 times), and make sure that Root Access is set to both Apps and ADB. Now as far as gathering these logs, SysLog is by far one of the easiest ways- download it, open it, and press "Take Log." It pop up a toast message saying that your logs are in /sdcard/SysLog/<DATE_TIME>.zip and it'll even give you the option to share it via email, Dropbox, or anything else you might use. Post that and you'll have even better chances of getting help. For simplicity, I'm not going to details on manually pulling logs, however if you're stuck in a bootloop or something like that and can't run the app, use "adb pull /proc/last_kmsg" and post a link to that file.
TL;DR
Sh*t happens, learn to deal with it or go back to stock
Verify your download with an MD5 Checksum
Wipe system in addition to factory reset (dalvik, cache, & data)
Flash ROM and gapps without installing anything else or restoring any data
Pull a log, it's really easy
Now is the best time to make a post about your problem
Radio/Reception Problems on the DNA?
First things first- Double check your settings in Settings > More > Mobile networks. They should be as follows:
Data Enabled: Yes
Data Roaming: No (unless you're actually roaming)
National Data Roaming: Yes (otherwise you'll probably lose data; this won't get you any roaming fees)
Network Mode (Verizon): LTE/CDMA/EvDO (or Global, which is everything, I've never noticed any difference between the two)
Network Mode (GSM): GSM/WCDMA preferred (depending on the ROM, you may also need to flash the GSM patch courtesy of Flyhalf205 from the 2nd post in the original CM10.1 thread.)
System Select/CDMA Roaming: Automatic
CDMA Subscription: RUIM/SIM
GSM users may also need to manually enter APN settings for your carrier to get things like MMS functioning properly. I'm not going to compile a worldwide list, but if Google fails you, your carrier should have support documentation with these settings. Recently, I noticed this file in the android source lists tons of APNs, so try finding your carrier in there too.
Why do I have 0-1 bars? I got a lot more on Sense
Don't be alarmed if your reception looks low/non-existent. Sense "pads" the signal bar to get it to show bars more "accurately," but AOSP does not, so expect a drop in bars. To get an accurate assessment, you want to be looking at your actual signal in dB before trying to diagnose anything by going to Settings > Interface > Status Bar and changing Signal Status Style to Text, and your signal bars will be replaced with a negative number, therefore a value closer to zero indicates a stronger signal. If you don't like negative numbers, another way of thinking about this is as if the phone was telling you how far you are away from the nearest tower. What would normally be 5 bars on Sense equates to -70dB, and 1 bar equates to -115, but these are approximate values and depending on your location and environment, you might bee numbers outside this range.
I'm still having problems
Unfortunately, our phone is known to have problems with reading the SIM card. Some say it's purely software, some say its purely hardware, but I believe it can be either. I'd first suggest giving your SIM card a cleaning by popping it out and gently rubbing the contacts with a clean rubber eraser, another more risky option is a just drop of isopropyl alcohol on a cotton swab. If you have compressed air, you can give that a small blast into the SIM slot from a few inches away. If the phone is still having issues with reading the SIM after that, it might need to be replaced.
Another possibility is issues with the radio firmware. You can try updating the firmware by following the instructions in this post. Personally, I recommend the most recent version, 2.06.605.1. Some users, myself included, have reported that sometimes a full RUU back to 100% stock is necessary to restore proper radio function. Instructions for that can be found here, but be aware that this can be a lengthy, tedious process. You'll end up having to re-unlock and root your phone before you'll be able to flash anything else again, so I only recommend this as a last resort, but is nonetheless something to bear in mind.
Stickie this?
Sent from my HTC6435LVW using Tapatalk 4
I'm going to stick it for now, it's actually good basic info. But I am moving it to the Q&A forum.
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
pyroguysf said:
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
Click to expand...
Click to collapse
Yeah that makes sense, and I was hoping this would also cut down on unnecessary thread starts.
I think what I'll do is have this in both development forums as a sticky, hopefully this will help out some of the chefs.
If you edit one thread, be sure to edit the clone in the other forum.
I am going to let you clean this up as much as possible over the weekend, then maybe move it to the dev threads Monday as a polished product, see if you can get as much info as possible about GSM to include about the signal issues etc.
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
orangekid said:
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
Click to expand...
Click to collapse
I've noticed this, but I made this in hopes of giving people a place to link back to rather than having to waste time typing out the same things over and over, which is why I also put the link in my sig.
orangekid said:
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
Click to expand...
Click to collapse
Good ideas. I'll try to add a section for apps when I get a chance. I tried to briefly touch on the kernel situation by saying to read the OP for recommended settings, but I'll definitely expand on that.
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
pyroguysf said:
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
Click to expand...
Click to collapse
Sounds good.
Moved to dev forum.
If you want to go ahead and create the same thread and copy / paste the first 2 posts, I can sticky it.
LOS 17.1 is now available and developers say that LOS's own recovery is going to be the preferred recovery.
Last year Google announced that adb is very likely to be removed soon.
Those two statements brings up an important question: how can users create a full backup of their devices **without** having to root them in order to make backup apps work?
I am not talking about backing up pictures, media, calendars or address books, there are plenty of ways to do this without root access. I am talking about a full backup, including the whole system partition and user data. TWRP was an excellent tool for this job: a backup could be created any time, any where, completely independent whether a PC was near or not. You could even write the backup directly onto a USB storage, and the phone could always be restored as well any where and any time.
That is a feature that I miss very much in LOS's own recovery and to my opinion this is an issue that needs to be solved.
Will this feature be added to LOS recovery in the (near) future? Or are there any other solutions to do a full backup without the need for root access?
dvdram said:
LOS 17.1 is now available and developers say that LOS's own recovery is going to be the preferred recovery.
Last year Google announced that adb is very likely to be removed soon.
Those two statements brings up an important question: how can users create a full backup of their devices **without** having to root them in order to make backup apps work?
I am not talking about backing up pictures, media, calendars or address books, there are plenty of ways to do this without root access. I am talking about a full backup, including the whole system partition and user data. TWRP was an excellent tool for this job: a backup could be created any time, any where, completely independent whether a PC was near or not. You could even write the backup directly onto a USB storage, and the phone could always be restored as well any where and any time.
That is a feature that I miss very much in LOS's own recovery and to my opinion this is an issue that needs to be solved.
Will this feature be added to LOS recovery in the (near) future? Or are there any other solutions to do a full backup without the need for root access?
Click to expand...
Click to collapse
Making a complete system backup requires root and/or custom recovery, period.
That is he way it is, you can't change that. There are no alternatives.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Making a complete system backup requires root and/or custom recovery, period.
Click to expand...
Click to collapse
Pardon me, but that is a very harsh answer to a seriously asked question of common interest.
"We take security very seriously"...
Do you know where these words are written?
Maybe you'd like to try looking at this issue this way:
Many users who install LOS, are doing this because of security reasons. Imagine some of these users having bad luck and their phones get compromised by some bogus apps. And then they read an answer like this, telling them nothing different than: sorry, we can't and we won't help you!
And know imagine this:
Users can create snapshots or images of their running systems, with all of their apps included, as well as all necessary accounts, logins and passwords. When the "impossible thing" happens to a device running LOS, they have the option to restore the complete system without having to do a factory reset and without having to reinstall each and every app and the corresponding accounts.
What do you think, which one would please the users of your product more: an answer with an attitude like that one above, or the second possibility?
Furthermore: I was not bagging you to include this possibility. I was asking how this kind of back up could be made in the future, when TWRP won't work with Android 10, and when Google will remove adb. And frankly, I don't see why a recovery made by LOS should not be able to do a task that a third party recovery is capable of. If TWRP developers can put together such a piece of code, I am sure LOS developers should be able to do so as well.
Another possibility would be to reverse Google's decision and to keep adb.
So, from my perspective, there are at least two possible ways of dealing with this. But I am a user, not a developer, and I don't know if or why any one of these possibilities is a bad idea, or if there are really serious arguments against it, or whatever pro or con there might be. I simply don't know about these things and that's why I was asking about it. I am a user who doesn't like having to do a complete re-installation after a crash. And I am pretty sure that I am not the only user with this kind of antipathy.
A polite answer to the question would have included at least a glimpse of explanation why this and why not that.. And an open minded developer would have even cared to discuss about this.
dvdram said:
Pardon me, but that is a very harsh answer to a seriously asked question of common interest.
"We take security very seriously"...
Do you know where these words are written?
Maybe you'd like to try looking at this issue this way:
Many users who install LOS, are doing this because of security reasons. Imagine some of these users having bad luck and their phones get compromised by some bogus apps. And then they read an answer like this, telling them nothing different than: sorry, we can't and we won't help you!
And know imagine this:
Users can create snapshots or images of their running systems, with all of their apps included, as well as all necessary accounts, logins and passwords. When the "impossible thing" happens to a device running LOS, they have the option to restore the complete system without having to do a factory reset and without having to reinstall each and every app and the corresponding accounts.
What do you think, which one would please the users of your product more: an answer with an attitude like that one above, or the second possibility?
Furthermore: I was not bagging you to include this possibility. I was asking how this kind of back up could be made in the future, when TWRP won't work with Android 10, and when Google will remove adb. And frankly, I don't see why a recovery made by LOS should not be able to do a task that a third party recovery is capable of. If TWRP developers can put together such a piece of code, I am sure LOS developers should be able to do so as well.
Another possibility would be to reverse Google's decision and to keep adb.
So, from my perspective, there are at least two possible ways of dealing with this. But I am a user, not a developer, and I don't know if or why any one of these possibilities is a bad idea, or if there are really serious arguments against it, or whatever pro or con there might be. I simply don't know about these things and that's why I was asking about it. I am a user who doesn't like having to do a complete re-installation after a crash. And I am pretty sure that I am not the only user with this kind of antipathy.
A polite answer to the question would have included at least a glimpse of explanation why this and why not that.. And an open minded developer would have even cared to discuss about this.
Click to expand...
Click to collapse
Your reaction is a very butt-hurt reaction for a question that has been asked AND has been answered many times on this website and could have easily been found by you if you had searched.
Unless, of course, you did search and you did read where it has been answered before and, for whatever reason, you mistakenly thought that you would get a different answer just because you needed it to.
My point was, there is no way to access system partition or data partition without root. This forum is full of posts from other users asking the same thing, they all got the same answer, it can't be done without root or TWRP. Android just does not work that way, it has a linux kernel, which means, everything requires specific permissions and it is not in the best interests of OEM/carriers to allow access to /system and /data that easily and there is no way to give you "limited" access that only allows you to backup the /system and /data. There is only full permissions or none and they will not allow full permissions to the user.
That is entirely the whole point of people like us that find ways of rooting devices and installing custom recovery in the first place, because it is the ONLY way we can access /system and /data to make backups or modifications.
As for your thoughts of whether there will be a "new" way of making backups if adb and TWRP are no longer viable options....
Who knows? None of us will know until that time comes. We will all just have to wait and see if any takes the time to develop a new method.
Sent from my SM-S767VL using Tapatalk
dvdram said:
...
Last year Google announced that adb is very likely to be removed soon.
...
Click to expand...
Click to collapse
Android Debug Bridge (ADB) is a Server - Client pair software
ADB Server runs in the Android device
ADB Client runs in Windows / Linux / Mac iOS
ADB completely is open source. Hence everyone can grab the source code and compile it matching the target Android OS / computer OS. Manufacturers like Samsung & ZTE actually already provide their build of ADB Client suitable to their Android devices: they don't recommend to make use of universal ADB Client that floats around the WEB.
AFAIK Google announced to remove backup / restore feature from ADB Client, not ADB at whole.
jwoegerbauer said:
Android Debug Bridge (ADB) is a Server - Client pair software
ADB Server runs in the Android device
ADB Client runs in Windows / Linux / Mac iOS
ADB completely is open source. Hence everyone can grab the source code and compile it matching the target Android OS / computer OS. Manufacturers like Samsung & ZTE actually already provide their build of ADB Client suitable to their Android devices: they don't recommend to make use of universal ADB Client that floats around the WEB.
AFAIK Google announced to remove backup / restore feature from ADB Client, not ADB at whole.
Click to expand...
Click to collapse
Yeah, I can't see Google completely removing adb, it is too valuable of a tool for development even for the stuff the carriers and their developers do on their end. Removing it would be like building cars and engines but completely disallowing the production or use of tools to assemble/disassemble the cars or engines.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
My point was, there is no way to access system partition or data partition without root.
Click to expand...
Click to collapse
I know that and I understand that. I've been using Linux on my private and on my working machines for at least 30 years now, and I know about permissions. And I also understand that there are good reasons for not rooting an Android device.
But that is not the point here.
I am and I always was talking about the recovery here, not the running LOS system, that you run every day to make any use of your phone at all. From my point of view, as a Linux user, booting into recovery is like taking a secondary boot device, eg a USB memory, and starting another Linux system that is completely independent of the one that my PC is running in normal cases. Using this secondary Linux I can do anything to the system and the hard drive that I want, regardless of permissions. I can re-install the boot manager, I can copy or delete files, I can repair the file system, and, most important: I can create images and snapshots of the system that will serve as an lifeline, a certain point in time that I can return to if it should become necessary.
My question was and still is, why a custom recovery like TWRP can include this function, but the recovery made by LOS can or will not do so, or if there is a chance that the LOS recovery will include this function in the future.
Again: I am not talking (and I never was) about making root available in LOS.
@dvdram
...
My question was and still is, why a custom recovery like TWRP can include this function, but the recovery made by LOS can or will not do so, or if there is a chance that the LOS recovery will include this function in the future.
....
Click to expand...
Click to collapse
Wondering why you don't ask this question to the developers of LineageOS?
jwoegerbauer said:
@dvdram
Wondering why you don't ask this question to the developers of LineageOS?
Click to expand...
Click to collapse
Silly me! I actually believed there would be developers reading this forum. How could I mistaken this statement on the starting page:
"XDA Developers was founded by developers, for developers."
I guess the word "developers" must have another meaning than I have always believed. Thank you for showing me my wrong!