Hey guys, I've been using CM13 builds on my Nexus 6p for last few months. Generally, i flash new builds after 3/4 days from the last one. Everything's works fine, no big issues; but recently from last months build which ever update i flash on the device, the WiFi seems not working. It shows, it's on - Searching for Networks; but not able to connect or even find any network at all. And i tried to flash back to the older builds of CM13, the WiFi works fine on those builds quite fine. Beside this, I've tried Paranoid Android ROM on this device, WiFi works fine on that rom. So, have any of you faced such problem on CM13? And, please can anyone help me out on this matter?... Thanks in advance...
rudra_666 said:
Hey guys, I've been using CM13 builds on my Nexus 6p for last few months. Generally, i flash new builds after 3/4 days from the last one. Everything's works fine, no big issues; but recently from last months build which ever update i flash on the device, the WiFi seems not working. It shows, it's on - Searching for Networks; but not able to connect or even find any network at all. And i tried to flash back to the older builds of CM13, the WiFi works fine on those builds quite fine. Beside this, I've tried Paranoid Android ROM on this device, WiFi works fine on that rom. So, have any of you faced such problem on CM13? And, please can anyone help me out on this matter?... Thanks in advance...
Click to expand...
Click to collapse
I've been successively flashing the nightlies from 07/24 until today and have had no issues with Wi-Fi. Sounds like yoh crossed over drom June to July build. Flash the July vendor image then re-flash latest cm and you should be good to go. If you use a custom kernel also make sure you are using the latest version made for this month.
blitzkriegger said:
I've been successively flashing the nightlies from 07/24 until today and have had no issues with Wi-Fi. Sounds like yoh crossed over drom June to July build. Flash the July vendor image then re-flash latest cm and you should be good to go. If you use a custom kernel also make sure you are using the latest version made for this month.
Click to expand...
Click to collapse
Thanks a lot, brother. I've just flashed the latest vendor image, and it's working smoothly...
Related
Hey there,
I am an active reader of this forum for 4 years now - thank you for all the information - and have a uncommon problem with my nexus 4,
yesterday i upgraded my purity rom to the actual build and have no cellular connection since then 8excuse me for my english right away)
What seems to be a trivila problem is kinda tricky (of course a looked a lot for possible causes and resolves in the forum).
the problem is: i have flashe the actual bootloader, radio and made a factory image flash and my nexus is working when on stock rom.
but when i flash a custom rom - i tried purity, psx and cm 10.1 - the cellular connectivity and in some cases wifi is gone. once i flash the factory image everything is fine again.
can you imagine a possible explanation?
one more information: when flashing the new purity update, i accidentally flashed not the current one, but the 2 month old version... but i allready made a clean-flash, wiping everything and flashing just the rom.
i'm on the most recent bootloader, radio und cwm-recovery
Any idea? Thanks in advance...
alex
update to latest recovery for either cwm or twrp its a common issue that many have posted issues about
hey,
it worked, reverted to an earlier cwm build and it works again. thank you very much
Hello struq and Kayant,
congratulations on this excellent ROM.
For me it is after many attempts with CM11 a surprise how stable and fast our Defy + can run under KitKat, even though both ROMs run on the same kernel.
Now a few more translations into German and the ROM would be perfect.
Please continue developing this ROM.
regards
Defy_Duke
Great OmniRom
It is definitely a great KitKat rom: fast and stable :good:
Thank you!
Thank you for new relase of the OmniROM.
I have only two problems:
1. No TWRP Recovery boot function (i have fix it with your ramdisk-recovery file )
2. OmniSwitch not working
the rest works fine, stable and fast.
greets
About the Question
I also noticed no deep sleep with wifi connected, do you have this too?
Click to expand...
Click to collapse
in this Thread http://forum.xda-developers.com/showthread.php?t=2614453&page=14
For me the deep sleep works fine.
Very fluid
Well this is one of the ROMs I kept longer since was so fluid but I don't know why is not updated?
Anyway super rom.
Yes, OmniROM is a super ROM for the Defy. :laugh:
There is a newer Version out (20140228), but this has an big bug in TWRP recovery boot, so is better not install this version.
I think struq is work on next version of OmniROM. :good:
well is it better than quarx ?
It has the same Kernel from Quarx and Blechdose, but struq has only stable versions of the kernelcode in his Rom.
For me is the Omnirom much more smoother and stable as CM11.
Omni for Defy March 8th version / Google Play problem
I've installed the new Omni version this morning and it is very nice! Performance of my Defy is acceptable.
I had one problem since I had a working internet connection but couldn't access Google Play. After installing 2-27_GApps_Minimal_4.4.2_signed.zip the problem was solved.
Many thanks for this ROM! Now I can use the same environment on my Nexus 7, I9305 and my old Defy.
Klaus
Thank you struq for the new version.
TWRP works fine now, no bootloops and start in TWRP works.
Works perfect for me.
Wow, i have never threy a better ROM on my Defy+.
I hope that i now have 10 post and can answer in dev. threat.
Thank you all for your awesome work.
I installed omni-4.4.2-20140308-mb526-TEST.zip and had some issues at first:
-after a dirty flash over the version 20140202, supersu (flashed via twrp) was not working
-clean flash: same error as Post #159 in original thread:
status bar, lock screen, etc doesn't appear ie system ui doesn't start
Click to expand...
Click to collapse
-another clean flash worked fine but no usb mass storage, only mtp/ptp (I am almost certain that I had us mass storage on 20140202)
did not yet try to enable it via terminal emulator
(since I am a forum newbie, I can't post in the dev-threat)
I think me have since KitKat only MTP/PTP
Fine that the new OmniROM now works on your phone. :laugh:
Yeah youre right. Went back to build 20140202 since I had some charging issues and there is only MTP/PTP too.
Maybe it was just a dream
But will stay on this one for now, feels more stable...
Omni for Defy March 11th version / Google Play problem gone
mklmkl said:
I've installed the new Omni version this morning and it is very nice! Performance of my Defy is acceptable.
I had one problem since I had a working internet connection but couldn't access Google Play. After installing 2-27_GApps_Minimal_4.4.2_signed.zip the problem was solved.
Many thanks for this ROM! Now I can use the same environment on my Nexus 7, I9305 and my old Defy.
Klaus
Click to expand...
Click to collapse
Just installed the March 11th version. Google Play now works out-of-the-box.
Nice ROM, thank you!
Klaus
What are the main differences between Quarx's CM11 and OmniRom? (...an SlimKat??) :silly:.
newer version possible
Is there maybe a chance for a new version which incorporates latest Quarx's & Omni changes?
Would be great!
Hey guys,
I'm currently using OzcanRom and it's just great - strongly recommended!
My only issue is exactly the same issue as described in this post:
I'm facing a very strange problem as i'm unable to switch on my bluetooth... last week only i rooted my phone and installed CWM recovery...then i installed Custom Rom's like Hassan ROM, Omega ROM, Cyanogenmod 11 Rom, Pacman ROM etc etc just to check various Rom's and their features out.....At first i installed only one ROM at a time and den also dual booted two ROM's by romswitcher...While i was checking my phone once i discovered that my phone's Bluetooth is not turning ON...The toggle is only becoming light green and also from the settings its only showing turning Bluetooth On but it's unable to turn bluetooth On.....Now i googled my problem and read across various forums for solution...I tried various things also flashed my firmware to stock samsung but still bluetooth does not turn On...also i flashed with stock samsung firmware of feb and march 2014 and updated my phone over OTA but still the problem persists....i even installed latest perseus kernel while rooted but still could not turn my bluetooth ON.
I would be very grateful if someone can help me solve my problem and help me Switch ON my bluetooth as it is very needed aspect for my daily use.
My Version of S4 is i9500 with android kitkat 4.4.2. Also all my other features are working normally on custom ROM's too.
Click to expand...
Click to collapse
I too installed this Omega rom at some point and once I did that these problems started.
A user in that thread posted a reply in which he uploaded a file which he claims fixed his problem.
I really need my bluetooth to work again and would love to flash this file using Odin if it would fix the problem
BUT
I have no clue what implications flashing this file can have, can it mess other things up? I've spent the last four hours setting things up again in my new ROM and I would hate to have to do it again or even worse, cause some unsolvable problem with my phone.
I assume some of the developers here could help me out - should I run it?
Thanks!
For anyone who doesn't know; MoKee Nightlies are available for Thea, if anyone wants to try. It's pretty good.
http://download.mokeedev.com/?device=thea
Their original dev (and unkwon) must create a post for more detailed information...! But thanks for the advice.
Obviously. They haven't yet! Just telling people it's there.
It's pretty good, but at the moment Bluetooth is not working, can't connect to my Android Wear, so back to CM12 but I'll keep trying =)
hugoprh said:
It's pretty good, but at the moment Bluetooth is not working, can't connect to my Android Wear, so back to CM12 but I'll keep trying =)
Click to expand...
Click to collapse
Were you using a nightly or release build? Bluetooth is working fine for me. I'm on the latest release build. Smooth and stable.
mej0248 said:
Were you using a nightly or release build? Bluetooth is working fine for me. I'm on the latest release build. Smooth and stable.
Click to expand...
Click to collapse
Yep it was nightly 2015-05-23 , later I'll try the new nightly and if that does not work, then I will try the release build. Cheers for the info =)
How good is it? Is it better than CM?
I prefer it to CM. The release builds are great. No issues for me.
I4ve been on this ROM for a day now and it works like a charm. Mokee is really great. No buigs or FC for now
EDIT : GPS works for You ? I can't get a fix.... Did a clean flash of Mokee but still no GPS Fix
EDIT #2 : OK now it works, just have o erase modemst1 and modemst2 with fastboot
Hi everyone,
I've been enjoying Mokee for a week, flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Is it the same for you too? Thanks
metalmoot said:
Hi everyone,
I've been enjoying Mokee for a week, flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Is it the same for you too? Thanks
Click to expand...
Click to collapse
I don't use OTA.
I heard that it broke ever, then they fixed. I'll link to him.
Try using the Release builds instead. More stable and OTAs are every week or so.
Yes but releases are odexed and xposed does not work with odexed roms
Ok, I don't ever use Xposed with custom roms. Just stock.
Caution ! The 28/06 nightly doesn't work !
I will go back to CM because the 29/06 crashes when I use a theme.
Great rom but I honestly can't see the advantage over CM. Ota would be a plus but it fails.
Back on CM with Cyandelta for incremental updates
Another update on Mokee on Thea :
- OTA works great but you must not remove /system apps and modify build.prop however the phone will bootloop.
- OTA doesn't work with Xposed as well, bootloop
- Release versions (odexed ROM) are really smooth and seem to be more battery friendly than nightly releases...
- The ROM is bugfree, I've been using Mokke for two weeks now and no reboot, no freeze, perfect experience
metalmoot said:
flashed nightlys every two days and just discovered that their OTA system just download the changes from the rom installed to the new build. I tried to DL it and flash but I've an endless bootanimation after.
Click to expand...
Click to collapse
Same here, I'm really happy with Mokee (running release version), no bugs so far and smooth performance. However I tried as you did to download incremental update through Mokee Center and automatically flash through recovery (TWRP), but got endless boot animation, had to download full ROM and flash after wiping system/data/cache/dalvik.
Does anyone know if Mokee can be upgraded simply by flashing full ROM zip without wiping system and data?
Tried again updating through Mokee Center, this time downloading full ROM. Didn't get endless bootloop, but performance was really bad, moto g suddenly rebooted 2 times, very unstable. I decided to wipe all and reflash manually through TWRP. Working fine now... it seems that auto-update are not working very well. Anyone who didn't get those problems and successfully updated through Mokee Center?
I managed to have incremental updates working on release versions. You must not touch anything in /system (you can freeze apps however)
I've been updating like that for two releases and it works
Just a quick for OTA updates on nightly builds with Xposed.
Ota works if you uninstall xposed with the uninstaller zip before flashing OTA !
Hello,
I have a couple of problems with my Samsung Galaxy S III Duos (I9300). CM 12, CM 12.1.
1. I cannot switch to use Internet from another sim card. It always uses just one of them. I tried swapping cards, It just chooses one of them, not always sim in slot 1.
2. Problem with Bluetooth in car (BMW, CCC). When I call (incoming/outgoing call) from one sim card everything is fine. When I call from another sim, car answers the phone and shows duration of a call, but no sound.
U are using latest build?
ziad311 said:
U are using latest build?
Click to expand...
Click to collapse
I noticed these bugs when I was on CM12 or CM11 (not sure which one, November 2015 release, Android 5.0.1 if I'm not mistaken), flashed back to stock 4.4.4, both bugs disappeared, so I guess it was not a hardware problem. Then I tried CM 12.1 20151225 release, both bugs were still in the ROM, so I flashed 4.4.4 again.
Can anyone confirm if they have the same bugs or if they are known at all.
Thanks.
Flash latest cm12.1 not cm12
Android 5.1.1 not 5.0.2
ziad311 said:
Flash latest cm12.1 not cm12
Android 5.1.1 not 5.0.2
Click to expand...
Click to collapse
As I already wrote I did flash CM12.1 dated 25.12.2015 from here
http://forum.xda-developers.com/galaxy-s3-neo/orig-development/rom-cyanogenmod-12-1-s3-neo-t3099384
It didn't work either. Is it possible that I chose the wrong GApps and this was the reason?
I think I used open gapps stock version, but not sure, don't have that SD card and can't check now.
i have used CM12 and 12.1 rox and RR and i don't recall these two problems that you have mentioned specially the internet problem to me it was perfect but with a little reboot here and there so soory i couldn't help.
P.S :soory for my bad english