[Q] Tablet is melting down - Galaxy Tab S Q&A, Help & Troubleshooting

I went to use my tablet before bed, and I found it on, very dim, with the standard Samsung logo displayed. It was stuck, so I had to hold the power button and volume buttons down to reset it. After that, it would take close to 3 minutes to boot, be at a black screen, and come up with a standard Android error box saying: "Process system isn't responding." with the "Wait" or "OK" options. Pressing wait made the box go away, the screen stay black (albeit with the time and battery visible), and nothing happened. Pressing "OK" made the system reboot and start the whole process over.
After a couple times of this, I took out the SD card to see if it was the culprit, and then started in safe mode. Safe mode started properly, and everything worked fine (minus all my applications being gone because they're on the card). I turned it off, inserted the card, and restarted. It loaded properly again, however this time, it wouldn't load any widgets and several of my icons were just missing. There was no corrolation to what was appearing properly and what wasn't that I could find. I restarted from the menu again, and it started the black screen error screen process again. I'm kind of at a loss, because I have no idea what this means.
I'd obviously love to go without wiping the device, but even more obviously am willing to before accepting defeat. It's on the stock 5.0.4 image (the Korean one ¬_¬), and I'm unlocked and rooted, though nothing fancy has been done. Is this hardware? Software? Anyone run into this before? Every search I did ended up with someone having it be a ROM issue, but since I'm not on a ROM, I don't know where to go from here. :-/ Any advice would be greatly appreciated!
I couldn't take a screenshot of the black screen, but I've attached what it looked like when everything failed to load. Facebook and Google Play Books should be on the bottom menu, and a lot of my drawers are missing a ton of apps. However, Hearthstone and Fenix still show up, both of which are on my SD card. I'm so confused.

It looks like the os has become corrupt somehow. Reflash the stock firmware from sammobile or samsung-updates.
By the way a Rom is the operating system software.

ashyx said:
It looks like the os has become corrupt somehow. Reflash the stock firmware from sammobile or samsung-updates.
By the way a Rom is the operating system software.
Click to expand...
Click to collapse
Do you know how that would happen? Is it random? I'm trying to figure out what caused it. :-/ Are there any good 5.1 ROMs you would recommend? May as well go there if I have to reflash everything anyway.

The widget errors on your picture, have you moved the apps to you microsd, when you remove your microsd and reboot, the widgets cannot find the data as it was on the microsd.
John.

Tinderbox (UK) said:
The widget errors on your picture, have you moved the apps to you microsd, when you remove your microsd and reboot, the widgets cannot find the data as it was on the microsd.
John.
Click to expand...
Click to collapse
This picture was taken while the SD card was in and functioning. Several of the games and apps I have show up on there as well. The top widget in the picture is just a clock widget, which is on the main device.

If it starts ok in safe mode then you probably need to do a data partition wipe as something is corrupt.
Back up everything you need and then wipe data/reset in recovery.

ashyx said:
If it starts ok in safe mode then you probably need to do a data partition wipe as something is corrupt.
Back up everything you need and then wipe data/reset in recovery.
Click to expand...
Click to collapse
I'll have to try that in the morning. I'm a bit noobish at the detailed workings, if I do a nandroid it will just copy whatever is corrupt, right? I'd need to do a legit wipe?

greycobalt said:
I'll have to try that in the morning. I'm a bit noobish at the detailed workings, if I do a nandroid it will just copy whatever is corrupt, right? I'd need to do a legit wipe?
Click to expand...
Click to collapse
Better to back everything up with titanium backup then restore what you need from that.

ashyx said:
Better to back everything up with titanium backup then restore what you need from that.
Click to expand...
Click to collapse
All right. I'll probably do that now. Is there any decent 5.1 image anyone can recommend? As long as I can use it to read books and connect it to my stereo, I'm good waiting for bugs to be fixed.

greycobalt said:
All right. I'll probably do that now. Is there any decent 5.1 image anyone can recommend? As long as I can use it to read books and connect it to my stereo, I'm good waiting for bugs to be fixed.
Click to expand...
Click to collapse
Wipe data/reset won't affect the system partition so no need to reflash.

ashyx said:
Wipe data/reset won't affect the system partition so no need to reflash.
Click to expand...
Click to collapse
So I tried a couple ROMs out, and I'm having a few problems:
- None of them account for a tablet-sized screen, so the pull-down part of status/notification bar is teeny-tiny and my sausage fingers mash all the buttons. I don't suppose there's any way to make it the same size as the stock bar?
- When I'm playing a game (not even anything graphic-intensive) the back of the tablet gets insanely hot. Specifically the top-right portion of it. This never happened before...is this a general problem?
- When I'm playing music or noises through bluetooth, the sound is delayed by as much 5 seconds. If I tap play, the tablet will play it, but it won't start coming out of the speaker for 5 seconds.
Are these fairly common? Any advice? I was thinking of just going back to stock 5.0.2 so I don't have to whine.

Related

[Q] Motherboard

So yea...as much as I know my desire's motherboard needs replacement...And I dont have warranty. Is there any way to fix it without changeing whole motherboard?
You provide us no information at all about what's wrong with your device.
What do you want to do with it? Solder stuff?
There is a 100% chance that you will destroy your phone when you open it and mess around with the subminiaturized highly vulnerable microelectronics.
There's something called insurance.
Swyped...
hypophysis said:
You provide us no information at all about what's wrong with your device.
What do you want to do with it? Solder stuff?
There is a 100% chance that you will destroy your phone when you open it and mess around with the subminiaturized highly vulnerable microelectronics.
Click to expand...
Click to collapse
It restarts,boot loop i think it's called. So I cant afford new motherboard so could I take my phone to some1 that knows what he's doing and could he fix it?
LordRyver said:
It restarts,boot loop i think it's called. So I cant afford new motherboard so could I take my phone to some1 that knows what he's doing and could he fix it?
Click to expand...
Click to collapse
Maybe the forum can help you
For this we need some more information:
1. Do you have the original HTC Sense ROM?
1a. If YES skip the points 2 - 5 and continue with 6.
2. If NO: which ROM you have installed?
3. Did you change the Radio ROM?
4. Have you unrooted your phone?
5. Are you S-Off / changed Hboot (partition table)
6. Do you use the original SD-Card?
7. Since your reboots started: have you installed any software just before?
8. Which program(s)
If you can answer these question we can help you - I don't think (hope) your motherboard is dead. Often there are simple solution to fix a "dead" phone
MonacoHias said:
Maybe the forum can help you
For this we need some more information:
1. Do you have the original HTC Sense ROM?
1a. If YES skip the points 2 - 5 and continue with 6.
2. If NO: which ROM you have installed?
3. Did you change the Radio ROM?
4. Have you unrooted your phone?
5. Are you S-Off / changed Hboot (partition table)
6. Do you use the original SD-Card?
7. Since your reboots started: have you installed any software just before?
8. Which program(s)
If you can answer these question we can help you - I don't think (hope) your motherboard is dead. Often there are simple solution to fix a "dead" phone
Click to expand...
Click to collapse
1. I had,but it used to turn off and get into boot loop while playing games like GRave defense. Never happened while playing shoot bubbules.
2. DevNull. First was dev,then leedroid,now back to dev. I keep him in sd card in case my phone wont turn on. Sometimes it restarts in middle of movie so I left him 2 times until morning and it first time turned on and second time didnt,again started to restart. Same with reflashing roms. Sometimes helps,sometimes no.
3.Yes.Radio_32.56.00.32U_5.17.05.08
4.Yes. I had hboot 0.83 or 0.93 and I used AlpharevX and then unrevoked.
5.Yes.
6.I dont know, I got it when I bought phone. (it was used when I bought it.)
7.Hm......Well...I dont think so...when I bought it, I turned phone off and after um... about 1 h I tryed turn it on and it started restarting. Then after some time turened on again.
And btw now it sometimes starts restarting not even hot.
So your problem is random reboots? or does your device not start up at all?
If the problem is just a bootloop, you won't need to replace the motherboard. You just need to flash the correct and working software.
mortenmhp said:
So your problem is random reboots? or does your device not start up at all?
If the problem is just a bootloop, you won't need to replace the motherboard. You just need to flash the correct and working software.
Click to expand...
Click to collapse
But that used to happened with original rom too...un...one guy said that bootloop is because motherboard is faulty. Now I just watched whole movie. And it was ok. But I tink if I would use market or opera it would restart. But im not sure. Sometimes it dosnt restart. And if I would flash all correct software my phone would turn on quicker?
oh god...
Don't answer my question with the word but. It's NOT an answer. So lets take the question again and this time do only reply to the question:
Is you problem random reboots or a bootloop?
Those 2 are NOT the same, while random reboots is exactly what the name implies a bootloop implies that your phone is unable to enter the android system due to a failure on startup.
So please in order for anyone to help you, you must make it very clear what you problem is, as otherwise we cannot tell you what to do.
Everything you have told up until now is that you have some problem(you use bootloop and random reboot equally) and that you might or might not know that it happens when running some specific apps.
mortenmhp said:
oh god...
Don't answer my question with the word but. It's NOT an answer. So lets take the question again and this time do only reply to the question:
Is you problem random reboots or a bootloop?
Those 2 are NOT the same, while random reboots is exactly what the name implies a bootloop implies that your phone is unable to enter the android system due to a failure on startup.
So please in order for anyone to help you, you must make it very clear what you problem is, as otherwise we cannot tell you what to do.
Everything you have told up until now is that you have some problem(you use bootloop and random reboot equally) and that you might or might not know that it happens when running some specific apps.
Click to expand...
Click to collapse
Sorry. By bootloop I mean my phone restarts and then just starts viberating and just stays in white htc logo screen. But after some time I can enter android system. This happanes when I do something with my phone.
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
777ace said:
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
Click to expand...
Click to collapse
Did that already...first time all was the same,but now looks kinnda better. If it wont go to restarting screen while chagring i'll be happy...After doing factory reset it started to move things from pc to sd very slowly.
777ace said:
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
Click to expand...
Click to collapse
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
MonacoHias said:
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
Click to expand...
Click to collapse
Well now it runs rll great And I didn't do anything different. It restarted while charging but at about 98% it was cold again and I succesufly turened it on with first try. If something will go wrong i'll try do 777ace guide. Now I would like to ask...what to do that files would get transefered from my pc to sd faster? Because when my battery is not full it starts charging and overheating and restarting. Also isnt overheating and restarting caused by bad motherboard?
MonacoHias said:
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
Click to expand...
Click to collapse
Also if there is bad app,could I try downloading it again after restoring with titanium?
LordRyver said:
Also if there is bad app,could I try downloading it again after restoring with titanium?
Click to expand...
Click to collapse
Sure you can.
With a bad app I ment that an app can mess up your system (not a corrupted program file).
For example task killers I would name "bad" apps as they are useless in current ROM and maybe could things worse.
A very important tip at the end: perform Nandroid backups on a regular basis - so you can allways come back to a working system.
LordRyver said:
...
Now I would like to ask...what to do that files would get transefered from my pc to sd faster? Because when my battery is not full it starts charging and overheating and restarting. Also isnt overheating and restarting caused by bad motherboard?
Click to expand...
Click to collapse
Do you use Windows or Linux? For me file transfer on Linux is much slower compared to Windows. Sometimes it helps to switch to another USB port on your PC.
Does your Desire also restarts when you use the power supply (charging not via PC)?
MonacoHias said:
Do you use Windows or Linux? For me file transfer on Linux is much slower compared to Windows. Sometimes it helps to switch to another USB port on your PC.
Does your Desire also restarts when you use the power supply (charging not via PC)?
Click to expand...
Click to collapse
Windows. Yes. It gets overheat. And switching to another USB port didn't helped. But I noticed that usb cable's part that puts into pc was a bit hot.
MonacoHias said:
Sure you can.
With a bad app I ment that an app can mess up your system (not a corrupted program file).
For example task killers I would name "bad" apps as they are useless in current ROM and maybe could things worse.
A very important tip at the end: perform Nandroid backups on a regular basis - so you can allways come back to a working system.
Click to expand...
Click to collapse
hm...I think problems start when I install classic ghost radar
Ok...can some1 explain me. my phone started to restart while moving movie from pc to sd. Now it's cold. But when I turn it on, it loads and after 1 sec in android system it starts restarting again. why?

[Q] Unusual problem installing Jellytime R16

I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?
I don't think it's permanent maybe a bad zip? Did you check MD5 checksum before you flash? And did you full wipe?
Sorry, I don't think I made myself clear. I do have a damaged touch screen nothing to do with the rom. There is a section of the touch screen that just doesn't work. It is this part that sits exactly where the start button is. It is a shame these start screens don't rotate or the start button was slightly bigger.
So if I could skip this fisr language selection screen I would probably be ok for using the rest of the rom.
I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).
foxx1337 said:
I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).
Click to expand...
Click to collapse
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.
Skunkworx said:
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.
Click to expand...
Click to collapse
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."
bananagranola said:
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."
Click to expand...
Click to collapse
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?
Skunkworx said:
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?
Click to expand...
Click to collapse
Yes there is. You can use the "adb shell input keyevent <event_code>" command.
You'll probably want to send the DPAD_CENTER command to click that button. I think its event code is 23. Try typing "adb shell input keyevent 23".
Try the code for KEYCODE_ENTER as well.. its 66.
There is a whole list of keyevents at this link:
http://developer.android.com/reference/android/view/KeyEvent.html
Just lookup the "Constant Value" in the description of whatever KEYCODE_xxx you're trying to simulate and use that constant value as the event_code for the command.
I've tried simulating the DPAD_LEFT and DPAD_RIGHT keypress and they're working like a charm
---------- Post added at 04:34 PM ---------- Previous post was at 04:14 PM ----------
Yup. I've tried working with these Keycodes and they work fine.
Use event_codes 19 for UP, 20 for DOWN, 21 for LEFT, 22 for RIGHT to navigate to whatever button you need to press and then use 23 for pressing that button.
Should solve your problem.
Skunkworx said:
I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?
Click to expand...
Click to collapse
Hi, did you flash Gapps as well? I've moved from ARHD (which has the configuration start screen) to JellyTime and never got the language or any other configuration start screen (which I'm glad to get rid of). I always full wiped, clean flashed just the ROM, then booted into the OS for the first time to check it out. No Gapps and no language/configuration screen - it would always go straight to the lock screen where I would just swipe to the right and it would ask me to choose either the Nova or Trebuchet launcher. I'd then rebooted into recovery again and flashed Gapps. Hope this helps.
if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Skunkworx said:
if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
For moving SMS, I'd suggest this app : https://play.google.com/store/apps/...mNvbS5yaXRlc2hzYWh1LlNNU0JhY2t1cFJlc3RvcmUiXQ..
And as far as flashing the updates of JellyTime are concerned... It is recommended to always full wipe but you might get away with flashing the update over the previous version without a wipe. In some updates the author of the ROM explicitly says that full wipe is needed... in those cases you must. In other cases you can flash the ROM without the wipe which will keep your apps and data intact. However, it would still be better to wipe your cache and dalvik cache atleast.
Using Titanium Backup is not recommended at all when you're switching between different Android versions.. however I personally think it works ok when used between updates of the same ROM.
Skunkworx said:
Divche: Thanks, that did the trick perfectly.
Click to expand...
Click to collapse
I never encountered the config screen, so it was more of a guess based on what I did, so I'm glad it helped!
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom.
Click to expand...
Click to collapse
I also had all my contacts as phone contacts too. I chose to convert my contacts (and my calendar as well) to google for ease of syncing later on, so I have no tried and tested suggestions on how to maintain them as phone contacts. What I did was let HTC Sync synchronise with Outlook (I created a new PST file for this, then specified it in HTC Sync), then used GO Contact Sync Mod (sorry I can't post links yet) to sync it with my gmail account.
If you really wanted to leave as phone contacts, you could try Titanium Backup - but since your phone contacts are saved as system data it's a bad idea - so I'd recommend against it. If you're backing up your nandroid for ARHD, you could always try TiBu and let us know how it went - I think it was labeled Dialer Storage - filter to system data and just look through all the green-colored items for something that says "CONTACTS" or "PEOPLE".
However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
+1 to what if4!ct0r said regarding wiping before flashing.
There will always be some system settings that you will have to re-enter manually if you customize them a lot even when updating builds of the same ROM (probably because these are the system items that you shouldn't be restoring). These will depend on the ROM, but for me and JellyTime, the ones I had to redo were developer, lock screen, system/status bar, sound, display, language, as well as ringtone/sound notifications for alarms, messaging and calendar. Also you'll have to manually set up your widgets again - typically ones that require you to configure it as you place it.
As for TiBu not being recommended - personally I didn't have a problem with it when moving over to JellyTime. I actually purchased the Pro version just for this and for flashing new JellyTime builds. There are two things to consider when restoring via TiBu: 1) system data; and 2) app and app data.
System data: The main concern here is, when changing to a completely different ROM, do NOT restore any system data (unless you're aware whether it was updated in the new build or just experimenting). Even when you're updating to a new build of the same ROM, you should at least avoid restoring the red-coloured items and just stick to green and yellow items that may contain useful data such as contacts, sms, call logs, saved wifi access points, bookmarks, etc.
App and app data: I personally think it's ok to restore your apps themselves, but you could always record a list of what you had and download them manually again just to be safe - not a big deal unless you have over a hundred apps. When switching ROMs, try to avoid restoring the app's data unless you really wanted/needed it for certain apps - in that case, be conservative with what you choose. I'm not a programmer or developer, so I don't know how this would affect your system/app if switching to a ROM with a different Android version. Restoring app data between builds of the same ROM should be fine, as I've done it between all my JellyTime flashes with no issue even when it updated to Android 4.1.2.
Tip: after flashing the ROM, and doing your typical post-ROM-flash stuff (like fixing permissions, rebooting, wiping cache+dalvik, flashing Gapps, etc), and you've tested it and are happy with its stability, download TiBu again (or if you had the apk stored somewhere after you purchased it, just install it manually), boot to recovery and make a nandroid of the new ROM as it stands: nice and clean before any apps are installed. This way you've got a recovery option without having to go through the hassle of re-flashing the ROM build again, setting it up, etc if all you did was stuff up while experimenting with restoring data on TiBu.
As always, make a nandroid backup before flashing. As I mentioned, if you're initially happy with the ROM, I recommended also doing one after you flash while the system is fresh and clean. Sorry if this post is a bit wordy, but I thought more info would help, as it helped me in the past.
Skunkworx said:
So I am looking for a soloution ... to move my sms messages over.
Click to expand...
Click to collapse
if4ct0r said:
For moving SMS, I'd suggest this app...
Click to expand...
Click to collapse
+1 for SMS Backup & Restore; I also used it, but keep in mind AFAIK it doesn't save MMS. I also used Call Logs Backup & Restore, in case you're interested in backing this up too. But since I started using TiBu, I don't need either of these apps any more.
Maybe changing the digitizer could help asd
Sent from my Galaxy Nexus using xda app-developers app

[RE-FLEXxx] Q&A Thread

In this thread you can post your experience, questions, and all other stuff that is not directly related to the RE-FLEXxx rom.
I do this to keep the dev thread clean.
Thank you for your understanding.
I will take a look into this thread from time to time but the main goal is so that users of the RE-FLEXxx rom can help out each other and that they can find help from each other in one place.
Regards, civ.
I installed 2.0 on my N5110 (coming from 1.9) and it is working well but the top of my tablet is non-responsive to touch. Happened on other releases but a reboot always fixed it. This time the problem remained, so I tried wiping cache, dalvik, fixing permissions, reboots, and all sorts of combinations. I did finally manage to fix the issue yesterday after one of those reboots but now the problem just reappeared and won't go away. Any suggestions?
Edit: Finally got it resolved with a full wipe of data, cache, and dalvik through cwm recovery. Then I flashed Civz reflexx Rom 2.1 and rebooted. The top of the screen still did not respond to touch, so I rebooted and now everything works perfectly. :thumbup:
anybody else still having SNote FC on them in 2.0? also the extended menu items will not work for me...setting fc
dpaik said:
anybody else still having SNote FC on them in 2.0? also the extended menu items will not work for me...setting fc
Click to expand...
Click to collapse
no snote and extended menu all working for me. Maybe you had a bad download? Otherwise try wiping and installing fresh.
dpaik said:
anybody else still having SNote FC on them in 2.0? also the extended menu items will not work for me...setting fc
Click to expand...
Click to collapse
yes, hd happened to me, I re downloaded and reflashed it again and is OK now..
well, I finally installed twrp, and backed up my stock rom, so I am getting ready to flash the first custom rom on any tablet I have had!
one quick question; I am a very experienced rom flasher; I see in TWRP, there are several options under the wipe menu, and, I know to check the first 4 options before flashing this rom; then, there are 2 more options, wipe internal card, and wipe external card.
I know not to wipe my external card, since all my "stuff" is there...should I wipe the internal card before flashing, or is that not necessary when flashing this rom from a stock rom?
I apoligize if this belongs in the the TWRP thread, but I thought since others have probably gone through this, I wanted to post the question here as well. I guess I should post it in the TWRP thread as well...
thank you!
wase4711 said:
well, I finally installed twrp, and backed up my stock rom, so I am getting ready to flash the first custom rom on any tablet I have had!
one quick question; I am a very experienced rom flasher; I see in TWRP, there are several options under the wipe menu, and, I know to check the first 4 options before flashing this rom; then, there are 2 more options, wipe internal card, and wipe external card.
I know not to wipe my external card, since all my "stuff" is there...should I wipe the internal card before flashing, or is that not necessary when flashing this rom from a stock rom?
I apoligize if this belongs in the the TWRP thread, but I thought since others have probably gone through this, I wanted to post the question here as well. I guess I should post it in the TWRP thread as well...
thank you!
Click to expand...
Click to collapse
This is my opinion on it.....I usually only wipe the internal card if I am starting completely over with flashing a device. Wiping data/cache is usually all that is needed but if there are a lot of apps that get installed over time their folders get left and every so often I like to wipe it to get rid of all the "orphaned" folders. If you are going to just restore all those apps anyways then it won't make a difference either way. If you are going from the stock rom to a TW custom based on the stock it shouldn't be necessary to flash internal.
thanks man, that is what I thought, but, since I have never flashed a custom rom on to any tablet I have owned, I wasnt sure if there was other "stuff" on the internal card that might be needed no matter what; and, yes, since I will just be restoring all of my apps pretty much once I flash this custom rom, I might as well just leave the internal card alone...
I appriciate your fast reply!
wase4711 said:
thanks man, that is what I thought, but, since I have never flashed a custom rom on to any tablet I have owned, I wasnt sure if there was other "stuff" on the internal card that might be needed no matter what; and, yes, since I will just be restoring all of my apps pretty much once I flash this custom rom, I might as well just leave the internal card alone...
I appriciate your fast reply!
Click to expand...
Click to collapse
Please take my advice with caution...I did not take your point into consideration because I have yet to do it on this particular tablet (only had the Note for 1 day). Never had a problem on any other tablets/devices but who knows. I wouldn't think there would be an issue. However, like you say probably no reason to wipe internal if you will just be restoring them back anyways.
CCallahan said:
Please take my advice with caution...I did not take your point into consideration because I have yet to do it on this particular tablet (only had the Note for 1 day). Never had a problem on any other tablets/devices but who knows. I wouldn't think there would be an issue. However, like you say probably no reason to wipe internal if you will just be restoring them back anyways.
Click to expand...
Click to collapse
no probs, it worked like a charm!!
just trying to figure out the easiest way to get a nav bar to show up, without having to lower the screen dpi, or to maually edit the buildprop..
thanks!
wase4711 said:
no probs, it worked like a charm!!
just trying to figure out the easiest way to get a nav bar to show up, without having to lower the screen dpi, or to maually edit the buildprop..
thanks!
Click to expand...
Click to collapse
Use the terminal command on my rom
su
softkey_on
all info is in rom thread OP.
thanks, I thought I had read every terminal command in the thread, but I guess I didnt!
tun.ko or tap.ko?
I'm trying to get openvpn to work on REFLEX2.0 in tap mode. Looks like I need a tap.ko kernel module for either the stock kernel or the CivZ-StormBorn_Rev2.0-OC kernel. Anyone know where I might find such a thing?
---------- Post added at 03:59 PM ---------- Previous post was at 03:54 PM ----------
I notice the CivZ-StormBorn_Rev2.0-OC kernel has no /proc/config.gz file. That means the kernel was not compiled with the CONFIG_IKCONFIG option. Is there a way to see what options are baked in to the kernel?
Problem with softtouch Key "back"
hi everyone. I enebled softtouch Keys, but softtouch Key "back" doesn't work correctly. sometimes, it doesn't work, and i must tap it a lot of times.
Why i have with problem?
thanks in advance.
USB Mass Storage Unexpectedly Removed Loop
Hi,
Not sure if I am posting this in the right spot but I am getting a mass storage device unexpectedly removed loop message whenever I attached my USB flash drive? I am using the V2.1 ROM and kernel so wondering if anyone else is facing this same issue? Thanks!
MrAlexey said:
hi everyone. I enebled softtouch Keys, but softtouch Key "back" doesn't work correctly. sometimes, it doesn't work, and i must tap it a lot of times.
Why i have with problem?
thanks in advance.
Click to expand...
Click to collapse
i have better luck if i tap at the bottom of the softkey. it's almost as if the icon is bigger than the actual location that the press registers.
Chrome screen bug solution
Basically the problem is the notification bar, combined with the lack of on-screen softkeys. In order to fix it, you need the following:
Xposed Framework:
http://mohammadag.xceleo.org/public/Android/XposedInstallerDownloadUnsigned.apk
How it works:
http://forum.xda-developers.com/showthread.php?t=1574401
App Settings manager:
http://mohammadag.xceleo.org/public/Android/Xposed/AppSettings_0.4.apk
I've been using this combination on my tablet for a while now. It lets me change the resolution for individual apps. For instance, I want the tablet mode of Gmail, but I want my tablet to run in phablet mode so that I get the top notification bar and no softkeys.
The Chrome fix is simple. The app settings for the Chrome executable should have the fullscreen option toggled, the DPI set to 160, and the screen resolution set to 800x1200. It then hides the notification bar on top while you're in the browser, and shifts the screen that quarter of an inch where it is offset due to the Chrome bug on tablets without softkeys. If you need to access the notification bar, simply swipe down on the screen from the top edge and it will pop up.
If the print size is too small, you can use the accessibility settings in Chrome to scale up the font size.
acfc81 said:
Hi,
Not sure if I am posting this in the right spot but I am getting a mass storage device unexpectedly removed loop message whenever I attached my USB flash drive? I am using the V2.1 ROM and kernel so wondering if anyone else is facing this same issue? Thanks!
Click to expand...
Click to collapse
Hi,
Please ignore my last message as the issue was using the wrong kernel on my part. Thanks!
Question
I'm thinking of flashing a new ROM having used stock for month or so now. My concern is regarding the apps I have installed and am currently using, specifically FolderMount.
If I flash a new ROM (either civs older 4.1 build or his newer 4.2 one depending on how he is progressing), will I lose the links?
I have about 25GB worth of game obb and data transferred over from my internal memory to my micro SD. I dont fancy using up all my download allowance having to re- download and install all of those (plus the time it takes to transfer them all over). I dont mind losing the layout of my homescreens as I'm thinking of shaking that up anyway.
I've only one past experience of flashing a Rom and that ended up with me having to reinstall and set up all my apps (jump from ICS to JB on my Asus TF101)
flex beam 4.2.2 download unsuccessful
flex beam 4.2.2 download unsuccessful
Please upload

desktop App Icons locked

My app icons worked fine last week as far as dragging/deleting from desktop but now if I long press on desktop, the only thing that happens is the app launches... I cannot bring up widget/wallpaper menu either by long pressing screen.
I don't believe there is any lock/unlock feature that would be causing such a problem though...using rooted stock ROM, I have flashed some other ROMS to see if this was just an issue with the stock ROM but still didn't work... malfunction maybe?
I wonder if it is dead spots on the screen. To be sure I would Odin back to stock, that's always a first step to verify it's hardware or software, but it sounds hardware related.
metalfan78 said:
I wonder if it is dead spots on the screen. To be sure I would Odin back to stock, that's always a first step to verify it's hardware or software, but it sounds hardware related.
Click to expand...
Click to collapse
Would I lose my Boost Flash if I did Odin or is there any way around it? ... other than re-flashing
Odin will put everything back to stock. Maybe it's an app behaving badly. If you don't want to reset everything, back up your apps and uninstall them all and wipe dalvik, and cache and reboot and see if the problem is there, then install apps one at a time. What have you downloaded recently?
metalfan78 said:
Odin will put everything back to stock. Maybe it's an app behaving badly. If you don't want to reset everything, back up your apps and uninstall them all and wipe dalvik, and cache and reboot and see if the problem is there, then install apps one at a time. What have you downloaded recently?
Click to expand...
Click to collapse
It was working fine... then I downloaded ESPN SportCenter app.. went to move it to a side screen.. which it did but right then after it moved is when the problem occurred.. because I tried to move another app icon and nothing worked

phone freezes and stuters

My phone is freezing and stutering all the time, it's most noticeable when i press the apps key (third on the right). I've tried several different ROMs (always wipping data,cache system) as it appeared to be a software problem but it starts right off as i'm at the initial configuration, keys are not even responding properly, when i press a key it takes about 3 to 4 seconds to respond
I'm also under the impression the phone is overheating, it's getting really hot on top back near the camera. Any suggestions of what i might try?
brunobliss said:
My phone is freezing and stutering all the time, it's most noticeable when i press the apps key (third on the right). I've tried several different ROMs (always wipping data,cache system) as it appeared to be a software problem but it starts right off as i'm at the initial configuration, keys are not even responding properly, when i press a key it takes about 3 to 4 seconds to respond
I'm also under the impression the phone is overheating, it's getting really hot on top back near the camera. Any suggestions of what i might try?
Click to expand...
Click to collapse
Are you using cyanogenmod or CM-based ROM by a chance? I've had horrible lags on it, especially on the latest nightlies. If that's the case, try something light and AOSP-based like slimkat.
I have tried slimkat, aokp, cm11 and they all seem to be getting slower everytime i flash a new rom I think this started to happen when i first attempted to do a full backup, the phone froze during the process because it was running out of memory. It was a pain to get it working again because it was sooooooooooooooo slowwwwwwwww.
Then i just booted to cwm did a full system, data, cache wipe and installed a new ROM, during the initial steps phone starts stutering, no matter what rom it is.
My guess is that there are still some files somewhere causing the problem.
First thing, Always keep >4Gb of free space.
Install/run Lagfix app.
Backup all important/personal files to PC, delete all files/folder on GN, copy over only ROM/gapps zips and flash a clean install(wipe data 3 times in row) and after ROM boot up copy back your files.
Oh, in that case it is most likely a free space issue as isajoo pointed out. I suggest using clean master to free up some space and get rid of some big files you don't need.

Categories

Resources