Related
Hello.
My Wildfire S has a vary nasty bug - screen is freezing after unlocking. Well, I can wait few seconds if i just want to start gmail app etc. But when the call is finished and i have to press the Red Button, screen is freezed and that's very annoying.
What should I do to get rid of that?
i have same problem some help?
Same problem here...need help<<<<<<
i some time press home button to make it work>>>>>
got a video
I got a video example for those who can potentially help but don't undertand me)
youtube. com /watch?v=IBOCQYZJK9k
And a question - does hard reset do the same as if I flash totally new official firmware? I meen, does HR leaves something after it or only flashing new firmaware can give my phone a totally clean (like just out-of-the-box) memory?
hm, when I did hard reset, no app left, but still seeing that bug...
I'm using it with official ROM too, but i want to know - does flashing new ROM means the same as hard resetting, or HR is a little bit "softer"?
If someone has experience in flashing phones and spotting this bug, can you try to re-flash?
I've got bad news. I flashed the phone by myself and that bug still is on. That means only one - we should go to the service centre and they'll have to deal with it
never experienced that bug. I have 1.35.707.3 CL48651 release keys.
Very strange, mine will hang for a second on the odd occasion but it's never that bad. Only bug I've noticed is sometimes when I power it off the 4 buttons at the very bottom stay lit, again that only happens every now and again.
Does that mean it's HTC sense's problem? Some people on 4pda(russian smartphone forum) say that their phones have been repaired in service centre by replacing touchscreen. I can't understand - is this hardware or software problem?
I have the same problem. Upon unlocking, right side of screen is not working for a couple of seconds.
Tried to hard reset, and it didn't help. Also tried diferent launcher, and problem remained.
Maybe bug in htc firmware. Has anyone tried flashing it with cyanogenmod of something like that?
dojik said:
hm, when I did hard reset, no app left, but still seeing that bug...
I'm using it with official ROM too, but i want to know - does flashing new ROM means the same as hard resetting, or HR is a little bit "softer"?
If someone has experience in flashing phones and spotting this bug, can you try to re-flash?
Click to expand...
Click to collapse
If you mean factory reset with hard reset, only /data and /cache are wiped.
Flashing a new ROM does wipe /system and replace the content with the new one, nothing happens with /data or /cache here, except within the ROM zip is a cleanup script.
Within /data is all userdata stored, settings, apps and so on (standart behavior, with links2sd its different), within cache is like the name says cached data of the system that shortens the system boot time and stuff like this. In most common you have to clear this before using a different ROM cause it could cause faults, but if the whole base of the rom is different you also have to wipe /data cause this can within this case also cause problems.
Sry, for the off-topic.
---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------
nestorkg said:
I have the same problem. Upon unlocking, right side of screen is not working for a couple of seconds.
Tried to hard reset, and it didn't help. Also tried diferent launcher, and problem remained.
Maybe bug in htc firmware. Has anyone tried flashing it with cyanogenmod of something like that?
Click to expand...
Click to collapse
Different launchers are only apps, they can't solve this problem when it's related to the lockscreen app, maybe switching to another lockscreen version can solve the problem.
same here, after unlocking left side of screen doesnt work until waiting a few seconds or touching other side
Diferent lock application didn't solve problem either. I tried that. I am using ripple lock now.
nestorkg said:
Diferent lock application didn't solve problem either. I tried that. I am using ripple lock now.
Click to expand...
Click to collapse
Could be that it's kernel related. Maybe it's just a big lag, because the CPU governor needs some time to switch the CPU speed after idle.
Swyped from my HTC Desire S
Tectas said:
Could be that it's kernel related. Maybe it's just a big lag, because the CPU governor needs some time to switch the CPU speed after idle.
Swyped from my HTC Desire S
Click to expand...
Click to collapse
It is weird that only right side of screen isn't working properly.
Hope it's not a hardware issue.
Cyanogenmod for wildfire s isn't out yet, so i can't try flashing.
Anyone with some definitive solution?
try without sd card. then reformat the card in a pc the again in phone. worked for me before i used the cm7 rom
greavey said:
try without sd card. then reformat the card in a pc the again in phone. worked for me before i used the cm7 rom
Click to expand...
Click to collapse
Tried this, used the CM7 rom, did what you said above, reverted to stock and im still in the same boat, this HAS to be software related, anyone got any idea's???
Ko_Ka said:
Tried this, used the CM7 rom, did what you said above, reverted to stock and im still in the same boat, this HAS to be software related, anyone got any idea's???
Click to expand...
Click to collapse
This is really doing my head in, its the only thing really ruining my enjoyment of the phone now that I have S-off!
I wiped cache, dalvik cache, sd card everything through clockwork before using the RUU flasher, it has to be software, is there a newer version of the RUU flasher since the 1.30.401.0?
Just a suggestion but temporary remove all your widgets to see if that is what might be causing it.
I found some widgets try to refresh once the phone is woke up even before the screen is unlocked. So I uninstalled any that I did not use.
Also you might try these setting in your build.prop file:
Code:
view.touch_slop = 12
view.minimum_fling_velocity = 30
gsm.proximity.enable=false
debug.sf.hw=1
windowsmgr.max_events_per_sec=80
Hello and good afternoon,
I received this Xperia Arc (LT15a) from my dad to fix and I can't get it worked out so here it is
When you unlock the phone the screen responds to touch, I can swipe back and forth as one would expect. If you keep your finger on the screen or touch it atleast every second the screen stays responsive. If however you stop using the screen, sometimes for 10 seconds most the time just 1 second and the screen will no longer respond. In order to get the screen to respond you have to lock the device and unlock it again, as if refreshing it or restarting the touch screen service in the phone is the fix... temporarily.
I saw a thread somewhat like this and the fix was to downgrade to make sure no bad firmware had been put on so I downgraded to the 4.0.2.A.0.42 that the phone shipped with. This didn't solve the issue. I tried all sorts of firmwares thinking perhaps one would work. My dad tells me that this started happening when he updated the phone to 4.0.4 through the Sony upgrade software.
Has anyone run into this or do you guys believe this is more likely to be a hardware problem (which seems strange because I would think the screen should either work or not)
Thank in advance.
Hi @Laydas,
This is a weird one, for sure.
I've seen something similar on my phone, and for me the problem was definitely linked to an "upgrade / downgrade" kind of thing.
My solution was to install another rom.
So now I guess your bootloader is locked (because the phone is not rooted).
So the best thing to do is to try flashing a stock rom using "flashtool".
Here's some pointers to help you on your way...
Try this thread - http://forum.xda-developers.com/showthread.php?t=1304634
you're looking for info on flashtool, and on stock roms (I think that some stock roms are available in post 2 of the thread)
On top of that, there is an older thread (so a bit outdated) here - http://forum.xda-developers.com/showthread.php?t=1133650
It has good background reading thread to get a grip on all the ideas involved.
Good luck
I forgot to mention that I had already rooted the phone
I have used flashtool to restore the stock rom which didn't solve the issue either.
I have now taken the phone apart to check for loose connections, everything looked good.
I put the phone back together, tried it out, I still have the same screen issue.
Laydas said:
I forgot to mention that I had already rooted the phone
I have used flashtool to restore the stock rom which didn't solve the issue either.
I have now taken the phone apart to check for loose connections, everything looked good.
I put the phone back together, tried it out, I still have the same screen issue.
Click to expand...
Click to collapse
OK, wow. This problem is really sticking around.
So my next question is: - Do you have an unlocked bootloader?
If yes, then try flashing a custom kernel and a custom rom.
My favourite ICS based rom is JJ's Hybrid - http://forum.xda-developers.com/showthread.php?t=1537717&highlight=jj+hybrid
It works 100% with the ArcKnight kernel.
If your bootloader is locked, then you cannot flash a custom kernel. You can still try try the JJ Hybrid rom to see if it sorts out the problem.
At this point I'm running out of ideas. For me this issue was software related, so flashing a different kernel and rom fixed my problem.
It seems like your issue is software related too (because it popped up after an upgrade), but if you flash a rom and a kernel, then there's not much else that you can try flashing,,,
OK, maybe there's also a base-band you can try flashing - There's a base-band thread here - http://forum.xda-developers.com/showthread.php?t=1688049
So try a custom rom and a custom kernel, and if that fails try updating your baseband to 72 or 77.
That's all I can think of to completely overhaul your phone's software.
Please let me know how it goes...
Take care,
Hotfingers
The bootloader is locked on this phone unfortunately.
This phone is not like my other phones, even trying to get a custom rom onto it is a hassle as installs from zips in CWM almost always fail.
Pushing roms from flashtool works but I couldn't find the JJ hybrid rom in a ftf format for flashtool.
At this point I will continue trying to get a custom rom onto this phone when I have time but it has dropped off my priority list as it is being so difficult haha.
Thanks for the help, hopefully sometime next week I will be able to go through some of these steps and get back to this post on what helped
Laydas said:
The bootloader is locked on this phone unfortunately.
This phone is not like my other phones, even trying to get a custom rom onto it is a hassle as installs from zips in CWM almost always fail.
Pushing roms from flashtool works but I couldn't find the JJ hybrid rom in a ftf format for flashtool.
At this point I will continue trying to get a custom rom onto this phone when I have time but it has dropped off my priority list as it is being so difficult haha.
Thanks for the help, hopefully sometime next week I will be able to go through some of these steps and get back to this post on what helped
Click to expand...
Click to collapse
OK, thanks for the feedback. This isdefinitely weird...
After restarting my sgh-m919 I can Bypass the Pin or Password Lockscreen Security by immediately swiping. If i press the power button to lock the screen and awake the phone i still can bypass security by swiping. After several seconds the Lockscreen Pin or Password starts working and it continues to work until i restart the phone again.
This is with an MDL Bootloader and 4.4.2 Kit Kat Touchwiz based roms. I've tried Fenny's rom, Sickness, and some other roms.like wicked, virgin, hyperdrive, etc. Just not sure which ones were Touchwiz based after trying so many different roms. I tried GPE rom and lockscreen security works, and other AOSP rom like CM are working. So are 4.3 based roms.
I guess the latest KNOX security (update M919UVUFNB4 4.4.2) make the Bootloader and OS rely on each other when booting up to make the lockscreen work?
Can anyone here confirm that (with the NB4 Bootloader and Touchwiz based 4.4.2 roms) you can or cannot bypass pin or password security immediately after your phone restarts?
I don't get it. Why are people not even talking about this. There are many people with the old MDL bootloader (without KNOX VOID WARRANTY) but I don't see anyone really talking about it. Is this not that serious of an issue? The only person i saw mention something about the lockscreen and Pin not working cause of KNOX was Fenny on this Post.
http://forum.xda-developers.com/showpost.php?p=51047002&postcount=4
In the same thread vicvon asked if the pin on lockscreen was working as it isn't on i9505 4.4.2 but i'm not sure if he's talking about the same issue here?
http://forum.xda-developers.com/showpost.php?p=51068642&postcount=38
In this thread i mentioned to sickness about this issue and he didn't even know about it. Crawler said that it's happening to him also.
http://forum.xda-developers.com/showthread.php?t=2683507&page=72
I just want to know that it's not just me and that were trying to figure out what is going on or atleast find a temporary solution.
Come on let's talk about this, it's a major security flaw, i don't even know where to start to try and fix this myself.
I give much props, respect, honor, appreciation, and thanks to all the developers and others that put effort into making these roms work and fixing issues that Samsung and other phone companies don't even want to bother with. Any input is appreciated, even if it's not negative.
What do others do? Do you just deal with it? Would you just update your bootloader to make it work? Are you just using older version like 4.2 or 4.3 roms until a solution is discovered? Or are others just using non-touchwiz roms.
I've always been a user of pure android stock aosp roms like vanilla but I rather use touchwiz roms on my Galaxy S4 just to get all the features , then customize what i want or not want.
Use Pattern option for the lockscreen as a temporary solution.
I just noticed that if i use a Pattern for the Lockscreen it works fine, even if i swipe incorrectly several times i can then enter my pin afterwards. The Pattern lockscreen seems to be working fine after restarting the phone.
So for anyone who is experiencing this problem, use the Pattern including Pin setting for the lockscreen.
What do you mean by bypass? Btw you gotta give people time to read your post, research your post, then reply. Can't expect everything right away.
Sent from my SGH-M919 using Tapatalk
elesbb said:
What do you mean by bypass? Btw you gotta give people time to read your post, research your post, then reply. Can't expect everything right away.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
OK sorry, i'm not use to posting. I understand.
I've been trying some roms. I setup my lockscreen with a pin or password. Then i restart my phone. As soon as it loads up i can swipe and the phone unlocks to homescreen without having to enter the pin or password.
These are the rom's I've tried that does it.
http://forum.xda-developers.com/showpost.php?p=51043905&postcount=1
http://forum.xda-developers.com/showpost.php?p=51130759&postcount=1
ish800 said:
OK sorry, i'm not use to posting. I understand.
I've been trying some roms. I setup my lockscreen with a pin or password. Then i restart my phone. As soon as it loads up i can swipe and the phone unlocks to homescreen without having to enter the pin or password.
These are the rom's I've tried that does it.
http://forum.xda-developers.com/showpost.php?p=51043905&postcount=1
http://forum.xda-developers.com/showpost.php?p=51130759&postcount=1
Click to expand...
Click to collapse
Have you wiped your data after flashing the ROM?
I just tried it on my ROM and it works perfectly. I'm on MDL bootloader running the NB4 modem with T-Mobile 4.4.2 ROM.
elesbb said:
Have you wiped your data after flashing the ROM?
I just tried it on my ROM and it works perfectly. I'm on MDL bootloader running the MK2 modem with T-Mobile 4.4.2 ROM.
Click to expand...
Click to collapse
Yes I wipe cache dalvik system, everything.
I just tried this rom TMO 4.2.2 Rom from elesbb and it works fine.
http://forum.xda-developers.com/showpost.php?p=51111038&postcount=1
BTW I have MDL Bootloader and NB4 Baseband.
Oh, I just realized the rom i tried thats working is yours, Thanks bro.
I wonder if it's the kernel that you use that makes it work. Try one of the roms that i listed and see what I'm talking about. I'm going to flash the roms i'm experiencing the issue with a different kernel to see if it works.
I just tried sickness rom (insane kit kat) with this kernel ([KERNEL][TMO][AOSP/TW/GE - 4.4/4.3/4.2][03/27/2014] KT-SGS4 - MJ5 - KTweaker) and it worked fine. The lockscreen works as it should.
This worked for me. But in the oddest way actually. I was at a family party and friends would keep snatching my phone, so I put a lock on it. For some reason however, i'm guessing the Google keyboard had a glitch when I was putting in the pin and it completely misinterpreted what I input... twice? Anyways, I set it all up and locked my phone and thought nothing of it. When I pressed the home key to turn my screen on, I tried putting the code in and it locked me out. Terrified I had no backup of ANYTHING, I didn't know what to do. So I reflashed my ROM without wiping, and it didn't work. So I reboot my phone trying to see if it'll help, and the lock pin and clock were gone but I had my finger on the screen and the flare effect happened. I slid the screen and it worked. So I re-tried this a few extra times and it still worked. Backed everything up, got home and wiped away.
I'd never think I'd say this but, wow that bug SAVED my ass!
So I just got an LS980 and immediately got it unlocked. The unlocker put TWRP on it and installed Cloudy G3 4.4.2 rom. The issue that im having is that the phone will randomly force close apps and restarts when ever it feels like it. Im not sure if its because its a sprint unlocked for GSM use (its on cricket) or if there is some sort of other software issue. What im thinking it could be is that any old stuff that is on the internal storage could be effect it now, but then again I dont know what im talking about.
Ive tried Factory resetting, installing 3rd party messenger and keyboard. Ive used different browsers and tried it with no apps installed. The physical condition is fantastic, I feel like its not a hardware issue. I think what it may be is the rom, the only thing is, ive tried another rom and that one had more issues and it locked it back to sprint.
If it could be a rom issue, which rom could I get for it that wouldnt relock the carrier? I dont want to completely whipe the phone as that could interfere with either the unlocking, or the internal storage which holds the rom install files and gapps. Then again, could I wipe internal storage on the cloudy g3 rom and not relock the phone?
Any help would be greatly appreciated. Thanks!
chasetacos said:
So I just got an LS980 and immediately got it unlocked. The unlocker put TWRP on it and installed Cloudy G3 4.4.2 rom. The issue that im having is that the phone will randomly force close apps and restarts when ever it feels like it. Im not sure if its because its a sprint unlocked for GSM use (its on cricket) or if there is some sort of other software issue. What im thinking it could be is that any old stuff that is on the internal storage could be effect it now, but then again I dont know what im talking about.
Ive tried Factory resetting, installing 3rd party messenger and keyboard. Ive used different browsers and tried it with no apps installed. The physical condition is fantastic, I feel like its not a hardware issue. I think what it may be is the rom, the only thing is, ive tried another rom and that one had more issues and it locked it back to sprint.
If it could be a rom issue, which rom could I get for it that wouldnt relock the carrier? I dont want to completely whipe the phone as that could interfere with either the unlocking, or the internal storage which holds the rom install files and gapps. Then again, could I wipe internal storage on the cloudy g3 rom and not relock the phone?
Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Check to see if the phone is over or under clocked and also check to see if it is undervolted. It could be a custom kernel or even Cloudy's rom causing the issue. As long as it's not a hardware issue you can always go back to stock an unlock it your self easily.
http://forum.xda-developers.com/showthread.php?t=2798566
jsergio123 said:
Check to see if the phone is over or under clocked and also check to see if it is undervolted. It could be a custom kernel or even Cloudy's rom causing the issue. As long as it's not a hardware issue you can always go back to stock an unlock it your self easily.
http://forum.xda-developers.com/showthread.php?t=2798566
Click to expand...
Click to collapse
awesome. im going to try that now. Ive found that its cloudys rom. do you know if I would be able to install a custom rom after the unlocking process? I was looking into the pacman rom, but i dont know if thatll undo any of these changes
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Aztek92 said:
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Click to expand...
Click to collapse
You must have had a bad install as I've not heard of anyone else with those sorts of issues. Though it could be an incompatible app or bad/old data etc Z you might want to ry fixing first eg wiping all app data or factory reset or fresh install (backup your files first )
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Aztek92 said:
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Click to expand...
Click to collapse
1. I see from your link you have the 3g version of the mini, I didn't think that one supports NFC, only the LTE (I9195) has it I think. As NFC needs the right hardware you won't be able to get it. But I don't have the 3g version so I'm not 100% certain if it has support or not.
2. Ii don't think the battery is related to CM13 directly otherwise there would be lots of people with the issue. What is the exact date of the snapshot? There was one that had battery issue but they updated it a few days later is it definitely 20160820 and not the one from a few days before you are running?
Else: If there any app showing high battery usage that doesn't normally? Or is there a problem white a wakelock? You can install an app like Trepn that will show you apps with high cpu usage (even when they are showing in about the usual place in battery stats, my browser recently locked into some sort of loop and was using a high % of cpu occasionally)
3. Always possible but unlikely it's due to Heimdal flash. TWRP should do fine. More likely the wrong Gapps causing instability, you should be on Open Gapps 6 for CM13
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Click to expand...
Click to collapse
edit: see arco's reply below,
The 3g CM ROM will not have the NFC code I guess
No do not check "update recovery" as you might lose your current recovery
gotta go get my son now!
Sent from my Galaxy S4 Mini using XDA Labs
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
Click to expand...
Click to collapse
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
arco68 said:
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
Click to expand...
Click to collapse
Thanks Arco!
(I was trying to say toggle the "signature verification" option but that could lead to more problems if he has the wrong recovery!)
Sent from my Galaxy S4 Mini using XDA Labs
Yup, its GT-I9195, maybe that's from all the problems comes, wrong rom, wrong recovery. I feel kinda dumb, that i didn't check under battery before, sorry for that.
I have work to do today i guess.
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Aztek92 said:
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Click to expand...
Click to collapse
Hi, sorry for bringing up this somehow old thread, but I have the exact same battery issue on my wife's serranoltexx.
I just installed CM13 on her phone, and after a reboot battery dropped from 40% to 5%. This happened twice, so no coincidence here.
Have you found where the problem came for ? Was your battery dead or have you found a fix ?
Also, I have seen your post about sview cover, very interesting. Will try it out tonight !
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Aztek92 said:
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Click to expand...
Click to collapse
Thanks for your answer !
If changing ROM and calibrating did not help, then I guess it's a hardware problem. That was my first thought when I saw this drop yesterday and I already told my wife that we'll have to buy a new one. Cheers to Samsung for building phones with replaceable batteries !
Even a geeky workaround for the sview cover might suit her needs. I think she just wants to check the time and her notifications with the cover on, I don't think she even needs to answer calls (she said it never worked for her, a touchscreen sensitivity issue I believe).
If she doesn't like it, I still have the possibility to downgrade her to CM11. It seems that sview worked fine on this release. And I'm sure she won't mind kitkat as she's not as geeky as I can be
I've been using CM13 nightly (latest) for 4 days or so.
Pros:
Battery last much longer, you have many battery profiles which is nice.
External SD can be integrated as Internal (nice that some apps are automatically installed onto SD)
Cons:
Can't find tar file which is backup I made using CWM recovery rom. Looked everywhere!
Icons dissappear from home after every bootup
Can't move sys apps or preinstalled apps to ext sd card. Can't use Link2SD once you configure External SD as internal. Not so flexible.
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
kennyk09 said:
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
Click to expand...
Click to collapse
Look in /data/media it should be there somewhere. Need root access though.
I recommend using TWRP instead of CWM.
arco68 said:
I recommend using TWRP instead of CWM.
Click to expand...
Click to collapse
Yes, but TWRP can't flash CM11 if I'm not mistaken. Old ROM, I know, but it's the latest one with S-View Cover support.
Also yesterday, I tried to restore my stock ROM backup with TWRP but could not get it to work. Stuck on "starting apps" during boot. Wiping Dalvik and cache did not help.
@thewild
If changing ROM and calibrating did not help, then I guess it's a hardware problem.
Click to expand...
Click to collapse
Not nessessary. Please notice, that i moved from CM13 (i9590) to... CM13 (i9595). I had an issue with wrong recovery. I also didn't have any problem on stock rom. If you're still gonna change battery, tell me how it worked for you.
Btw. there is something called hall monitor https://github.com/durka/HallMonitor But still i have no idea how and if it (still) works.
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10€, so I'll give them a try and let you know.
thewild said:
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10â?¬, so I'll give them a try and let you know.
Click to expand...
Click to collapse
€10, they would have to be fake! (or used)
What is the screen on time (battery>screen) you are getting? I bet it's low & that is the reason for your sudden drops, with my old battery (original Samsung) I was lucky to get 3hrs and that had sudden drops, new battery gives me 6hrs SOT.
Can't tell you the sot because it's not my phone, but it sure is very low. And the battery drops from ~50% to 0% in seconds.
10€ seems to be the right price. They are 20€ on samsung's store, but 10€ is on Amazon, sold by Amazon. I never got fake / used items from them.
Anyway, it's worth a try. I can send it back for free if it's not OK.