Related
Obsolete
This workaround was only relevant some time ago while custom kernels did not yet have updated sources from Samsung to work on 4.0.4 ROMs. This is no longer the case so this info is completely irrelevant now.
There are plenty of people complaining about camera and video playback problems when using custom kernels on the newest 4.0.4 builds such as XXLQ5 or XWLPM .
I tried a few things and managed to find a fix for it.
Installation
Just take the CWM zip file and apply it on your ROM. It will leave a backup of the 2 files that will be replaced.
Removal
The Restore zip can be "installed" to remove the patched files and put back the original ones that were kept on your device.
Tested and working both for Camera preview and Video playback, on XWLPM.
Note: This is a temporary fix until the kernel devs have enough information to properly update their code, and when that happens this fix can be uninstalled.
Heyy Tungstwenty, another great fix by you!
Well done, it works great! Now also videoplayback works fine with siya on 4.0.4!
Now the only thing left not working on 4.0.4 with Siya is the bluetooth...
Thanks again!
he he he go 4.04 gooo!
Thanks man.
Hi @Tungstwenty
Time to go OUT of stock Kernel XWLPM and move to Siyha Kernel, thanks a lot my friend...
Cheers
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
EDIT: SOLVED by doing a wipe.
It must have been some old data from the nandroid data backup I restored.
Normally I don't post stuff like this if I'm not completely sure.
But the strange part of this story remains that I did had the above issues with one kernel and not with the other.
So I guessed it was kernel related.
This turned out to be a false conclusion.
Thanks for the tips!
The Undertakerr said:
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
Click to expand...
Click to collapse
I actually had that happen to me when i was on Neat Rom. Don't know what caused it but I ended up switching roms.
The Undertakerr said:
Thanks again for the fix.
But I found a mayor problem with custom 4.0.3 kernels on 4.0.4 firmware.
This bug is, to my opinion, so big, it's not worth anymore to use a custom 4.0.3kernel on 4.0.4...
I tested this with all Siya kernels 3.3.2 and above.
Try this to reproduce this bug:
1)Put on your wifi
2) Reboot your device with wifi on.
3) Go to: settings-display-brighteness/ Try to change a value, and see if it sticks.
It doesn't. For example: I had it on autobrightness. Can't get it off autobrighteness anymore, with wifi turned on.
But it is not only brighteness settings. Other settings cannot be made also with wifi on. For example put lockscreentext on your lockscreen. You can't; it doesn't show on the lockscreen. And probably many other settings have the same problem..
When I turn off wifi, and reboot, all off a sudden I can make the changes, and they stick.
Then i flashed CFroot 4.0.4 kernel. Now I can make changes with wifi on...
Can anybody try and see if they can reproduce this issue?
Thanks in advance...
EDIT: SOLVED by doing a wipe.
It must have been some old data from the nandroid data backup I restored.
Normally I don't post stuff like this if I'm not completely sure.
But the strange part of this story remains that I did had the above issues with one kernel and not with the other.
So I guessed it was kernel related.
This turned out to be a false conclusion.
Click to expand...
Click to collapse
Just did the test now and when I was about to post the results I saw your edit
I'm using 3.3.3d XWLPG and installed a minimal deodexed XWLPM as a secondary ROM to work on this fix.
I did the steps you mentioned (for brightness level and for lockscreen owner info) and didn't manage to find any problems, so I'm glad it now works for you as well.
BTW, was it a full wipe or wipe cache/dalvik?
Tungstwenty said:
Just did the test now and when I was about to post the results I saw your edit
I'm using 3.3.3d XWLPG and installed a minimal deodexed XWLPM as a secondary ROM to work on this fix.
I did the steps you mentioned (for brightness level and for lockscreen owner info) and didn't manage to find any problems, so I'm glad it now works for you as well.
BTW, was it a full wipe or wipe cache/dalvik?
Click to expand...
Click to collapse
I'm getting offtopic here, because it has nothing to do with your camera fix
But I'm still investigating the matter now as we speak.
When on Siya, only a full wipe solves the problem I have above.
Because I'm curious(And lazy), I restored my Nandroid Data backup again(XWLPG nandroid with Siya 3.3.2) I only restore data.
Then I have the above problem again.
Now the strange part: Also Dorimanxx Kernel solves my problem.
So this thing I have, seems to be contained to SIYA kernel.
When I flash back to Siya, I have the problem again.(All new Siya versions tested)
Flashing then to any other Kernel, problem solved again.
But Siya can't be the problem also, because when I fully wipe also Siya will work.
I'm going further back to an older Siya to try if it makes any difference, but I think this will become one of the "android secrets" I will never find the cause of...
Sorry for the offtopic.
The Undertakerr said:
I'm getting offtopic here, because it has nothing to do with your camera fix
But I'm still investigating the matter now as we speak.
When on Siya, only a full wipe solves the problem I have above.
Because I'm curious(And lazy), I restored my Nandroid Data backup again(XWLPG nandroid with Siya 3.3.2) I only restore data.
Then I have the above problem again.
Now the strange part: Also Dorimanxx Kernel solves my problem.
So this thing I have, seems to be contained to SIYA kernel.
When I flash back to Siya, I have the problem again.(All new Siya versions tested)
Flashing then to any other Kernel, problem solved again.
But Siya can't be the problem also, because when I fully wipe also Siya will work.
I'm going further back to an older Siya to try if it makes any difference, but I think this will become one of the "android secrets" I will never find the cause of...
Sorry for the offtopic.
Click to expand...
Click to collapse
I don't think it's offtopic
This is indeed very strange, but here's a possible explanation:
The custom kernels (Siyah, Dorimanxx, ...) each have their own tweaks; they're not exactly the same. While they might share lots of common changes and improvements, they do have different things hence the word "custom".
There's a possibility that the sequence of events to make the camera work is contained not only on the binaries (the ones in the zip file I posted), but also on some cached data that was already picked up when you first ran the camera app, which invoked a service, which in turn invoked a library, etc. Later, when reopening the camera, now with the "fixed" binaries, there might still be bad data that a particular kernel is not expecting. Even if you came from Siyah when initially running the camera app, the original libraries might have cached strange data that the kernel will no longer recognize even after the binaries are now in line with the kernel. And another kernel might have code that is lenient enough to still work with it.
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Tungstwenty said:
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Click to expand...
Click to collapse
thanks a lot for the camera fix now I can use official 4.0.4 more often with my favourite kernel - Siyah
Tungstwenty said:
There are plenty of people complaining about camera and video playback problems when using custom kernels on the newest 4.0.4 builds such as XXLQ5 or XWLPM .
I tried a few things and managed to find a fix
Click to expand...
Click to collapse
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Sent from my GT-I9100 using xda app-developers app
cdaarif said:
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Click to expand...
Click to collapse
I have worked on this fix using XWLPM as a secondary ROM (I'm still on XWLPG) but this should work both for LPM and LQ5.
cdaarif said:
Hay man tnx. Im trying to fix my LQ5 with siyah 3.3.3d kernel.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.
Sent from my GT-I9100 using xda app-developers app
Tungstwenty said:
I have been fiddling with the bluetooth part to try to make it work, and this was exactly one of my steps. Whenever attempting code changes, I wiped all the data to make sure the device is starting fresh and if it doesn't work, it isn't due to bad starting data but only the code.
Unfortunately, none of the several things I tried worked and I don't think it's very likely I'll find a solution for bluetooth.
Click to expand...
Click to collapse
cdaarif said:
Man Bluetooth don't work my LQ5 with siyah 3.3.3d kernel. Plz work n fix this.
Click to expand...
Click to collapse
This is just a fix for Camera + Video. I know bluetooth is also not working but as I posted before, I tried to fix it as well but don't think it's doable without changing the kernels. Kernel devs will have to find a way to fix it.
Working bluetooth on LPM with stock Kernel and camera with your hack.
marbutina said:
Working bluetooth on LPM with stock Kernel and camera with your hack.
Click to expand...
Click to collapse
If you're using stock kernel you can (should) uninstall my camera/video hack. It's only needed for custom kernels.
Thanks.
In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms
It seems to be a kernel issue like Tungstwenty said earlier
hardcore said:
Well whaddaya know...
K3-9:
- Bluetooth now works for 4.0.4 ROMS
Click to expand...
Click to collapse
maybe his fix will work for S2 4.0.4 roms too
link to his site/news article
link to the newest hardcore note kernel source code
Krendelrus said:
In the Galaxy Note forums it appears that hardcore has fixed the bluetooth in 4.0.4 sammy roms
It seems to be a kernel issue like Tungstwenty said earlier
maybe his fix will work for S2 4.0.4 roms too
link to his site/news article
link to the newest hardcore note kernel source code
Click to expand...
Click to collapse
Thanks for the above info!
Best to repeat this message in the Siya thread, and/or send Gokhanmoral this info by PM. He might be able to use Hardcore's sources to fix bluetooth in Siya kernel...
Edit: I see you allready did that. Thanks again! Maybe soon we can have working bluetooth with a custom kernel, that would be great!
**Symptom**
Loosing GPS fix on I9300 after 20sec-20mins on latest XXELK4 / Omega v33.1+v33.2 ROM mainly in case of 1st lock on more then >10 satellites.
**Possible solution**
Flash in CWM this one for fixing the GPS issue on Omega v33.2 (tested on 33.1 and was working).
**How it's done**
I simply took all related GPS files from previous Omega version where GPS was working fine and replaced them.
**How to install**
Simply via CWM and perform eventually permission fix after (just for case)
**Result**
Before I was loosing all GPS satellites in 20-30sec, now it looks stable, locking up to 15(17max) satellites
**Which solution I tried before and didn't help**
FasterGPS, setting the parameters
Reflashing Omega on Omega (noWipe)
Reseting aGPS data, downloading new one
Installing another modem, now I'm on I9300DDDLJ1
Turning off GPS, Google location, location via Wifi, rebooting phone and re-enabling again.
Wiping cache + Dalvik-cache + Fixing permissions (after this step I had to reflash no-Wipe the ROM)
Flashing another kernels - stock, GalaxiSih, now I'm on Boeffla-Kernel
**Warning**
Be sure you have nandroid backup and/or reflash no-wipe in case of troubles (wasn't however observing any issues by myself so far).
**Where you can use it ?**
Tested so far on Omega v33.1, confirmed working on Omega v33.2 as well including some other XXELK4 stock/custom based ROMs
Not needed for Omega >=v33.3 or patched stock ROM XXELK4
**Just press THANKS if it worked**
Thanks to Omegas Team.
All you need to do to fix is flash a different kernel
Kickasskev said:
All you need to do to fix is flash a different kernel
Click to expand...
Click to collapse
Incorrect. Lots of people running 4.1.2 on various kernels and still facing the same problem. Myself included having tried 3 different kernels.
Sent from my GT-I9300 using xda app-developers app
Kickasskev said:
All you need to do to fix is flash a different kernel
Click to expand...
Click to collapse
Not helping. Already tried. This is nearly annoying like the hello hello bug. Not all got it and every phone needs a different fix.
Edit: Tried the fix before and don't work for me. Can't get no fix after flashing but it could also related that I got a custom kernel installed. You say you on custom kernel too. Did you flashed the video fix?
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member
Chris_84 said:
Edit: Tried the fix before and don't work for me. Can't get no fix after flashing but it could also related that I got a custom kernel installed. You say you on custom kernel too. Did you flashed the video fix?
Click to expand...
Click to collapse
No, just Omega, custom Kernel and then this simple fix. Wait for the 1st fix, also be connected to data/Wifi. Best for testing is GPS test.
*sorry* I just flashed also another modem just prior to that fix, see 1st post...however when I flashed different modem before I was trying to fix GPS issue, it didn't help at all
shaarky said:
No, just Omega, custom Kernel and then this simple fix. Wait for the 1st fix, also be connected to data/Wifi. Best for testing is GPS test.
Click to expand...
Click to collapse
Don't know for sure but think maybe the video fix who install the old libs brake GPS again but I'm not sure. As I wrote in omega thread. After dirty flash it works perfect even with custom kernel and after installing the video fix it brake down again.
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member
It's working so far.
I haven't flashed fix video but installed siyah so sooner or later I'll need the video fix.
I'll let you know how it goes.
Sent from my GT-I9300 using xda app-developers app
shaarky said:
**Symptom**
Loosing GPS fix on I9300 after 20sec-20mins on latest XXELK4 / Omega v33.x ROM mainly in case of 1st lock on more then >10 satellites.
**Possible solution**
Flash in CWM this one for fixing the GPS issue on Omega v33.2 (tested on 33.1 and was working).
**How it's done**
I simply took all related GPS files from previous Omega version where GPS was working fine and replaced them.
**How to install**
Simply via CWM and perform eventually permission fix after (just for case)
**Result**
Before I was loosing all GPS satellites in 20-30sec, now it looks stable, locking up to 15(17max) satellites
**Which solution I tried before and didn't help**
FasterGPS, setting the parameters
Reflashing Omega on Omega (noWipe)
Reseting aGPS data, downloading new one
Installing another modem, now I'm on I9300DDDLJ1
Turning off GPS, Google location, location via Wifi, rebooting phone and re-enabling again.
Wiping cache + Dalvik-cache + Fixing permissions (after this step I had to reflash no-Wipe the ROM)
Flashing another kernels - stock, GalaxiSih, now I'm on Boeffla-Kernel
**Warning**
Be sure you have nandroid backup and/or reflash no-wipe in case of troubles (wasn't however observing any issues by myself so far). Tested so far on Omega v33.1 only, but should work on v33.2 as well including some other XXELK4 stock based ROMs
**Report and let others know if this helps or not and/or press THANKS**
Thanks to Omegas Team.
Click to expand...
Click to collapse
Tried all what you have said you had tried and also no luck - still having GPS problems.
Installed the fix.
Before installation, using Waze, I used to get a fix within 5 seconds, and then I used to lose the signal after 3-5 Mins. max.
After installation - got a fix same within ~5 secs, and I kept it on for about 10 mins and I had no signal loss.
I will try it further on my way home (about 20-30 min drive) and post results.
Thanks alot - hope this might just do it!
***EDIT***
Drove 20-25 mins home - all working fine.
Will do more testing tomorrow, but looks like this is the fix, for me anyhow.
Big thanks!
Work for me.
This fix work for me. Test during 40 min of navigation .I´m on Omega 33.1 with video fix and Kernel Perseus 26.1
Will test again on the end of the day.
is the "use wireless network" is turn on on your rom??
or turn off??
not working for me on omega 33.2 + stock kernel
liad1981 said:
is the "use wireless network" is turn on on your rom??
or turn off??
Click to expand...
Click to collapse
Is ON
Sent from my GT-I9300 using Tapatalk 2
Small report:
Today morning I use GPS (Waze and Be On Road) to navigate to my work (15km).
Lost signal every 3 - 5 minutes. Strange.
In my work I flash your fix.
Navigate (Be On Road) approximately 15km to customer and 15km to work. Working absolutely good.
Thank you.
I will test later much more and report again.
Update1: On the way home from work gps navigation (Be On Road) work like a charm. I am lucky
Update2: Today on way from home to work, working very well. Thank you. Now I vote for YES
Hi my friend. But suddenly your fix work here. Did another full wipe. Installed my usual stuff and got no fix. Then I thought I try again your zip and it works for now. Will test how long but really hope that's it.
Sent from my GT-I9300 using xda premium
i installed 33.2 with no wipe on 33.1 and i had the gps problem.
it found the first fix but after 2-3 minutes the fix isnt possible.
i did a first check with your fix and it seems to work now...tomorrow on my way to office i will give it a try
thx
How did I miss this! Going to flash and test on the way to work tomorrow...looks promising!
Sent from my GT-I9300 using Tapatalk 2
Not sure i tried this one, but just flashed it and will try in about 2 hours and will report back.
For me it's working now.. I'm on Omega 33.2 and latest Siyah
tapatalked via SGS3 on OMEGA and Motomoto00
Oke, just had my 25 minutes drive.
Flashed your zip before went on the road, double checked that Use wireless networks was enabled again, this afternoon i disabled it and gps worked again.
And from work to home, not one single drop off gps noticed using Sygic.
Also watched carefully to Sygics speed meter and it was corresponding with the speed i actually drove, not going from 30 to 100 i saw yesterday before gps broke down.
Looks your file did it for me.
Deleted
I just installed the 4.4.2 of AOSP which in theory supports find 7 QHD. There is a bug like in cyanogen mod (i just read that there is), that after unlocking the phone, the screen stays black after turned on. Everything operates in the background, as i hear the unlock and feel vibration if pressing a button.
Is there a solution for that?
I have same issue with CyanogenMod in all versions include M8
some discussion about this problem is here http://forum.xda-developers.com/find-7/find7-development/tutorial-how-to-install-cyanogenmod-t2801982 but I still can't find solution
All the CM11 based ROM has the black screen issue. Only Gummy ROM doesn't at the moment. I'm not discouraging anyone to use CM11, but for now, use Gummy ROM if you really don't want to use ColorOS and also don't want the black screen issue.
Same Issue on PA 4.4.2
hey guys im having the same black screen issue on PA ROM, where can i download that GUMMY ROM?
... it would help if someone could give me a last_kmesg and logcat
ayysir said:
... it would help if someone could give me a last_kmesg and logcat
Click to expand...
Click to collapse
Under the assumption it's not killing ADB, dmesg is what would be needed, not last_kmesg
Gummy rom does not have this issue.
Sebring5 said:
Gummy rom does not have this issue.
Click to expand...
Click to collapse
thats swell
Entropy512 said:
Under the assumption it's not killing ADB, dmesg is what would be needed, not last_kmesg
Click to expand...
Click to collapse
my mistake
dmesg: http://pastebin.com/XVEszqrJ
logcat: http://pastebin.com/SDH7FXQv
I think it has something to do with thermal throttle and screen dim.
This logs are from CM.
rroohh93 said:
hey guys im having the same black screen issue on PA ROM, where can i download that GUMMY ROM?
Click to expand...
Click to collapse
http://www.oppoforums.com/threads/rom-aosp-find7a-find7-team-gummy-rom.15593/
Problem Fixed!
mestermagyar said:
I just installed the 4.4.2 of AOSP which in theory supports find 7 QHD. There is a bug like in cyanogen mod (i just read that there is), that after unlocking the phone, the screen stays black after turned on. Everything operates in the background, as i hear the unlock and feel vibration if pressing a button.
Is there a solution for that?
Click to expand...
Click to collapse
So CM pushed some fixes to address this black screen issue, a friend of mine already compiled them into a kernel, this kernel is compatible with any CM based ROM like PA or Cyanogen.
Just flash it and goodbye to black screen issue.
http: // aospal.hostingsharedbox. com/ayysir/find7/ kernel/ParanoidAndroid-find7-kernel-signed. zip
Latest update: 2016-10-27 To view a changelog, you can visit http://www.cmxlog.com/13/quark/ for a rough idea up to the build date.
Hi all. I was able to compile this stock build of CM 13.0 thanks to the efforts/hard works of Skrilax_CZ, baybutcher27, the folks who created Resurrection Rom Remix, and those over at CyanogenMod. It takes some minor features from Resurrection Rom apparently (i.e. notification light, some tiny performance/battery tweaks, and the ability to install Motorola apps). It is otherwise stock CM 13 and I use this daily. I and the other authors/devs assume no responsibility if you damage your device somehow.
Please don't feel pressured to update any more often than you wish .
Notes:
In order to make my calling work for Verizon, I had to go under Settings->Cellular networks->Preferred network type, and select LTE/CDMA (not LTE/GSM/UMTS). I assume GSM users should be fine with the defaults.
My recommendations to install:
Install TWRP 3.0.2 if you haven't already: http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
Perform a backup of your current system/ROM (not really needed if just flashing a newer version).
Perform a factory reset/wipe (if coming from another ROM). If not coming from another ROM, still safest to do a dalvik/art cache reset.
Install the .zip
Install the appropriate google apps (http://opengapps.org/ , ARM, 6.0). I would think nano or micro is best.
(Optional) Install a custom kernel. The best at the time of this writing are at:
http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526 (CM-NX-RR-M builds for Marshmallow)
The latest is here: https://www.androidfilehost.com/?w=files&flid=50122
Wipe dalvik/art cache if you install another kernel.
Reboot and enjoy
Kernel Adiutor is very good for performance/power saving adjustments:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
If you are using bhb27 kernels, then you should use his version of Kernel Adiutor:
https://www.androidfilehost.com/?w=files&flid=48767
Here is the link to the latest ROM on the hosting website:
[2016-10-27]https://www.androidfilehost.com/?fid=457095661767104611
Previous Builds:
https://www.androidfilehost.com/?w=files&flid=52716&sort_by=date&sort_dir=DESC
I'll be back to post updates fairly regularly (~every 1-2 weeks), but I also work full time in addition to being a Dad (those of you who are know how that is ) and won't really be able to response to PMs very well. The sources I used can be found under the post on XDA here at http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232 (device, vendor, and kernel trees). Thanks and God bless.
I just flash this version and its absolutely amazing.
Good job devs!
Bugs I noticed:
-Settings for LED doesn't work.
-Android Auto says is not a supported device.
-Quick Charge 2.0 doesn't seems to work.
-Phone gets really hot when charging.
-...
I have been tempted to flash this all day, but I love how smooth my phone has been on resurrection remix and I enjoy the extra customizations it has. I'm eagerly awaiting the next resurrection remix build for all the latest git changes
emi.guego said:
Bugs I noticed:
-Settings for LED doesn't work.
-Android Auto says is not a supported device.
-Quick Charge 2.0 doesn't seems to work.
-Phone gets really hot when charging.
-...
Click to expand...
Click to collapse
That's a bummer with some of those bugs. Hopefully those will be taken care of soon and I'll be able to sync and rebuild. Did all of these happen to be with the stock kernel, or did you happen to flash another (like baybutchers)? I've seen a few specific to the tiles, but I dont have an Android Auto system to check against. Also, if they are working (or some) in resurrection then I could possibly try to patch this.
calsurferpunk said:
That's a bummer with some of those bugs. Hopefully those will be taken care of soon and I'll be able to sync and rebuild. Did all of these happen to be with the stock kernel, or did you happen to flash another (like baybutchers)? I've seen a few specific to the tiles, but I dont have an Android Auto system to check against. Also, if they are working (or some) in resurrection then I could possibly try to patch this.
Click to expand...
Click to collapse
I don't know exactly, I installed it by downloading the zip and gapps to my PC and used the ADB sideload, before that I was using the last nightly of CM12.1. I did that and I didn't loose my info (either way I did a TWRP backup of everything, except cache previously), so I think it was the CM kernel. When I installed for the first time CM I flashed also the zip and gapps, if that way the stock kernel is changed with the CM kernel I think I'm using CM kernel.
emi.guego said:
I don't know exactly, I installed it by downloading the zip and gapps to my PC and used the ADB sideload, before that I was using the last nightly of CM12.1. I did that and I didn't loose my info (either way I did a TWRP backup of everything, except cache previously), so I think it was the CM kernel. When I installed for the first time CM I flashed also the zip and gapps, if that way the stock kernel is changed with the CM kernel I think I'm using CM kernel.
Click to expand...
Click to collapse
Yeah that sounds like the stock cm kernel then if you didn't flash anything like that separately. I don't know if it would help, but you could always try the other kernel I posted about and see if Android Auto works (would have to restore your backup if you didn't want to keep it). It just depends how much you care and if it's worth staying with the ROM to you. There's obviously bound to be some bugs, but I enjoy using a lean version of the latest and greatest system. Thanks for the feedback .
Installed it 2h ago, everything is running fine so far.
This is smoother than the old cm and than rr too. I'm impressed!
I'm using Bhb Kernel.
My phone is turbo charging, led is working...
No bugs for me.
Nice job, mate! I'm glad we got a new cyanogenmod that we can have updates. Keep strong!
Enviado de meu Moto MAXX usando Tapatalk
thanks,
hope bat drain @ standby will be best from rom's i tested.
somebody can advice what app use to get best standby time? im using Purify but i think it doesnt help much. also on mostly rom'z even when battery mode is set to eco that doesnt help much
Maro' said:
thanks,
hope bat drain @ standby will be best from rom's i tested.
somebody can advice what app use to get best standby time? im using Purify but i think it doesnt help much. also on mostly rom'z even when battery mode is set to eco that doesnt help much
Click to expand...
Click to collapse
I've just been going under the built in privacy guard and setting advanced permissions to where apps I don't need to start at boot are denied, in addition to also denying a lot of them from being allowed to keep the device awake. I get very little battery drain in standby this way. If the cell signal is too weak though, it's really hard to prevent extra drain as it over compensates to get a good signal.
Updated ROM to CyanogenMod 13 changes as of March 24.
calsurferpunk said:
Updated ROM to changes as of March 24.
Click to expand...
Click to collapse
Changelog?
Debuffer said:
Changelog?
Click to expand...
Click to collapse
It's a little hard to say since there is a lot and I am just syncing to the main CyanogenMod 13 repository. However, this is a good link if you go by the date and something similar (such as the Nexus 6 which shares a lot of hardware).
http://www.cmxlog.com/13/shamu/
This may be a dumb question but does this have VoLTE enabled and working(Verizon user)? Since it is CyanogenMod based I assume not but just waned to ask.
calsurferpunk, can you fix wifi on XT1254 with stock Brasil 1225's 6.0.1 ROM? CM12.1 and CM13 detect Moto Maxx and Droid Turbo radio very good!
*GPS*
working for U guys? For me not (BB kernel, location: Europe)
soccertolive said:
This may be a dumb question but does this have VoLTE enabled and working(Verizon user)? Since it is CyanogenMod based I assume not but just waned to ask.
Click to expand...
Click to collapse
Your assumption is correct. I don't believe this has ever worked with CyanogenMod. I'm on Verizon and haven't seen it.
Maro' said:
*GPS*
working for U guys? For me not (BB kernel, location: Europe)
Click to expand...
Click to collapse
I had this problem on other ROMs as well until I restored the original manufacturer ROM, set GPS to device only, verified it worked, then flashed the new ROM. You might have to do the same here. I believe it's been a long ongoing bug with CyanogenMod (and probably others).
pretty thx for the cm13,did it have ambient display?
I am downloading this at work right now. It is slow and will take me a couple to download.
While it is dl'g, I have a question about wiping. Do I still need to do a factory reset if I am coming from a marshmallow cm13 RR rom?Baybutchers?
Also, I have not been able to get my GPS to work properly. In your post #17, you referred to original manufacturer rom. Where can I get this rom to set the gps? I do have computerfreek's room saved as a backup if I could use it? I don't have easy access to a computer to do a fastboot.
Thx.
Sent from my DROID Turbo using Tapatalk
Wait, ROM was updated to day 24?
LineageOS 14.1 has been started.
https://download.lineageos.org/d2tmo
I'm running latest nightly with no problems so far.
Sent from my SGH-T999 using XDA-Developers Legacy app
Awesome to see this. I'm waiting on a few things to wrap up but will updating my t999 ASAP.
Questions, which exact gapps did you use ? Does lineage have their own forums ?
toro143 said:
Awesome to see this. I'm waiting on a few things to wrap up but will updating my t999 ASAP.
Questions, which exact gapps did you use ? Does lineage have their own forums ?
Click to expand...
Click to collapse
For Gapps: http://opengapps.org/
Lineage OS community: http://lineageos.org/community/
So far I'm loving it! Tried to dirty flash from CM but got an error.
So clean install and so far so good, must play with it some more and feels familiar
Thanks!
Camera crashes when going to movie mode. Open camera works fine.
Today weekly it's not installed. It gives an error code 7...
This problem was on cm roms before i ran linageos on my t999, usb tethering this service doesnt work when i turn on the wifi but when i restart my device and active it emediatly it works ,is there any solution ???
hi guys, i install this rom in my t999, and now i have a very rare problem ... i can't call, and no show signal ... (look the image), the problem become rare because i can recieve calls (says call from emergency service) and SMS ... i'm looking for this problem in google .. and nothing...
https://drive.google.com/open?id=0BxMZVpOD7gCdeWVEbHJjRlZ4UW8
https://drive.google.com/open?id=0BxMZVpOD7gCdd3FINWdEUUNnSDQ
what modem and nightly?
No sound at all
I recently experienced a problem after using CM 13 for quite a while on my S3 T-999. The phone doesn`t make any sound at all. Neither the speaker nor the microphone. I flashed LineageOS a few days ago but the problem still persists. I also tried Mokee rom but it also couldn`t get rid of this issue. I finally flashed stock rom and the sound is back. I can make calls and use youtube, the audio is just fine on stock rom.
The only problem is jellybean is too slow and battery consuming for my aging S3. Guy do you have any idea how can I make the sound work on this rom ? Any help would be appreciated.
What are the best custom Kernels to go with this ROM ???
is there any news about supporting d2 verisons or say goodbye to this device
hasan.sy said:
is there any news about supporting d2 verisons or say goodbye to this device
Click to expand...
Click to collapse
Support is discontinued.
hudson: Pull d2
* I don't have time to maintain these anymore
Click to expand...
Click to collapse
This device is still Rock solid and it's a shame we don't have support on this device anymore. I understand the developer though and I thank him for all his effort up until now. I hope someone else could continue his work on this great phone
pcaseiro said:
I hope someone else could continue his work on this great phone
Click to expand...
Click to collapse
Mokee rom updated every day. Carbon rom supporting too.
Hey, guys. Autocorrect for me isn't working even though it's on. When I type text in the virtual keyboard, it doesn't correct misspelled words. Any way to fix this?