{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi taking this project over from spleef. First build here.
Downloads
Changelog:
10/28
rebase against shel's latest
XDA:DevDB Information
Unofficial Liquid Smooth 4.3, a ROM for the Sprint LG Optimus G
Contributors
neighborhoodhacker, spleef, Shelnutt2
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Based On: Liquid Smooth
Version Information
Status: Stable
Created 2013-10-29
Last Updated 2013-10-29
Thanks for building Liquid! I'm glad to finally have my favorite ROM back on the LGOG, and with 4.3 to boot!
mpbean said:
Thanks for building Liquid! I'm glad to finally have my favorite ROM back on the LGOG, and with 4.3 to boot!
Click to expand...
Click to collapse
can you confirm it's working haven't booted it myself
neighborhoodhacker said:
can you confirm it's working haven't booted it myself
Click to expand...
Click to collapse
Just flashed it.
First attempt - factory reset in TWRP, flashed ROM, booted up, but no data, and got a demigod kernel crash the instant I pulled the notification shade down. Decided to wipe and reflash rather than troubleshoot.
Second attempt - advanced wipe in TWRP (all but the sd), factory reset in TWRP, flashed ROM, booted up and got data right away (including 4G LTE), minor poking around seems to indicate no problems.
Looks good so far! I'll flash gapps and restore my other apps and use it as my daily driver today. If you want me to check on anything specific, let me know.
mpbean said:
Just flashed it.
First attempt - factory reset in TWRP, flashed ROM, booted up, but no data, and got a demigod kernel crash the instant I pulled the notification shade down. Decided to wipe and reflash rather than troubleshoot.
Second attempt - advanced wipe in TWRP (all but the sd), factory reset in TWRP, flashed ROM, booted up and got data right away (including 4G LTE), minor poking around seems to indicate no problems.
Looks good so far! I'll flash gapps and restore my other apps and use it as my daily driver today. If you want me to check on anything specific, let me know.
Click to expand...
Click to collapse
Thanks glad you can confirm we at up and going
Nothing specific
neighborhoodhacker said:
Thanks glad you can confirm we at up and going
Nothing specific
Click to expand...
Click to collapse
Looks like I spoke too soon.
Data is not working correctly. 3G/4G works, but once you connect to wifi and then leave the wireless network (or even toggle wifi off), the data dies. The airplane mode toggle trick doesn't work reliably either.
I toggled airplane mode, rebooted, restored an old, working EFS from both stock ZVC and the previous ROM I was using that had no data issues (Beanstalk)... but no luck. Any time you connect to a wireless network and then leave it (toggling off), the cellular data connection dies.
I've had similar problems on other ROMs, but never as bad as it is here on Liquid. On other ROMs, the issue was sporadic and random and the airplane mode toggle usually worked. Here, the data dies every time I turn wireless off and sometimes won't come back up at all (I've had to dirty flash the rom a few times now to get data back in those cases).
Also interesting - when I dirty flashed the rom, my gapps disappeared. I don't think that normally happens.
Anyway, I know I had planned to bang on the ROM all day during work and such, but I can't do that if the data is borked. :crying: So I'm going to have to go back to Beanstalk for now (which is a 4.3 ROM that doesn't give me any data issues at all. Slimbean also hasn't given me any issues on 4.3).
So many ROMs!!!!!! I want to flash them all but I was just starting to love carbon.
Sent from my LG-LS970 using Tapatalk
mpbean said:
Looks like I spoke too soon.
Data is not working correctly. 3G/4G works, but once you connect to wifi and then leave the wireless network (or even toggle wifi off), the data dies. The airplane mode toggle trick doesn't work reliably either.
I toggled airplane mode, rebooted, restored an old, working EFS from both stock ZVC and the previous ROM I was using that had no data issues (Beanstalk)... but no luck. Any time you connect to a wireless network and then leave it (toggling off), the cellular data connection dies.
I've had similar problems on other ROMs, but never as bad as it is here on Liquid. On other ROMs, the issue was sporadic and random and the airplane mode toggle usually worked. Here, the data dies every time I turn wireless off and sometimes won't come back up at all (I've had to dirty flash the rom a few times now to get data back in those cases).
Also interesting - when I dirty flashed the rom, my gapps disappeared. I don't think that normally happens.
Anyway, I know I had planned to bang on the ROM all day during work and such, but I can't do that if the data is borked. :crying: So I'm going to have to go back to Beanstalk for now (which is a 4.3 ROM that doesn't give me any data issues at all. Slimbean also hasn't given me any issues on 4.3).
Click to expand...
Click to collapse
The issue is upstream and actually I think it was just fixed give 10/31 a go. I am not flashing this seeing as I am maintaining to many to flash
Repeating phone process force closes on 10-31 after a clean install.
Same deal on Carbon.
Sent from my LG-LS970 using xda app-developers app
neighborhoodhacker said:
The issue is upstream and actually I think it was just fixed give 10/31 a go. I am not flashing this seeing as I am maintaining to many to flash
Click to expand...
Click to collapse
Just flashed 10/31. Factory reset, clean install. Same problem with the data. Connect to wifi, then disconnect from wifi and the data dies and doesn't come back up.
Wasn't sure if I should've made a new thread or not but just saw this earlier today..
Official Liquid Smooth 4.3 !!!
https://plus.google.com/102153960718796996774/posts/K4QsHyduD72
Haven't had a chance to flash yet but plan on it soon!
Sent from my LG-LS970 using xda app-developers app
Warlord721 said:
Wasn't sure if I should've made a new thread or not but just saw this earlier today..
Official Liquid Smooth 4.3 !!!
https://plus.google.com/102153960718796996774/posts/K4QsHyduD72
Haven't had a chance to flash yet but plan on it soon!
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
Runs pretty smooth so far. The only hiccup I came across was the com.android always fc'in. The xml file fixes that. Another is that their is no Voice Dialer in the setup. So I don't know how to access the APN to select the correct one.
oohaylima said:
Runs pretty smooth so far. The only hiccup I came across was the com.android always fc'in. The xml file fixes that. Another is that their is no Voice Dialer in the setup. So I don't know how to access the APN to select the correct one.
Click to expand...
Click to collapse
you might be able to get into it with the app offline sim database. Should let youopen the shortcut directly.
4.4.2 beta builds for geespr up here: http://www.drdevs.com/devs/teamliquid/official/Beta3/
Sent from my LG-LS970 using Tapatalk
iamterence said:
4.4.2 beta builds for geespr up here: http://www.drdevs.com/devs/teamliquid/official/Beta3/
Sent from my LG-LS970 using Tapatalk
Click to expand...
Click to collapse
Don't know if it was because I flashed the new f93 kernel, but twice in a row the screen wouldn't come back on after sleeping. The LED would come on but the screen would be black. Forced to reset the device.
prowlingfox said:
Don't know if it was because I flashed the new f93 kernel, but twice in a row the screen wouldn't come back on after sleeping. The LED would come on but the screen would be black. Forced to reset the device.
Click to expand...
Click to collapse
Which f93 kernel version did you flash? I'm on the AOSP kernel and it seems to be working fine for me so far. *knocks on wood*
Sent from my Optimus G using Tapatalk
iamterence said:
Which f93 kernel version did you flash? I'm on the AOSP kernel and it seems to be working fine for me so far. *knocks on wood*
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
Same, the one that fixes camera focus. Did you enable ART?
prowlingfox said:
Same, the one that fixes camera focus. Did you enable ART?
Click to expand...
Click to collapse
Not yet, kinda afraid to because the ROM is running so good, and I know ART can muck some certain ROMs up. Did you enable ART?
Sent from my Optimus G using Tapatalk
To all of you on 4.4 beta 3, DO NOT, I repeat DO NOT, turn on charging animation's, when its on, and you plug the phone in, the phone phone spazzs out and every 3 seconds puts a lockscreen.
Sent from my Optimus G using xda app-developers app
iamterence said:
Not yet, kinda afraid to because the ROM is running so good, and I know ART can muck some certain ROMs up. Did you enable ART?
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
I did, so that could also have something to do with it. I'll try again later with vanilla kernel and dalvik.
-------------------
EDIT: I did another clean flash then enabled ART then flashed f93 kernel. Then I was installing apps from Google play and I let the display go to sleep. Upon trying to wake the device it just froze with a black screen. So it happened again. But it seems to only happen when Google play is installing apps. Since it finished I haven't had that problem.
Right now this is absolutely my favorite 4.4 ROM. So many features, and it's so bloody fast and responsive. Not to mention DarkLiquid is beautiful AF.
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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Resurrection Remix the ROM has been based on CM,slim.omni and original Remix ROM builds, this creates an awesome combination of performance, customization, power and the most new features, brought directly to your Device
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Resurrection Remix
Special thanks to, the CM team,OMNI team ,SLIMROMS and of course to all the supporters
download: https://www.mediafire.com/folder/51hajv463yfxb/otterx
http://opengapps.org/ (arm, 6.0)
Kernel auditor - Low memory killer - Very aggressive
one important note: each flashing rom need flashing gaaps (pico for assurance)
If you install Gapps after the ROM has been booted for the first time you either need to wipe data and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
very nice rom although there are still some lag so i had to change the CPU Governor to performance and and change all of the animations to 0 but other than that it's a nice rom
nvm wifi is working for me again
Kytherium said:
very nice rom although there are still some lag so i had to change the CPU Governor to performance and and change all of the animations to 0 but other than that it's a nice rom
nvm wifi is working for me again
Click to expand...
Click to collapse
try Kernel auditor - Low memory killer - Very aggressive
transi1 said:
try Kernel auditor - Low memory killer - Very aggressive
Click to expand...
Click to collapse
i already had that turned on also is it possible to overclock it beyond 1.2 GHz
Can this ROM be installed on Kindle Fire 1st gen?
I have KF 1st Gen. I want to install latest Android on it. I am new to this stuff. Can someone list the bootloader, recovery and the steps to install this ROM on KF 1st Gen?
kuldeepsidhu said:
Can this ROM be installed on Kindle Fire 1st gen?
I have KF 1st Gen. I want to install latest Android on it. I am new to this stuff. Can someone list the bootloader, recovery and the steps to install this ROM on KF 1st Gen?
Click to expand...
Click to collapse
This ROM is for the 1st gen KF but with the Otterx partitioning. Follow the instructions in the 1st post here:
http://forum.xda-developers.com/showthread.php?t=2671619
This should get you going. Hope this helps.
Any update of this ROM ?
build(5.6.5) 20160316 spyder (backup before flash, gaaps need for upgrade and don`t flash SuperSU): http://www.mediafire.com/download/1jcds8eb30l122i/ResurrectionRemix-M-v5.6.5-20160316-otterx.zip
ps. r22, march security
I have a problem with the rom. Whenever I boot into the rom after installing Gapps I get stuck and it continually says setupwizard.apk has stopped working. Any solutions? Would really appreciate it!
shadow726425 said:
I have a problem with the rom. Whenever I boot into the rom after installing Gapps I get stuck and it continually says setupwizard.apk has stopped working. Any solutions? Would really appreciate it!
Click to expand...
Click to collapse
If you booted the ROM before installing Gapps you need to wipe data. The last paragraph of the OP gives this detail. If this doesn't work let us know your install process and which Gapps you are using.
chykal said:
If you booted the ROM before installing Gapps you need to wipe data. The last paragraph of the OP gives this detail. If this doesn't work let us know your install process and which Gapps you are using.
Click to expand...
Click to collapse
I already did do that. I tried reinstalling and did Gapps before but that didn't work. When I start up the rom without Gapps it works so I'm pretty confused. When installing the rom I wipe everything and then adb push the files onto the kindle. After that I installl. The Gapps I am using is micro from the link the op gave. Any help would be appreciated!
shadow726425 said:
I already did do that. I tried reinstalling and did Gapps before but that didn't work. When I start up the rom without Gapps it works so I'm pretty confused. When installing the rom I wipe everything and then adb push the files onto the kindle. After that I installl. The Gapps I am using is micro from the link the op gave. Any help would be appreciated!
Click to expand...
Click to collapse
Are you flashing the ROM in the OP or the update from the 17th? Which TWRP version do you have? I will try to recreate the problem after work tonight and see if I can find a resolution.
I got past the select wifi screen and exited the setup wizard but I still cant get wifi to work. It shows turning wifi on but never comes on. I've tried restarting several times. Everything else seems to be working. Any suggestions?
coreygator said:
I got past the select wifi screen and exited the setup wizard but I still cant get wifi to work. It shows turning wifi on but never comes on. I've tried restarting several times. Everything else seems to be working. Any suggestions?
Click to expand...
Click to collapse
Try rebooting your router and forgetting the SSID on your OtterX. Then reconnect.
chykal said:
Try rebooting your router and forgetting the SSID on your OtterX. Then reconnect.
Click to expand...
Click to collapse
Thanks for the advice. It did not work. I don't have the option to forget the SSID because it doesn't even get that far. I looked into it a little more and the MAC address isn't correct so wifi wont turn on. Still don't have an answer but that's the problem. I'm going to try and reflash the bootloader.
Does anyone have a copy of a bootloader that it know to work with this ROM. Wifi is the only thing not working.
chykal said:
Are you flashing the ROM in the OP or the update from the 17th? Which TWRP version do you have? I will try to recreate the problem after work tonight and see if I can find a resolution.
Click to expand...
Click to collapse
I was using the update from the 17th. And I went off to college so my kindle is at home. If I remember right it's the newest version. Doubt that helps but when I get back home I can tell you exactly. That will be in a month though
Sent from my SM-G920T using XDA-Developers mobile app
Flash ROM Findings
I made time today to do some testing with this ROM since it showed promise to be full featured and not laggy when set up properly. There is also some question as to how to get it to flash and set up properly after the March 17th update.
If you first flash the march 17th update with Gapps it will not get past the WiFi selection. I tried many boot and reboot options to no avail.
I found that you need to flash the original version in the OP along with Gapps, nano worked for me, and then boot the ROM. Set up and WiFi work properly and most features I tried worked. The only issues I found setting it up to my liking were with setting the color in things like Slim Recents and status bar clock with settings force closing . This is a very small issue considering all the great features in this ROM. Not to mention the fact that we can now run Marshmallow on OtterX. AMAZING!
I spent some time setting it up with all my usual settings. I also set Kernel Auditor (included, thanks) - low memory killer to very aggressive. This seems to greatly reduce lag although I only used it for about half an hour.
I then flashed the March 17th update along with Gapps. It broke WiFi. Back to the original version.
I hope this helps anyone who is having issues up to this point.
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
coreygator said:
Thanks for the advice. It did not work. I don't have the option to forget the SSID because it doesn't even get that far. I looked into it a little more and the MAC address isn't correct so wifi wont turn on. Still don't have an answer but that's the problem. I'm going to try and reflash the bootloader.
Does anyone have a copy of a bootloader that it know to work with this ROM. Wifi is the only thing not working.
Click to expand...
Click to collapse
shadow726425 said:
I was using the update from the 17th. And I went off to college so my kindle is at home. If I remember right it's the newest version. Doubt that helps but when I get back home I can tell you exactly. That will be in a month though
Sent from my SM-G920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Forgot to mention the users who were having the issues. @shadow726425 and @coreygator
@transi1
Thanks once again for working so many ROMs.
The first release of this , (ResurrectionRemix-M-v5.6.2-20160205-otterx.zip)along with open gapps, runs more than well enough to be a daily driver.
I kept getting audioFX errors , but after an uninstall, and tweaking through Aduitor and ES Task manager to minimize what runs on startup, this is a very respectable ROM
cant get any ROM for otterx to run with /cache as f2fs, but /data is fine.
I've tried all the updated roms for otterx, and this one leads the pack . The UI is very responsive, no other load works as well IMO.
Thank you again, I'm glad you reelased it
New recruit. Clean install via twrp otterx.
I installed your latest, with gapps micro, and can't get past the "turning on WiFi" cm/mm nag screen during device setup. No networks populate the list after 5 min.
Rebooted to see if that helped. It did not.
AMRivlin said:
New recruit. Clean install via twrp otterx.
I installed your latest, with gapps micro, and can't get past the "turning on WiFi" cm/mm nag screen during device setup. No networks populate the list after 5 min.
Rebooted to see if that helped. It did not.
Click to expand...
Click to collapse
Read my posts on this issue a few posts back. I go into detail on how to flash this ROM.
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?
XenonHD ROM for Xiaomi Mi Mix 2
A Team Horizon ROM
Based on AOSP r36 7.1.2
This ROM has all the features XenonHD has to offer.
All hardware functions including:
NFC
Bluetooth Audio
Fingerprint Scanner
Doze & Wake-up Gestures (dtw works after the first reboot)
And...many more things.
Magisk is no longer built in, so you'll need to flash it when first installing, and after every dirty flash.
VoLTE doesn't work (at least on T-Mobile). I believe most of the pieces are in place, but there may be something in the firmware that's preventing it? If I could figure out how to tap into the stock cust files, I might be able to figure out how to get it working.
Proximity Sensor is working:
Notification Light:
I have slowed down the notification light so it isn't all amped up. To make it completely usable, go to:
Fixed default notification blinks for built-in apps so they are slowed down without needing to go to settings.
For use-installed apps, add them to custom notification list in settings > notifications > gear icon > notification light > + in upper right corner > select app. Apps added to that list will have slow notification blinks.
I simply cannot find a way to make user-installed app notifications behave the same as built-in apps. Grrr!!
I have also made the light sensor wait longer before dimming the screen. This helps with left-handed activities blocking the light sensor and almost immediately dimming the screen.
Reduced time to go back from dim to bright. Screen will dim after 5 seconds, returns to bright after 2 seconds.
I've remove configpanel & pocketmode...they did little to nothing, and may have caused more battery drain than I care for.
Required prior to installing:
Unlock Bootloader
Install custom recovery: https://www.androidfilehost.com/?fid=962021903579490303
HUGE thanks to IceMan for bringing this to Mix 2!
A quirk with this TWRP: This one looks for backups in TWRP/BACKUPS/MIX_2 folder. Normally, the MIX_2 folder is named after serial number of your device.
So, you existing backups won't be found until you rename the folder in BACKUPS to MIX_2.
Installation Instructions:
Dirty flash is now available with the above TWRP and 10-26-2017 rom.
Download the most recent build: https://www.androidfilehost.com/?fid=673791459329071426
Download Gapps (I use Open Gapps Mini) --> http://opengapps.org/
All versions from 10-24-2017 are now encryptable.
From TWRP Recovery:
IF COMING FROM MIUI-BASED ROM: FULL WIPE AND FORMAT DATA!!
If you encounter ERROR 7, during XenonHD install, install Global MIUI ROM, then do full wipe and data format again, then install XenonHD rom.
If coming from AOSP-based ROM:
- Full wipe (Cache, Davlik/ART Cache, System & Data)
- Flash ROM zip
- Flash Gapps zip
Huge thanks to Mokee for bringing this device up and making a great place to start.
Also a very HUGE thanks to @Arasthel for his work on proximity sensor and figuring out the bluetooth reboot stuff and other hints, suggestions and incalculable work.
I'd also like to thank all of you folks here for trying this ROM and providing constructive feedback.
In addition, I appreciate your patience when issues come up that need to be fixed. I am not a developer, and I have a full time job and a wife that takes precedence most of the time
Sources:
Vendor:
https://github.com/hondajohn88/android_vendor_xiaomi_msm8998-common
https://github.com/hondajohn88/android_vendor_xiaomi_chiron/tree/xenonhd
Kernel:
https://github.com/hondajohn88/android_kernel_xiaomi_msm8998/tree/xenonhd
Device:
https://github.com/hondajohn88/android_device_xiaomi_chiron/tree/xenonhd
https://github.com/hondajohn88/android_device_xiaomi_msm8998-common/tree/xenonhd
reserved
reserved 2
Does safety net pass with or without magisk?
subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
With magisk its working
Gesendet von meinem MI Mix 2 mit Tapatalk
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
KOLIOSIS said:
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Click to expand...
Click to collapse
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
subashchandran said:
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
Click to expand...
Click to collapse
Glad everything is working for you so far. Bluetooth audio in car should work (it does on mine), but I found the volume on the car set to zero so needed to turn that up. That was a brief "oh crap" moment that I thought it wasn't working lol
subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
I think it fails without it, but magisk is built in, so if have to remove it to find out for sure.
hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
IT'S ALL GOOD @hondajohn88 . :good:
This ROM is daily-driver material,every update from here on out is a bonus & very much appreciated. :good:
hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Arasthel said:
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Click to expand...
Click to collapse
That's cool you got the Bluetooth working on RR, knocking little things out one by one ?
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ??
By the way, does android auto work on your rr?
Everything except proximity sensor works and works as good as stock. I have installed custom font, black swift substratum OMS theme without any hiccups. The rom is buttery smooth and I've been getting a better battery drain trend on this compared to resurrection/mokee. I have naptime doze installed to see if i can ooze out more battery goodness to the levels of epic Rom(miui 9)
Overall this is super encouraging to see a daily driver rom this early for mi mix 2.
There is one edge case which might be a bug, when connected on car Bluetooth and watching something on YouTube.. And then you get a call, i pressed answer on the car knobs/buttons.. I couldn't hear the person talking.. Car was displaying "audio disabled message ”. But talking/call and video/music in isolation works just fine.
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
slyyke said:
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
Click to expand...
Click to collapse
Thanks for the info about android auto on RR. I'll take a look at their repo and see if I messed up a USB setting somehow.
As far as I'm concerned, other ROMs can be discussed here.
Open source should be crowd sourced for maximum problem resolution.
RR probably (?) Did the same as me... Mokee made a commit in qcom/audio that did the trick.
hondajohn88 said:
That's cool you got the Bluetooth working on RR, knocking little things out one by one
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ?
By the way, does android auto work on your rr?
Click to expand...
Click to collapse
Hi... Thank you again for the wlan.ko tip. I deleted all instances of that in my out folder, dirty built and it's all good. Sped up my test time considerably! Woohoo! :good:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
stu5797 said:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
Click to expand...
Click to collapse
I haven't used rr for this phone, but I think at this point rr probably has more options. This one has quite a few, and as son as I get most of this ROM straightened out, I'll try adding more options.
I'll add some screen shots of the settings to help people decide.
Thanks ?
Great work by a great Dev,
Thanks for putting in the work, smoothhhh rom~