I'm having a very strange issue when using ANY CyanogenMod based roms on the D851. It's hard to explain. As soon as the ROM boots, the screen is split vertically right down the middle. One side (right) is lower than the left side of the display. I have experienced this will ALL AOSP roms I have tried. Has anyone seen this? When I flash a stock based ROM, everything works fine and the display isn't split down the middle.
Any help is greatly appreciated.
Same for me, Im not a super user, sometimes I flash a custom rom and that is exactly what happened to my phone, then I have to come back to CloudyG3 or jump to Lollipop
It has to do with the modem. I think if you go back to 10r...or something like, that it will fix it. I am on BlissPop version 4 on the 20E modem. It happens on start up only, all good after boot.
You can flash the newest OTA (Lollipop) and then go back to AOSP. http://forum.xda-developers.com/tmobile-lg-g3/development/rom-sr-remix-kitkat-stable-deodex-t2961412
Hope this helps!
Pretty sure this is a bootloader issue, CM roms on the newest firmware cause this. Flashing the kitkat bootloader solves your issue
Sent from my HTC One M8 using Tapatalk
Related
I've had this problem FAR too long. I'm running a custom ROM but whether i revert to a stock ROM or not, the problem does not go away. Whenever I try to load my camera, the screen just stays black. There is no camera icon for when the app is loading it's just black.
I've had my phone for over a year and i think taking it to sprint is out of the question. I could load a stock ROM to bring it in i just think it's been too long.
I'm using Deck's ICS right now and am aware that the camera doesn't work for the version i am on. I'm flashing to the stock ROM now so that those doubts can be set to rest.
Has anyone experienced this problem and how did they fix it?
dougfalk said:
I've had this problem FAR too long. I'm running a custom ROM but whether i revert to a stock ROM or not, the problem does not go away. Whenever I try to load my camera, the screen just stays black. There is no camera icon for when the app is loading it's just black.
I've had my phone for over a year and i think taking it to sprint is out of the question. I could load a stock ROM to bring it in i just think it's been too long.
I'm using Deck's ICS right now and am aware that the camera doesn't work for the version i am on. I'm flashing to the stock ROM now so that those doubts can be set to rest.
Has anyone experienced this problem and how did they fix it?
Click to expand...
Click to collapse
So i did a full wipe 3 times and put back a stock ROM and it DOES work. The reason i posted was because the problem was becoming progressively worse and the last few ties i put stock on it didn't work. but now perhaps with the three wipes it did! We'll see how long this lasts...
Right now my G2 is running Cyanogenmod-7.1.0 RC1. For the last few months any time I try to update past this version of the rom I lose my microphone. It works absolutely fine with 7.1 but when I go to 7.2 it breaks. For example, When I am on a call I can hear the other person but it is silent on my end. Voice recording programs do not work either, all that it records is a low level of static noise.
I have also tried CM9 and audacity beta4 with the exact same results. When I flash my phone back to 7.1 everything is fine.
Is there some way that I can flash just the old microphone drivers onto the new roms? I am competent enough to follow instructions but not enough to start breaking builds apart for the individual pieces so I don't know where to start.
I have always done a full wipe on everything before I flash.
Does anyone have any ideas? Thank you!
Currently I am running:
Radio: 12.52.60.25U_26.08.04.30_M3
Kernal: [email protected] #1
Mod: Cyanogenmod-7.1.0 RC1 vision
Build number: GRJ22
a
Didn't try any of those,
but this rom:
http://forum.xda-developers.com/showthread.php?t=1492461
works great on my HTC Desire Z with absolutely no issues
It does take a bit of customizing.
I've tried that rom as well but have a whole different issue with that one for some reason. I flash it and then start to reboot and once the phone gets to the white htc screen it freezes with a few horizontal lines running across it. I have to pull the battery and then flash back to my older rom. I have no idea what is going wrong there.
Here might be a dumb question...
Would it help to flash a new kernal? Are the appropriate kernals included in the roms already?
haymaker said:
I've tried that rom as well but have a whole different issue with that one for some reason. I flash it and then start to reboot and once the phone gets to the white htc screen it freezes with a few horizontal lines running across it. I have to pull the battery and then flash back to my older rom. I have no idea what is going wrong there.
Here might be a dumb question...
Would it help to flash a new kernal? Are the appropriate kernals included in the roms already?
Click to expand...
Click to collapse
Hi! Do you solve your problem? I have the same thing there. All the CM roms above 7.0.3 not working with microphone. Do you have still the Cyanogenmod-7.1.0 RC1 file rom and can you upload for me?
Thank you!
Ok so ever since I updated to any of the 4.4.2 rom (i.e. Cm11, Cyanfox, SlimKat and Carbon Rom) my accelerometer won't work correctly.
At first I thought it was a GPS issue but after looking into it more the GPS locks fine. It's only the direct in google maps or any other GPS like app that is messed up. For instance, when I'm using google maps and I'm facing north it will show me facing east, then when I change directions it can't figure out which direction I'm facing and spins around in circles and maps will crash. Same thing happens when I use GPS Status, the app will say I'm facing the wrong direction and when I move direction it starts to spin out of control.
I defiantly don't think its a hardware issue since everything was working fine with the touchwiz rom and 4.3 roms. If anyone has any clue on how to fix this I would greatly appreciate it. This is pretty much the only thing that is wrong for me with any kitkat roms.
I have a tmobile galaxy s3 and current running SlimKat build 3. :crying:
Try FasterFix app
Perseus71 said:
Try FasterFix app
Click to expand...
Click to collapse
I gave it a shot but no luck. I have also used GPS status and FasterGPS but like I said before I don't think its a GPS issue because it does lock on to my location fine. It's just my compass doesn't work correctly.
I believe CM has a Advanced Option to Re-Calibrate Accelarometer. Settings > Advanced is where the option is I think. I use Slim Bean so I don't have CM details.
Oh yeah I forgot about that but it still didn't work. I appreciate all the ideas though.
You may want to go back to Stock and then try. Just to rule out any hardware issues. It will also wipe any corrupt firmware.
Perseus71 said:
You may want to go back to Stock and then try. Just to rule out any hardware issues. It will also wipe any corrupt firmware.
Click to expand...
Click to collapse
Do you mean odin to stock or just flash a stock rom? If it's odin I'll definitely try it when I get home. The thing I find weird is that when I flashed the S3Rx rom, everything was working fine.
I'd do Odin before trying anything else.
So I odin back to stock and like before everything was working properly. Then when I flashed back to carbon rom, is back to pointing in the wrong direction and spinning out of control.
I'm surprised that I'm one of the only if not the only one with this problem. Is there an app that I can manually calibrate which direction I'm pointing?
I'm out of ideas...
Can you flash a different kernel on top of Carbon ?
Perseus71 said:
Can you flash a different kernel on top of Carbon ?
Click to expand...
Click to collapse
I flashed KT kernel, BMS, Harkness and DKP. For a little while it seemed like BMS had fixed it but then went back to the same ol' sad story. :crying:
Try Another Rom please. Not just Carbon. This time try a 4.3 rather than Kitkat.
I have tried other roms and I stated that this didn't happen till I started using Kitkat roms. When I was on carbon 4.3.1 there weren't any problems as well as on S3Rx 4.3 rom. Not sure why this only happens on Kitkat roms and what seems like only to me. I'll continue to look for solutions cause I really like the look and feel of Kitkat.
So after searching and searching I finally found a fix! I was about to give up hope but decided to try one last kernel, Quantum kernel. At first it seemed like it wasn't working but I had to calibrate my accelerometer with GPS Status. After that everything was gravy! I hope this helps others that have the same problem I did!
My touch screen seems to work fine on 4.2.2 (specifically the rom at: http://forum.xda-developers.com/showthread.php?t=2719411) but when I flash a 4.4.2 rom, it does not seem to track my finger well. Half way through a swipe it will just stop reacting to my finger, and no matter how hard I press or move it around it will not detect my finger again until I lift it and place it again.
This is very bothersome as it makes the tablet almost unusable. Any help is very appreciated.
This is ANY 4.4.2, stock based, or AOSP I have tried multiple roms from aosp, and ive tried both the A and B roms at http://forum.xda-developers.com/showthread.php?t=2707363
Update
So I went back to a 10a 4.2.2 base stock. Like usual the touch screen behaved normally here, Then I flashed the latest Mahdi and it once again stopped tracking my finger.
I then flashed the discontinued dyn kernel (gpeish works too) and it started tracking normally. I wanted to use the AIC kernel for AOSP, but unfortunately it does not correct the issue. So what I did was, flash dyn to get it working correctly, then flashed AIC over top of that. It seemed to do the trick. I don't have the issue now. Though I am not sure what this means, or if other people have this problem.
zetorung said:
So I went back to a 10a 4.2.2 base stock. Like usual the touch screen behaved normally here, Then I flashed the latest Mahdi and it once again stopped tracking my finger.
I then flashed the discontinued dyn kernel (gpeish works too) and it started tracking normally. I wanted to use the AIC kernel for AOSP, but unfortunately it does not correct the issue. So what I did was, flash dyn to get it working correctly, then flashed AIC over top of that. It seemed to do the trick. I don't have the issue now. Though I am not sure what this means, or if other people have this problem.
Click to expand...
Click to collapse
Thank you so much, I thought that I got a defective PAD, I have
I know that this is a veeery old post, so to clarify and be sure about what you did
Flashed stock 10a 4.2.2
Flashed DYN Kernel
Flashed AIC
Have you figured out any way to resolve the issue with 4.4.2?
thank you
Orochikun said:
Thank you so much, I thought that I got a defective PAD, I have
I know that this is a veeery old post, so to clarify and be sure about what you did
Flashed stock 10a 4.2.2
Flashed DYN Kernel
Flashed AIC
Have you figured out any way to resolve the issue with 4.4.2?
thank you
Click to expand...
Click to collapse
Unfortunately no. I ended up selling it after a year or so to buy a nexus 9. Sorry I cant be of more help.
zetorung said:
Unfortunately no. I ended up selling it after a year or so to buy a nexus 9. Sorry I cant be of more help.
Click to expand...
Click to collapse
Thank you for the reply
Well I just keep flashing till it works like it should lol
I have the same issue ! For a moment there I thought the G Pad had a non-sensitive area like the iPads have xD
The strange thing is, this problem also appears on Lollipop roms...
Is there any solution available? Still having this issue with AOSP 6...
Someone showed me the thread with the 12.1 cm rom and the .img for the recovery is it okay if I use flashify to put the recovery on my phone instead of using odin after rooting? Or does someone have a .tar recovery for the L520 in a drop box somewhere? also do I need to update my firmware before flashing a rom? I think I'm on firmware na7 on 4.2.2
it's fine, trust me use flashify. Odin doesn't flash .img files. No, you don't need to update your firmware, it's going to be flashed over anyways.
Seemed to work fine. That cm 12.1 rom still working okay for you?
There's a few little annoyances but it's working okay otherwise. I get an exclamation point by my bars sometimes and have to reset the apn to fix it. GPS has some issues so it's become more a roadmap than actual guidance and I can't send mms but that's not really an issue as I have unlimited data and can just facebook messenger as a workaround. I hope that these issues get fixed but I understand that alot of 5.1 roms have issues with the exclamation point thing and even some unrooted 5.1 phones have the problem. It would be nice to see a fix for these issues but I don't see anyone making any more roms for this phone and the guy that made this rom seems to have landed a job with cyanogenmod and is too busy to update this rom. What a shame but at least I have 5.1 now.
Hmm I suppose I'll stay at 4.2.2 till I feel like flashing 12.1 thanks for all the info. You don't have any overheating issues or random restarts right? Also how does the GPS not work well?
No overheating or random restarts. All things considered its a pretty smooth rom if just a little incomplete. I only tried using the GPS once and it came up with my location and the route for where I needed to go but when i was driving along the GLS was not updating my location. It may have been just a one time thing, idk, I havent needed to use GPS since.
Cool do you know a way to go back to stock if I don't like the cm 12.1 rom?