Hi,
So ~3 weeks ago I got my HTC Sensation XE, eveything has been working flawlessly up until last week.
Issue:
When I start playing video on YouTube App. ( latest version ), it lags for 2-3 seconds, then the next 2-3 seconds are played in slight fast forward and so rinse and repeat. For some videos it's much more distinctive, for some - barely noticeable. This issue causes sound to be desynced as well, for a brief period.
I did factory data reset and nothing changed ( well obviously.. ) except that the preinstalled/default YouTube App. has a different issue. Video playback is fine and such, but it starts lagging whenever I bring up the timeline bar and does not stop unless it disappears.
I did notice that phone has been responding in a sluggish way as well. For example, it sometimes lags when scrolling a list in an App ( Market, etc. ) or just scrolling a change log text ( not that huge ) for an App; thing is - about 80% of the scroll..it scrolls like a slideshow and sometimes it just scrolls flawlessly. You might say that problem is in loading the lists/videos..., however I think that's not the case because the videos are cached fine, signal strength is good. I did test for these issues on different WiFi's and 3G, however, to no avail.
Warranty "Service" + Test
I did take my phone to Warranty service, they did * reprogram* it ( My guess is that they did factory reset ), of course problem was no fixed. I did take it back again to show it, but they replied that they did what they could ... ( part where I get pissed ... might as well as return to them ... )
Well since I am in a conversation with HTC Support, the conclusion that they made was much more appealing and logical - it's either antenna, need for a re-flash or mobo change.
So since my network is working fine and I have no trouble or whatsoever with LOADING the video, the issue HAS to be in the PLAYBACK part ...
I decided to some deductive testing.
I ran YouTube App and Internet browser to check for these problems.
As it turned out, I had no problems in video playback using internet browser both for youtube.com and m.youtube.com, it even played 1080p video ( not really well, but it was much ,much more bearable that those 2-3 second lags and also .. it might be part of the issue I am having )
Then put my phone side by side to PC. Videos using Internet browser were played 1:1, when I played them on YouTube app., phone was noticeably lagging behind and catching up all the time.
So this points to software problem direction.
However I am still concered about Hardware problem since the 1080p was not played really smoothly ( well, it should, shouldn't it ? ) and generally sluggish phone.
Click to expand...
Click to collapse
Questions:
1. Are these Software or Hardware issues? How do I exactly tell that?
2. Since I am seriously concering ROOTing the phone and flashing with CM if the issue is software based, what are main tips to search for? ( What causes bricking of the phone/how to avoid that... etc. )
3. Can any of you give a quick rundown of these terms and how do they differ?
ROM - that's Android OS 2.3.4 (Gingerbread) ... ICS etc., right?
Firmware - ???
Kernel - Hardware level controller??
Baseband - Radio ( WiFi/3G/GSM ?? )
and some more off from "About phone"
- what is Software number?
- what is build version?
- what is Browser version?
Hello,
a while ago a friend of mine bought a Sensation as well.
It´s stock ICS, unrooted.
It worked well for about a half year and now the Camera closes every time.
When you push on camera App, the background gets black and the buttons appear. Short before you should see anything, you get back to the homescreen.
The backlight doesnt get lower.
Now the surprise:
If you open the videocamera-App, it workes! Frontcamera works with both (video & picture)!
Change back to main camera and it dissapears...
Starting camera from App (WhatsApp) doesn´t work either. Camera-Apps from market are working.
Untli yet, we tried deleting Camera-Data & some restarts.
I´d S-off this thing, root & try a different ROM. But it´s not my phone
The point of the topic:
Post your issues found in STOCK / CM11 or post a solution.Simple as that,very productive.
I'll start with a list of bugs:
CM11 ISSUES:
-Video recording lags in reduced luminosity.
-The phone heats too much when playing/watch videos for long time and so on.
-Volume during call is too low.
-Ocasionally freezes & crashes.
-Some graphical issues when the phone freezes.
-Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
STOCK ISSUES:
-Video blinks in low light(from what I've read it focuses wrong on the light source and starts blinking).
-The proximity sensor remains on after a missed call.
-Multi touch doesn't work as well as on CM11.
-Some weird freezes during call ( the screen remains off / freezes and you can't end the call / sometimes even answer )
-Camera doesn't have as much detail as in CM11 ( if you zoom in,the image doesn't clarify).
-Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
CM11 FIXES:
-Lag in video recording can be reduced by lowering the exposure.In medium to low light " - 1 " works pretty good and in very low to low light " - 2 " .However,when you use " - 2 " ,the recorded video will be very dark.Still haven't found a solution for this.
-About heating problem,you might want to try @Shivam Kuchhal 's kernel.He reported that his phone doesn't get heat up more than normal.
-About volume during call,it's been solved partially in newer releases by editing snd_soc_msm file.However,if the value is too high,the phne volume will also be too high and the speaker will produce distorsioned sound.However,I see they found a resonable value and both,the volume during call & speaker is about fine.
-For headset buttons not working,you must edit Generic.kl file.Here's a short tutorial to help you:
Go to: system/usr/keylayout/Generic.kl and change as below
key 226 HEADSETHOOK
key 256 BUTTON_1
change to
key 226 BUTTON_1
key 256 HEADSETHOOK
STOCK FIXES:
-For proximity sensor and weird freezes during a call use this tutorial .Haven't tested it personally,but people reported it works even on latest .17 fw.
-For Mac issue [ works for cm11 as well ]
1)Restore original MAC Address
Open /data/etc/wlan_macaddr0
Copy it's content. Ex: 01:12:13:14:15:16
Open /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Find this line
Code:
Intf0MacAddress=000AF58989FF
Replace 000AF58989FF with the content of wlan_macaddr0, but write back to front. Ex: from 01:12:13:14:15:16, write to 161514131201. So it will look like this
Code:
Intf0MacAddress=161514131201
Save & Exit, Reboot the phone
That's all for now,continue to post bugs&fixes and most important:
HELP EACHOTHER
Marius Cristian said:
The point of the topic:
Post your issues found in STOCK / CM11 or post a solution.Simple as that,very productive.
I'll start with a list of bugs:
Click to expand...
Click to collapse
Proximity fix not working!!!
More Kitkat Bugs List:-
1. Headset buttons
2. Camera experiencing crashes randomly, sometimes cause overexposure and being unstable at flash mode
3. Black graphical glitch/scanning effect first time after you turn your screen off then on again after first restart/turning on phone.
4. Call bugs(e.g. distortion etc.)
5. Lag when using the video camera
6. battery draining faster then on stock rom. (was improved on early nightly releases....now its back again)
7. GPS not working again (for some it does...others it doesnt....again...wasnt there on first nightlies)(Mostly Happens In CM11)
8. Camera quality is much,much worse then on stock rom
9 . Phone may left hanging and screen wont turn on for several seconds...
10. Some apps are unsupported on playstore...
CM11 bugs
CM11:
1. Switch to HDR mode and within 3 snaps camera app will FC.
2. Headset buttons.. I have to manually edit that Generic.kl after every nightly update.
3. As mentioned above, graphical glitch after updates.
Some of bugs that u mentioned @David pro has been fixed by users, but device maintainer didn't merged it for some reason in official builds. So, get started:
1. These buttons can be fixed, someone(I don't remember who, Sorry) has created a modified Generic.kl. You can find that file somewhere on this forum.
2. Camera quality is medium, but videos are very poor..
3. Still exist
4. @up
5. As I said, videos are bad
6. Caused by Google Play Services, 1st method is use xposed Framework and one of its add-ons, 2nd is just disable Services from Settings>Apps(i'm using second one, because I just don't like Xposed)
7.GPS is working fine, at least for me. No fix needed
8.Yep, on stock it is better.
9.It's caused by "Black graphical glitch/scanning effect first time after you turn your screen off then on again after first restart/turning on phone."
10.Well, some of them are only for one platform or type of devices,eg. Tegra 4 games.
No heating issues noticed so far(I use my kernel obviously) and yeah the camera and video quality isn't anything worth praising. Also the hwcomposer issue happens only one time after every boot, after that its all fine.
I normally use AOSPA.
Actually,I think the cm11 camera takes better photos than stock,but it can be buggy sometimes :silly:
About GPS,it's working fine for me too.
About video camera being laggy...I think it's because our phone lacks drivers update.It's hard to believe the video camera will ever be 100% fixed.
I'm sorry I'm kinda busy those days and I don't have time to administrate this thread.I'll edit the main post as soon as I can with solution you guys posted.But it's true,there are things which can't be fixed.Until I come back, HELP EACHOTHER
an another bug with stock rom is that "camera not available "or the camera takes a long time to recover after taking a shot
chrome browser restarts the phone or makes the phone to hang
vishalaestro said:
an another bug with stock rom is that "camera not available "or the camera takes a long time to recover after taking a shot
chrome browser restarts the phone or makes the phone to hang
Click to expand...
Click to collapse
Haven't experienced those kind of issues when I used stock.Try to do a factory reset or flash the ftf again.Maybe you added some mods or apps which affected the system.
Overall,we have to admit that CM11 is blazing fast and that's why I'm still using it.I'll update the OP now with your solutions.Thanks guys and keep helping eachother.
Marius Cristian said:
Haven't experienced those kind of issues when I used stock.Try to do a factory reset or flash the ftf again.Maybe you added some mods or apps which affected the system.
Overall,we have to admit that CM11 is blazing fast and that's why I'm still using it.I'll update the OP now with your solutions.Thanks guys and keep helping eachother.
Click to expand...
Click to collapse
another BUG with the stock ROM
1)walkman app flickers in the widget lockscreen
2)poor memory management need to restart the phone daily else the phone lags like a hell
3)camera app didn't respond ,it doesn't even the focus sometimes ,clearing the app data solves this problem temporarily and i think it was not present with the .12 update ,so if anybody could extract the camera app from the .12 update similar to the phone app freeze issue the problem might be solved.
3)walkman app or any other music player makes music to stutter when the same song is played more than one time provided if the songs are stored in memory card also i know that my sdcard doesn't have any problem because it worked fine with galaxy s3.my sd card is sandisk ultra class 10 32 gb
4)battery drain heavy when wifi is switched on compared to previous android 4.1.2
note:i have not rooted my phone or modded my firmware .all i run is the apps taken from the playstore.i have done a factory reset for more than 4 times.
CM11 / Stock (using custom kernel) bug:
Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
Solution:
Restore original MAC Address
Open /data/etc/wlan_macaddr0
Copy it's content. Ex: 01:12:13:14:15:16
Open /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Find this line
Code:
Intf0MacAddress=000AF58989FF
Replace 000AF58989FF with the content of wlan_macaddr0, but write back to front. Ex: from 01:12:13:14:15:16, write to 161514131201. So it will look like this
Code:
Intf0MacAddress=161514131201
Save & Exit, Reboot the phone
solution for Play Services battery drain in CM11
CM11 issues
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
chinmay1234 said:
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
Click to expand...
Click to collapse
Nfc icon not in statusbar is on all cyanogenmod/aosp based rom
chinmay1234 said:
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
Click to expand...
Click to collapse
1. For many people works,for some don't.I don't understand how's possible...
2.Haven't tested it...for me it's a useless feature.
4.Well,crashes happens.However,they're not too frequent.
5.I really like the photos cm11 takes.About video...another story.Try to notice the details in the photos in comparison with stock.
I am going back to stock in order to see if I can obtain(with all the bug fixes from here) a more stable software than cm11.I'll report to you soon guys.Until then, help eachother
@underd0g
Nice fix for WiFi-Mac interference problem. :good:
Marius Cristian said:
1. For many people works,for some don't.I don't understand how's possible...
2.Haven't tested it...for me it's a useless feature.
4.Well,crashes happens.However,they're not too frequent.
5.I really like the photos cm11 takes.About video...another story.Try to notice the details in the photos in comparison with stock.
I am going back to stock in order to see if I can obtain(with all the bug fixes from here) a more stable software than cm11.I'll report to you soon guys.Until then, help eachother
Click to expand...
Click to collapse
guys please try to solve the issues with stock ROM because they are the stable ones and the bugs are easily repairable if the bugs are reached to right hands.so pls first concentrate on stock ROM
I've been playing around with 4.4 video recording..what i think is the lags occurs when we record in low lights related with the kernel..i'm testing with snapcam as its has auto flash when recording in low lights..First result is same as stock..but in snapcam it has touch to focus when recording..after touch,the recording will get a bit darker when it refocus and walla..no lags..
What i found is, the camera will automatically reduced the exposure to -1 for avoiding the lags even it is on default setting..
When moving the camera in low lights,the recording will lags again after few second..that is with continuous focus..set to normal or auto..no lags..so our stock cam using continuous focus for recording..
Back to the kernel thing..from what i see from the recording is same like this when i'm playing with cnt rom to to get wifi and overclock working.
Ok,so I went back to stock.I'm amazed by the battery life,it lasted 2 days and I used the phone a lot ( especially for calls ).
However,after using the fix for freezes during call and so on,I still have experienced this morning an issue.While I was talking to someone,someone else called and the phone was beeping but the screen was frozen.I had to press the power button to lock the device then unlock it to get the screen to show who's calling and to give me the possibility to answer the call.What do you think I should do?For now I'll wipe phone app data,but I'm also waiting if someone knows a good,another solution to post.
Anyone know a way to remove the automatic shutdown?
My phone shuts down if it reaches 25%
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
pesche80 said:
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
pesche80 said:
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Click to expand...
Click to collapse
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Click to expand...
Click to collapse
Thanks!
I'm going to consider a new display... but not a new gf
pesche80 said:
Thanks!
I'm going to consider a new display... but not a new gf
Click to expand...
Click to collapse
Don't forget to invite me to your wedding.