In CM 11 and stock(not in cm10.1 and 12/13) something really weird happens.
When the battery indicator shows lower than 20,phone starts killing apps and ghost touch starts.
Its like someone randomly touching the screen
So,I enabled touch pointer to see where actually it happens.
It was at down left corner of the phone.
N.B : Nothings wrong with the hardware.
Rotation(0' vertical)
Happens only on cm11 and stock.
Not related with kernel(stock and r10)
Happens on low battery only.
Sir, @LahKeda @corphish
Any ideas?
I faced the issues too.
And I dont really know its cause.
Seeing it happens only in stock and CM-11 and not in cm-12,13, surely tells its a software issue.
Maybe it is caused by blobs, lots of unused blobs were removed in cm-12.1 and 13 eventually, so maybe that's why...
BatDroid said:
In CM 11 and stock(not in cm10.1 and 12/13) something really weird happens.
When the battery indicator shows lower than 20,phone starts killing apps and ghost touch starts.
Its like someone randomly touching the screen
So,I enabled touch pointer to see where actually it happens.
It was at down left corner of the phone.
N.B : Nothings wrong with the hardware.
Rotation(0' vertical)
Happens only on cm11 and stock.
Not related with kernel(stock and r10)
Happens on low battery only.
Sir, @[email protected]
Any ideas?
Click to expand...
Click to collapse
I have same issue too!
It also automatically press back button.
The solution is simple. Just lock phone for 4-5 seconds then unlock it.
Sohammirikar said:
I have same issue too!
It also automatically press back button.
The solution is simple. Just lock phone for 4-5 seconds then unlock it.
Click to expand...
Click to collapse
I do that all the time.
But actually its not a solution.
It will start after a little while.
BatDroid said:
I do that all the time.
But actually its not a solution.
It will start after a little while.
Click to expand...
Click to collapse
The problem don't appear when connected charger while battery is less than 10 percent too.
Sohammirikar said:
The problem don't appear when connected charger while battery is less than 10 percent too.
Click to expand...
Click to collapse
forgot to say that
corphish said:
I faced the issues too.
And I dont really know its cause.
Seeing it happens only in stock and CM-11 and not in cm-12,13, surely tells its a software issue.
Maybe it is caused by blobs, lots of unused blobs were removed in cm-12.1 and 13 eventually, so maybe that's why...
Click to expand...
Click to collapse
weird
happens on SlimKk too :-/
BatDroid said:
weird
happens on SlimKk too :-/
Click to expand...
Click to collapse
In slimkat i use blobs from cm12.1 and cm11 and the kernel from cm11 ... In fact I didn't face this issue before as I remember . anyway It maybe like as corphish said ....
LahKeda said:
In slimkat i use blobs from cm12.1 and cm11 and the kernel from cm11 ... In fact I didn't face this issue before as I remember . anyway It maybe like as corphish said ....
Click to expand...
Click to collapse
Is there anything u can do?
will u try to remove unnecessary blobs as corphish did in cm12?
corphish said:
I faced the issues too.
And I dont really know its cause.
Seeing it happens only in stock and CM-11 and not in cm-12,13, surely tells its a software issue.
Maybe it is caused by blobs, lots of unused blobs were removed in cm-12.1 and 13 eventually, so maybe that's why...
Click to expand...
Click to collapse
Sir,
Will u please do a clean build of cm10 or 11 after removing unused blobs from them?
Only if u have enough time
I'm having same problem,but I'm running on cm 13 when the battery reaches 20% or below suddenly ghost touch starts whenever the cellular data is on works fine in WiFi
I was having this issue in stock ROM also...
Dev's please help me out here....
adth98 said:
I'm having same problem,but I'm running on cm 13 when the battery reaches 20% or below suddenly ghost touch starts whenever the cellular data is on works fine in WiFi
I was having this issue in stock ROM also...
Dev's please help me out here....
Click to expand...
Click to collapse
And this is really annoying
sir @corphish
sir @LahKeda
can u please check it?
i didnt face this on galaxy star but on other phone(alcatel ot 990) i faced that while charging...
$amoxinH said:
i didnt face this on galaxy star but on other phone(alcatel ot 990) i faced that while charging...
Click to expand...
Click to collapse
The main reason for ghost touch arises due to the charger, I fixed my issue in star using new charger(and wen I say new means not the cheap Chinese one)
Also make sure socket is propperly working:silly: I mean its outlet is normal:laugh:
Related
Hello,
I'm running Gingerbard GBX0A on my Rhod100FR and noticed only two minor issues :
1st one, the less annoying :
takes in average 5-7 seconds to light the screen up when i press the power button
2nd one, a bit more annoying
unexpected reboot, last one occured in the middle of a phone call.
I was wondering it this was bugs from the kernel files, the rootfs or the build itself ?
Knowing about that would allow me to test different kernel or rootfs.
Going back to FRX06 would force me to start over configuring the whole system and resintalling the apps, unless there's to change ext2 file or something to switch from GB to FR ?
Cheers
Edit : my current kernel is 1320 dated 5/14
Long wakeup -> kernel.
Reboot -> probably kernel as well, usually a kernel panic causes reboots. Not always the kernel's fault, but the kernel should be able to handle anything without panicing.
Have you tried an older kernel? Some of the newer kernels aren't as stable. I still bundle 1276 for a reason.
Also, please post in the build thread. No need for another thread...
arrrghhh said:
Long wakeup -> kernel.
Reboot -> probably kernel as well, usually a kernel panic causes reboots. Not always the kernel's fault, but the kernel should be able to handle anything without panicing.
Have you tried an older kernel? Some of the newer kernels aren't as stable. I still bundle 1276 for a reason.
Also, please post in the build thread. No need for another thread...
Click to expand...
Click to collapse
Thanks arrrghhh, i'll go back to 1276, it seemed to far away in the past compared to 131x or 1320 and my idea was to take latest.
I've never tried older than 1295 as far as i remember. I'll give a try with 1276.
I created a new thread b/c i was not sure it was related to GB and i didn't to mispost in the build topic ... Admin can close or move
diegolvobanania said:
Hello,
I'm running Gingerbard GBX0A on my Rhod100FR and noticed only two minor issues :
1st one, the less annoying :
takes in average 5-7 seconds to light the screen up when i press the power button
2nd one, a bit more annoying
unexpected reboot, last one occured in the middle of a phone call.
I was wondering it this was bugs from the kernel files, the rootfs or the build itself ?
Knowing about that would allow me to test different kernel or rootfs.
Going back to FRX06 would force me to start over configuring the whole system and resintalling the apps, unless there's to change ext2 file or something to switch from GB to FR ?
Cheers
Edit : my current kernel is 1320 dated 5/14
Click to expand...
Click to collapse
Same issue, it was running great, fast UI, data was fine, I rebooted then the same issues appeared on my next boot>
I just wanted to let it be known, he's not the only one with these issues
I also have this problem of rebooting. its very annoying. I use the FRX06 and wistilt2 kernel. Wats more annoying is when it reboots i cant even use my winmo cos it still keeps rebooting in winmo. anyone know how to fix this pls?
I decided to go back to FRX06 with stock kernel (1276) and without overclocking because i'd like to use it daily instead of WinMo.
Gingerbread is a bot nicer, ans a couple of extr&a fetures, but is alpha - not stable enough to operate daily.
prexzone said:
I also have this problem of rebooting. its very annoying. I use the FRX06 and wistilt2 kernel. Wats more annoying is when it reboots i cant even use my winmo cos it still keeps rebooting in winmo. anyone know how to fix this pls?
Click to expand...
Click to collapse
That one's weird - I've had spontaneous autoreboots to WinMo, but I've never had WinMo itself bootloop.
You might have failing hardware?
Sounds like that battery issue people were experiencing.
Remove battery for a few hours put it in and charge it, then turn it on only AFTER charging.
There's a chip in the battery that needs resetting, this should do so.
Thanks. ur solution has been working so far but i cant be removing my battery for hours every now n then. is there a way to reset the chip on the battery of i just get a new one?
prexzone said:
Thanks. ur solution has been working so far but i cant be removing my battery for hours every now n then. is there a way to reset the chip on the battery of i just get a new one?
Click to expand...
Click to collapse
Well, hopefully this bug doesn't hit you that often. You can avoid it by shutting down before battery hits 0 (though most of the time battery hitting 0 doesn't trigger this).
You can also avoid this by:
*Getting a second battery. When this bug hits your first battery, just boot Android with the second, and then while plugged in, swap in your first battery. I believe it should start charging normally.
*Getting an external battery charger.
Last time I checked, you could pick up 3 third-party spare batteries with an external charger for like 10 bucks of eBay.
i changed my kernel n it fixed it. well not really but it doesnt bother me as much n im happy wit it now but the problem is this new kernel im using drains my battery. idk if its cos of the constant red led light. anyone know a kernel that fixes this? pls post link
prexzone said:
i changed my kernel n it fixed it. well not really but it doesnt bother me as much n im happy wit it now but the problem is this new kernel im using drains my battery. idk if its cos of the constant red led light. anyone know a kernel that fixes this? pls post link
Click to expand...
Click to collapse
Uhm, the kernel I bundle with my packages (1276) is pretty solid. You can grab a newer kernel, but some of 'em are not as stable.
arrrghhh said:
Uhm, the kernel I bundle with my packages (1276) is pretty solid. You can grab a newer kernel, but some of 'em are not as stable.
Click to expand...
Click to collapse
The only black spot i faced with 1276 is hte screen not lighting up when unlocking the device.
That happened randomly, and of course, this is alayhs when yhou need it the most.
I steped up to wilstilt2's 1300 to get rid of this.
Thanks dvs for your work and support.
It's arela pleasure to use the portage everyday.
guys can anyone pls give me the link to the kernel. whether its 1276 or wistilt 1300
If you go to ryannathans' "Intro to Android - SD card" sticky, the link to the kernels is up near the top of the first post - along with many other useful links.
prexzone said:
guys can anyone pls give me the link to the kernel. whether its 1276 or wistilt 1300
Click to expand...
Click to collapse
Here you can find tons of kernels :
http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Wilstilt2 ones available from there maybe
http://forum.xda-developers.com/showthread.php?t=885550&highlight=Wistilt
but link in 1st post leads ot v1321.
i don't remeber where i founf v1300... sorry
Hello guys, I'm having a very weird issue with the 4.2.1 stock firmware (it only has root).
My phone boots up normally, but after a couple of hours or even a day, by some reason the background image gets screwed up on the top it like you can check on the images and also my battery starts to drain (it shows up huge consumption on "Android OS"). After the graphic issue the only temporary solution is a reboot... any ideas? I've flashed the rom twice and it keeps coming back... can this be a software (app) related problem? Or do you think it is a bug from the actual rom since it is still a leak?
Tks
that's a known bug in the leak
damn it... I was thinking that it was but couldn't find it on google or XDA...
you mean both things right? drain + graphical issue?
tks for your reply!
Better to wait for the officia 4.2.1update from Samsung,
OR there will be ANDROID 4.3 with CM10.2.. vote for GSIII
(Link at my sign)..
BHARGAV33 said:
Better to wait for the officia 4.2.1update from Samsung,
OR there will be ANDROID 4.3 with CM10.2.. vote for GSIII
(Link at my sign)..
Click to expand...
Click to collapse
thank you for your reply mate
casca said:
thank you
Click to expand...
Click to collapse
click it
Cheers mate, make sure you share that CM10.2 poll info for others..
Hello everyone,
So i did a fresh install of CM11 (coming from stock 4.3) hoping it would solve the wake lag issues the stock rom had because it was really annoying having to wait 1-3 seconds for my phone to wake up.
I was surprised that almost nothing changed after the flashing CM11 (i admit there is a slight improvement but still not even close to what i expected).
Is anyone else having problems with wake lag?
Any help would be appreciated.
bump
anyone? i was thinking about flashing the boeffla kernel, would that help?
It's the deep sleep.
Choristav said:
It's the deep sleep.
Click to expand...
Click to collapse
i know, i found some apps that kinda help but they are very unreliable(OS kills them of course). is there a more reliable way to solve this?
H0pesfall said:
i know, i found some apps that kinda help but they are very unreliable(OS kills them of course). is there a more reliable way to solve this?
Click to expand...
Click to collapse
No, unless you want to eliminate deep sleep.
Choristav said:
No, unless you want to eliminate deep sleep.
Click to expand...
Click to collapse
so even flashing a new kernel won't help?
i read that ZRAM might be causing the problem, but the option to disable ZRAM is gone in CM11.
Im using CM11 and I could say the wake lag is not that much! And it is not the same from time to time! But generally it wakes up almost immidiately... Im on the CM11 nightlies, clean install, and didnt change anything else!
H0pesfall said:
so even flashing a new kernel won't help?
i read that ZRAM might be causing the problem, but the option to disable ZRAM is gone in CM11.
Click to expand...
Click to collapse
I'm unaware if that decreases the magnitude of the issue, but you can't ever fix it, save for eliminating deep sleep on an exynos device.
Choristav said:
I'm unaware if that decreases the magnitude of the issue, but you can't ever fix it, save for eliminating deep sleep on an exynos device.
Click to expand...
Click to collapse
well that sucks.
i also read that Yank555's kernel eliminates the lag, but it's only for 4.3.
Last couple of weeks, with different ROMs I have a strange issue where the screen suddenly starts to flicker in within seconds the
battery drains to being completely empty.
I don't even have a chance to get into BBS and check what process is the culprit.
Any idea what might be causing this problem?
kalda01 said:
Last couple of weeks, with different ROMs I have a strange issue where the screen suddenly starts to flicker in within seconds the
battery drains to being completely empty.
I don't even have a chance to get into BBS and check what process is the culprit.
Any idea what might be causing this problem?
Click to expand...
Click to collapse
Your ROM might be the issue.. Does this happens with all ROM or what? Which ROM are you using?
suyash1629 said:
Your ROM might be the issue.. Does this happens with all ROM or what? Which ROM are you using?
Click to expand...
Click to collapse
This happens on samsung based roms like Neatrom, Imperium & ARHD
also happens with CM11 OMNI and SLIM.
tested all these roms with full wipe and clean install.
Could it be a bad battery ?
kalda01 said:
This happens on samsung based roms like Neatrom, Imperium & ARHD
also happens with CM11 OMNI and SLIM.
tested all these roms with full wipe and clean install.
Could it be a bad battery ?
Click to expand...
Click to collapse
First check if this happens with stock ROM not the stock based ones.. And if same happens with complete stock than yes it can be battery issue.
Your battery is inflated? If yes, I think that you need a new battery
LuciIT said:
Your battery is inflated? If yes, I think that you need a new battery
Click to expand...
Click to collapse
Battery is not inflated at all.
kalda01 said:
Last couple of weeks, with different ROMs I have a strange issue where the screen suddenly starts to flicker in within seconds the
battery drains to being completely empty.
I don't even have a chance to get into BBS and check what process is the culprit.
Any idea what might be causing this problem?
Click to expand...
Click to collapse
I was facing same issue...i change my battery as it has 2 years old. So i resolved.
Hey there. Weird problem but my device has no deep sleep at all over 2 hours in screen off. Have had this problem for awhile and wanted to see if anyone could help. I have BBS and wake lock detector if it will help. See alot of event wake locks there but no clue what they mean.
Also I am currently on epic kenzo 6.11.10 but stock MIUI 8 has the same problem as well as cm13/Santosh and cm14.1 aoscp
any ideas?
Use greenify
BabyTedhu said:
Use greenify
Click to expand...
Click to collapse
tried greenify with xposed. still having the event wakelocks unfortunately
high chance is msm_otg issue. it seem to plague kenzo despite of any roms.
kzhkr said:
high chance is msm_otg issue. it seem to plague kenzo despite of any roms.
Click to expand...
Click to collapse
msm_otg is only at 1s on wakelock detector. could it still be a problem?
Tried resetting and multiple different kernels (agni. Radon) still have the event warlocks as usual. Anyone have a clue?
Zaccary said:
Hey there. Weird problem but my device has no deep sleep at all over 2 hours in screen off. Have had this problem for awhile and wanted to see if anyone could help. I have BBS and wake lock detector if it will help. See alot of event wake locks there but no clue what they mean.
Also I am currently on epic kenzo 6.11.10 but stock MIUI 8 has the same problem as well as cm13/Santosh and cm14.1 aoscp
Click to expand...
Click to collapse
Actually, the problem is that latest miui lollipop roms have a new modem which is breaking deep sleep by causing a fingerprint related wakelock, solution is to switch to an older modem from miui 8.0.2 global stable, I have made a recovery flashable zip for that.
Click to expand...
Click to collapse
not sure if it's the same issue for you, but i had similar problem on lollipop miui. You can find the link to the zip in this post
http://forum.xda-developers.com/showpost.php?p=68268086&postcount=2
tcchuin said:
not sure if it's the same issue for you, but i had similar problem on lollipop miui. You can find the link to the zip in this post
http://forum.xda-developers.com/showpost.php?p=68268086&postcount=2
Click to expand...
Click to collapse
lol tried that. broke my calling no sound. and still no deep sleep
just updated and flashed the newest miui global stable through miflash (flash_all bat and reunlocked bootloader) (8.1.1.0) and still no deep sleep sadly.
*edit
Woah weird wtf moment... miui says my phones sleeping yet another usage app in miui says im always awake i wonder which one is telling the truth.
*2nd edit.
also kinda weird... i have wifi off and scanning off so no clue why wifi on is showing?
So update, back again at the latest dev preview (7.1.5 at this point) aaaand still nothing, no deep sleep and ive lost almost 50% overnight. keep in mind that i have installed no apps what so ever and i even debloated the rom. any ideas anyone?
Lol, I got this problem like 1 year, and it seems like there is no solution. you can try CM 13 roms maybe, they seem to sleep. I have this problem in all MIUI roms and I'm not alone, there are lots of the on internet. I think, this ain't a software problem. It is hardware related.