Related
Back camera hangs most of the time; it works sometimes but most of the time it freezes and FC itself saying "Unfortunately, Camera has stopped." Front camera always works fine.
The back camera wont FC itself all the time, sometimes it just stays black (with all the buttons and interface working), and sometimes it stays with a freezed image of what the camera sees (also with the interface ok).
I've tried full wipes, I've flashed different roms, with different kernels; cleaned the camera's cache and data; tried the "Restart Camera" solution/workaround; I've even tried to "tap the camera hard" as some people has suggested.
What I haven't done is flashing stock rom, since I consider it won't be of any help (But if you advise me to, I'll do it). And I haven't tried Roms that are not 4.4.4
I'm currently using AICP Rom (4.4.4)
Sorry for any typo.
JCNouel said:
Back camera hangs most of the time; it works sometimes but most of the time it freezes and FC itself saying "Unfortunately, Camera has stopped." Front camera always works fine.
The back camera wont FC itself all the time, sometimes it just stays black (with all the buttons and interface working), and sometimes it stays with a freezed image of what the camera sees (also with the interface ok).
I've tried full wipes, I've flashed different roms, with different kernels; cleaned the camera's cache and data; tried the "Restart Camera" solution/workaround; I've even tried to "tap the camera hard" as some people has suggested.
What I haven't done is flashing stock rom, since I consider it won't be of any help (But if you advise me to, I'll do it). And I haven't tried Roms that are not 4.4.4
I'm currently using AICP Rom (4.4.4)
Sorry for any typo.
Click to expand...
Click to collapse
What roms have you tried? Maybe flashing stock rom will solve your problem. When this this problem start occurring?
gsstudios said:
What roms have you tried? Maybe flashing stock rom will solve your problem. When this this problem start occurring?
Click to expand...
Click to collapse
Hi, thanks for replying. I've lost count of how many, but as I remember, they all were KK Custom Roms, the ones I remember I've tried are AOKP, CM11, and AICP.
It started since... I don't even remember, it has been so long, I just hadn't been able to try to fix it, untill now.
I flashed the stock JB ROM and it fixed it. So I thought that there were corrupted files and since I have them now, I was going to work again if I flashed the AICP ROM back... but nope, it has the same issue.
I'll flash a JB Custom Rom (Probably CM10.2) to see what happens.
Update: I flashed a JB Custom Rom (Fusion Rom) and the camera is working good so far.
But still not working in KK.
Coming from the simplicity of a Nexus 7 and a Moto G, I am a little confused by how the Z3TC handles recovery and flashing. After a two hour session last night I finally got CM12 20150217 running but not matter what I try, I can't seem to get Xposed 2.7 alpha1 to run (it works just fine on Cm12 on my Nexus so it ought to work, somehow).
In the god awful CM12 recovery, flashing xposed fails with an error message I remain unable to read. Flashing it with the twrp that someone integrated into the stock kernel succeeds according to the twrp status but then the xposed installer still does not see the app_process (it sees the bridge however, which I find weird and have not seen like this before).
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
In principle, I am open to going to AOSP if someone can point me to a scorpion_windy image (all I can find on FXP is scorpion for AOSP, which is another weirdness that confuses me) and feels I have better chances of getting it to work there....
Hi,
what you need to do is to install twrp recovery to the FOTA partition.
(This will also allow you update cm12 through cyanDelta, which is not possibe with the crappy cm12 recovery)
It's all decribed here: http://forum.xda-developers.com/z3-tablet-compact/development/daily-cm12-unofficial-builds-t2983400
The twrp img is actually a modified Z2 twrp, but it seems to work.
(i am writing "it seems" because i have a SGP621 myself, for this one I can say "it works").
Please note:
- It is no problem if app_process displays only ---, that is a known bug of the alpha
- not all xposed modules are working. XGELS is working for sure, if you want to test.
- You need to invoke soft reboot from within the xposed app after each flashing of the xposed zip (which you need to flash after each ROM update). Otherwise xposed will not work currently.
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Edit: Or not, a 10 s power & vol + action followed by power on lets me boot both TWRP and CM12, very strange.
Now lets see if I can get Xprivacy to do its job (for starters, the boot.img contents are different than on the GOogle/Moto devices so we shall see)
nupi said:
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Click to expand...
Click to collapse
wow, I'm really sorry to hear that ... I have no idea what might have gone wrong.
You can turn off the device by holding the power button for 7-10 seconds.
If ou want to remove twrp from the FOTA partition, simply reinstall (ONLY) FOTA from the current ftf (SGP621_23.0.1.A.0.167_CE.ftf) through flashtools.
Never mind, I got it back and TWRP flashed xposed cleanly but I can't get it to work - soft reboot does not help, either
However, the kernel seems to have the wrong WiFi drivers for the SGP611 (at the very least, I don't get WiFi anymore). Back to flashing the CM12 kernel for now... I am thinking I should go back to KitKat until someone with a little more clue figures this one out
nupi said:
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
Click to expand...
Click to collapse
Cyanogen has made the worst mistake every with CM12 and CM Recovery Testing at the same Time.
As long as Cyanogen does not develop a real Recoveryfunction to CM Recovery this crap will block much more then Xposed.
Hello guys,
From the title, you might wonder what it has to do with the Z2 Tablet but I know for a fact it's the tablet and not the apps.
A few months back, I tried custom Roms; it all went fine until I tried CyanogenMod. The Rom itself was quite good but it messed up with the Recovery Partition, forcing the installation of the crappy Cyanogen Recovery (although the option to install it with updates was deactivated in the settings; I still don't understand how it got there). I had a hard time installing permanently another Recovery, it always got back to Cyanogen Recovery after a reboot.
A few issues also started to appear on non-Cyanogen ROMS : Adway wouldn't work. Titanium Backup sometimes couldn't find the backups. Youtube playback wouldn't work with the latest version. Gifs would never load on Relay for Reddit. It took me a while to realize that it was related to the ROM, until I actually tried Cyanogen again...where everything worked, sometimes using the same Titanium Backup for the apps !
I got fed up about this, so I decided to revert to full stock (latest 5.1) using the proper FTF.
And you know what ? Youtube Playback is not working, Gifs won't load in Relay. Can't speak for TiBu and Adaway as I didn't root but I'm sure they wouldn't work either. I'm also sure that other apps that I don't use have issues.
Do you have any idea what could be the source of these troubles ? Because if flashing a stock FTF still didn't fixed them, I think Cyanogen damaged my tablet more deeply than I thought...
Thanks !
Did you wipe data?
Not wiping data when going from cyanogen to stock causes problems very similar to yours. (only wiping cache isn't enough)
Sent from my SGP521 using XDA Premium HD app
I always wipe the datas when changing roms. And I did wipe the datas when I flashed the FTF as well...
OGYoutube won't work as well. If only I could identify the issue...
Ok, here's the solution : I forgot to relock my bootloader...
so.. that's so strange. how relocking the bootloader fixes the youtube problem? I've got the same problem with youtube, BUT only with original sony 5.0.. 5.1 firmware. with 4.4.2 or cyanogenmod doesn't happen.
well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'
After rooting my s9+ with the modified Magisk, my phone sometimes becomes unresponsive. I cannot identify any sort of trigger for this to happen, it just does. The AOD displays but does not update. The notification LED still blinks, but when I go to unlock the phone it freezes and I am forced to soft reset it. I am root with Magisk and have TWRP installed. I followed Max Lee's tutorial on how to root the S9+. Any ideas on why this is happening and how to fix it?
Hey, Did you have any luck with this, i am having the exact same issue?
having the same problem i followed Max Lee video and everything work fine until the phone started freezing
same issue on the G960F/DS....
wonder who can help us regarding with this issue.
For everyone having this freezing after rooting...attention to detail is absolute paramount, go back and re-read the twrp thread by jesec. For those (possibly those having freezing issues) who find that challenging, here is a snippet of jesec exact words..." Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection".
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.
To reiterate...flash a custom kernel before root or be SCREWED
I'm not saying this is 100% u guys issue, but seems kinda likely?
can someone post links or steps on how to fix this freezing lock screen issue, i tried reading the threads but did not find anything, thanks
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
crs_dev said:
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
Click to expand...
Click to collapse
Can we flash this Elementalx over the N965F_Root_for_OEM_issue_devices/Magisk we already installed ?
I already installed the TWRP, No-verity opt encrypt and the N965F_Root_for_OEM_issue_devices package on my friend's 960F.
I would be really greatful if anyone could help me with this.
I had the same issue after having troubles initially getting Lineage flashed and working on my S9.
I removed Magisk, reset and it still was freezing after a lock.
I reflashed Lineage through TWRP and now all seems to be back to normal with no freeze after lock.
Possibly try the steps I did and see if they worked out for you.
hey guys, you solved the issue?
i experience same Problem..
Any one notice , this issue occurs after we apply lock screen password or biometric security. in my device i notice, when i apply lockscreen password or biometric lock my phone freeze. after i remove all lock and set default to swipe...its not freezing. anyone sees that
I solved the same issue (1 hour ago, so I hope it's fixed now) installing first:
ElementalX Kernel
and than installing:
G965_Root_for_OEM_issue_devices_V5 (the lastest available right now)
Following the instruction on the XDA Thread
Hope this can be helpfull to solve it
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
KevAngelo14 said:
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
Click to expand...
Click to collapse
What is the different in Soldie between Patched Kernel and ELS custom kernel?