Related
Hi all, And my apologies if i am posting in the wrong section.
i've been searching for the solution for my problem, and so far i cudnt find one.
My HTC works fine, no screen flickering nothing at all.
what my unique problem is that, as my htc reaches to 80% charge, it starts acting like its in a red area zone. it crashes. I switch it one, and as it loads back to lock screen, it crashes again, and again and damn again , untill i put it on charge.
Initially i thought its a software bug so
i rooted my cell, installed custom rom ARHD 6.0, (didnt touch my kernal)
i was happy with the custom rom, battery got better, device became more smooth. but as it reached to 80%, bang. crashed, and crashed after every restart.
i installed LeeDroid rom and confronted the same problem again.
My uncle bought this from UK and i live in Pakistan, so replacement is out of the equation. I am not sure what should i do, even if i give this for repair, what should i ask for that? battery?
i made a video of this, please help me out.
http://db.tt/cpicQdWh
guys, anyone?
If the phone did it out of the box running stock s/w and no other apps it's h/w. Since you're rooted and have played with multiple ROMs it's hard to tell. If I were you I'd go back to the stock ROM, not load any apps, and see if the phone still has the problem. If it doesn't it's something s/w related that you've done to the phone.
Moix123 said:
guys, anyone?
Click to expand...
Click to collapse
I assume there is no official HTC service center available there (as there is non in Iran) in that case I suggest you do this two things before testing local unauthorized repair centers.
1- Flash the latest franco kernel (I suggest franco cause I've tested it myself, you can also use any other kernel)
2- let the battery charge up to 100% and then go to CWM recovery and wipe battery stat
BarryH_GEG said:
If the phone did it out of the box running stock s/w and no other apps it's h/w. Since you're rooted and have played with multiple ROMs it's hard to tell. If I were you I'd go back to the stock ROM, not load any apps, and see if the phone still has the problem. If it doesn't it's something s/w related that you've done to the phone.
Click to expand...
Click to collapse
i was facing this problem when i was on stock. My phone had Vodaphone UK RUU.
i contacted htc, got the following reply
With reference to your query, please kindly update your phone to the latest software version since we have released a recent update which optimizes system performance as well as battery performance.
Meanwhile, you can also follow below steps to set your phone under safe mode for monitoring:
First verify that Fast Boot is not enabled, Settings > Power > Make sure Fast Boot is not selected. To enable safe mode:
1. With the device turned off.
2. Press the power button.
3. Once the device turns press and holds the volume down, once you see the splash screen.
4. Press and hold thevolume down button (DO NOT RELEASE THE VOLUME DOWN).
You will know it has worked because the device will give a brief vibrate or 3 quick vibes. Once it loads you will see on the “Safe Mode” on the bottom left of the screen. This disables all 3rd party apps and drivers from launching. Use the phone normally for 24-48 hours like this. Do not use 3rd party apps or install from the market or the test will be inconclusive.
If the issue will not occur under safe mode, please uninstall the 3rd applications.
Should the problem still persist when your phone is under safe mode, please kindly back up your personal user data and follow below steps to set your phone back to factory default settings:
Settings> Storage> Factory Data Reset".
but this happened on Safe mode too, so i decided to go and get replace by the market guy, but he ..... nvm
After that i switched roms and faced the same issue
srashedian said:
I assume there is no official HTC service center available there (as there is non in Iran) in that case I suggest you do this two things before testing local unauthorized repair centers.
1- Flash the latest franco kernel (I suggest franco cause I've tested it myself, you can also use any other kernel)
2- let the battery charge up to 100% and then go to CWM recovery and wipe battery stat
Click to expand...
Click to collapse
yes indeed this is the main issue,
i actually couldnt find franco kernel for htc =/ can u help me out with this, ( Thanks)
Moix123 said:
yes indeed this is the main issue,
i actually couldnt find franco kernel for htc =/ can u help me out with this, ( Thanks)
Click to expand...
Click to collapse
You find it in
Home> HTC One X> One X Android development
btw is this possible that my stats are incorrect, reason for asking is that. it shut downs like its out of power. and it takes ages to charge up completely even if its on 86%. I install franco, and now its on charging, it will take almost 2 hours plus to get charge completely.
I will post update after wiping battery state
Moix123 said:
Hi all, And my apologies if i am posting in the wrong section.
i've been searching for the solution for my problem, and so far i cudnt find one.
My HTC works fine, no screen flickering nothing at all.
what my unique problem is that, as my htc reaches to 80% charge, it starts acting like its in a red area zone. it crashes. I switch it one, and as it loads back to lock screen, it crashes again, and again and damn again , untill i put it on charge.
Initially i thought its a software bug so
i rooted my cell, installed custom rom ARHD 6.0, (didnt touch my kernal)
i was happy with the custom rom, battery got better, device became more smooth. but as it reached to 80%, bang. crashed, and crashed after every restart.
i installed LeeDroid rom and confronted the same problem again.
My uncle bought this from UK and i live in Pakistan, so replacement is out of the equation. I am not sure what should i do, even if i give this for repair, what should i ask for that? battery?
i made a video of this, please help me out.
http://db.tt/cpicQdWh
Click to expand...
Click to collapse
You should flash every ROM's specific kernel.
Sent from my HTC One X using xda premium
theDroidfanatic said:
You should flash every ROM's specific kernel.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
yes sir i did try that out too,
I flashed the kernel and i charged my battery to 100%
and tried battery stats wipe, still i am having same issue.
After trying a few custom ROMs, I've decided to revert back to the old stock ROM, and unroot because I still had my warranty left. So I downloaded the latest ROM available in the Stock ROMs thread, to be specific I8150DXLM3 Malaysia. :victory:
And after flashing via odin, at random times it would shut itself off, which is rather annoying. There was a phone call from a VIP and I couldn't answer it due to the sudden disappearance. HELP. Grr! I hate the stock ROM now. The only reason I used it I really like the Touchwiz. (Don't really care that much for the warranty) Is there any custom ROM that has Touchwiz that doesn't have all the Samsung bloatware?
meeshvl said:
After trying a few custom ROMs, I've decided to revert back to the old stock ROM, and unroot because I still had my warranty left. So I downloaded the latest ROM available in the Stock ROMs thread, to be specific I8150DXLM3 Malaysia. :victory:
And after flashing via odin, at random times it would shut itself off, which is rather annoying. There was a phone call from a VIP and I couldn't answer it due to the sudden disappearance. HELP. Grr! I hate the stock ROM now. The only reason I used it I really like the Touchwiz. (Don't really care that much for the warranty) Is there any custom ROM that has Touchwiz that doesn't have all the Samsung bloatware?
Click to expand...
Click to collapse
Before going back to stock, go pristine using CWM 1st. Format data, system and everything you can see. Then reboot into download mode and flash Stock ROM back.
Odds are unless your phone breaks in hardware stage, the SSC will still know its been rooted before. But then in Malaysia they're all lazy asses so you'd wanna find the one that looks the laziest. **malaysian here
KiD3991 said:
Before going back to stock, go pristine using CWM 1st. Format data, system and everything you can see. Then reboot into download mode and flash Stock ROM back.
Odds are unless your phone breaks in hardware stage, the SSC will still know its been rooted before. But then in Malaysia they're all lazy asses so you'd wanna find the one that looks the laziest. **malaysian here
Click to expand...
Click to collapse
I already went Pristine. :crying: LOL Heyy Malaysian! :highfive:
check the status of your battery. if it is swollen you must change it. it's happened to me some weeks ago and to some many other users that hava the wonder from one year!! if it is ok simply try factory reset
my phone only shut down itself in paranoid rom..
SpadaBoss said:
check the status of your battery. if it is swollen you must change it. it's happened to me some weeks ago and to some many other users that hava the wonder from one year!! if it is ok simply try factory reset
Click to expand...
Click to collapse
Swollen?!
Haha, no. I just checked the batteryy it's not.
Although, after rooting again, and installing XXLM8 Kernel and Seeders V5 apk it works smoothly and no shut downs so far.
intralot said:
my phone only shut down itself in paranoid rom..
Click to expand...
Click to collapse
Oh.
identical situation here in the philippines,,, regarding samsung care center,,,,
i guess,, they really dont have a way to detect whether yours is rooted or installed with a custom rom,,
i've sent my phone too,, because of a power issue,, as it wont turn on,, :crying:
before that,, ive installed cow bionic rom 2,,, then it shuts down itself,, and had no other means of powering it on,,,
so ive gambled myself in bringing it to them,,,
after a week,, they've said that its a board problem,, and needed to be replaced for free ,, since its under warranty,,, but had to be with them for at least a month,,,
after a month,, theyve returned it to me,,,,, and they even didnt detect that its rooted,, has cwm recovery,,, and installed with a custom rom,,,,
santiagoruel13 said:
identical situation here in the philippines,,, regarding samsung care center,,,,
i guess,, they really dont have a way to detect whether yours is rooted or installed with a custom rom,,
i've sent my phone too,, because of a power issue,, as it wont turn on,, :crying:
before that,, ive installed cow bionic rom 2,,, then it shuts down itself,, and had no other means of powering it on,,,
so ive gambled myself in bringing it to them,,,
after a week,, they've said that its a board problem,, and needed to be replaced for free ,, since its under warranty,,, but had to be with them for at least a month,,,
after a month,, theyve returned it to me,,,,, and they even didnt detect that its rooted,, has cwm recovery,,, and installed with a custom rom,,,,
Click to expand...
Click to collapse
This is why I love Asian countries. :good:
20%
hi evrybody!
my wonder has turned off simultaniusly on 20% on Stock and on Custom Rom, Ive had the battery 2 weeks ago changed. Whats the matter?
On my stock T210R I experienced the system freeze and reboot just a few seconds after power up, it was all stock.
I installed TWRP 2.7.1.0, then wiped it off. Installed gr8nole's ROM (Nov '13 deodexed, rooted). After doing so, there was a Kernel Panic on boot, so I installed Blackhawk kernel 2.1.
After doing all of the above, it still boots up, comes to the initial setup page, runs a few seconds, freezes and reboots.
Do you think this is a hardware problem?
Any suggestions before I sell it for parts on ebay?
Thanks in advance
logs?
poodleDoo said:
On my stock T210R I experienced the system freeze and reboot just a few seconds after power up, it was all stock.
I installed TWRP 2.7.1.0, then wiped it off. Installed gr8nole's ROM (Nov '13 deodexed, rooted). After doing so, there was a Kernel Panic on boot, so I installed Blackhawk kernel 2.1.
After doing all of the above, it still boots up, comes to the initial setup page, runs a few seconds, freezes and reboots.
Do you think this is a hardware problem?
Any suggestions before I sell it for parts on ebay?
Thanks in advance
Click to expand...
Click to collapse
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
moonbutt74 said:
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
Click to expand...
Click to collapse
Sometimes it goes for several minutes before it freezes, especially if the battery is full, even then apps just randomly close without a notification... Maybe storage related?
Care to share how to gather logs?
Thanks
I would use ODIN or KYES to flash it back to OEM stock firmware. Also remove the micro SD card if you have one in there, sometimes corrupt cards can cause boot loop.
true
moonbutt74 said:
does it stay long enough to get logs? even if you have to boot a few times to get them onto your pc and check them out from there?
also with twrp there's some unexplained issue of /data getting corrupted on flashes, the only remedy for which seems to be using the format data option.
m
Click to expand...
Click to collapse
@moonbutt74 there is a prob with corrupted flashes sometimes sometimes not
but i would just go to odin and reinstall the stock firmware then trt again
sharing
poodleDoo said:
Sometimes it goes for several minutes before it freezes, especially if the battery is full, even then apps just randomly close without a notification... Maybe storage related?
Care to share how to gather logs?
Thanks
Click to expand...
Click to collapse
the answer i got to the same question
http://forum.xda-developers.com/showthread.php?t=1520508
http://forum.xda-developers.com/showthread.php?t=2185929
fyi- you can get a lot of different info from files that have info to give with
cat /directory/file > /sdcard/output.file
mostly from /proc and digging through /sys
when you get something crazy looking that goes on forever press ctrl then c to stop.
m
dsilx said:
@moonbutt74 there is a prob with corrupted flashes sometimes sometimes not
but i would just go to odin and reinstall the stock firmware then trt again
Click to expand...
Click to collapse
The tablet did the same without the sdcard, and I tried a couple times to do a factory reset with no luck.
The fact that it does the same with a different ROM and kernel is what makes me think it's hardware related
moonbutt74 said:
the answer i got to the same question
http://forum.xda-developers.com/showthread.php?t=1520508
http://forum.xda-developers.com/showthread.php?t=2185929
fyi- you can get a lot of different info from files that have info to give with
cat /directory/file > /sdcard/output.file
mostly from /proc and digging through /sys
when you get something crazy looking that goes on forever press ctrl then c to stop.
m
Click to expand...
Click to collapse
Cool, i'll get syslog installed and see if I can find anything.
Weird thing... It's been up for a day now, I have catlog running and recording; the only different thing is that I enabled battery saving mode, and batt is 94%; I have not used any apps other than checking battery and running catlog, but I did not have to use it for it to freeze and reboot...
If it is still running by this evening, I'll enable one thing at a time (GPS, sound, etc...)
Thanks @moonbutt74 and @dsilx
awesome
poodleDoo said:
Weird thing... It's been up for a day now, I have catlog running and recording; the only different thing is that I enabled battery saving mode, and batt is 94%; I have not used any apps other than checking battery and running catlog, but I did not have to use it for it to freeze and reboot...
If it is still running by this evening, I'll enable one thing at a time (GPS, sound, etc...)
Thanks @moonbutt74 and @dsilx
Click to expand...
Click to collapse
Awesome to hear sounds like @moonbutt74 was right
Hope it keeps working have fun
Ok, it seems to be hardware, as soon as I disable Power Saving mode, the tablet freezes and reboots.
As I understand, power saving mode limits the CPU to a lower performance tier; so I think the CPU is having troubles.
Oh well, as long as I don't try to mine bitcoins with the tablet, I should be good to go.
cool
poodleDoo said:
Ok, it seems to be hardware, as soon as I disable Power Saving mode, the tablet freezes and reboots.
As I understand, power saving mode limits the CPU to a lower performance tier; so I think the CPU is having troubles.
Oh well, as long as I don't try to mine bitcoins with the tablet, I should be good to go.
Click to expand...
Click to collapse
Well that sucks u have to have battery saver on all the time but at least its working now
hmmm
p,
out of curiosity, are you running any custom cpu/battery/governor apps ?
are you on 4.1 of 4.2, and have you tried ketut's kernel ?
m
moonbutt74 said:
p,
out of curiosity, are you running any custom cpu/battery/governor apps ?
are you on 4.1 of 4.2, and have you tried ketut's kernel ?
m
Click to expand...
Click to collapse
I'm running rooted deodexed stock ROM with Blackhawk 2.1 kernel.
But as I mentioned in the OP, the problem was there with the full stock device, the new ROM and kernel were installed after the problem started.
ouch
i think you pegged it right with internal storage being damaged.
only thing i can think of besides getting your money back is do a full data partition wipe and format
and a full system wipe and format
either way that has to suck. sorry i couldn't help.
m
Q&A for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Rooting Tab Pro 12.2 with last firm done!
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Don't needed. You can root the normal cf-auto-root with latest sock without problem.
After we pm chat last days about rollback to T900UEUAND4 as unique possibility for rooting, i decided to do a last try before that, and luckily works perfect:
-just did a factory reset to restore from B3 recovery i been trying to prev installed T900UEUANI1 stock, wipe caché with stock recovery, odined cf-auto-root and voilá, just rooted!
No need to do the old B3-rollback-prior-D4 method now. Just a normal auto-root with no hassling.
temp maybe?
chhaggerty said:
It sounds like you maybe having a "Sleep of Death" (SOD) issue. The T520 and P900 have had similar problems. I will out of town until Monday but I'll do some research and hope to have a solution soon.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
crpalmer said:
There is a deadlock in Samsung's code triggered by the CPU boost driver. Look in the t520 device repo for the commit that disables it (actually probably 2 commits because I removed some functionality that doesn't make sense for this processor).
Click to expand...
Click to collapse
Dauntless said:
Device: SM-T900
Android: 4.4.2 (Stock, unrooted)
Kernel: 3.4.39-2534013
When putting the tablet into sleep mode, it will automatically shut itself down. When I try to turn it back on, the tablet will only do so after I plugged in the charger. The battery itself is fully charged.
I've updated to the latest available firmware version that's available to me. I couldn't find any list of known issues, so I'm wondering if this is a common problem and if I should return my tablet?
Click to expand...
Click to collapse
Same here. It seems that the problem maybe is temperature: after some time charging it gets really hot and maybe can't awake from that and need rebooting.
I've disabled the magnet sensor vía 3rd app to off the close-lid functionality but don't improve the problem.
Here in summer the room gets to +30°c and the Tab ups to almost 65°c when it gets hot!
Maybe it just reach the temp threshold and self shutdown, or intend that not letting awake.
Perhaps CM11 build here charges battery too fast, with higher voltage than allowed and provoque overheating. I mean, i really feels that it's charging real fast..
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Posted update last night, check it out
Thanks, btw, i was able to use ODIN to get a good version of TWRP and the ROM installed smoothly. I have encountered a few small bugs but nothing to report that is new. I noticed the "sleep of death" I think you are referring to, deep sleep resulting in a manual reboot to wake up. I have noticed my bluetooth disconnects and reconnects every few minutes during deep sleep..not sure why. will report back. Thanks SO SO much for the development, i love it, so sick of the green and blue and the settings tabs on this stock OS disgust me. I am curious tho, am I the only one who noticed significant slowdown and lag compared to stock? I do not put a lot of stock in benchmarks (skewed toward uncle sammy) but they also showed big slowdown....just my very humble and grateful early experiences. Thanks again.
total reflashing needed?
chhaggerty said:
Posted update last night, check it out
Click to expand...
Click to collapse
Well thanks, but,i don't see a flashing update but an entire 221MBs rom to flash..
Can you post just the little update file , if there's any, to flash above the installed rom?
I don't want to install rom, apps and config all over again.
Thanks!
-----
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
-----
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Reboot from Android with 'reboot to recovery' option and when the TWRP splash logo shows it enter in a bootloop always to this instance that TWRP logo appears.
Then i just installed the good old UAND4 rom and it works fine.
Maybe i shouldn't go to recovery direct from android to prevent bootloop happen and try to go the normal way from boot.
Don't know, maybe I'll try some day.., or maybe better wait to Android L comes to us.
Please advice all that stuff in the respective threads, i can't.., cause' these 'noobs-wait-to-10-posting-before' rules..
Greetings.
bertoxo said:
1. Can you post just the little update file , if there's any, to flash above the installed rom?
2. Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
3. Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Click to expand...
Click to collapse
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
arcadia2uk said:
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
Click to expand...
Click to collapse
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
bertoxo said:
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
Click to expand...
Click to collapse
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
arcadia2uk said:
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
Click to expand...
Click to collapse
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
bertoxo said:
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
Click to expand...
Click to collapse
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
Click to expand...
Click to collapse
Thanks!
Installed boot.img and works flawlessly. Now i can back using lid cover again and no more hangs.
I hope they can solve the auto-rotate thing next time.
flashing screen, powering down...
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
My guess is that gaming need more power, why I would stop greeify and reset the governor to interactive while gaming. But other than that I have no ideas, as I haven't heard of this problem before.
This ROM is fantastic! Smooth, fast, responsive and just as described...big thanks.
spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
I don't know if you noticed, but chhaggerty just released a version 3, maybe this will work as there has been some work on the governors.
chhaggerty said:
New update see OP
Click to expand...
Click to collapse
Can i use the 4.4.4 GAPPS instead of 4.4.3 you are posting?
arcadia2uk said:
Thanks for another quality update, notably when reading how other cm11 exynos versions always seems to break something. With your T-900 cm11, I have never had any issues. The latest version is still running smooth, the changes in the CPU governor will probably allow for better battery life with the added conservative setting. However, I don't know what trade-off this will have on performance.
Click to expand...
Click to collapse
Maybe they start to use the big.LITTLE behavior of the Exynos, instead of ever using just the full power a15 cluster (battery eater).
I've haven't tried it but since it's a 4.4.4 rom they should work fine.
Error flashing ROM
Hi guys,
I get this error message when I try to flash CM11:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
This is a brand new rooted SMT-900 Tab Pro 12.2". Here's some notes:
- I received the error using V1, V2, and V3, all receive the error message
- I downloaded two copies of v3 from two separate mirrors (CA and AZ), both receive the error message
- I did a factory reset and still received the error message
- Wiped davlik/cache/system partitions
- Tried on TWRP 2.7 and 2.8, both receive same error message
- All I have done to this tablet is root it, install TWRP, and create one backup
Any thoughts? I can try using CWM if someone can give me a quick overview of how to install it and remove TWRP (or keep TWRP).
Guys I don't know if there's something wrong with my phone or not. Whichever rom or kernel I try, there is an abnormal shut down of my device. Like I'm using it and I leave it for a few minutes or so and it shuts down. I'm not sure if it had something to do with deep sleep or anything, but I need help. Please guys anyone
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
YasuHamed said:
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
Click to expand...
Click to collapse
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
promiscuss said:
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
Click to expand...
Click to collapse
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
YasuHamed said:
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
Click to expand...
Click to collapse
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
promiscuss said:
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
Click to expand...
Click to collapse
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
promiscuss said:
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
Click to expand...
Click to collapse
sir, which custom ROM + kernel + anrdoid version are you on ?
YasuHamed said:
sir, which custom ROM + kernel + anrdoid version are you on ?
Click to expand...
Click to collapse
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
promiscuss said:
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
Click to expand...
Click to collapse
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
YasuHamed said:
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
Click to expand...
Click to collapse
Thanks for all your effort, the problem seems to have resolved on its own. I'm not sure what it was.
now it's happening to me but it's much more severe. First it started slowly now it's so frequent that the phone might shut down even on boot. This is really frustrating.
I had the same problem with my redmi note 7, flashed stock rom with MI flash tool, fixed everything for me