Hi All, am a new member to this website. I've been reading all the threads related to my device (Xperia Ion Lt28h) and actually installed a custom ROM for the same for the first time. The ROM i chose was http://forum.xda-developers.com/showthread.php?t=2616450. It is actually cool to use. I have the kitkat feel in my phone but lately I've been experiencing some issues with the ROM. I tried to reply in the same thread but the usual 'New members with less than 10 posts' thing popped up. So i couldn't find any other way to ask someone regarding the issues that am facing. As am new to this , i may know how to contact someone or how to post it in a efficient way, if there are some, please let me know. If not, the below are the problems am facing and am seeking all the seniors help to solve it.
1) Sometimes, when am getting a call, phone rings, vibrates but the screen is still in standby mode and it takes around 5-10 seconds to see the caller info. This happens in 70% cases.
2) Camera doesn't work properly. In JB holding up and down the volume button zooms the camera but here it is taking picture. Also i searched if there is any option to zoom, i couldn't find it.
3) Some of the applications doesn't work. For Ex, Super beam is not working, as soon as i scan the QR code from other mobile to receive a file, my phone gets hang and gets restarted.
4) HDMI is not working, which was working in JB.
All these are the issues am facing. Please help me.
Related
I have problem with rom cm 7.2. This rom is the best, but i have a problem with display usage battery, i have a 70% usage. Brightness i have a low level and still is this problem, and my battery drain a very fast with using. Help me please
bump
I have the same issue. I found that on stock Rom the main reason of battery drain so fast was dialer, now on cm7 display take about 50%
Try CM9... battery works for up to 2 days at normal use... Instead of the lopusy 12 hours on stock and cm7...
on cm9 i have this same
Since I am not allowed to post in development section (new user, 10 posts rule) this thread title is the closest one to my questions. I am currently on latest CM7 rom (thanks adlx.xda) and I am facing some issues.
First of all, the rom itself is great. It would be nice to update it with the latest sources. I tried all versions and in the last one there is a huge scrolling lag that was not present in the previous versions (one can see this in browser, opera mini etc. when scrolling down or up with physical keys). I think it has something to do with framework, but not sure. I ported another CM7 rom from various different phones, using adlx's as a base, and those didn't have that lag, but I couldn't remove the default on-screen keyboard because when I remove it the sym key when pressed keeps popping up to select input method.
Speaking of keyboard, when I use browser or any other browser (except opera) the key "enter" will not open the selected link. It will do nothing. This is only on CM7 and SuperOSR. It is working properly on stock, CM9 and CM10. This is very much needed since sometimes I am having trouble opening a link with my big fingers so I use the arrows to select a link and enter to open a link. I have tried to play with the keypad files but without much success.
The last issue I was having has something to do with the camera. I don't care about the front cam, I believe 90% of us doesn't care about it as well. But I was having issues with flash. It is out of sync most of the times. It works, but it is not in sync with the actual moment of taking the pictures so most of the times my pictures are dark and sometimes not visible at all. But I can live with that, just wanted to point it out.
Adlx, I hope you read the general section, and I would really appreciate if you could give me some pointers about keypad files and why enter button when I try to open a link with it is not working only in those two roms.
Best regards.
S
Little bump. Still need 2 more posts
Received this phone (THL W8S) 5 days ago, and straight out of the box it has had a serious issue where the phone will lock up, the screen will fade slowly to black, and then reboot itself. The problem occurs both after factory resetting AND in safe mode.
The phone is unrooted and running the stock ROM.
Basically during use, the screen suddenly becomes unresponsive to touch and the physical buttons (home, volume, power) all stop functioning. As soon as the phone locks up this way, the screen slowly fades to black over about 60 seconds, at which point I have to leave it to fade completely before it reboots itself.
It happens most frequently when using any browser (stock, or otherwise) taking from less than 5 seconds to around 5min before the random lock up occurs) but also happens when scrolling through messages; scrolling through emails in either of the stock apps; using a compass app which came pre-installed (very quickly).
Initially I thought it might have to do with WiFi, but problem also cropped up with WiFi off, using 2/3G. Then in troubleshooting also managed to get it to happen using the camera (lot of motion, and repeatedly taking snaps).
Also odd is that the batteries I received in the box were generic black ones, not the official stamped/logo'ed THL ones I've seen on every website and every unboxing of this particular phone. So while there's a possibility this may be a battery issue, the fact that the phone hasn't done this while using a more battery draining app (Beach Buggy Blitz; Rayman Jungle Run) makes me think this is a deeper hardware fault related to , although I don't know enough about voltages and such to rule it out completely.
I have a couple videos showing the problem, but unfortunately I'm not allowed to put the links here. Should both be easily found by searching:
THL W8S issue Kostas P
if interested.
Any thoughts/views would be greatly appreciated!
kostako said:
Received this phone (THL W8S) 5 days ago, and straight out of the box it has had a serious issue where the phone will lock up, the screen will fade slowly to black, and then reboot itself. The problem occurs both after factory resetting AND in safe mode.
The phone is unrooted and running the stock ROM.
Basically during use, the screen suddenly becomes unresponsive to touch and the physical buttons (home, volume, power) all stop functioning. As soon as the phone locks up this way, the screen slowly fades to black over about 60 seconds, at which point I have to leave it to fade completely before it reboots itself.
It happens most frequently when using any browser (stock, or otherwise) taking from less than 5 seconds to around 5min before the random lock up occurs) but also happens when scrolling through messages; scrolling through emails in either of the stock apps; using a compass app which came pre-installed (very quickly).
Initially I thought it might have to do with WiFi, but problem also cropped up with WiFi off, using 2/3G. Then in troubleshooting also managed to get it to happen using the camera (lot of motion, and repeatedly taking snaps).
Also odd is that the batteries I received in the box were generic black ones, not the official stamped/logo'ed THL ones I've seen on every website and every unboxing of this particular phone. So while there's a possibility this may be a battery issue, the fact that the phone hasn't done this while using a more battery draining app (Beach Buggy Blitz; Rayman Jungle Run) makes me think this is a deeper hardware fault related to , although I don't know enough about voltages and such to rule it out completely.
I have a couple videos showing the problem, but unfortunately I'm not allowed to put the links here. Should both be easily found by searching:
THL W8S issue Kostas P
if interested.
Any thoughts/views would be greatly appreciated!
Click to expand...
Click to collapse
Hi, I also have the same problem described by kostako. Please look for your feedback as soon as possible.
thank you very much
Best regards.
san_tony said:
Hi, I also have the same problem described by kostako. Please look for your feedback as soon as possible.
thank you very much
Best regards.
Click to expand...
Click to collapse
Hello, I wanted to inform you that lately the reboot occur concurrently with application updates.
They are like your impressions.
Best regards
THL W8S the screen fade and reboot too!!
Hello!
I received the phone on 12 September. The screen faded from the first minutes of use. Yesterday I came three times. In "THL mobile store" recommend updating the firmware. But the update I have not found anywhere.
any suggestions
Thank you very much in advance.
[Q&A] [ROM][4.4.x][OFFICIAL & NIGHTLIES][MOTO_MSM8960] MoKee OpenSource Project
Q&A for [ROM][4.4.x][OFFICIAL & NIGHTLIES][MOTO_MSM8960] MoKee OpenSource Project
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][4.4.x][OFFICIAL & NIGHTLIES][MOTO_MSM8960] MoKee OpenSource Project. 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!
After the update jbbl-141 118-release, my CAM died no longer opens.
:crying:
Hi guys.. Anyone knwos if the razr hd support USB otg? I'm on kk jbbl of november.. I tried but it didnt work for me
Sent from my RAZR HD using xda app-developers app
Don't know if this is of use to the DEV but I'm posting anyways for any bugs they may be trying to fix.
Device: Razr Maxx HD
MoKee Version: MK44.4-moto_msm8960-150124-RELEASE
I've run with this ROM now for a few months, mostly because anything is better than running stock. The ROM runs very smoothly, I hardly ever have lag anymore and navigation is a breeze. I really wanted to thank the devs for this. I do however have a few issues that bother me, some more than others.
First off, the lock screen seems to have difficulties unlocking, to the point that I have to make several attempts at unlocking my device as the pattern entry looses touch sensivity or something during entry. This might not be an issue with the ROM itself as stock did this too only way worse and more often. the bigger issue is that at times it even changes the pattern size on me for no reason that I can gather. Like, the pattern entry will become quarter the size of the normal one and turning the screen off then on again doesn't fix it.
Second, back to the screen, there is often some sort of error going on with the notifications that appears on screen. So, I'll have notifications appears that will now and then lap over code entry and get locked in place that a swipe to the side does not fix. This then makes the phone inaccessible because my pattern lock no longer acknowledges my touch as a notification is now taking the space above it. It is not a hard lock of the phone far as I can tell as my device doubles as my main MP3 playback device and the audio continues playing, the volume rocker increases and decreases the volume levels and the power button turns the screen off and then off again. This has also occured when switching to the lock screen camera where the screen gets half way between screens and then locks into place
Third, last time on the screen, I promise. What has happened today and several times prior to today is that sometimes when I lock the device and turn off the screen via the power button I can then not turn the screen back on via said power button. So today I had this happen while playing music and just like the issue above I could once again control volume but my screen whould not turn on unless I did a full reset via power/vol down. Funny thing is that the snap shot notification goes off when doing this but the screen doesn't come back.
I do use the music control lock screen features off PowerAMP on my pattern screen but I had never experience issues like the above three on stock.
Forth, my GPS is now useless. Though I have an Otterbox Commuter Series case, I have a hard time believing this at fault for absoulutly no ability at using GPS. In my profession I act as a service tech some weeks and may in fact need to be dispatched out to a site I may have never been to before. The GPS on my phone is a life saver as I'm a horrible driver and get lost often, I tend to stay in a lot. Anyways, I tried using it my last service call for Google Maps and though it found where I was, it was unable to give me instructions on the way to the site as it kept claiming the GPS signal was lost. It did provide turn-by-turn instructions which helped but made my journey that mach more difficult. Maybe an app issue but I had my mobile and GPS on pluse setting my options between battery and high accuracy to no avail.
WCDMA stopped working
Since I installed this rom my 3G (WCDMA) signal stopped working. Could anyone help me fix this?
Hello dear members. I have spent at least 3 hours of googling for proper solution just for turn off vibration but with no luck. It is common software issue 6.0+, that users need to turn off vibration for every app separately but there is no option for that in many apps, like fb, chrome, etc.
Other problem, phone is random rebooting when using stock camera, making call, ending call, switching to air plane mode etc.. I've tried everything, custom kernels, encryption off, custom rom, N preview, now I am back at stock 6.0.1 no root, locked bootloader. I ve tried battery calibration also..
I am so freaking mad at this piece of **** nexus 6! The worst problem is that these problems like top speaker white noise, reboots, speaker buzz, battery drain, etc.. and more problems that my device is not facing are not solved over other threads and forums, people said that they returned back to google and get new one also with same problem. 0% reliable, take urgent picture of smt special or make urgent call.. emergency etc..
Help me or I will break this **** with big hammer.
Hello and thanks for using XDA Assist,
A dedicated forum for your device is located here. You can visit Nexus 6 Q&A, Help & Troubleshooting and ask your questions there, experts for your device should be able to help you there.
Always read carefully before proceeding.
Good luck,
DC07
This is my first time installing custom ROM's on my otherwise stock Sprint Motorola photon 4G LTE. After successfully flashing CM13 (2016_08_20 snapshot release), I tried to make a call, and upon hitting "call" from the dialer, the screen goes black and stays that way. The only recourse is to hold down power button long enough to reboot. While the screen is black, there is no sound from the ear piece (i.e. it does not appear that the call is connected). Finally, while the screen is black, the phone does exhibit some reactions: it vibrates sometimes if I hit the power button, in other words, the device is still 'on" until I have to reboot it.
After this happened, I gave up on CM13 and flashed CM-12 (the latest snapshot release, from 2015) , and experienced the same behavior.
The call apparently was completed, because the other party received a missed call. However, there was no sound on my end (although there was side-tone, when I breathed on it)
I googled for about an hour, and saw examples of the same behavior on other devices claiming to be related to the proximity sensor (though in those cases, there apparently was audio in the ear piece-- ie. the call completed, and was in progress while the screen was black). This behavior was not observed a few minutes before under stock ROM in the same device (so doubt it's a strictly hardware issue, so doubt I need to open the device and clean the sensor, per some of the suggestions out there).
I suspect the answer is very basic, because I found no similar threads searching XDA.
Please let me know any ideas. I did not do anything about updating my baseband version from stock before flashing the CM ROMs., but don't know if I have to I'm a noob at custom Rom's and just remembered that you had to worry about the baseband / radio version back on the HTC Evo 8 years ago, which was my last time flashing. Again, the ROM itself worked fine-- wifi and 3G/LTE connectivity was a success.
Let me know any ideas.
thanks
After restoring to stock, dialing worked again on the phone, but the behavior on the device was different from two other photons I tested next to it.
In the stock ROM, the call connected, but the screen turned off immediately upon hitting "call" (even when the phone was on the desk). You could get the screen back (in stock only) by hitting the power button.
In my other two photons, the black screen does not kick-in immediately. So it does appear it could be something having to do with the proximity sensor (i.e. it's always engaged). I don't have the skills to confirm. I am writing-off this phone for now, and have a different device (so not a high-priority thread at this point), but let me know if anyone has any ideas. Thx.
There's a way to validate if the prox sensor is working - zDeviceTest in the Play Store will test all of the hardware, and it will also show the metrics each piece of hardware is receiving - the prox sensor being fairly simple, it just identifies if an object is "near" or "far".
I always recommend making sure everything works in the stock ROM before flashing anything custom - as you need to validate everything works before making tweaks.
My advice is the same as arrrghhhs. (This name really looks like it was typed with a Photon Q with some characters repeated by the device >.>)
I noticed that my proximity sensor sometimes "stuck" to near (I use some different app [SatStat] so it shows 3 cm or 100 cm instead of near/far). Winking a little above the sensor helps sometimes. But your problem sounds like a defect.