Related
My sensation is turning off randomly. Its very strange i think. sometimes turns off 2 -3 a day sometimes 5 - 10 times a day and sometimes never. i tried to fabrication reset but it cant help. after the reset it starts again in couple of days. My battery is about % 70 but after the turning off it says battery is % 6. then i restart my phone it turns normal % 70. I m not rooted my device yet. Today i spoke with support service they say try to use in safe mod. i used and my device doesnt turns off. but it could be coincidence. I dont know what to do. Any suggestions ?
hi, i have same problem, i am using official rom. i have found this:
http://forum.xda-developers.com/showthread.php?t=1160054
but there is no confirmed reason or method to solve this problem.
does anybody have an idea?? is it software or hardware issue?
soft-reset? hard-reset? or other rom??
help somebody please
I've also had this problem, I discovered that it was what I suspected, the battery. I took advantage and bought a new evo3d battery.
Already spent a month and never had this issue again.
Mains said:
I've also had this problem, I discovered that it was what I suspected, the battery. I took advantage and bought a new evo3d battery.
Already spent a month and never had this issue again.
Click to expand...
Click to collapse
I had the same problem, did a factory reset, a new ROm at the store and nowthey gave my phone a boardswap. i hope that helps....
Same problem here, but not with every Rom and only with the Anker battery... not with the officale htc battery.
i am using official htc battery, official android, now at version 2.3.4, sense version 3.0 and software number 1.45.401.3
i am not sure if flashing other rom helps and if no, i have a problem, bcs with flashing unofficial rom, it breaks warranty.
I try out various ROMs and various kernels including stock rom and kernel. The result was sometimes worked well for a while other times it turn off short time after installation. Turning off some things like wifi, bluetooth and making an underclock the processor helps the phone to hold up better. In my case, having less than 30% of battery life make a call the phone turns off immediately.
This has happened to me on sense miui and cm7 :/
Sent from my Sensation 4g using xda premium
aneroidsk said:
i am using official htc battery, official android, now at version 2.3.4, sense version 3.0 and software number 1.45.401.3
i am not sure if flashing other rom helps and if no, i have a problem, bcs with flashing unofficial rom, it breaks warranty.
Click to expand...
Click to collapse
Root your sensation and flash another rom, it seems like it's a software issue. Also, unlocking your bootloader is what voids the warranty, but there's a way to relock it as well (so if you do get any problems, all you have to do is install the RUU you initially had and relock the bootloader and no one will ever know it happened )
http://forum.xda-developers.com/showthread.php?t=1192300
Here's the thread with the guide to unlocking and relocking your bootloader
Hope this helps
I tried to flashing many roms but it didnt help. I think battery cause this problem. I will buy new battery but not htc`s battery.
snah65 said:
I had the same problem, did a factory reset, a new ROm at the store and nowthey gave my phone a boardswap. i hope that helps....
Click to expand...
Click to collapse
Factory reset doesnt help. Maybe 2 - 3 days it wont turn off then it starts again...
ababak said:
I tried to flashing many roms but it didnt help. I think battery cause this problem. I will buy new battery but not htc`s battery.
Click to expand...
Click to collapse
let us know, if it helps or no
ababak said:
I tried to flashing many roms but it didnt help. I think battery cause this problem. I will buy new battery but not htc`s battery.
Click to expand...
Click to collapse
As i said before, I bought the battery from evo3d and the problem was solved besides that the autonomy is great.
Tell us if with a new battery the problem maintained.
i have unlocked my boot loader i have rooted and i have s-off!
the attached images give my complete firmware info:
i have noticed that my phone feels very stable but somewhat less on performance and battery life.
besides there are strange things i have observed (which happened even before rooting)
a) that my battery takes a lot of time to recharge!
b) at times it wont make it up to 100% will be stuck at 99%
c) and if i power off my device and start it up it just drastically reduces by 10% or so
also my phone doesn't heat up it much 34 C is the temp i see in those battery monitoring apps and the battery drop is stable when the phone is not used. And power saver doesn't make much difference!
so i wanted to flash a kernel..
ttherefore i wanted to ask which kernel will work with my present firmware?
and
how to flash a kernel?
any guide about kernels which will help me get through can also work!:good:
PS m a complete noob but trying to learn things so some detailed help regarding the procedure will be appreciated!:angel:
Sonone said:
a) that my battery takes a lot of time to recharge!
Click to expand...
Click to collapse
What is a "long time"? Can you be more specific? Mine usually charges for near empty to full in maybe 1.5 to 2 hours.
Rooting and S-off won't effect charge time or battery life. Going to Sense 5 might has some effect on battery life (I personally haven't seen a significant change), but would not have any effect on charge time, per se. But if there is fast battery drain, then the phone will take longer to charge, if you are charging with the phone on (as many of us do).
Are you on the 2.15 firmware? You might be having a signal issue affecting battery drain.
Sonone said:
b) at times it wont make it up to 100% will be stuck at 99%
Click to expand...
Click to collapse
How many times did you charge the phone after updating to Sense 5? It takes at least one full discharge/charge cycle after updating the ROM, for the battery meter to be accurate.
Also, charging will automatically shutoff once the battery is charged (this is a mandatory safety feature). Then once the charge has dropped a bit, it will top off again. So I've often seen it drop to 99% while on the charger.
Sonone said:
c) and if i power off my device and start it up it just drastically reduces by 10% or so
Click to expand...
Click to collapse
Probably just a metering error, and the new reading is the correct one. I've seen this happen to myself and others when rebooting the phone. Although, it shouldn't be common. Although might be, if you haven't calibrated the meter properly as I mentioned above.
Sonone said:
ttherefore i wanted to ask which kernel will work with my present firmware?
and
how to flash a kernel?
Click to expand...
Click to collapse
I beleive Beastmode is your only choice for Sense 5 ROMs at the present time: http://forum.xda-developers.com/showthread.php?t=2165880
Just download to your phone, and flash in recovery. Wipe cache and Dalvik after flashing, then reboot.
redpoint73 said:
What is a "long time"? Can you be more specific?
Rooting and S-off won't effect charge time or battery life. Going to Sense 5 might has some effect on battery life (I haven't seen a significant change), but would not have any effect on charge time. I haven't seen any change in charge time across many ROM flashes. It charges from almost empty to full, in about 1.5 hours, or maybe 2 hours.
How many times did you charge the phone after updating to Sense 5? It takes at least one full discharge/charge cycle after updating the ROM, for the battery meter to be accurate.
Also, charging will intentionally shutoff once the battery is charged (this is a mandatory safety feature). Then once the charge has dropped a bit, it will top off again. So I've often seen it drop to 99% while on the charger.
Probably just a metering error, and the new reading is the correct one. I've seen this happen to myself and others when rebooting the phone. Although, it shouldn't be common. Although might be, if you haven't calibrated the meter properly as I mentioned above.
I beleive Beastmode is your only choice for Sense 5 ROMs at the present time: http://forum.xda-developers.com/showthread.php?t=2165880
Just download to your phone, and flash in recovery. Wipe cache and Dalvik after flashing, then reboot.
Click to expand...
Click to collapse
Thanks a lot for your reply.:good:
it takes 2 hours to charge.. slightly more...
i have read people saying getting a 2 0r 3% battery drop in 5 hours or so.. for me its around 6% an hour..
i dont play games...i have removed unecessary apps some bloatware.. i dont use greenify module or set cpu etc.. besides my usage is normal.. and "auto sync" and blink feed is off.. its only whats app messenger but even thats not on auto sync
i use 3g for data plans... thats pretty much about my usage.
about the kernel you recommended is it compatible with my present scenario (ie firmware and 4.2.2 etc)
and it wont affect anything like the "sim(carrier unlock), bootloader,radio etc" [m sorry as i said m a newbie] ?
and which version of beastmode exactly u will recommend?
Sonone said:
Thanks a lot for your reply.:good:
it takes 2 hours to charge.. slightly more...
Click to expand...
Click to collapse
That sounds pretty normal. I assume the phone is on when you are charging, so if you are seeing higher battery drain on Sense 5, then this will of course affect charge time (1 step backward for every 2 steps forward, so to speak).
So if you are seeing slower charging on Sense 5 than before, it might not be charging time per se, but a battery drain issue.
Sonone said:
i have read people saying getting a 2 0r 3% battery drop in 5 hours or so.. for me its around 6% an hour..
Click to expand...
Click to collapse
2-3% per 5 hours seems extremely low. I can get 48 hours on a charge with low usage (phone mostly with the phone idle), on WiFi at home and LTE at work. So about 2% per hour. And I haven't heard reports of battery life much better than that, unless you turn the phone to airplane more or otherwise turn off the data network, which of course will greatly extend battery life but makes the phone much less useful.
And many people have battery life much worse than I've just stated (2% per hour while idle). It depends a lot on how you use your phone, and your location/reception. Drain of 6% per hour with the phone idle is not unheard of, probably even pretty common. When you say 6% per hour, is that with the phone idle and screen off? Is this much different than before you were on Sense 5?
One important question: How did you get on Sense 5? Was it by OTA, or did you flash a custom or stock rooted ROM from Development?
If you flashed a ROM, did you install the 2.15 firmware? This is not to be confused with the OS or ROM, but the 2.15 firmware contains the Sense 5 hboot, radio, as well as several other modules.
If you are not already on the 2.15 firmware, this may help. Of course, a different kernel may help also.
Sonone said:
about the kernel you recommended is it compatible with my present scenario (ie firmware and 4.2.2 etc)
and it wont affect anything like the "sim(carrier unlock), bootloader,radio etc" [m sorry as i said m a newbie] ?
and which version of beastmode exactly u will recommend?
Click to expand...
Click to collapse
Of course it works on your present setup. I already said its the kernel to use for Sense 5, and I wouldn't be recommended it to you if it didn't work on your setup.
Some folks are saying to flash Beastmode version 2.0, reboot, than flash 3.5. But I assume that many folks do just fine flashing the latest 3.5 version.
Flashing a kernel will not touch the radio or bootloader. Also, SIM unlock survives just about anything.
redpoint73 said:
One important question: How did you get on Sense 5? Was it by OTA, or did you flash a custom or stock rooted ROM from Development?
If you flashed a ROM, did you install the 2.15 firmware? This is not to be confused with the OS or ROM, but the 2.15 firmware contains the Sense 5 hboot, radio, as well as several other modules.
If you are not already on the 2.15 firmware, this may help. Of course, a different kernel may help also.
Click to expand...
Click to collapse
Well thats the mystery part. I had purchased this phone from ebay from a local vendor. I live in India as HTC one XL is not available all over the world this phone was 'sim/carrier unlocked' to work with the gsm service providers in India( a known fact) Interestingly when i checked it already came with Sense 5 and 4.2.2 and guess what also with the "SOFF" and "Unlocked Bootloader" as well as Super Cid (11111111) the rom however was not rooted it dint have any custom recovery flashed everything else was stock. Every HTC app worked.
so with this background i obviously thought that it may have some ported rom of sense 5 or a custom rom like 'magio' not 'clean rom 7' since it had some htc bloatware (not carrier bloatware) BUT then it dint have any trace of the developer or a signature or anything that could help me to actually understand which rom I am running!
it has hboot version 2.15.0000 and radio i1.30a.32.45.18
now its not a assembled or a fake version i used many apps like Setc cpu ,An tutu,Trickster Mod(every htc sync manager recognizes it) and it gives the detailed version of hardware which is the one that htc one Xl has so its definitely genuine and legit besides it has an 'imei number.
So that's what i m confused about!! I believe its from Asia hong kong or some where probably! Buts its definitely geniune
redpoint73 said:
Of course it works on your present setup. I already said its the kernel to use for Sense 5, and I wouldn't be recommended it to you if it didn't work on your setup.
Some folks are saying to flash Beastmode version 2.0, reboot, than flash 3.5. But I assume that many folks do just fine flashing the latest 3.5 version.
Flashing a kernel will not touch the radio or bootloader. Also, SIM unlock survives just about anything.
Click to expand...
Click to collapse
I read the thread much of it.. I guess the 3.5 version is jus the 3.0 version with Aroma,surprisingly when i flash try to flash it with TWRP 2.6 it says "FAIL"
besides the developer also mentioned to rename two files in the bin folder with" _old" as an extension does it need to be done with the latest kernel version?
and m a bit scared to do so because many have reported that the file for WiFi fix is missing!
About the battery thanks a ton for the explanation M really happy its normal.. and many apps do say that the health is good so YAY!! =)
now the only reason for flashing a kernel will be to get the extra juice out of my Snapdragon S4!!
*excited*
Sonone said:
Well thats the mystery part. I had purchased this phone from ebay from a local vendor. I live in India as HTC one XL is not available all over the world this phone was 'sim/carrier unlocked' to work with the gsm service providers in India( a known fact) Interestingly when i checked it already came with Sense 5 and 4.2.2 and guess what also with the "SOFF" and "Unlocked Bootloader" as well as Super Cid (11111111) the rom however was not rooted it dint have any custom recovery flashed everything else was stock. Every HTC app worked.
so with this background i obviously thought that it may have some ported rom of sense 5 or a custom rom like 'magio' not 'clean rom 7' since it had some htc bloatware (not carrier bloatware) BUT then it dint have any trace of the developer or a signature or anything that could help me to actually understand which rom I am running!
it has hboot version 2.15.0000 and radio i1.30a.32.45.18
now its not a assembled or a fake version i used many apps like Setc cpu ,An tutu,Trickster Mod(every htc sync manager recognizes it) and it gives the detailed version of hardware which is the one that htc one Xl has so its definitely genuine and legit besides it has an 'imei number.
So that's what i m confused about!! I believe its from Asia hong kong or some where probably! Buts its definitely geniune
I read the thread much of it.. I guess the 3.5 version is jus the 3.0 version with Aroma,surprisingly when i flash try to flash it with TWRP 2.6 it says "FAIL"
besides the developer also mentioned to rename two files in the bin folder with" _old" as an extension does it need to be done with the latest kernel version?
and m a bit scared to do so because many have reported that the file for WiFi fix is missing!
About the battery thanks a ton for the explanation M really happy its normal.. and many apps do say that the health is good so YAY!! =)
now the only reason for flashing a kernel will be to get the extra juice out of my Snapdragon S4!!
*excited*
Click to expand...
Click to collapse
How long ago did you purchase the phone? It seems to me that the seller has just loaded a stock ROM on it before selling it. You're lucky though, you've ended up with a phone that's already unlocked and already s-off, win win.
I may be wrong but I think the renaming of those files was only applicable to an older version of the kernel. I've flashed 3.0 (3.5 is exactly the same kernel but with an updated/different aroma installer) without renaming them a few times and have no issues. I saw someone mention that after the kernel install failed, that fixing permissions in recovery/advanced and then flashing the kernel worked.
Sent from my Evita
timmaaa said:
How long ago did you purchase the phone? It seems to me that the seller has just loaded a stock ROM on it before selling it. You're lucky though, you've ended up with a phone that's already unlocked and already s-off, win win.
Click to expand...
Click to collapse
its just been 4 or 5 days or so.. M sorry if m desperately over enthusiastic but as i said m a total noob and m jus learning!
Thats great my phone is unlocked and good to go!
btw htc is different god knows why they use lithium polymer batteries and that too do which have a relatively less capacity..
and one brief update m using "ondemand" as my governor i hope thats fine!?
timmaaa said:
I may be wrong but I think the renaming of those files was only applicable to an older version of the kernel. I've flashed 3.0 (3.5 is exactly the same kernel but with an updated/different aroma installer) without renaming them a few times and have no issues. I saw someone mention that after the kernel install failed, that fixing permissions in recovery/advanced and then flashing the kernel worked.
Sent from my Evita
Click to expand...
Click to collapse
So u suggest i should try and flash the 2.0 and then the 3.5? i will try that!
and friends btw just realized that my phone actually beats up the international version in Antutu Benchmarks its so close to Nexus 4 atleast on the graph (sorry for the off topic discussion its just that m very happy)
and as always god knows what i would have done without this forum and the explanations i get from you people!:angel:
Sonone said:
its just been 4 or 5 days or so.. M sorry if m desperately over enthusiastic but as i said m a total noob and m jus learning!
Thats great my phone is unlocked and good to go!
btw htc is different god knows why they use lithium polymer batteries and that too do which have a relatively less capacity..
and one brief update m using "ondemand" as my governor i hope thats fine!?
So u suggest i should try and flash the 2.0 and then the 3.5? i will try that!
and friends btw just realized that my phone actually beats up the international version in Antutu Benchmarks its so close to Nexus 4 atleast on the graph (sorry for the off topic discussion its just that m very happy)
and as always god knows what i would have done without this forum and the explanations i get from you people!:angel:
Click to expand...
Click to collapse
There's nothing wrong with being enthusiastic, and I always encourage people who actually want to learn how to modify their device. The ondemand governor should be fine, I've always used that or intellidemand (on the kernels that have it).
You can try flashing 2.0 before 3.5 or you can just try fixing permissions in recovery before just flashing 3.5, apparently either way works. I've never been a huge fan of benchmarks, but Zarboz asked me to do a couple while we were testing the Beastmode kernel, and apparently the result was half decent. I'll attach a screenshot in a minute.
Sent from my Evita
timmaaa said:
There's nothing wrong with being enthusiastic, and I always encourage people who actually want to learn how to modify their device. The ondemand governor should be fine, I've always used that or intellidemand (on the kernels that have it).
You can try flashing 2.0 before 3.5 or you can just try fixing permissions in recovery before just flashing 3.5, apparently either way works. I've never been a huge fan of benchmarks, but Zarboz asked me to do a couple while we were testing the Beastmode kernel, and apparently the result was half decent. I'll attach a screenshot in a minute.
Sent from my Evita
Click to expand...
Click to collapse
was the benchmarking app quadrant?
well it does seem good though like personally m a bit skeptical about benchmarks as they give a different result every time BUT what matters to me is the feedback the kernel has which is really great. And since it gives me a little more control of the functioning of my device m very much inclined to try it out!!
Sonone said:
so with this background i obviously thought that it may have some ported rom of sense 5 or a custom rom like 'magio' not 'clean rom 7' since it had some htc bloatware (not carrier bloatware) BUT then it dint have any trace of the developer or a signature or anything that could help me to actually understand which rom I am running!
it has hboot version 2.15.0000 and radio i1.30a.32.45.18
Click to expand...
Click to collapse
It has the version number (5.05.707.1) and baseband for the Singapore/Singtel Sense 5 OTA. So I'm going to guess that the seller actually RUU'ed to stock and than OTA'ed to the latest official OS, which is actually pretty impressive (went a bit beyond the call of duty, as a seller).
If this is true, all the 2.15 firmware modules should be installed, and you shouldn't need to mess with those.
redpoint73 said:
It has the version number (5.05.707.1) and baseband for the Singapore/Singtel Sense 5 OTA. So I'm going to guess that the seller actually RUU'ed to stock and than OTA'ed to the latest official OS, which is actually pretty impressive (went a bit beyond the call of duty, as a seller).
If this is true, all the 2.15 firmware modules should be installed, and you shouldn't need to mess with those.
Click to expand...
Click to collapse
and finally mystery solved :good::laugh: Genius :good:
but I dint get you? So u mean to say that everything is normal and i can go ahead withe flashing?
and its all good i mean the phone,all legit right?
one thing that i have often thought is that are the custom roms build to work specifically for a particular region or is it universal??
Sonone said:
and finally mystery solved :good::laugh: Genius :good:
but I dint get you? So u mean to say that everything is normal and i can go ahead withe flashing?
and its all good i mean the phone,all legit right?
one thing that i have often thought is that are the custom roms build to work specifically for a particular region or is it universal??
Click to expand...
Click to collapse
Well, its not a sure thing (my assumption on how the phone go to Sense 5). But its the likely scenario.
I'd say all is legit. I wouldn't expect there to be any signal issues due to mismatched firmware modules, as it appears that hboot, radio, and other modules are updated to 2.15 versions meant for the Sense 5 stock ROM.
Although, a few folks have reported poor reception on the Sense 5 radio (baseband), and getting better reception by flashing an older radio. But I think most people are going to see better performance with the newest (Sense 5) radio. Unless you have a reason to believe that reception is an issue, I'd leave it alone.
Any ROM meant for the EVITA will work on your phone (they are not region dependent). The one hitch, if the APN for your carrier is not included on the custom ROM, you will have to enter the APN info manually. But this is a minor issue. And if you already have the phone running on the stock Sense 5 ROM, it looks like you've already figured this out (or it was done for you).
There is also presently an exception, in that some AOSP ROMs do not play well with hboot 2.15. But each AOSP ROM will likely be compatible as the individual developers update their ROMs.
A thread about overclocking that lead to so many things! =)
redpoint73 said:
Well, its not a sure thing (my assumption on how the phone go to Sense 5). But its the likely scenario.
I'd say all is legit. I wouldn't expect there to be any signal issues due to mismatched firmware modules, as it appears that hboot, radio, and other modules are updated to 2.15 versions meant for the Sense 5 stock ROM.
Although, a few folks have reported poor reception on the Sense 5 radio (baseband), and getting better reception by flashing an older radio. But I think most people are going to see better performance with the newest (Sense 5) radio. Unless you have a reason to believe that reception is an issue, I'd leave it alone.
Any ROM meant for the EVITA will work on your phone (they are not region dependent). The one hitch, if the APN for your carrier is not included on the custom ROM, you will have to enter the APN info manually. But this is a minor issue. And if you already have the phone running on the stock Sense 5 ROM, it looks like you've already figured this out (or it was done for you).
There is also presently an exception, in that some AOSP ROMs do not play well with hboot 2.15. But each AOSP ROM will likely be compatible as the individual developers update their ROMs.
Click to expand...
Click to collapse
M happy its all good!
Ya Timmaaa had also mentioned that PAC man in particular is not compatible with 2.15... Access Points ya i can do that..
Reception has been good.... it was the same i had on my earlier cell!
i have to thanks the seller though.. Nice job done..
btw does the clean rom or magio for that matter have any at&t or telstra stuff!?
for clean rom its mentioned i guess anyways i can remove that,coz its actually of no use?
MagioRom has no carrier bloatware at all, it's been removed. I haven't run the new Cleanrom but I think Scott usually removes the bloatware too.
Sent from my Evita
timmaaa said:
MagioRom has no carrier bloatware at all, it's been removed. I haven't run the new Cleanrom but I think Scott usually removes the bloatware too.
Sent from my Evita
Click to expand...
Click to collapse
so no extra bars for network and dat at & t start up screen?
and completely debranded?
thanks for the feedback =)
Sonone said:
so no extra bars for network and dat at & t start up screen?
and completely debranded?
thanks for the feedback =)
Click to expand...
Click to collapse
I'm honestly not sure because I haven't flashed Cleanrom, he should have a list of features in his thread though.
Sent from my Evita
i installed Beastmode version 3.5 my phone is stuck on the start up screen with some something written in red "that its meant for development etc.... what to do?
Download Beastmode 2.0, flash that and then 3.5 afterwards and see if that works.
Sent from my Evita
Sonone said:
so no extra bars for network and dat at & t start up screen?
and completely debranded?
Click to expand...
Click to collapse
CleanROM 7 is actually based on the German T-Mobile stock ROM, but as scrocler says in the top post of the CleanROM thread "infused with AT&T settings!" Probably due to the fact that some 60% of One X/XL users here are on AT&T (based on a survey by Turge), and some things don't always play quite well on AT&T's network without AT&T build.prop, signal icons etc. Although, the stock German ROM is working fantastic for me on AT&T.
I haven't flashed the latest CleanROM either, so I'm not actually sure what AT&T aspects are present or not. You can read through the CleanROM thread, or post the question there. Or just flash it, and see for yourself.
I think scrosler is working on an AROMA version of CleanROM 7, in which case you may be able to customize what AT&T features are included or not.
when trying to install beast mode kernel i was stuck in bootloop so i went into twrp and by mistake wiped everything (i was such a fool my sddata along with my nandroid back up) got erased so i had no os..
when i rebooted it was again in bootloop
so i first flashed twrp
then i mounted usb storage and copied cyanogen mod {cm-10.0.0-evita} and flashed it!
{the version i downloaded was the only tsbale version}
it booted up and now my touch screen nor the capacitive buttons work please tell me what to do??
rilly messed up!
crazy touchscreen problem
After flashing a ROM my touchscreen x axis seems to have inverted itself, so right is left on the screen.
This problem happens during the recovery screen also
I have tried changing recovery's,Kernals,flashed ROM's that I know work
I have even returned the phone back to stock nothing fixed it.
I have even went as far as removing the motherboard and installing one out of a working phone and guess what it does the same thing.
So i ask all you knowledgeable people WTF wold cause this and how can I fix it ?
these are the last two ROM's I was trying out when all this happened
they both ran without a problem I just didn't like them
MokeeOS 44.2 24/12/2013 [UNOFFICIAL],
UNOFFICIAL AOKP][4.4.2] [S4] [12/26/13]
I'm in no way blaming the ROM developers for this issue I just need a little help
Strange problem. I think you should flash firmware, it is worth to try i guess
Sent from my One S using xda app-developers app
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
HomieOneKinobi said:
mines actually doing the same, and from what i've been reading, i believe it has to do with your hboot version and ics not being compatible with it. try flashing your original ruu if you can. that's what i'm trying to do as we speak. if i ever get my problem figured out, i'll let you know if it works.
Click to expand...
Click to collapse
This was my test phone I had flashed just about everything you can think of before I would install it on the phone I use every day
I guess my luck ran out
I ended up flashing the phone back to the original firmware and OS version using the factory RUU without a problem
If I try to install anything over 4.04 it goes right back to the same crap
I tried different firmware, kernels, roms with sense/ no sense doesn't matter.
the phone is being sold as I type this and I'm leaving my other two One S phones alone for now on
Nobody should have to go through this much bull for newer OS version so I'm saving for a Nexus 5
Thank you for the suggestion
So I'm running the newest Mahdi 4.4.4 mahdi rom on my g2 d802 international and none of my sensors are working, first i thought it was a temporary problem and it just needed a reboot but i cant rotate the screen in any apps or any games that require sensors. I decided to test the sensors using accelometer test on the playstore and rezound proximity tester and sensor kinetics and none of them are showing any activity. I never cracked my screen or replaced any parts i take good care of the phone and I dont think its the custom rom causing the problem because it didnt work on my stock rom before i installed Mahdi. It worked before though and then just one day i wake up and its not working . :/
Please help ! thanks in advance
UPDATE: Thanks for all who helped! I just found out i was using a damaged kk modem with no rotation. :/
Yulianstefanov said:
So I'm running the newest Mahdi 4.4.4 mahdi rom on my g2 d802 international and none of my sensors are working, first i thought it was a temporary problem and it just needed a reboot but i cant rotate the screen in any apps or any games that require sensors. I decided to test the sensors using accelometer test on the playstore and rezound proximity tester and sensor kinetics and none of them are showing any activity. I never cracked my screen or replaced any parts i take good care of the phone and I dont think its the custom rom causing the problem because it didnt work on my stock rom before i installed Mahdi. It worked before though and then just one day i wake up and its not working . :/
Please help ! thanks in advance
Click to expand...
Click to collapse
Sounds like a hardware issue. I would send it in for repair. Even though you voided your warranty when you flashed a rom.
zelendel said:
Sounds like a hardware issue. I would send it in for repair. Even though you voided your warranty when you flashed a rom.
Click to expand...
Click to collapse
I just dont get it, it never fell and it has a cover. i just don't see why they don't work... Anyway i guess i'll have to send it to repair.
Yulianstefanov said:
I just dont get it, it never fell and it has a cover. i just don't see why they don't work... Anyway i guess i'll have to send it to repair.
Click to expand...
Click to collapse
Is there any way it could be a software issue?
If it did it on stock then it is most likely a hardware issue.
Just because you didn't drop it doesn't mean the hardware hasn't failed.
Yulianstefanov said:
So I'm running the newest Mahdi 4.4.4 mahdi rom on my g2 d802 international and none of my sensors are working, first i thought it was a temporary problem and it just needed a reboot but i cant rotate the screen in any apps or any games that require sensors. I decided to test the sensors using accelometer test on the playstore and rezound proximity tester and sensor kinetics and none of them are showing any activity. I never cracked my screen or replaced any parts i take good care of the phone and I dont think its the custom rom causing the problem because it didnt work on my stock rom before i installed Mahdi. It worked before though and then just one day i wake up and its not working . :/
Please help ! thanks in advance
Click to expand...
Click to collapse
Its a long shot, but try 're-flashing the modem file. Some of the sensors won't work if you have the wrong one installed, maybe part of your is just broken and need to be restored.
There is a thread in the g2 forum with the modem files, I remember getting mine there.
Maybe you will be lucky and that will fix it.
I think you should go to a Repair Service. But before go to repair service, you should try some ways!
1.Flash FULL STOCK ROM(Not part of stockrom!)
2.Just leave it for 1 days.
3. If there are some manufacture settings, please enter that setting, and check for sensor.(Like Korean SHV-E120 Number of manufacture setting is 319712358) you should find settings from google.
Jason Hyunwoo said:
I think you should go to a Repair Service. But before go to repair service, you should try some ways!
1.Flash FULL STOCK ROM(Not part of stockrom!)
2.Just leave it for 1 days.
3. If there are some manufacture settings, please enter that setting, and check for sensor.(Like Korean SHV-E120 Number of manufacture setting is 319712358) you should find settings from google.
Click to expand...
Click to collapse
Thank you so much , i restored back to full stock rom , messed around in the sensor settings and after a reboot everythings fine. THANKS!
bweN diorD said:
Its a long shot, but try 're-flashing the modem file. Some of the sensors won't work if you have the wrong one installed, maybe part of your is just broken and need to be restored.
There is a thread in the g2 forum with the modem files, I remember getting mine there.
Maybe you will be lucky and that will fix it.
Click to expand...
Click to collapse
Thanks but i saw your post a bit late and i restored to my stock rom already, but if i go back to mahdi ill definately try it. THANK YOU
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!