Common ICS Problems
If you plug in USB while your tablet is asleep you will have a SOD
Installation Problems
Install tips from tlb1961 here and lyricalpapa in post #3
Try not to use any backup's as they cause many problems.
Make sure your using CWM 5.5.0.4 Beta 15 (comes with the nvflash in TeamDRH ICS thread)
On your first boot let it sit for 30-60min (the longer, the better) and then reset.
If all else fails try this
Th3DmaN's G-Tablet Tools for anyone who is having trouble connecting and flashing their G-Table
Speed Problems
Different launchers such as Apex or Nova or any compatible launcher may or may not increase smoothness. There is no problem with installing them on top of the stock launcher as only one launcher runs at a time.
Battery and Power Problems
Your tablet went to sleep and wont wake up, try pushing the power button a couple of times and wait 5 seconds inbetween presses.
Your tablet has completely frozen, try pushing the power button for 30+ seconds. If that doesn't do it, you can leave your tablet alone for a couple hours and try again (may or may not work) or you can wait till the battery dies or if your impatient you can open the tablet up and press the internal reset, it looks like this. Here are some helpful pictures and a video for opening it up. If you have no reset button you will need to disconnect the battery, here's what it looks like. If you do get a SOD do this to help the developers.
Connection & Browser Problems
WiFi not working, try to "forget" the WiFi and re-enter your password. Also can try resetting your router or changing the security. Some say ICS does not like high channels.
If your having market errors, try force closing and clearing the cache in settings\apps\all. If that doesn't work then find every market reference and force close then clear the cache and reset.
Your computer doesn't recognize your tablet, you will need MTP drivers read the ICS rom page again. For Windows XP you need to disable debugging. For linux try Th3DmaN's guide.
Adhoc does not work with this build.
Stock browser seems to lock up after a bit. Possible fix is to disable java. Thanks plastikman
Screen and Sound Problems
1080p on H/W? Use Handbrake and import this profile. Here's the high profile settings for 720p, for those wanting the best quality.
Videoplayers such as MxVideo player, can play H/W video but the sound will need to be changed to S/W.
Icons and text too small? Try using this guide. CAUTION Changing the DPI really messes with the Market.
DSP Manager has been causing slowness/audio problems. Try stopping it to see if that's the problem. You can delete it safely if causing problems.
Game and Apps Problems
Alot of games and apps are not updated for ICS yet so they won't work correctly.
Hulu flash hack here. It should work. Anyone with Hulu can you post your results.MAY NOT WORK ANYMORE
Bypassing Exchange Security Policy try this
Connecting the ICS Mail app to Microsoft's Cloud hosted Exchange services check here
Gamepad support - follow jazzruby's guide here
Miscellaneous Problems
Errors popping up constantly, you need to reinstall again and make sure this time you erase everything.
Nandroid backups, you need to follow this guide
Important Notes
The SOD (sleep of death) we talk about is when the device goes into a sleep mode and there is absolutely no other way out but by pressing the internal reset. This is also called a kernel panic.
We are always talking about roms on Bootloader 1.2 unless specified.
When installing or removing things from the system, it is always a good idea to reset and clean the cache, clean the dalvik cache and fix permissions.
USB problems sometimes are caused by your own computer, you may have to restart/change USB port/change USB cables/check your USB drivers
Windows 7 is the implied OS most are working on, if you have different then ask.
IF I'M MISSING SOMETHING PLEASE LET ME KNOW
Stuff that WILL cause a SOD (sleep of death) causing you to push the internal reset
DON'T DO THESE
If you plug in USB while your tablet is asleep you will have a SOD
If you do get a SOD please do this so the developers can help.
Use the reset button
Don't power the tablet off at all, just use the internal reset button
Don't touch the tab or do anything but logging into adb.
If for some reason you can't open adb, you can use terminal on the rom
At the prompt type:
Code:
su
Hit enter and then
Code:
cat /proc/last_kmsg
If this doesn't work, the easier way is to access it is with a root explorer by going to /proc and then copy last_kmsg to /sdcard (rename to last_kmsg.txt or zip it up in a file).
Copy and paste the results to a paste bin and post the link. If you don't know pastebin then just post the last 10 lines or so.
tlb1961 install guide
Howdy all,
Glad to hear most are having good luck with this newer revision. To those seeing odd issues after install, I would suggest start over from scratch and clean out the gTab prior to reinstall including repartition the internal SDCard. Run the ROM for a bit before installing anything else. If you have a lot of media files on an microSD card then let it sit for a little while. Once the ROM is running smoothly you should then apply the latest the3dman GApps package.
I know it's tempting to try and hang onto old configs and settings, but it will give you a better experience in the long run if all old data is cleared.
Click to expand...
Click to collapse
lyricalpapa installation essentials
Here's some things I do that work for me:
1. Give my tablet time to boot - let G-Mail, Google Maps, and the other apps load in, talk to the mail server, etc. I watch the activity in the "broadcast" symbol and wait for the browser widget to display its bookmarked pages.
2. Follow the dev's install instructions and @serialplague's FAQ - goes without saying.
3. Have Patience - I give the cache driver's balancing and optimising routines time to do their work after I load a ROM, plus any time I add/remove apps or any time I make changes to the settings. Remember this is a Beta Test ROM and not a snapshot image of a fully tested, optimised, and balanced ROM that you would get if you were to buy a new ASUS Transformer or whatever.
4. Use the apps the Dev's gave us with the Beta ROM - I use the Elixir app regularly to check if the CPU and I/O activity levels have dropped down to near 0% for both. I check them after installing my ROM's, etc. (I also now use the Diagnosis app thanks to @oldtimer)
5. Remember the G tablet only has 512M DDR-2 RAM on board and was built to run with a 2.2 Froyo ROM, a cadged 2.6.32 kernel, and slow generic drivers. Google's minimum published specification for a system running Honeycomb or newer is a Nvidia Tegra-2 processor and 1G of RAM. So the challenge is to modify and tune the 2.6.39 kernel drivers and the ICS ROM to live within the available 512M RAM.
6. edit-no longer needed
7. Killing unnecessary apps sometimes frees up enough memory to stop the CPU and I/O churning. But I have to be careful which apps I kill using an app like Advanced Task Accelerator - it can shut down necessary services - although Android will usually restart them automatically (and kick up the CPU and I/O activity while doing so)
8. Remember that Google Apps come with a high overhead price - the standard Viewsonic set-up for the G tablet does not include GAPPs, and it runs very fast. The same for many other tablets that don't have a Tegra-2 and 1G of RAM. Game players might want to experiment with not loading GAPPs. In the past I've done this by downloading all the apps that I was interested in from GAPPs, then copying them all out to my PC using the "adb pull" command ("adb remount" to get in as root). Then I wipe and reload the ROM without GAPPs, and use "adb push" to put the apps in the right directories. Then on my G tablet, I find the apps using Root Explorer and "click" on them to install them.
Lyricalpapa
Click to expand...
Click to collapse
How do I stop my tablet from downloading every app I have ever owned or used from the market when I log into my android account.
I suspect I am doing something wrong because the tablet is very laggy with ICS.
When you first install it will ask you if you want to use your backups, just uncheck that. Or you can let it sit for awhile, 30min to an hour, it sucks but once everything calms down its much better.
Android Keyboard
Good men of this forum,
It seems that with the new ICS rom, I am having issues with my android keyboard. If my tablet is vertical, I have the dialpad-looking keyboard with what seems to be Japanese characters on a few buttons. When my tablet is in the horizontal orientation, the keyboard disappears completely. I have searched the popular forums here and with Google. I'm terribly sorry if I have missed a tip somewhere.
I used the flashing procedure on the TeamDRH website to the letter, and I am no stranger to flashing custom ROMs to android devices. The keyboard continues to work beautifully under Froyo and Gingerbread ROMs, as well as the earliest beta of ICS. I only seem to have an issue with this version of ICS.
I'm also getting frequent Google Apps errors about the services stopping. After signing in with my account, Market crashed and disappeared from my apps menu altogether.
It seems that I have a fairly unique problem. I'm a linux sysadmin and I'm very handy with the command line if you need dmesg or kernel output.
Thank you in advance.
I've heard a couple of people are having problems with the GApps, have you tried installing with the lite 7b GApps?
No Luck
Thanks for the reply!
I have tried both the full and lite versions of 7A and 7B for this ROM with no luck. When I perform a first-time boot of the tablet after a ROM and Gapps, the very first message I encounter is "Unfortunately, the process com.google.process.gapps has stopped" for any version of Gapps, and it continues to pop up every several seconds that the tablet is in use.
I have also tried installing the ROM without Gapps at all and the keyboard is still nowhere to be found. Odd that the keyboard works in the first beta (1E), but this ICS (2B) is much faster than the old one
If anyone has a link to download the ICS Preview 2A instead of 2B I would be interested in trying it out, the links on TeamDRH's website all point to 2B now.
Other useful info: I know for certain that I am running the 1.2 bootloader and I'm using the newest Clockworkmod v5.5.0.4 Beta 15. I like to re-format before every flash to ensure a clean start.
Thats very odd it sounds like the download may have been corrupted. I've seen it happen a couple of people.
I still have 2A and some previous ones, kinda a catalog lol, just PM if you want to go that way.
I'm a newb
Thank you very much for the help you've provided me.
I tried downloading 2B a few more times with the same issue :/ so strange. Unfortunately for me, I am below the 10 post minimum to allow PMs. It's kind of ironic actually, I've been a member for years and always found my answers without having to ask because xda is wonderful about providing info
Thanks again.
Sent ya an email
simplyphp has a great writeup on an installation method you could try his way
SUCCESS!
Using the simplyphp method you referred me to, not only does the 2A ROM work, but the newest ROM and Gapps as well! I must admit that I'm a little embarrassed that I can't actually identify the original problem, but I believe it has something to do with my installation of Clockworkmod. I got it from a forum here that is trustworthy, but it didn't seem to work exactly as I needed it until I installed it with nvflash. I also had a strange problem with the first flash (out of the two that I am supposed to do) in that it wouldn't boot all the way into the TnT factory OS and was in an endless reboot. I simply turned it off, booted into APX mode once again, and continued with the listed steps and it worked flawlessly. I would thank simplyphp but I can't post on development threads yet!
So thank you and have a "Thanks!", I hope I've contributed to your wealth of knowledge on troubleshooting.
Related
After installing TNT 4.1.0 the market goes out almost daily. Even the market fix still sometimes won't take. I'm restoring the previous version of TNT until further updates.
Q: Has anyone else had this issue or has been able to solve the market problem?
Thanks in advance!
Most Market issues are resolved when you set your partition to 2048 with 0 swap. Did you install the data2loop? This is another culprit of having Market issues..
Also, make sure when you shut down you do a proper shut down and don't just hold the power button. I suspect many are not doing a proper shut down and are causing corruption on their file system. You will know your doing a full shut down if you get the Viewsonic Screen.
We must all realize that under the covers this is linux and need to follow all the same best practices to ensure integrity of the system.
Having the suspend / resume button as the same as a full power off really is a bad design for this type of device. This is why on the iPAD/iPHone you can not perform a hard reboot unless you hold down two buttons.
Droiddoes said:
After installing TNT 4.1.0 the market goes out almost daily. Even the market fix still sometimes won't take. I'm restoring the previous version of TNT until further updates.
Q: Has anyone else had this issue or has been able to solve the market problem?
Thanks in advance!
Click to expand...
Click to collapse
No I have not done an improper shut down, I hit power button select POWER OFF then again POWER OFF and get POWERING OFF with the animated circle. As fas as data2loop, I have not installed it and I've never changed the partition or swap information.
I was just wonfering if anyone else was having this issue? By the way I really appreciate your quick response to my post!
===========================================================
Another problem that users have is that they don't realize that if they are not connected to the internet, there is no market. Some folks with less experience think that the tablet is just like their phone with an always on connection. I thought I'd mention it in case someone is reading this thread that has had this happen. I don't want to mention names (MY WIFE) was trying to use the market while not connected. Oops looks like I'm sleeping with the dog tonight
Google itself is having problems with market itself the last week. I am seeing more problems related to this with the new TnT. I haven't really had any problems with Vegan. You probably should repartition your sdcard if you haven't already done so. This seems to help random problems. Something about the way the factory partition seems to be off. Make a backup of your apps with Titanium and put a copy on either an external sdcard, your pc or make a dropbox account and sync your backup there. Partition your sdcard, flash your rom and then restore your apps
I'm back on a vanilla 4.1.0 and (so far) no market issues. Vanilla meaning no customized kernels. Been running it for two days, now.
roebeet said:
I'm back on a vanilla 4.1.0 and (so far) no market issues. Vanilla meaning no customized kernels. Been running it for two days, now.
Click to expand...
Click to collapse
Same here! Everything's Stable. No Market issues here.
I had the same Market issue once after updating from 2.2 to 4.1. I always shut down correctly. It's been a couple days now without problems.
Anyone have any tips for troubleshooting unresponsefulness in running the latest version of TeamDRH ICS (7/2/12 release)?
I'm experiencing random pauses where apps just won't respond for a few seconds, although the system asks if I want to FC or wait, so it doesn't seem like the underlying system is not working.
WiFi is also painfully slow for some reason--and it shows the signal strength as not being full even though I may be very close to the AP.
I've been reading about resetting the cache and fixing permissions to try and address both issues. Will be trying it and reporting, but can anyone offer any other tips?
in the main thread for the rom, there are several tweaks, most notably changing your build.prop to user from userdebug. Also, you can turn off a few transition animations. SEARCH the main thread for these tweaks, there are four, and they are listed together. Once you do a fresh install of this rom, BEFORE you login to your google account, let the tablet sit turned on for about an hour. I dont even have a google account logged in on mine. I also never have the pauses you're talking about.
redeyedjedi said:
in the main thread for the rom, there are several tweaks, most notably changing your build.prop to user from userdebug. Also, you can turn off a few transition animations. SEARCH the main thread for these tweaks, there are four, and they are listed together. Once you do a fresh install of this rom, BEFORE you login to your google account, let the tablet sit turned on for about an hour. I dont even have a google account logged in on mine. I also never have the pauses you're talking about.
Click to expand...
Click to collapse
I followed those steps but I didn't leave it alone for that long. I too however have long lags.
redeyedjedi said:
in the main thread for the rom, there are several tweaks, most notably changing your build.prop to user from userdebug. Also, you can turn off a few transition animations. SEARCH the main thread for these tweaks, there are four, and they are listed together. Once you do a fresh install of this rom, BEFORE you login to your google account, let the tablet sit turned on for about an hour. I dont even have a google account logged in on mine. I also never have the pauses you're talking about.
Click to expand...
Click to collapse
Alright. I reset the cache and fixed permissions, and everything is FC'ing like crazy. I also see the resource monitor mostly blue. I'm going to start over from literally square zero after I run Appbak and Ti to backup everything onto an external SD card.
One thing I noticed when I first went through the setup was that I only have one SD card, when I seemed to remember there were two--one for internal system, and one for the internal SD card. Then, when I plugged in a "real" SD card, there was another one.
I'm not sure if I screwed something up along the way--this tablet's had more ROM's than I can remember.
redeyedjedi said:
Once you do a fresh install of this rom, BEFORE you login to your google account, let the tablet sit turned on for about an hour. I dont even have a google account logged in on mine.
Click to expand...
Click to collapse
Did a fresh install and now am booted at page where it's asking me for the WiFi password. Is this where I let it sit? Or can/should I connect WiFi and then let it sit for the hour or more?
Final Update
I waited an hour, and then logged into the WiFi, and waiting another hour or so before I did anything. Then I went ahead and did the following from this post:
http://forum.xda-developers.com/showthread.php?p=28984759&highlight=rom+control#post28984759
"I also see that the ro.build.type is set to "userdebug" in /system/build.prop instead of the commonly seen build.type of "user". Changing the build.type to "user" stops most of the ANRs. I don't know how Android is built, but, in the Linux world, we usually have 2 kinds of builds for a product: release (what gets shipped) and internal (AKA engineering). The difference is mainly in what compiler flags are used when building the product. For engineering builds, compiler optimizations are turned off and the debugging flags are turned on. These builds are pretty slow and use a lot more memory and CPU than the release builds. Going by what I said about the build.type and ANRs above, this is one thing for the devs to check.
Try these things to reduce lag:
In Settings > ROM Control (set on boot if you're happy with)
1. Reduce dalvik VM heap size for apps to 64M.
2. Reduce the free memory setting to 50MB.
In Settings > Developer options (need to set on each boot)
3. Reduce the no. of Background Processes to 1 or 2.
4. Check the Destroy Activities ... option."
Seems to working okay--especially no. 3.
Fingers crossed.
HI guys, I'm hoping you can help me with a problem that's led me to start threatening my galaxy ace (S5830i) with a hammer.
Actually it's not the phone's fault it's purely my own stupidity, but none-the-less I'm here for help because I've spent all day and night trawling the net, trying to figure out how to proceed to resolve my issue on my own but I simply cannot make sense of the conflicting information I'm finding.
I promise you thing thing if nothing else, I have tried my very best to read around a hundred other forums, pages, and how 'to's but I'm finding that I have no resolution that I can work with because either:
- The tutorials turned out to be for the S5830 - not the i model - when I got to the forum
- The youtube videos all seem to be spoken in accents I cannot understand or not explained clearly, or are too technical
- Links I go to to get apk files etc are broken, wrong or leading me up another path I cannot follow
- Software does NOT look on my screen as it does on tutorials or websites (SDK for example)
- The people explaining the resolution type with such poor English I cannot understand what they're actually saying
- The solutions that work for others are too technical or advanced for me to understand and I'm finding it difficult to learn as I go (apart frm the root instructions which I found quite easy)
Anyway, I'll start at the beginning:
I have a samsung galaxy ace (S5830i) running:
- Gingerbread 2.3.6
- Baseband version S5830iXXLK1
- Kernel version 2.6.35.7
- Build number GINGERBREAD.XXLK3
I've already rooted it so I have superuser access, and I managed that perfectly well on my own
I installed titanium backup and somehow I managed to uninstall the stock email that comes with the phone. I think this is my problem because I now cannot download anything from google play, nor can I add a new gmail account to do so, so I'm stuck in no mans land not able to use googleplay (because my gmail account is now missing from my phone) nor can I seem to figure out how to get th apk file directly into the phone so that I can start fresh.
I'm also absolutely stuck on how to flash the phone and start again because nothing I seem to read is explaining it in simple clear terms that a layman can understand. When I do find a simple explanation, I find it's only for the non 'i' version of the phone, or if I find a simple instruction it's zip files for the rom do not contain all the files I need to use with odin v1.5
Also, there are conflicting explanations on flashing the rom on different forums/sites so I dare not use one over the other because another one contradicts it. I do not want to ruin my phone as right now it still basically works for now as a phone.
In my phone menu, the gmail icon is still there, just not the icon/app that said "email". The icon is now missing from my menus and with it there is now no way to use the play services without a gmail account on the phone.
When I click the gmail icon, it stats to open and then just shuts off quickly, not opening gmail, so I'm pretty sure all this is due to me deleting the email app using titanium backup.
Make sense?
What I'd really be grateful for is if on of you guys could help me out and explain in very simple terms what I need to do to either install the apk directly (preferred) so that I can add a gmail account to the phone and get access to google play again, or failing that a simple how to flash the rom with stock gingerbread, together with links to software that's known to be bonafide.
I am literally being driven mad going around in circles on forums and sites to keep going back to square one.
Any help will be very gratefully received. Or I'm afraid this may mean I'm going to smash my new phone int a wall and never use a smartphone again, because obviously I'm too stupid to play around with them on my own.
I really appreciate your help if someone would be able to invest a little time here.
Thanks very much for your time, guys
Jobeeey
additional info
Right, these are the instructions I found on this forum, but I'm unclear if I'm approaching this right..
Flashing s5830i with Odin v1.85
1.Turn off the phone and put it in Download mode by pressing Power+Volume Up+volume down.
2.Open Odin v1.85.Run as Administrator!.
3.Put the files in Odin and don't touch the settings
4.If it's a one-file firmware put it in PDA section.
If it's multiple put the files in the correct section.
5.Click start and don't touch the phone!Don't turn off computer and don't unplug the phone!It will reboot automatically and the first boot will take some time,so don't panic!
Click to expand...
Click to collapse
I've found a rom (which is a single file) and if I'm reading this right I place that in the PDA section of Odin after installing the usb drivers onto my pc (done that and windows recognizes my phone in the sense that it isn't now hassling me for drivers every two seconds).
Ok.. so I seem to have got the correct rom for my specific ace model.. and the instructions seem to be that I now:
1) Connect usb cable
2) Boot my phone into download mode (I can do that I think).. but at what point do I press vol down to download a new os.. before or after pressing start in Odin?
3) Open Odin and add file as in my attached screenshot (I can do that)
4) Click 'start' in Odin
5) Wait for my phone to reboot
And that should be job done, the phone should be flashed with the stock rom again and that should get me back on track, right? Or am I about to screw up my phone and ruin it even further?
Thanks for reading. I hope someone can advise if I'm doing this right as I've seen other forums say that I should tick the 'Re-partition' box, and other that say I shouldn't, and this one says nothing about it at all.
This is one of the tings that's confusing me, and once I'm now flashing a phone for the first time it's flippin scary to do it on my lonesome!
This is what I mean..
I've just tested going into download mode with odin ready, and the phone gets there (vol up+down + power on).. but each time it gets into download mode it seems to disconnect from odin and no com port is open. I get the windows device disconnected/connected beeping and the connection seems to sever.
What the Fffff...
This is exactly what I'm talking about.. nothing seems to be working like it's meant to be and I'm getting nowhere with any instructions I can find after god knows how many hours researching this.
:crying:
update (lol)
Mornin all,
So, just in case anyone finds this useful..
The flashing problem is kind of irrelevant now because:
A) Odin (tried several versions) simply will not stay connected to my phone when it boots into download mode, and having checked many tutorials for this it sees that this is a problem some of us cannot get past.
Anyway, one of the methods to resolve this was to wipe the cache and clear all data etc, which I did, and now my phone is stuck on the "pres the android" screen, and my phone will no longer get past that. Tried pressing clockwise in all four corners but still nothing.
No probs.. so we move on to a new step of trying to split the roms via cygwin, but guess what? Every single time I try to download the cygwin files, that freezes at about 98% and will not download, no matter which mirror I select.
So, this is what I call a curse that isn't going to be lifted by me no matter hat. It's not not meant to be.
Therefore, what I'm going to do is take it to a local shop that unlocks mobiles and give it to them to flash back to stock rom for me.
If that doesn't work, do you know what I'm gonna do?
Nothing. Because there's nothing you can do when the processes do not follow the same progress as they do in the tutorials.
I hope other novice S5830i users save themselves all his time and trouble and don't bother following the same process and become locked out of their phone at the touch android screen.
Update
Yipee,
Right, I stumbled across a solution that worked for me.
What I did was get my 2gb msd card that came with the phone and slapped MindCR v1.0.12 on the card and whacked that in my phone (this bypassed not being able to get a new rom on the sd card as it wasn't unmounted before the crash, so my pc wouldn't recognise the date to put it on via the pc).
Then I updated the rom from that 2gb card (vol up + menu + power to get into recovery mode) and it took it a few minutes to update the firmware and give me back the full use of my phone, and with a shiny new os on it. Whoop!
I didn't bother with CWM as I'd forgotten to add it before flashing, but it worked none-the-less and I'm now back in business (wiped it manually).
As it turned out this version of MindCR works really well so far as I can tell. I realise there are updated roms now but I've come to the conclusion after the scare I had that if you're not entirely sure what you're doing, it's best to leave it alone if it ain't broke.
SO.. now I have a phone with what seems to be a better os than the stock and less bloatware on it, no phone problems I can see after thorough testing... and from what I can tell it turned out to be better than it was before the disaster.
And I learned a bit in the process. Like for example, don't feck around removing apps from smartphones with titanium unless you've backed them up and you're prepared to stress out for over 20hrs wondering what to do about it.
And, also, don't expect much help from a forum because you may not always get it. << That' not a dig at xda by the way. It's just a BIG forum so your threads may not be seen by the right person before they get buried in past pages.
Hope my little journey helps another unsuspecting S5830i user who comes across the thread.
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)
Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*
I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.
JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.
Logs or it didn't happen.
Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.
I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...
Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.
Im new to all this so pay no attention if its nonsence...
My S5 G900f has a qualcomm snapdragon chipset, that doesn't support monitor mode, which i believe means that it doesnt support packet injections or packet capturing (driver related?)
using the dsploit.apk for things like session hijacking, replacing web page images of a target and using script 'injection' to inject custom java script into a target web page, all sounds like things you'd need monitor mode to do. and if it is then i was able to do it with my S5.
I dont know a lot about coding or how it all fits together and communicates with the hardware, so i may sound completely stupid, but this has done my head in for ages, so why not get it out there.
1. when i attempted to upgrade from my first custom rom, i had a bit of trouble, softbricked my phone and then flashed the two roms in various, alternate, wipe, format and install combinations until it finally booted to set up, and i stopped panicking. but this caused features from the first rom to appear within the second rom.
ie: 3minute battery mod was installed through a add-on zip along with the first rom and nothing to do with the second at all.
2. inconsistencies within the file system, like file names that were apps included with the first rom.
3. dsploit.apk was bugged and crashed every 5 or 10 minutes. then would seem to glitch or stutter for a couple seconds before correcting its self and accomplishing its pen test.
4. i also remember watching green text in the terminal as it failed to connect or ID some part of the system but continued to retry in quick succession until it glitched and worked. (i think this was a similar type of app i was trying out at the same time but instead of GUI stutters, i could see the text rapidly stuttering and glitching.)
4. the dsploit.apk worked for me back then, even though it was temperamental. ive downloaded the apk a couple times since with various roms and ive got no where with it...
was thinking maybe different aspects of the two roms had been filed or grouped together and created unstable triggers within the software, allowing it to briefly communicate with the chipset. i may be way off, but ive been sat here waiting for someone to solve this issue forever, i thought id share my thoughts, on the off chance it turns out to be something and i can finally get my S5 into monitor mode without OTG cables and other unwanted auxiliary components.
thanks in advance
G Carter
Do a clean install of you ROM, and please, don't panick. If you want to have a good time flashing ROMs and stuff, panicking is the last thing you want to do, it will cause stress and stress can lead to not being careful enough so stuff like this happens, well, always, if you are experiencing issues do a clean install. Just boot into recovery (I recommend TWRP) and wipe everything except external sd. Open ADB and sideload the ROM (or, if you have enough memory on a flash drive, plug it into your android and flash it from there) and then Google Apps.