Develop Bugs

[FIX] No Power Button Menu And No Lockscreen

New Update: Icenight89 made this into a cwm flashable fix. Great work bro
Check out his thread here:
http://forum.xda-developers.com/showthread.php?t=1611796
--- Old Post ---
Update. I fixed it !!
I was goofing with chroot / Linux in the loop which apparently caused my issue. Random things appear to cause it as any root application can modify this partition ( I'd bet to keep the screen from locking with the screen timing out as it could interrupt a long install ). Neither Nandroid backups , Odining to stock, or factory resets touch the /efs partition. I would absolutely reccommend manually copying the contents somewhere using a root explorer (making a safe backup)!!! We need to talk to the creater of our cwm to see if they can add /efs in the nandroid backup process.
Here is how to fix power menu on long press :
Use a root explorer and paste this file to /efs/imei
( don't worry its just a string and a value )
http://db.tt/Pk2U8Nws
This file also fixes lock screen. Just reboot!!
Hope this helps a few of you out ! If so please drop me a thanks ! :-D Also go to the Dewizzed thread under android development and thank RK ( RoyalKnight ). I couldn't have figured this out without him giving me a dump of his good efs partition to compare it to !!
--Original Post --
Hello,
I seldom post looking for assistance or guidance, however im at my wits end with this phone. I was using the linux installer on the market ( Chrooted Linux subsystem ) and in the process borked my rom. I reinstalled from backup and I have no power button pop up menu for shutting down. It immediately kills / shuts off the phone without a confirmation if you hold the power button for a second.
What i have tried:
Nandroid backups ( Both stock and prior custom installs )
I Odin'd to stock
I Odin'd CWM
I reinstalled the radio via cwm
Installed fresh roms to test
Ive looked all over the web and it looks like some others had the same problem and fixed it by taking a photo ( yes its odd but its fixed others ) and enable/disable secure credentials. Neither of those have resolved the issue.
Does anyone else have any ideas? The phone runs fine aside from the power button no longer having a menu. I put my phone in my pocket and have had it pop up to shut down in the past.... im positive it will get turned off if i dont constantly check to see if its on.
Any ideas? I saw somewhere where another dev created an advanced power menu adding recovery / reboot to the menu. There has to be a way to re-bind it to the power button!
Oh, and i just checked. I have no lock screen either! Ugh!

Ive had this same issue, you must have used one of the "secret codes" for the phone to disable it.
Type *#*#7594#*#* from dialer and hit dial then uncheck the only option that appears...to re enable lockscreen and power menu
I tried to test but it doesn't work for me anymore I'm guessing cause I'm now running juggs and the dev removed that particular option but I had the EXACT same problem the first month I had the phone and was on stock rom it had me frustrated beyond reason I'm a very security conscious person and lock screen not functioning is simply unacceptable.
If the code doesn't work try searching "7594 t989" or something as im positive this is your issue and that is the right code but I'm not positive of the "#*" order in the code. Try it, and if it actually dials out instead of taking you to a hidden menu its wrong.
Please hit thanks if I've helped you! =]
Sent from my SGH-T989

ApexZeph said:
Ive had this same issue, you must have used one of the "secret codes" for the phone to disable it.
Type *#*#7594#*#* from dialer and hit dial then uncheck the only option that appears...to re enable lockscreen and power menu
I tried to test but it doesn't work for me anymore I'm guessing cause I'm now running juggs and the dev removed that particular option but I had the EXACT same problem the first month I had the phone and was on stock rom it had me frustrated beyond reason I'm a very security conscious person and lock screen not functioning is simply unacceptable.
If the code doesn't work try searching "7594 t989" or something as im positive this is your issue and that is the right code but I'm not positive of the "#*" order in the code. Try it, and if it actually dials out instead of taking you to a hidden menu its wrong.
Please hit thanks if I've helped you! =]
Sent from my SGH-T989
Click to expand...
Click to collapse
Well, It was already unchecked sadly. What part of the firmware controls this? I thought it would be radio but ive already flashed a new radio....... it shouldnt be persistant.
I checked it, rebooted, unchecked it rebooted.... still the same. ugh. I gave you a thanks anyway. Any other ideas?
My last shot will be to flast an ATT kernel/radio/rom via Odin if i dont have any other options. Im hoping it should wipe out this issue
The interesting thing is Golocker will work with golauncher installed :/

Well I'm completely befuddled man I appreciate the thanks but when I heard you describe the literal EXACT same problem I had I was certain it was the same thing. Perhaps its the fault of the custom rom that the option is unticked but actually on? I suppose the issue could be originating from another source but with symptoms as specific as yours (both lock screen and power menu gone) it makes me think it may still be connected to what I mentioned. I'm no dev tho so I can't give you much technical support. Hopefully others see this thread and can go on what we have discussed. I have to say I'm a bit disappointed the fix didn't work since we had the same issue that obviously is a deal breaker.
Your saying its the radio cause you flashed nandroid and didn't fix issue?
I remember flashing a nandroid as well and it didn't help at all.
Sent from my SGH-T989

ApexZeph said:
Well I'm completely befuddled man I appreciate the thanks but when I heard you describe the literal EXACT same problem I had I was certain it was the same thing. Perhaps its the fault of the custom rom that the option is unticked but actually on? I suppose the issue could be originating from another source but with symptoms as specific as yours (both lock screen and power menu gone) it makes me think it may still be connected to what I mentioned. I'm no dev tho so I can't give you much technical support. Hopefully others see this thread and can go on what we have discussed. I have to say I'm a bit disappointed the fix didn't work since we had the same issue that obviously is a deal breaker.
Your saying its the radio cause you flashed nandroid and didn't fix issue?
I remember flashing a nandroid as well and it didn't help at all.
Sent from my SGH-T989
Click to expand...
Click to collapse
Unfortunately this isnt a rom related issue. I was thinking that MAYBE the radio controlled it but even that im not so sure of anymore. I even had the exact same issue when I reverted back to stock via Odin...... Sigh
I actually flashed everything possible via Odin ( recovery , stock image , stock kernel , stock radio )
Looks like im stuck using Go Launcher + Go Locker until i can figure this out ( yes i am a security conscious person too )
Here is what i installed https://market.android.com/details?id=com.galoula.LinuxInstall&hl=en
I may need an expert on what exactly the linux installer does to our devices >.> I was under the impression that it used the loop interface and ran the guest OS off of /data. Apparently something deeper went on there

Factory reset will fix it.
Sent from my SGH-T989 using xda premium

zender2k said:
Factory reset will fix it.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Hmmmmmmm did you read my OP?
I appreciate the input but im well beyond just factory resetting it. Ive already reverted to backups via CWM, Ive flashed new roms via CWM, Ive used Odin and flashed back to stock kernels / OS, Ive flashed a new CWM. Ive flashed new radios via CWM, And of course wiped data/cache/dalvik/system/ext-sd. My partitions were wiped, ( All to include my data storage and SD card )
Any other possible suggestions?

Research shows that /efs Might have something to do with the lock screen. Playing around with it now ( its the 1 partition which doesn't get touched during Odin / cwm flashes )
Sent from my SGH-T989 using xda premium

pyraxiate said:
Hmmmmmmm did you read my OP?
I appreciate the input but im well beyond just factory resetting it. Ive already reverted to backups via CWM, Ive flashed new roms via CWM, Ive used Odin and flashed back to stock kernels / OS, Ive flashed a new CWM. Ive flashed new radios via CWM, And of course wiped data/cache/dalvik/system/ext-sd. My partitions were wiped, ( All to include my data storage and SD card )
Any other possible suggestions?
Click to expand...
Click to collapse
I've read your post. The same thing happened to me. After a fresh flash, no power menu, no lockscreen, reboot after touching power button. Again, factory reset fixed it.
Sent from my SGH-T989 using xda premium

FWIW, I have the same symptoms (no lock screen, no power menu) running on rooted stock rom and can say that factory reset has not fixed it, nor has any of the other fixes in threads discussing this issue (*# codes, etc). Still looking for a solution, but wanted to clarify that there doesn't seem to be "one master fix" for people experiencing the issue

Are you referring to the factory reset within the settings menu ? I haven't tried that yet but I have used cwm's factory reset to no avail. I've odin'd back to stock which should be better than a factory reset as it rewrites all partitions ( efs aside ). Ill try it now and report back
Sent from my SGH-T989 using xda premium

fg said:
FWIW, I have the same symptoms (no lock screen, no power menu) running on rooted stock rom and can say that factory reset has not fixed it, nor has any of the other fixes in threads discussing this issue (*# codes,
Click to expand...
Click to collapse
Hi there, I'm looking into it but I think we suffer from a corrupt efs partition. I know our phone isn't the 9100 but it appears to be common there. I have someone dumping their efs for me and I'm going to wipe mine and replace it with his. I've researched and there are only two files I'd need to rewrite ( and nv data doesn't appear to be there...odd )
I'm going to get creative and see if i can't figure this out for us. I've used an efs backup tool to back mine up, format and restore mine already so I know we have access to the partition.
We do have a ton of memory blocks / partitions so I'm hoping the issue isn't with one of the others. If the efs isn't it, I'm going to look at the dump someone posted to try to figure this out ( replacing mine one by one after creating a dump of mine first )
Sent from my SGH-T989 using xda premium

pyraxiate said:
Hi there, I'm looking into it but I think we suffer from a corrupt efs partition. I know our phone isn't the 9100 but it appears to be common there. I have someone dumping their efs for me and I'm going to wipe mine and replace it with his. I've researched and there are only two files I'd need to rewrite ( and nv data doesn't appear to be there...odd )
I'm going to get creative and see if i can't figure this out for us. I've used an efs backup tool to back mine up, format and restore mine already so I know we have access to the partition.
We do have a ton of memory blocks / partitions so I'm hoping the issue isn't with one of the others. If the efs isn't it, I'm going to look at the dump someone posted to try to figure this out ( replacing mine one by one after creating a dump of mine first )
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Funny you should mention efs and post about it so quickly. After my post, i started reading through some of the other threads on the subject during lunch and found this post which talks about a missing file in the /efs directory which i hadn't noticed before:
http://forum.xda-developers.com/showpost.php?p=19388122&postcount=19
All the other threads were talking about test modes and other random things which I *may* have done, but had no memory of. The post about efs struck a cord and I do remember messing with the files there for no good reason when I first got the phone and having made a backup of the directory.
Looking through my backup, I saw a number of files that were no longer in /efs, including the /efs/imei/keystr file containing nothing but the word ON. I quickly copied over the missing files from my backup to /efs using Total Commander (my favorite file manager) and without even a reboot, both the lock screen and power menu have returned.
Coming back to this thread to update my previous message, you were already going down the same path. I have a feeling only the keystr file was needed in my case, but I restored everything to be a) safe and b) if I can't remember what I was doing in /egs, it obviously wasn't useful or important.
This fixed my problem, hopefully it will fix yours as well. I will post a listing of what was in my working and non-working /efs later today for further reference

pyraxiate said:
Are you referring to the factory reset within the settings menu ? I haven't tried that yet but I have used cwm's factory reset to no avail. I've odin'd back to stock which should be better than a factory reset as it rewrites all partitions ( efs aside ). Ill try it now and report back
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes! "factory data reset" under settings > privacy
Sent from my SGH-T989 using xda premium

/efs differences
Reviewing the contents of /efs between my original copy and what was currently on my phone, the following 4 files were missing from my /efs directory:
/efs/cryptprop_rebootMode : 1 byte file, empty
/efs/cryptprop_sdcard : 5 byte file with the word NULL
/efs/imei/bt.txt - 23 byte file with the word bt_macaddr:HEXBTMACADDR
/efs/imei/keystr - 2 byte file with the word ON
If someone can create a sticky master thread for known lockscreen & power menu causes and tested solutions, it would be AMAZING!
---------- Post added at 07:09 PM ---------- Previous post was at 07:08 PM ----------
zender2k said:
Yes! "factory data reset" under settings > privacy
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Doesn't work for everyone!

A factory reset only wipes /data /cache /sd-ext. When you install a new rom generally those are replaced as well as /system. Using Odin , those plus the radio are wiped clean and replaced.
My friend just copied his /efs for me. He used a tool to create a backup ( efs.img ) and just by creating the backup, it created the no lockscreen / power menu symptom. /Efs absolutely has something to do with this problem. He fixed his issue by copying the backup from his sd card to the /efs partition so this is looking promising. I'm copying files back and forth testing as I write this.
I may have found the cause and solution ! :-D
Sent from my SGH-T989 using xda premium

zender2k said:
I've read your post. The same thing happened to me. After a fresh flash, no power menu, no lockscreen, reboot after touching power button. Again, factory reset fixed it.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I'm pretty sure your issue was due to a borked install of a program or the rom. Since you noted your lockscreen disappeared as well. Also your power button causes a reboot while ops is a power down. the factory reset is already what op did by wiping data and cache from recovery. Nice input though, all ideas are welcomed on these types of threads!!!

pyraxiate said:
A factory reset only wipes /data /cache /sd-ext. When you install a new rom generally those are replaced as well as /system. Using Odin , those plus the radio are wiped clean and replaced.
My friend just copied his /efs for me. He used a tool to create a backup ( efs.img ) and just by creating the backup, it created the no lockscreen / power menu symptom. /Efs absolutely has something to do with this problem. He fixed his issue by copying the backup from his sd card to the /efs partition so this is looking promising. I'm copying files back and forth testing as I write this.
I may have found the cause and solution ! :-D
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Have you figured out the cause thay may have started this?

I was goofing with chroot / Linux in the loop. Random things appear to cause it.
Here is how to fix power menu on long press :
Use a root explorer and paste this file to /efs/imei
http://db.tt/Pk2U8Nws
I'm working on the lock screen now.
Edit :
This file also fixes lock screen. Just reboot ! ;-)
Hope this helps a few of you out ! If so please drop me a thanks ! :-D Also go to the Dewizzed thread and thank RK ( RoyalKnight ) I couldn't have figured this out without him giving me a dump of his good efs partition to compare it to !!
Sent from my SGH-T989 using xda premium

MODS
Please sticky this as its a fix and please change the post title to [Fixed] No Power Button Or Lockscreen
Thanks RoyalKnight. Couldn't have done this without your efs dump bro
First post updated with fix
Sent from my SGH-T989 using xda premium

[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

[Q] Phone unusable after being plugged in overnight

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.

Pac-man rom

I've had the pack-rom for awhile and like it slot. I am by no means a newb to flashing ROMs, mods,APS, and all that other good stuff but for some reason I can not figure out how to take a screen **** with this ROM. Can someone please fill me in on this, thanks.....
Sent from my GT-N7105 using xda premium

i don't have the rom installed right now, sorry that my instructions will be a little vague and won't tell you exactly where to go.
you need to find where the power menu options are. I find it in settings ==> rom control ==> power menu. you should be able to enable getting a screenshot through the power menu there. after that, hold down the power button and select screenshot.
hopefully pacman has that setting in the same place...
sent from my i747 with xda-premium

thatmetaldude85 said:
I've had the pack-rom for awhile and like it slot. I am by no means a newb to flashing ROMs, mods,APS, and all that other good stuff but for some reason I can not figure out how to take a screen **** with this ROM. Can someone please fill me in on this, thanks.....
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Hold down the volume down and power button simultaneously.

Pacman Rom-Blame Tyler errors
I'm not sure if this is the right place to post this, but I cant post in the rom thread and none of my searches have been helpful.
I'm coming from 4.2.2 and I've tried flashing several nightlies of the 4.3 update, however I keep getting errors immediately after flashing. The homes creen has not even fully updated when immediately it tells me "insufficient storage", so it wont update any of my apps. On top of that, I get another message that reappears immediately after hitting "ok". It's something like "We're sorry, acore has stopped. Blame Tyler."
I vaguely remember having a similar error when I tried to flash 4.2 and I read that updating the drivers was necessary. So that's what I did, and it worked for 4.2.
Now that I'm having this issue again for 4.3, I'm trying to find out if this is the way to fix it...? I'm a little panicked. This last time I got the error, I tried to wipe cache, dalvik, and restore, but even the restore is not working. And prior to that I might add, none of my latest restore files worked. For example, the last time I flashed successfully was 7/28/13, so I did a back up. Since then, I've backed up several times, tried to flash with no luck, restored with the latest backup file with no luck either. The only backup that will work is the same 7/28/13 file. Ever since then, I have not been able to flash anything successfully, nor restore to any of my latest backup files. Prior to 7/28, I had no issues flashing roms. Now, not even the 7/28 backup will work.
Please help. Not sure where to go from here.

[Q] Quantum 3 RC2 - screen doesnt wake up after lock

I just performed a clean install of Quantum rom 3 RC2 and all seems to be going perfectly except that, when the screen goes off after a timeout, i cant get it back on (power button or home key). If i hit eitehr key immediately after teh screen shuts off it works fine but if i wait a few minutes, i can't get it back at all.
The screen is responsive to touch apprently (if i hit the power button and perform a swipe to unlock i get the tactile feedback. teh same with long press on power button after unlock (which usually shows the power menu)).
Any thoughts?

degener8 said:
I just performed a clean install of Quantum rom 3 RC2 and all seems to be going perfectly except that, when the screen goes off after a timeout, i cant get it back on (power button or home key). If i hit eitehr key immediately after teh screen shuts off it works fine but if i wait a few minutes, i can't get it back at all.
The screen is responsive to touch apprently (if i hit the power button and perform a swipe to unlock i get the tactile feedback. teh same with long press on power button after unlock (which usually shows the power menu)).
Any thoughts?
Click to expand...
Click to collapse
Probably if you have underclocked your kernel on the screen off profile that is the issue. Try to add some values. I used to have that issue.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Prufta said:
Probably if you have underclocked your kernel on the screen off profile that is the issue. Try to add some values. I used to have that issue.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Thanks for your response Prufta.
This is a fresh install so no messing around with under(or over)clocking or voltage has occurred.
It seems that the issue is only experienced when unplugging from charge while the screen is off (and has been for some time).
Strangely enough, it seems to happen much less often with the Nova launcher than the base 4.4 launcher.
I'll try a more systematic attempt to reliably reproduce the issue... this seems a little too inconsistent for my tastes

I'm also having some problems with Quantum RC2... It reboots pretty much every 10 minutes.

I reccomend checking to make sure the bootloader is up to date, make sure you are using the newest CWM and doing a fresh reinstall make sure to Wipe Data/Cache/Dalvik and Format /system and then install the rom and you shouldn't have any other problems. Also make sure that you have the 4.4 GApps from 11/18. If you camera starts acting up when you take front camera pictures then delete Camera 2 and Gallery 2 apk. and install the one I will attach. And if you are still having problems after that let me know.

Mr.Rageface said:
I reccomend checking to make sure the bootloader is up to date, make sure you are using the newest CWM and doing a fresh reinstall make sure to Wipe Data/Cache/Dalvik and Format /system and then install the rom and you shouldn't have any other problems. Also make sure that you have the 4.4 GApps from 11/18. If you camera starts acting up when you take front camera pictures then delete Camera 2 and Gallery 2 apk. and install the one I will attach. And if you are still having problems after that let me know.
Click to expand...
Click to collapse
Bootloader is up to date. latest cwm for the i747 , about as fully clean wipe as possible before this install.
Feeling kinda mentally deficient at this time in relation to your camera comment. How do i delete the camera2.apk (I assume you mean in /system/app) rofs (using es file explorer. also fail to install the apk you provided. I'm sure i'm missing some key silly thing here