Related
If you've poked a bit with the Play and you've done a hard-reset (wiped the /data and /cache partition in CWM) later on, you'll find that you have a different wallpaper and that the Home button dies. This makes custom ROMs impossible to keep in the long run, since every hard reset would kill said button, and of course, when you make custom ROMs you wipe your phone quite frequently.
Has anyone investigated which can be the cause of this behavior? My guess is that there's something in the /data partition which should be left untouched, in order to preserve the Home button. What's your take?
I doubt it, on more than one occation i have fastboot erased /system /boot /data. And have never lost home button functionality. Maybe its something CWM is doing wrong?
Sent from my R800i using Tapatalk
I have reproduced the issue using the standard (aka, the GUI-activated) hard reset method as well. Home button dies.
Ive read flashing Gapps after the wipe repairs the home button?
That can work in CM7... but what if you're using a stock rom as a base? (which was the GP2Xperia case)
When you wipe, of course you're going to have a different wallpaper. Home button keeps working just fine, no matter how many times you wipe. I suspect you're using a CM7 ROM, which for a time had the home button not working.
Flash to stock and it will be fine.
Perhaps it'd be good to link the GP2Xperia thread: I'm noticing I wasn't alone in those issues.
http://forum.xda-developers.com/showthread.php?t=1145729
Lol, after re-reading it, the last post is actually the same as the OP here
Logseman said:
Perhaps it'd be good to link the GP2Xperia thread: I'm noticing I wasn't alone in those issues.
http://forum.xda-developers.com/showthread.php?t=1145729
Click to expand...
Click to collapse
So maybe it's something you added or took away from your rom thats causing the issue?
Sent from my R800i using Tapatalk
And that gets me back to the Start square: considering that I've added nothing, and I've only substracted things, whose wiping is killing the Home button?
I believe it's something stored on data not system that causes the issue
Sent from my HTC Sensation Z710e using XDA App
My home button wasn't working on CM7 until I re-installed g-apps.
'Setup Wizard' is required to "activate" home button
How's the APK called? I can't find it with Titanium Backup.
/system/app/SEMCSetupWizard.apk - "Setup Guide 1.0"
Logseman said:
How's the APK called? I can't find it with Titanium Backup.
Click to expand...
Click to collapse
zerojay said:
/system/app/SEMCSetupWizard.apk - "Setup Guide 1.0"
Click to expand...
Click to collapse
so did it work?
It does work. The Setup thing itself looks funny as I've chopped half of the things, but the Home button works as intended. So, if you want to do a custom Rom, make sure that SEMCSetupWizard.apk is in the System folder!
.Just broke my home button deleting apks on stock rom. Re added as posted works fine again
Hey,
How can i do a Full Reinstall of the OS clean install,
Thank You
- Sonny Dickson
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
This happens about once every two nights. I hit the power button and the lock screen comes up fine, i unlock it with the slider and then home screen starts flickering slowly and is completely unusable. Is this the dreaded redraw issue I've heard mentioned? A forum search doesn't bring up any solutions for this. Any idea what to look for in logcat?
This is on 28i running ICS 2.29, rooted/deodexed+ "bloatware removal script" from deodex forum. Phone works great throughout the entire day.
twent4 said:
This happens about once every two nights. I hit the power button and the lock screen comes up fine, i unlock it with the slider and then home screen starts flickering slowly and is completely unusable. Is this the dreaded redraw issue I've heard mentioned? A forum search doesn't bring up any solutions for this. Any idea what to look for in logcat?
This is on 28i running ICS 2.29, rooted/deodexed+ "bloatware removal script" from deodex forum. Phone works great throughout the entire day.
Click to expand...
Click to collapse
I've never heard of this dreaded redraw issue, nor have I had it happen to me. Maybe doing a fresh fw flash, and add customizations one by one, making a CWM back up as you add each mod. Then see where and why the issue starts. Here is my process:
1. Flash Firmware > Root > CWM
2. Make a CWM backup called something like: 29fw_clean_base--
3. install busybox and deodex
4. Make a CWM backup called: 29fw_clean_BB_DO--
5. Install init.d
6. Make a CWM backup
7. Then start adding my mods one by one maing backups as I go called 29fw_running"1,2,3, etc."--
8. Then I can go back and delete or archive CWM backups as to what I need. Always keeping the "clean_base" ready for use if need be.
jeriku said:
I've never heard of this dreaded redraw issue, nor have I had it happen to me. Maybe doing a fresh fw flash, and add customizations one by one, making a CWM back up as you add each mod. Then see where and why the issue starts. Here is my process:
1. Flash Firmware > Root > CWM
2. Make a CWM backup called something like: 29fw_clean_base--
3. install busybox and deodex
4. Make a CWM backup called: 29fw_clean_BB_DO--
5. Install init.d
6. Make a CWM backup
7. Then start adding my mods one by one maing backups as I go called 29fw_running"1,2,3, etc."--
8. Then I can go back and delete or archive CWM backups as to what I need. Always keeping the "clean_base" ready for use if need be.
Click to expand...
Click to collapse
Heh you're everywhere today man! I never even installed init.d, guessing this is for startup scripts or something? I will have to give reflashing a shot, odd thing is it was a fresh install from last week and i pretty much did the first 3 steps in that order.
Do you (or anyone who replies) have a good method for analyzing logcats? tools for proper syntax highlighting maybe? some app must do something in the middle of the night to cause this crap.
thanks
twent4 said:
Heh you're everywhere today man! I never even installed init.d, guessing this is for startup scripts or something? I will have to give reflashing a shot, odd thing is it was a fresh install from last week and i pretty much did the first 3 steps in that order.
Do you (or anyone who replies) have a good method for analyzing logcats? tools for proper syntax highlighting maybe? some app must do something in the middle of the night to cause this crap.
thanks
Click to expand...
Click to collapse
I know, since getting my LT28 I'm always checking the forum, lol.
Yes, init.d for start up / optimization scripts. It's most important to me for my led brightness script. I might suggest going back to the start and doing the bloat removal thing last. See what that gets you. I have not used that script and don't plan to. I'll remove manually what I know I want removed.
I have no knowledge on how to analyaze logcats, sorry.
twent4 said:
This happens about once every two nights. I hit the power button and the lock screen comes up fine, i unlock it with the slider and then home screen starts flickering slowly and is completely unusable. Is this the dreaded redraw issue I've heard mentioned? A forum search doesn't bring up any solutions for this. Any idea what to look for in logcat?
This is on 28i running ICS 2.29, rooted/deodexed+ "bloatware removal script" from deodex forum. Phone works great throughout the entire day.
Click to expand...
Click to collapse
I have two suggestions for you. 1}.Try going into settings>Security>Screenlock and choosing "None". This will reduce the memory usage and prolong battery life. 2).The second is to upgrade to the latest Calendar app if you use the calendar widget.
https://play.google.com/store/apps/...yLDEsImNvbS5nb29nbGUuYW5kcm9pZC5jYWxlbmRhciJd
I was having re-draw issues even on stock firmware with the old calendar / widget installed. I'm guessing this is software / memory management related issues with ICS. Could be wrong but my phone works better with the above settings / app.
Also, try the PIN lock. The slider lock screen is a hog.
I'm having the same problem. I changed to PIN screenlock but even there, I have to press each button slowly and wait for the phone to respond .. It's almost like the CPU is hung while charging .. any other idea's why this is happening? This is only happening to me while charging the phone.
I'd re flash the ftf so you'll lose root deodex and the scripts then give it a week see what happens if it works fine try rooting wait a week see what happens then deodex and see what happens
My guess is when you deodexed something got misplaced or formatted improperly and it screws up the phone while trying to unlock you may also want to boot into cwm mode clear cache dalvik and fix permissions. You never really want to install a bunch of changes at once because if one breaks the phone you cannot pinpoint the issue that's why I waited a few days before I deodexed after rooting
Sent from my LT28at using xda premium
Maybe this is a bug on ICS 2.29, that's what I'm on. Anyone seeing this on 1.19 ?
enrique71 said:
Maybe this is a bug on ICS 2.29, that's what I'm on. Anyone seeing this on 1.19 ?
Click to expand...
Click to collapse
Never had this problem. Never.
Sent from my Xperia ION on Cm9 using XDA Premium app.
So I was having the same issues as everybody else was with Aroma freezing a million times when trying to install a ROM. I tried a few things but eventually stumbled apon a workaround that seemed to work.
I'll explain what I did then others can try it out. If it works for more/everyone else then happy days. If not then maybe I just got lucky.
OK so firstly I was on rooted stock ROM. I'm sure that it's not important really. But I want to mention every step.
I flashed TWRP recovery.
Rooted etc...Standard stuff
Then I used ROM managed to flash non touch recovery via the app itself.
Then made sure CWM was my default recovery in Rom manager.
Rebooted to recovery from Rom Manager.
Wipe data + caches
Install zip. In my case Trickdroid 5.1.0
Then as Aroma is booting up don't touch your phone for a good 2 minutes. I was actually out doing shopping and got to the till so left my phone untouched as it as on the welcome screen.
Then using the touch screen to select what I wanted etc I just went straight through. Not one freeze or install crash. First time.
I think it could be a few things perhaps. Maybe heat with Aroma putting high loads on the phone. Maybe the extra time sat let it cool a bit before getting going. Also perhaps Aroma just needs a little extra time to fully load properly.
Anyway please try my guide out. Maybe you cab miss some bits out. Hopefully it works. Post up if it did or didn't.
Good luck and happy flashing!
Sent from my Tricked out 'One'
My suggestion is that do not connect the USB cable when using Aroma, you should get less chance of freezing.
willingtonyuan said:
My suggestion is that do not connect the USB cable when using Aroma, you should get less chance of freezing.
Click to expand...
Click to collapse
Yes. I think this may be to do with the heat increase.
Sent from my HTC One using xda app-developers app
I tried your method this morning and Aroma froze on 30%. Tried it again and it froze on 3%.
Restored my nandroid and half an hour later tried the 'normal' method for installing a new Rom and it went though without a problem.
Sent from my HTC One
Tried it ...
It freezed on 80%
Damn seems like I was just lucky then. That sucks a bit.
Sent from my Tricked out 'One'
Actually does it matter if your AROMA freezes or not? Because my AROMA has froze on 2 occasions for both installations (One was 30% and the other was 97%) on both ROMs (Renovate and ARHD) and there were no errors or whatsoever when rebooted right after the freeze. Is it just me or..? Hmmm.
LordKuroda said:
Actually does it matter if your AROMA freezes or not? Because my AROMA has froze on 2 occasions for both installations (One was 30% and the other was 97%) on both ROMs (Renovate and ARHD) and there were no errors or whatsoever when rebooted right after the freeze. Is it just me or..? Hmmm.
Click to expand...
Click to collapse
well if it doesnt go fully through i would not trust it flashed fully one bit. i am too paranoid.
Dont use the touch function in Aroma Installer! Choose the options with volume and power button... It works for me!
LordKuroda said:
Actually does it matter if your AROMA freezes or not? Because my AROMA has froze on 2 occasions for both installations (One was 30% and the other was 97%) on both ROMs (Renovate and ARHD) and there were no errors or whatsoever when rebooted right after the freeze. Is it just me or..? Hmmm.
Click to expand...
Click to collapse
It doesn't harm your phone it just means it hasn't worked. You have to long hold the power then just try again until it works.
Sent from my Tricked out 'One'
yes only with volume and power button to operate the Aroma installer ...
works for my (previously only problems)
send for my HTC One
The War Horse said:
It doesn't harm your phone it just means it hasn't worked. You have to long hold the power then just try again until it works.
Sent from my Tricked out 'One'
Click to expand...
Click to collapse
Yes it has been successfully flashed, I was on Renovate ROM before my AROMA installation (for ARHD) froze on 30%. I might have left it there for awhile, thinking that the installation is still going on. I long hold the power button, rebooted and I've successfully flashed ARHD when I checked my settings. No crashes or errors at all.
Try clockworkmod touch freezes less, also I did what someone mentioned to clear dalvic and cache before attempting to install a rom, flashing everything else like trikdroid tweaks works allright..
LordKuroda said:
Yes it has been successfully flashed, I was on Renovate ROM before my AROMA installation (for ARHD) froze on 30%. I might have left it there for awhile, thinking that the installation is still going on. I long hold the power button, rebooted and I've successfully flashed ARHD when I checked my settings. No crashes or errors at all.
Click to expand...
Click to collapse
It will hang on 30% for a while anyway but still be installing. Perhaps you missed it finishing up?
Sent from my Tricked out 'One'
None of these work for me....I managed to get through a full ROM install ONCE but since then I haven't had any luck. Talk about annoying....
aroma kept freezing on me. what i did to finally get it to complete was dalvik/cache wipe in cwm classic first.
once aroma was booted be quick choosing your selections using the power button/volume controls then stuck my hand in the freezer with the phone monitoring the install so when it would complete i could be quick to click the next and reboot buttons.
I tried all recoveries.
Aroma always freezes/crashes.
This is so annoying.
I think at this point it is more of a luck of the draw type of things. I have tried a lot of combinations and after trying like 20 times, it finally went through. Still freezes if I want to install tweaks or themes but less than for a ROM....go figure.
I think everyone should have a go at unchanging between the home key for advanced and occasionally if it's stops vibrating feedback then use next button.
I've had a lot more success this way
Sent from my HTC One using xda premium
tontondavid said:
I think at this point it is more of a luck of the draw type of things. I have tried a lot of combinations and after trying like 20 times, it finally went through. Still freezes if I want to install tweaks or themes but less than for a ROM....go figure.
Click to expand...
Click to collapse
What works for me EVERY time with zero freezes is when you are at the first Aroma screen, hold both volume up and volume down at the same time, then push power while holding all three. It will advance to the next screen. Do the same for every screen and dont touch the screen unless you are selecting to remove or add something. I also found that if I wait too long on a screen before making a choice, it will freeze.
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.