Related
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.
TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?
Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...
1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.
Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.
This is a continuation of the generic TCC8803 thread at http://forum.xda-developers.com/showthread.php?t=1119778
IMPORTANT - THERE IS A SYSTEM APP CALLED FWTOOL. DO NOT USE IT TO FLASH FIRMWARE OR YOU MAY END UP BRICKING YOUR TOUCHSCREEN. ALSO DO NOT FLASH ANY VERSION OF lk.rom OR YOU WILL BRICK YOUR TABLET.
To install clockworkmod
Download EM73-8K-recovery-signed.zip below. Rename it to update.zip and copy it to the root of your SD card.
With your tablet already turned off, press and hold down the Back button and then press the power on button while still holding down the Back button. This will open stock Recovery.
Use the buttons on the top of your tablet to navigate your way through recovery and to select menu items (menu = down, back = returns to previous menu, home = selects option).
Navigate to apply update.zip & follow the instructions. Reboot.
To use clockworkmod just press and hold down the Back button while powering up your tablet. Navigate the menu via the buttons (menu = down, back = returns to previous menu, home = selects option).
To make a Nandroid (clockworkmod) backup boot into clockworkmod recovery & navigate down to Backup then follow the instructions.
To root your tablet ** please see comment at end of post before continuing past this point
+++Make a full Nandroid (clockworkmod) backup before attempting this+++
Download & unzip Superoneclick from http://forum.xda-developers.com/showthread.php?t=803682 - NB you may need to turn off any antivirus program on your PC to allow downloading & use of Superoneclick.
Download & unzip the relevant Drivers folder (32 or 64 bit) from link below then connect your (powered on) tablet to your PC & point Device Manager to your unzipped drivers folder when it is looking for drivers.
Make sure USB debugging is allowed on your tablet (Settings -> Development -> USB debugging)
Right-click on Superoneclick.exe, select Run as administrator then click on the Root button. It will take 2 or 3 minutes for your device to be rooted.
This procedure has worked for my own tablet but I accept no responsibility if you end up bricking your device!
Another way to root your tablet is at http://forum.xda-developers.com/showthread.php?t=1119778
To stop battery drain & prevent screen from waking every few minutes - **only for original Kogan ROM**
(with thanks to hallokitty for this fix)
This happens because the tablet keeps looking for the 3G signal it cannot ever receive. To fix this, go to System/app using Root Explorer from the Market, delete (or rename) phone.apk and TelephonyProvider.apk. You will immediately start getting errors but just use the reset button at the back of the tablet and when you reboot the problem has been solved. If you ever want to restore these apk's (e.g. if you want to use a 3G modem) just flash the phone+telephony zip file below using clockwork mod.
Clockworkmod rescue backups
I've done a factory reset & wipe of my tablet & made clockworkmod backups which I've linked to below. Make sure you do a full Nandroid backup before applying any of these. Unzip the file & place it in the appropriate Nandroid folder on your SD card (/clockworkmod/backup/), don't try to flash the zip file using CWM! These are a slightly slimmed down versions of the ROMs - for the Kogan ROM I've removed phone.apk, telephony.apk, Email, Facebook, Twitter, FW tool (dangerous to have), ES Explorer, Live Wallpapers and ES task manager. I've upgraded Spare Parts to Spare Parts + and added Astro File Manager as a user app. I had removed most of these things from my ROM before I was ever asked to make this backup so if you want to reinstall them you can get them from the Market or flash the relevant apk's into the system/app folder using CWM. The ROM is still rooted. You will need to do a factory reset & wipe the Data partition & Dalvik cache with CWM prior to doing this. If you want to use a 3G modem you will need to flash the "phone + telephony.zip" file listed below with clockworkmod.
Kogan firmware clockworkmod rescue backup: http://www.mediafire.com/?izfedrz97iowi34
**If you're really lazy you can combine rooting the tablet, removing unnecessary system apps & applying the screen wake fix by installing clockworkmod then restoring the rescue backup (NB make sure you make your own Nandroid backup first!!!).
CM7 runs extremely well on the Kogan except for HDMI out & Camera which don't work yet. You will also need to install Gmail & Youtube apps from the Market if you want them. Make sure you do a full CWM/Nandroid backup before trying this as I had problems with an unresponsive touchscreen after flashing the most recent CM7 ROM. For more info head here.
Tips & Tricks
MoboPlayer is a good video player, particularly for its ability to let you change the volume & screen brightness by swiping up & down directly on the video you are watching. The volume softkeys on the Kogan are not visible if any app is in fullscreen mode.
Titanium Backup may not show all installed apps or any system apps. To fix this go to Titanium Backup's Preferences and tick "Force use system Busybox" and "Force use system SQlite".
OK mine has arrived lets see what we can do
flipside101 said:
OK mine has arrived lets see what we can do
Click to expand...
Click to collapse
Lucky you - they're really dragging their heels with mine. Can you upload the kernel & we can see about getting clockworkmod for it?
How do you rate it as a tablet? Is the keyboard OK? - some people have said it's a bit carp.
I got mine today. It's going back as soon as I can get Kogan to respond.
Turns itself on & off at random, poor quality screen, sound, responsiveness.
Touchscreen activates itself without being touched.
What was I thinking? I guess you get what you pay for.
Now if only I could get them to reply to an email.......
Ok i have to agree you get what you pay for so i had low exectations. Its no flyer,tab,transformer but then it was a 1/4 of the cost. Yes the screen has issues (partly i think due to the screen protecter and battery life is poor though ive had this on for about 2 hrs now and its about 2/3rds down.
All in all im happy though going to live with it for a bit and i reserve the right to change my mind.
Wil right more when i have aproper keyboard
yeh i get the same problem with the screen comming on and off randomly.. i wish i could stop that =P (would save the 3 hour battery life i have to 4 hours!)
you get what you pay for =P but i thought the screen was quite good considering.
did you try the recovery yet?
how nice would it be to port oxygen to the kogan haha
wlee2 said:
yeh i get the same problem with the screen comming on and off randomly.. i wish i could stop that =P (would save the 3 hour battery life i have to 4 hours!)
you get what you pay for =P but i thought the screen was quite good considering.
did you try the recovery yet?
how nice would it be to port oxygen to the kogan haha
Click to expand...
Click to collapse
The screen keeps coming on as the OS is looking for a 3G signal all the time. If you switch it to airplane mode it should stop happening. Or use http://www.appbrain.com/app/airplane-mode-wi-fi-tool/net.geekherd.airplanemode . Or you could even try adjusting the settings to use 2G only.
I can't adjust to 2g only on mine - it's greyed out.
Yes, I've put it back to factory setting a few times, but it's no better.
The switching on/off isn't the main problem (though it has used 30% of the batter life in 8 hours during the night).
The main issue is the touchscreen simply activating itself. If i go into a menu of any kind, it sometimes selects something for me. It happens too often to just ignore it.
Sounds like a faulty screen :-( - let us know how you get on returning it! If mine turns out to be rubbish when it arrives my Plan B is this one http://mp4nation.net/catalog/index.php?main_page=product_info&cPath=68&products_id=496
well im having the random on issues (thanks for the airplane mode idea ill give it a tray) but the screen activations are not a problem.
@dwl99 that mp4nation link is the same as the kogan (a rebranded em73) so its likely to have the same niggles i think
flipside101 said:
well im having the random on issues (thanks for the airplane mode idea ill give it a tray) but the screen activations are not a problem.
@dwl99 that mp4nation link is the same as the kogan (a rebranded em73) so its likely to have the same niggles i think
Click to expand...
Click to collapse
A lot of these tablets are very similar (Herotab C8, Dropad A8) but there seem to be some important differences in the components used. I've been lurking in some Heropad C8 forums and nobody seems to have reported touchscreen problems.
This one look exactl;y the same , button layout etc etc however i know what you saying as even within the same model different components can be swapped in as costs change between runs
BTW
Kernel
2.6.35.7
Build
EM73_SIS_GC2M_V2 20110516
WILL UPLOAD WHEN I GET A CHANCE TO DUMP IT
An app that sticks it in Airplane Mode when you put it into sleep mode is a good work around for now, try "Auto Airplane Mode" (I can't link because I haven't posted enough, it seems...
Hasn't randomly turned on since I installed this. Ahh, forget that, it seems to be doing it again, it just took a lot longer...
In general, this thing is a bit cheap and nasty, but I guess that's what I expected. The button placement is seriously weird, and the touchscreen and accelerometer are just inaccurate and jittery (try playing a game that uses the accelerometer! good luck!)
I feel like it could benefit a lot from a nice ROM though, to fix a few issues (where the hell is the accounts & sync menu?)
hallokitty said:
I feel like it could benefit a lot from a nice ROM though, to fix a few issues (where the hell is the accounts & sync menu?)
Click to expand...
Click to collapse
Been trying to find how to set these before
i found it once earlier on but i cant find it again!!!
it was not where i expected and i think i had to do a round about method to find it.
i have a feeling it had something to do when i was trying to sync email contact with a email app but i forgot which one lol..
dwl99 said:
The screen keeps coming on as the OS is looking for a 3G signal all the time. If you switch it to airplane mode it should stop happening. Or use http://www.appbrain.com/app/airplane-mode-wi-fi-tool/net.geekherd.airplanemode . Or you could even try adjusting the settings to use 2G only.
Click to expand...
Click to collapse
just FYI on the kogans you can activate aeroplane mode in settings then using the power controls widget on your home screen turn on wifi
it will keep the aeroplane mode on but wifi on as well atleast it worked on mine you dont need an app for it.
i actually wonder if the screen wake has something to do with background sync should try turn it off for a night and see.
Okay, so after being plugged in and fully charged, I unplugged it and left to drain overnight to see what would happen.
I had "Auto Airplane Mode" on, but as you'll understand, it helped, but not enough.
Even in Airplane Mode, the tablet would wake itself up, then "Auto Airplane Mode" would see the screen is on, and turn the wifi back on, then back off when the screen faded.
But, I'm thinking this might be because it has Sync enabled. I'm going to try it again with sync disabled.
The battery graph was a joke - it started smoothly going down at a reasonable pace, then -no lie- it spiked down.. then UP, then down, then up, throughout the night. It was at about 75% when I turned it back on after say, 8 hours. Then it dropped to 72%, then I plugged it in, and it immediately reported 98%. The biggest drain by a long way is "Mobile Standby".
However, for the most part, bar the bad accelerometer, terrible button placement, and slightly sharp edges, the hardware itself is not terrible for the money - 512MB RAM and 1GHz processor; I don't mind 800x480 at 7", it looks passable, although it's bad in sunlight. (Of course the viewing angles are bad, but for the cost, that's expected/OK).
But damn the software needs tweaking because it just has problems.
vv
Model number: EM73_SIS_GC2M_V2
Kernel Version: 2.6.35.7
Build number: EM73_SIS_GC2M_V2 20110516
Hi all since installing auto airplane I don't think im seeing wakes issues. I left the kogan overnight at about 50% battery and this morning it was at 35%. Ill test again tonight just to be sure as you seem to have the same build and kernel .
EDIT:
Ok i do still have it
Sent from my HTC Desire using XDA App
Though I have to agree the roms a joke accourding to quick system info 77% of my power useage has been down to mobile standby HUH.
Edit one thought is the 3g component in there for the 3g USB comparability and if so that was a new feature so could there be a rom that exists without it. I have added a topic in this forum asking if its possible to strip the 3g component out.
Sent from my HTC Desire using XDA App
Huh, no, it still seems to turn the screen on now and then even with sync off and in airplane mode. This thing needs a custom ROM as soon as possible. I imagine after a while people will start to sell them cheap because of problems that could mostly be fixed with better software, so I think it could be a pretty popular tablet for people willing to customise it..
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
slixzen said:
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
Click to expand...
Click to collapse
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
_MetalHead_ said:
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
Click to expand...
Click to collapse
I know this is a very late response.
The initial way that I installed the stock firmware was using fastboot, and installing each .img file separately.
I just re-flashed the factory image again (except for the recovery image), and am waiting for the phone to boot up (it seems like it takes ages for the phone to actually go from fresh install to fully booted), it has been over a 5 minutes now.
But once that is done, I will see what happens. Is there a way to check for bad hardware (I am specifically thinking flash storage)? Maybe that is causing the problem?
To start, I have lost access to the reaction video of my wife's first pregnancy announcement. So I would even be willing to make a donation to someone who can help me. (If that is against the rules, let me know)
I used an app from the Play store called Package Disabler Pro to disable some of the bloatware on my phone. In doing so, I disabled something necessary for Ultra Power Save Mode to function. (perhaps Touchwiz) I use Nova Launcher. I tried to show UPSM to a friend yesterday and was met with a black screen. The phone was still running, as I could get the notification window to drop down from swiping. But I had no option to leave UPSM in the settings. The settings that were listed were very limited. I tried everything and ended up soft restarting the phone. It booted back up into UPSM with black screen (no launcher). I finally started tinkering around with Recovery and cleared the cache. At some point, I don't know if it was caused by the cleared cache, it stopped booting fully. I now get stuck at the finished ATT boot animation.
I'm at a loss as to the next step. AFAIK there are no custom recoveries for Galaxy S6 Active yet. So pulling data from ADB in recovery is out. The only other option I have seen is a 'dirty' stock rom flash. But I don't even know if that is possible or will work. If there is anyone out there that has any clue what I should be doing, please help me. I need help. :crying:
Thank you.
Saafir said:
I'd say give the stock a try. The stock tars for our regular S6 dont wipe data. Let this be a learning experience to backup important items to the cloud or thumb drive
Click to expand...
Click to collapse
Is there a distinction between using Stock Recovery to flash stock and using Odin? Stock Recovery warns that user data will be formatted. So I'm assuming that it wipes the user data partition. All that aside, does anyone even know how to get ahold of S6 Active tars?
Ah! I have this same problem right now. Note5. Haven't dug myself that far into the hole yet, and I somehow got out of nova launcher and into TouchWiz (safe mode boot probably), but im stuck in grayscale and can't do anything other than the limited settings options or make phone calls. No texting, internet, full settings access, quicksettings, or really any apps but contacts and phone.
tip...
drapelyk said:
To start, I have lost access to the reaction video of my wife's first pregnancy announcement. So I would even be willing to make a donation to someone who can help me. (If that is against the rules, let me know)
I used an app from the Play store called Package Disabler Pro to disable some of the bloatware on my phone. In doing so, I disabled something necessary for Ultra Power Save Mode to function. (perhaps Touchwiz) I use Nova Launcher. I tried to show UPSM to a friend yesterday and was met with a black screen. The phone was still running, as I could get the notification window to drop down from swiping. But I had no option to leave UPSM in the settings. The settings that were listed were very limited. I tried everything and ended up soft restarting the phone. It booted back up into UPSM with black screen (no launcher). I finally started tinkering around with Recovery and cleared the cache. At some point, I don't know if it was caused by the cleared cache, it stopped booting fully. I now get stuck at the finished ATT boot animation.
I'm at a loss as to the next step. AFAIK there are no custom recoveries for Galaxy S6 Active yet. So pulling data from ADB in recovery is out. The only other option I have seen is a 'dirty' stock rom flash. But I don't even know if that is possible or will work. If there is anyone out there that has any clue what I should be doing, please help me. I need help. :crying:
Thank you.
Click to expand...
Click to collapse
Have tried starting the phone in Safe Mode? Thats what I'd try.
Try what sd_N suggested.
Turn your phone on by holding power button + volume down
When you get the samsung logo, release the power button but keep holding volume down all the way until you get lock screen.
If you are able to boot to safe mode then there's most likely something you have downloaded / something running during your regular boot that crashes / malfunctions.
- Renolz
I found a Solution for those who are still Stuck in Ultra Power Saving Mode.
Send an SMS to your number with Text "google.com"
Notification will appear.
Open the SMS and click the google.com link
Browser will open
Search for a Package DIsabler Software apk -ez disabler or package disabler pro etc.(You should pay the developer later)
Download and Install the app.
You will get Open Option right after Installation is finished.
Enable Emergency Launcher.
Press Home.
Voila, You can now exit UPSM without Factory Reset
Let me tell you a story (you can skip if you want to):
Once upon a time I ****ed up the back layer of the touch screen during repair and desperately tried to use my phone with my PC, found some tools online that let me simulate my phone's screen via ADB. Didn't got that working, ADB was unable to recognize my phone. Ok. Then i taped together the touchscreen (one of the absurdest things i ever did), reconnected it to the phone and guess what. It worked. I booted into recovery mode first and it worked flawlessly. No issues whatsoever. "Wonderful" i thought to myself, booting into system mode eagerly. The boot animation went by without any crashes, graphical issues or anything one could think off, and i even was able to enter my pin. When i did that i was full of enthuisasm. But that didn't last long. The SystemUI began to crash constantly, the lockscreen hasn't even finished building and it crashed again. I was absolutely unable to use the device and utterly devasted. Then i absolutely knew: i. ****ed. up.
But that didn't keep my from trying things out and eventually i was able to get past the lockscreen (without a SIM card so no PIN required) without any crashes and back up at least Whatsapp and a few other apps. But then i made the mistake of turning the screen off which set me back to square one: constant SystemUI crashes. I tried again and again and again and finally, after hours of work i got in a second time. This time, i thought to myself, i gonna make things differently. I backed up everything with Titanium, thought of myself to be safe. Which i technically was, i got backups of everything now. Then i decided to re-flash the rom without a factory reset which didn't do anything. Luckily there is an unofficial build of the ROM i'm using (Resurrection Remix) and i clean flashed it. It worked. Flawlessly. I was thrilled. The phone i was ready to toss into the trash finally worked again. I set everything up, thought myself to be safe but boy was i wrong. Google made regular (i think daily) backups of my apps and contacts and all so i wanted to restore that first. But it required a Pattern which i don't have because i always had a 5x5 pattern and it gave me a 3x3 pattern. I didn't know what to do with it!
I continued setting up my phone after failing to restore that backup and then instantly continued to restore the backup i made with Titanium, It installed all the missing apps, apparently restored the data. Nice. But there are a few apps that don't like that restored data so they just didn't use it and started from scratch again (like SwiftKey). Also, some of my contacts are missing and i'm lowkey too lazy to like the existing ones to Whatsapp again.
Tl;dr: ****ed up phone, got it working again, some apps didn't accept the Titanium backup and now i want to restore the Google backup which requires a 3x3 pattern which i don't have because i always used a 5x5 pattern.
Well, the question is simply: Is there a way to unlock the Google Drive backup without that pattern or do i need to try my luck again accessing the old Data (made a TWRP backup before flashing the new ROM)? If i do need to try again, how do i disable the lock on my backups? Do i only need to change my pattern to a 3x3 one?