Related
Posting here since I cannot yet post to the actual ROM forum.
I'm running the Synergy ROM, RC1 and have a couple of issues. First though, thanks to the DEVs for all of their time and efforts, this looks to be a very good ROM!
I've been through most of the 200+ pages on the ROM's thread and did not see any information that may help (except turning off auto rotate of the home screen), but it's possible I missed.
The main issues I have are slow response issues. They are:
Slow response when I pull down the navigation bar.
Slow response when hitting one of the soft buttons (i.e., the + button to launch the app specified by the settings in Rosie).
Very slow response when I come out of a game that was in landscape mode. It takes a couple of seconds for the screen to switch from landscape back to portrait (after flipping the phone to portrait) and then another few seconds for it to put all the icons back on the home screen (home screen is blank when I come out of the game). I did turn auto rotate off and that has helped, but was wondering why there was such slow response without it.
Google apps such as Maps and Calendar that are started by another application, but do not shut down the starting app exists. This, of course, drains the battery and was not an issue on the stock rom.
When I flashed the rom, I did do a factory reset and erased all other caches. My apps and app data (not system data) were restored via TB.
I have also frozen the following apps via TB:
Flash
All live wall paper apps
Stocks
Flickr
FM Radio
News
Stocks
Smoke & Visualization Wallpapers
Voice Dialer
Voice Search
Thanks!
Mike
When you flash a new rom, only restore Apps using titanium backup, restoring data too will cause problems.
Sent from my ADR6300 using XDA App
ithrewitontheground said:
When you flash a new rom, only restore Apps using titanium backup, restoring data too will cause problems.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Absolutely correct. On top of this, the other reason you may be seeing slow response would be the fact that this is a very large rom, and takes up more space in your usable memory than most roms. What I have done to *somewhat* alleviate this issue when I'm running the synergy rom is to move all of the apps that I can (except for those that I use widgets from) to the SD card.
Just my recommendation
ithrewitontheground said:
When you flash a new rom, only restore Apps using titanium backup, restoring data too will cause problems.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
My thought was that when restoring an app, such as WSOP Texas Hold'em, I also wanted to restore the data so it restored games won, amount of money, etc.
Is that data what you are saying I should lose when flashing new roms?
Thanks,
Mike
0soPolar said:
Absolutely correct. On top of this, the other reason you may be seeing slow response would be the fact that this is a very large rom, and takes up more space in your usable memory than most roms. What I have done to *somewhat* alleviate this issue when I'm running the synergy rom is to move all of the apps that I can (except for those that I use widgets from) to the SD card.
Just my recommendation
Click to expand...
Click to collapse
Quite a few of my apps are on the SD card. I have 313MB free on the internal storage. Should that be enough to reduce some of the lag.
Thanks!
HELP!!! I flashed synergy rom last night and today, it goes to the boot animation screen and freezes. It just shows the synergy rom bouncing around and wont go anywhere from there. I tried doing a recovery through bootloader, but it wont let me move down from fastboot. Did I just brick my phone or is there any other way to get past this screen? can i plug my sdcard into the computer and delete this boot animation and if so, where would I find it? Please help, it would be GREATLY appreciated!!!
Give the phone a minute. It will let you move it. I just keep hitting volume down. It will work.
Sent from my ADR6300 using XDA App
dysfunkshun said:
HELP!!! I flashed synergy rom last night and today, it goes to the boot animation screen and freezes. It just shows the synergy rom bouncing around and wont go anywhere from there. I tried doing a recovery through bootloader, but it wont let me move down from fastboot. Did I just brick my phone or is there any other way to get past this screen? can i plug my sdcard into the computer and delete this boot animation and if so, where would I find it? Please help, it would be GREATLY appreciated!!!
Click to expand...
Click to collapse
If you can boot into recovery, you did not brick your phone.
I've had this problem before and I don't even use Titanium. I also had plenty of free space on internal. Ram never seems to free up though. It's the strangest thing.
Sent from my ADR6300 using XDA App
Does anyone else have issues with anything that requires data syncing (Facebook, Twitter, SMS, etc) stopping unexpectedly? It seems to happen at around 30% battery and the only way I've consistantly stopped the problem is to wipe and reflash Synergy Rom.
Any ideas?
Yea Idk what's going on with it after about an hour I would get android.process has stopped and needs to force close. I can't even use any app as that constantly pops up. Great ROM but unusable at this point.
Did you do a complete wipe before you installed it. Most of the issues I have seen arise because a complete wipe has not been performed. If you like the rom, do a complete wipe (factory, partition and dalvik) and reflash it.
jlokos said:
Did you do a complete wipe before you installed it. Most of the issues I have seen arise because a complete wipe has not been performed. If you like the rom, do a complete wipe (factory, partition and dalvik) and reflash it.
Click to expand...
Click to collapse
This is after a full wipe, twice. Once the battery gets to a certain point, everything starts crashing and never recovers no matter what I do. Battery pull, full charge, cold restart. Nothing works.
Edit: I've also noticed that the GPS is locked on and I cannot shut it off.
Chindogg said:
This is after a full wipe, twice. Once the battery gets to a certain point, everything starts crashing and never recovers no matter what I do. Battery pull, full charge, cold restart. Nothing works.
Click to expand...
Click to collapse
Yea I also did a full wipe two different times. I didn't notice it happening once the battery gets to a point I just know that after an hour or so of use it was unusable.
1. If you use DualRomX2 would that possibly speed it up? Because doesnt it install Roms on EMMC?
2. Im also really frustrated by the slow response on alot of things like right rosie button and notification pulldown.
3. Video recording for me is just awful. Im not sure about actual quality but the framerate for sure is horrible. I compared a video i shot on stock and with Synergy and there is a HUGE difference. Synergy video being much worse.
Great Rom just plenty of little annoyances.
Synergy ROM loading issue
Flashed Synergy ROM last week and was very impressed. However, saw where 3.0 Sense items were missing and realized after reading several other posts that the carousel +widgets.zip should have been loaded with the ROM. So I reloaded the ROM and widgets through AMON-RA Recovery (Followed all of the original instructions I had followed the first time I loaded the ROM). Everything looked fine until I rebooted the system. Now Synergy ROM start-up screen loops over and over. At this rate the fill battery I started with will run out, and I'm not sure what will happen at that point.
Anyone have any suggestions for this issue? Any help would be appreciated. Thanks.
Options:
a) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, & flash a different rom.
b) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, flash Synergy again, reboot.
c) Pull your battery then turn on your phone like normal.
d) Pull your battery then boot into recovery, wipe cache/wipe dalvik cache, then boot into rom.
Edit: I don't use Amon_Ra, when I refer to "recovery" I was referring to CWM. Hopefully someone with experience comments in regards to Amon_Ra recovery.
Yeah I don't have too many issues with it... last night it got kinda squirrely so I fixed permissions in recovery and re-flashed the Warm Theme without wiping any data, it's been all good ever since.
The ROM is my daily driver... I really do think that these issues are app-related. There is something that certain apps do that this ROM is not built for, I'm just not sure what it is. It's been real good to me overall though, battery life and all.
SlimSnoopOS said:
Options:
a) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, & flash a different rom.
b) Pull your battery, boot into recovery, format data/wipe cache/dalvik cache/format boot/format system, flash Synergy again, reboot.
c) Pull your battery then turn on your phone like normal.
d) Pull your battery then boot into recovery, wipe cache/wipe dalvik cache, then boot into rom.
Edit: I don't use Amon_Ra, when I refer to "recovery" I was referring to CWM. Hopefully someone with experience comments in regards to Amon_Ra recovery.
Click to expand...
Click to collapse
SlimSnoopOS, as it turned out I pulled the battery and rebooted into Recovery after a few hours, but thanks for the direction. These were the exact things I did. The reason I used AMON-RA instead of CWM is that Synergy says in a number of places that it only loads with AMON-Ra (and I'm a coward!),
Awesome, glad everything is functional again!
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
My browser constantly crashes and I can't for the life of me figure out why, so I am turning to you guys for help with my first post. Here's what's up:
Within one minute of opening my browser, but often within a few seconds of browsing, the browser will crash. No dialog or anything, it just suddenly closes. Sometimes it will restore itself when I reopen it, sometimes not.
This has happened across multiple roms, including cm10(which I am on now) AOKP, Frostyjb etc. I've used all the wiping options in CWR including formating /sdcard but nothing has helped. I can't find anybody with a similar problem. Any ideas?
You didn't tell us which browser. Use a different one.
kaixo24 said:
My browser constantly crashes and I can't for the life of me figure out why, so I am turning to you guys for help with my first post. Here's what's up:
Within one minute of opening my browser, but often within a few seconds of browsing, the browser will crash. No dialog or anything, it just suddenly closes. Sometimes it will restore itself when I reopen it, sometimes not.
This has happened across multiple roms, including cm10(which I am on now) AOKP, Frostyjb etc. I've used all the wiping options in CWR including formating /sdcard but nothing has helped. I can't find anybody with a similar problem. Any ideas?
Click to expand...
Click to collapse
Goto: settings / apps / browser /
Clear the cache and data and if it says: un-install update try that too
boot in to recovery and wipe davik and cache and fix permissions
Worth a shot :/
WarlockW said:
Goto: settings / apps / browser /
Clear the cache and data and if it says: un-install update try that too
boot in to recovery and wipe davik and cache and fix permissions
Worth a shot :/
Click to expand...
Click to collapse
Tried all that before and tried it again just now. Seems to be a bit better for a minutes (no crashes) but within 5 minutes it starts crashing upon loading my homepage etc. It's strange because crashes of this nature never happened to me even when running highly experimental ROMs on my old Atrix 4g. Is it possible that there are some configuration files (say host files or something) that are not wiped by the factory reset in CWM and are tripping things up? I think I will try flashing a stock image using Odin (which should wipe everything on the phone, correct?) and see if that fixes things.
And I am talking about the stock browser. It's the best (usually) for me and I'm sure it shouldn't be acting like this. Chrome and firefox crash even on stable stock builds so I can't really tell from them, lol.
Flashing stock with odin would be my next suggestion.
But also, after your next flash, don't install anything. Go straight to the browser after boot and see how it acts.
Can you verify it happens on any network? 3G/4G or any wifi?
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Flashing stock with odin would be my next suggestion.
But also, after your next flash, don't install anything. Go straight to the browser after boot and see how it acts.
Can you verify it happens on any network? 3G/4G or any wifi?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your help and sorry to bring this topic back up, but my phone is really driving me crazy. For the past week I have experimented with Odin flashing the stock firmware on to my phone (both ICS and the recent JB) as well as constant factory resetting, but nothing changes the behavior. Using an alternative browser like Firefox (it sure has improved) results in a more stable experience, but things that use the default browser like gmail and (I think) Facebook still crash all the time. Also, the unlock screen often is unresponsive upon waking the phone, which is shortly followed by a reboot.
This behavior happens even if I do a factory reset, flash the stock firmware and boot up straight to the browser without signing in to my Google account or doing anything else. It happens irrespective of the network I am using.
I know we aren't supposed to use the repartition feature in Odin, but is there a safe way to do it or otherwise wipe everything off the internal memory leaving only the download mode so I can really start from a clean slate? I really want to rule out any software problem. The thing is, I'm getting a Nexus 4 and want to sell my sIII (it's still in mint condition) but I can't ethically do it knowing that my phone is somewhat borked. please help!!
I bought my phone new in box off of Ebay because I wanted the blue color. What a mistake. Samsung and T-Mobile are rebuffing any warranty requests I make (I didn't trip the flash counter) because I don't have a receipt. It would seem strange that this is a hardware problem as everything else works fine, but could I be wrong?. Only the default browser and apps that use it exhibit this behavior. Anybody have any ideas on what is going on??
kaixo24 said:
Thanks for your help and sorry to bring this topic back up, but my phone is really driving me crazy. For the past week I have experimented with Odin flashing the stock firmware on to my phone (both ICS and the recent JB) as well as constant factory resetting, but nothing changes the behavior. Using an alternative browser like Firefox (it sure has improved) results in a more stable experience, but things that use the default browser like gmail and (I think) Facebook still crash all the time. Also, the unlock screen often is unresponsive upon waking the phone, which is shortly followed by a reboot.
This behavior happens even if I do a factory reset, flash the stock firmware and boot up straight to the browser without signing in to my Google account or doing anything else. It happens irrespective of the network I am using.
I know we aren't supposed to use the repartition feature in Odin, but is there a safe way to do it or otherwise wipe everything off the internal memory leaving only the download mode so I can really start from a clean slate? I really want to rule out any software problem. The thing is, I'm getting a Nexus 4 and want to sell my sIII (it's still in mint condition) but I can't ethically do it knowing that my phone is somewhat borked. please help!!
Click to expand...
Click to collapse
This is a very sad story about my NoteII going bad.
I would describe myself as computer savvy and moderately experienced with Android. I equipped half of the family with various ROM-customized Android phones and am an enthusiastic Note user since it came out in 2011. Until now, I never had to ask a question in the forum.
Let me start in December 2012 when my NoteII arrived. I updated it, then came cwm and the monxdified ROM. For about a month I was a very, very pleased NoteII user.
Then, one day in Mid-January, I installed an app called "(root) Uninstaller pro", which began to auto-backup up all my apps to internal SD in a background process while I didnt notice. I only realized something had gone wrong when apps began to FC because no space was left on sdcard0. I removed the app and all the backups.
From the day after that , Play Store began to "randomly" refuse to update or install apps, because of "Not enough storage space available". Which was bull****. I literally had Gigabytes of free space on internal and external storage. For example, Play Store would refuse to update my tiny TB Pro key apk for "Not enough space" reasons but then happily install Asphalt7 and update Titanium Backup and Dolphin for me. Moreover, every affected app also does not install "manually" from apk. When removed, it can not be reinstalled, except via update.zip from the recovery.
Of course, I googled the error. I found no root cause explanation, just a bunch of hints. I deleted all app data from play store and various store-related apps. I deleted and re-setup my Play Store account. The usual suspects, cache and dalvik, got their wipe. Nothing helped. I downloaded the latest monx ROM and updated it from TWRP. Problem still there. Then my job required my full attention so I left the thing running with only partial updates for several weeks. After all, it still worked petty well.
Then, lately, I decided to tackle the issue again. I went to Settings and did a full factory reset WITH internal SD reformat. In TWRP, I did another factory reset and full wipe, then I flashed the latest (DMB2) monx ROM and restored from my TB backup.... "Not enough storage space available".
A friend suggested I should try "Fix permissions". Boy, what a bad Idea. From that moment, LBE Security guard caused a Hot Reboot every time I tried to use Active Protection. Many resets and wipes later, it still does today. I can only install it via update.zip, though, not properly reinstall it: "Not enough storage space available".
But all this still is only the beginning. I decided it was time to clean up the mess and factory resetted again (no SD wipe this time, after all it didnt help last time), took good old ODIN and completely reflashed with Stock XXDMB2. Result: Boot Loop. TWRP told me "cannout mount /data" and claimed internal and external SD to be empty (which was not the case). So I reverted to cwm6 and did a fullwipe/reset. Only after that, the newly flashed Stock DMB2 suddenly booted. I went on and reinstalled monxdified DMB2 (the very same zip that had worked before!). But regardless of what I tried, all I got was another boot loop.
Back to Odin, Stock again. This time (and every time after) it booted right away without needing help from cwm, BUT on the very first GUI ("choose country") it told me that UIDs were wrong and suggested to reformat /data. Wait, wasnt that what Odin just did? Instantly after this error, com.google.gapps did an FC. CWM to the rescue. This time, "fix permissions" seemed to actually fix them.
To make this long story a bit shorter, I reiterated though quite a number of futile attempts to install a booting custom ROM until 2am, and failed. Now I am on Stock DMB2 with a non-working LBE and only a handful of the most important apps restored. The "Not enough storage space available" problem is still here.
I wonder how the "Not enough storage" problem was able to survive so many flashes and resets. I am utterly helpless about how a Stock ROM, flashed from Odin can expose UID problems and FCs on first boot. Could this be a sign of a malfunction on the internal flash storage? If so, how would I be able to find out? Or could it be that this "uninstaller" did something nasty to the secure storage system of JB (which I dont have any idea of how it works and what it needs at all), at a point that all my wipes and flashes did not actually reach?
What else could I do to really, really reset every possible bit on this otherwise wonderful piece of hardware and possibly get rid of all those pesky problems (and back into a Custom ROM)?
Please help me to make this baby shine again!
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Ive read your story and i feel really bad for you. Good luck m8, if I had some knowledge id help you for sure but im new to android ) goodluck! Dont give up x
Sent from my GT-N7100 using xda premium
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Sent from my GT-N7100
Re: MegaWipe
UtkarshGupta said:
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Click to expand...
Click to collapse
Ok. So I found MegaWipe and put it on my SD-Card. I started it and the aroma Installer presented to me the Mega Wipe Option which I chose. A text screen appeared which said, that several partitions had been wiped but it happened in less than a second which I foudn to be suspicious. Then, when tapping "Next" again in the MegaWipe Aroma Tool, I found out Aroma was frozen and the recovery system did not react to any key press or tap anymore. I had to press the Power button for a while to get back into recovery where I flashed a ROM, then rebooted.
Guess what: all my apps were still present, the SMS history and Launcher fully intact. Dalvik had been wiped apparently (all apps re-optimized), though, and my Wifi AP settings were gone. Of course, the "not enough memory" problem is still here, too!
It appears like whatever problem I have, it also prevents me from using MegaWipe properly. Any more ideas?
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Try again.
Sent from my GT-N7100
Re: MegaWipe
UtkarshGupta said:
Try again.
Click to expand...
Click to collapse
Tried again. Twice. Internal SD contents were gone. Froze again after "Installation complete". Maybe that "Mega Wipe" took two seconds instead of one this time. The second time I tried flashing Omega after the wipe just for the kicks and that (full wipe Option in Aroma) apparently took my user data away, finally.
To my not-so-big surprise it greeted me with "Inconsistend System UIDs" right after startup, completely with the gapps FC I had already seen with stock so many times, now. This does not feel like real progress.
I have read around a bit. Maybe I should try to flash a multipart ROM in Odin with repartition? Appears to be pretty dangerous, though, and I dont know where to find one that matches my "DBT" CSC properly...
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Flash latest stock rom for your country.
Sent from my GT-N7100
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
u use CWM? i had a problem with cwm if i use aroma it always freeze use a other recovery and do the megawipes?? iam not very good at this but i wish you all the luck ..
Sent from my GT-N7100 using xda app-developers app
Re: MegaWipe
UtkarshGupta said:
Flash latest stock rom for your country.
Click to expand...
Click to collapse
XXDMB2 *is* the latest Stock ROM for my country. In my first post I described how I flashed it and it did not work out very well.
nameejokerx said:
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Click to expand...
Click to collapse
Yes, and which one would be such a ROM? I was not very adventurous with ROMS until now and did never flash multipart ROMs. I am afraid bad things could happen if I flash something with wrong CSC. Where exactly should I look for such a ROM and what do I have to take care of? Of course HOWTO pointers are welcome, too.
Sorry if this sounds too clueless but I really dont want to make things even worse.
Maybe SDS
Hi all,
after some more wiping and flashing, fiddling and tiddling and basically reinstalling everything from scratch, mostly without help from Titanium, I got my NoteII back to work. I only restored my most important app data, all apks reloaded from play store instead from backup, made several backups with twrp during this process. Two times, the "no space" problem came back and both times I basically reverted back to the last working backup from twrp. This way, I managed to turn it back into a usable system.
Not for long though, because two hours ago, in the midde of buying an ebook in kindle, my NoteII screen went black and now the whole thing is completely dead. I took out the battery for 10 minutes, but it won't come back on again; not even a download screen or battery loading animation.
So my problems might just have been the harbingers of its future death. I just read that "SDS" also affects some Note2 models and it has something to do with the internal storage which would be sort of a match for the symptoms I experienced. Looks like I'll have to send it in. Because of all the flashing and restoring I had not yet encrypted my internal storage and will have to change all passwords. Duh
I really should have stayed with my trusty old Note1 which never failed on me...
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.