Hi,
do you have some advice how to fix A6 bug - Slimport is not working after update to latest FW?
I have tested 2 yotaphones with 4.4 and 5.0 androids and no problem, but after upgrade to 6 is not working anymore
(I tryied to reflash FW twice, reset to factory defaults, clean Dalvik cache)
Thx,
M.
They might have dropped support for the hardware. Mirroring still works though and Chromecast more aptly respects mobility.
Related
Hello
I have a Nexus 4 with Paranoid Android 3.69 (the 4.2.2 version), and I'm wondering myself if i can update to PA 3.92 (the 4.3 version) without doing a factory reset. Is it possible?
Thanks s lot :cyclops:
The newest version won't work correctly without a full wipe. You can make it work, but a full wipe is recommended.
Just follow Moles' instructions in the OP.
I've recently moved to a new state and have been having to use my phone's GPS several times a week.
At the time I was using one of the Cyanogenmod 11 snapshot builds(sorry, I can't remember which one ). The GPS worked flawlessly. I would always update to the next snapshot build as they came out. One our two updates later my GPS couldn't seem to get a fix on my location. I tried wiping and doing a clean install of the ROM. Still had issues.
Eventually I got fed up with cyanogenmod and wiped my phone and installed Paranoid Android 4 beta 1. Had the same problem with the GPS. I tried several of the other beta releases as they came out to see if the problem was resolved. It wasn't.
So I restored my phone to stock using the Google factory images (4.4.2). The GPS worked beautifully. So I stuck with stock for a while and did the OTA update to 4.4.3.
After a while I started to miss the features and customizations that come with custom ROMs. So I wiped and flashed Paranoid Android 4.4 RC2. The GPS still can't seem to lock. On the rare occasion that it does it can't keep up with my car, especially if I turn onto another road.
Does anyone know what's up with the GPS? Didn't seen to have this issue at all on Jelly Bean custom ROMs. Is this an issue with Kitkat custom ROMs? Possibly a hardware issue? Any help would greatly appreciated.
Current setup:
Phone: Nexus 4(16gb)
ROM: Paranoid Android 4.4 RC2
Sent from my Nexus 4 using XDA Free mobile app
There appears to be an issue with KitKat and GPS. I'm running stock 4.4.4 and I can't get a GPS lock. I've tried everything I can, including a factory reset. I don't remember having the issue with 4.4.3, but I've seen issues reported going back to 4.4.2.
I don't know about you, but a reboot usually does it for me.
Dear Community,
I hope that this is the right place to post and any of you can help me.
My (aktual) Hardware/Software bits:
Galaxy Note 3 (SM-N9005)
Android: 5.1.1
Baseband-Version: N9005XXUGBOD3
Kernel-Version 3.4.108-f2fs-temasek-cm12.1-hlte-v1.25+
temaseksnappy #1
Temasek unofficial version V16.4
Build: LMY48J test-keys
Recovery: twrp 2.8.7.0-hlte-4.4
My actual problem is the following: My Note 3 by default had a 4.4.2 OFW on it, which I early upgraded to Lolipop 5.0.1. Everything works for the OFW 4.4.2 and 5.0.1 fine. As soon as I try to flash it with a CFW like CM11, CM12, CM12.1, CM12.1 (temaseksnappy), Gummy 4.4.4 I am losing the feature of auto rotation.
Of cource I did a clean flash, wiping DALVIK/CACHE/DATA and system, double time even one befor the flash, one after.
I also tried to put the battery, sim and sd out for few min before rebooting, while autorotation is manualy turned off.
Even a MODEM I flushed to fix this issue, but without success. Nothing helps but going back to OFW.
My last try was downgrading to the original 4.4.2, including baseband trieing from there to go to any CFW (CM11) as well as from OFW 4.4.2 -> OFW 5.0.1 -> CFW 5.1.1 (http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375)
There was also a post about a possible missing or broken lib in /system/lib which I replaced
Nothing helps (libGNU... something). This helped me alreay once in OFW after kicking out all the junk apps, but this is a different storry and not related anyhow.
Is there anybody out there who has the same problem or even better knows a solution?
My shot would be that:
1) CM has a problem with my particular hard-/software (Kernel, Baseband, Recovery, whatever) as I just tied CM or at least CM based CFWs.
PLEASE HELP.
Thank you very much in advance.
After about almost a year I cam back, giving again a try to CM, However I still have the same issue. Finally Anybody please!
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Rosli59564 said:
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Click to expand...
Click to collapse
Hello,
Thx for your reply. Right now I am on CM13 (temasek hlte v9.6)
http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375
This might should be specially compiled for sm-n9005 like mine.
Everything expect rotation works fine. However The accelleration is also working fine as I tested with "sensor test". Even the integrated camera App is rotating, however the rest is not.
In addition I downloaded "adaptive rotationfree", If I set it "stock Auto" nothing happens, but if I set it to "force auto" the rotation will work exacly once and then stops undtil I force it to portrait again.
What do you mean exactly with "touchwiz"? Is this jus a different kernel or a whole CFW?
As I wrote in the frist post I tried already a lot of CFW and ALL had this issue, but the OFW ;(
What shell I flush to get this working, which is not OFW?
BIG THX for YOUR HELP
Touchwizz is the firmware that comes with the stock Samsung firmware .
Also in custom Samsung based roms .
Hello,
thx for the tip with TouchWiz vs aosp. At the moment I am running "DarkLord N5 Release Candidate 2.12" which can get find here: http://forum.xda-developers.com/galaxy-note-3/development/rom-darklord-s6-port-alpha-t3083087
This Rom is TouchWiz Based and guess what ....
Autorotation works.
However I do not understand what the problem realy is and would prefer to run cm13 insteat. I mean even samsung devices got a accellerator within which works also fine with AOSP software, showing numbers moving while turning the phone. In addition for example on the post http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375 it is said that this is explicite for note 3 including the model n9005. So ...
Can anybody point me to the problem or even better to the fix?
Is there any chance CM would fix this?
Regards
Hey,
My 910c is on cm 13 at this time, i tried to install kitkat, lollipop, and now marshmallow through the odin, but always after installation there is a bootloop, even when i wipe the data, cache and do the factory reset. All cyanogenmod based roms works fine, but all samsung based roms are not working. I got also knox 0-1, anybody know how to make that official firmware work?
Hey guys! I'm trying to understand on which stock ROM you have flashed a Nougat custom ROM.
Personally, I'm on the latest RETEU 6.0.1 MPDS24.107-52-5 + January security patch (I don't remember, maybe 107-70) and I run AospExtended 4.3 with Optimus kernel r21.
So... what's your base firmware? Is it all ok?
I am using the combination you read in my signature. I have to disable HW overlays after every restart in order to have full screen video and stock camera working right. Except those, the device is faster and i love it.
melodystyle2003 said:
I am using the combination you read in my signature. I have to disable HW overlays after every restart in order to have full screen video and stock camera working right. Except those, the device is faster and i love it.
Click to expand...
Click to collapse
And what is the stock ROM you have on the base?
Hm, didn't notice that part of your question from my tablet. If it may be of any help, i was using stock mm 6.0.1 but i erased system, data, cache and dalvik (clean installation) prior flasing the AOSiP 6.0.
melodystyle2003 said:
Hm, didn't notice that part of your question from my tablet. If it may be of any help, i was using stock mm 6.0.1 but i erased system, data, cache and dalvik (clean installation) prior flasing the AOSiP 6.0.
Click to expand...
Click to collapse
The latest? And which version? European, Asian...
This one: XT1562_LUX_RETASIA_DS_6.0.1_MPDS24.107-52-5_cid7_subsidy-DEFAULT_CFC (which i used to convert it from single sim to dual sim). There is also a newer one, you can find it here.