[4.4.x]Omni Nightlies for Find 7a/7s

Search This thread

Deanicus

Senior Member
Jan 11, 2011
50
8
Just wanted to let u know I flashed the kk modem zip I posted last night, I have had no reboots all day, and I seem to have had better signal all day too :) even getting LTE in places where I didn't think my carrier had it, lol, so it must have improved my phone no end :)
Thank u very much for the help!!

Just to be clear did you flash the 1.2.5 kk modem or the international one that you quoted? I know you say kk but wanted to be 100% certain :)

Also, does anyone know if there are any benefits in flashing the 1.2.7 modem?

The bluetooth on my device does not play well with my car. My previous HTC One M7 with 4.4.4 worked fine. I originally thought that the issues lay with ColorOs but I am having the same issues with the latest nightly. Perhaps it is a modem/radio issue? Does the above modems affect BT at all?

Thanks
 

Adam3Sixty

Senior Member
Apr 23, 2011
1,891
762
Exeter
linktr.ee
OnePlus 7T
Just to be clear did you flash the 1.2.5 kk modem or the international one that you quoted? I know you say kk but wanted to be 100% certain :)

Also, does anyone know if there are any benefits in flashing the 1.2.7 modem?

The bluetooth on my device does not play well with my car. My previous HTC One M7 with 4.4.4 worked fine. I originally thought that the issues lay with ColorOs but I am having the same issues with the latest nightly. Perhaps it is a modem/radio issue? Does the above modems affect BT at all?

Thanks
I flashed the 1.2.5 KK file that was posted a few pages back. Working lovely now.
Never had any issues with Bluetooth in my work van, and its connected for about 8 hours a day, music playing most of that and probably 2 hours of calls too.
 
  • Like
Reactions: Deanicus

Deanicus

Senior Member
Jan 11, 2011
50
8
I flashed the 1.2.5 KK file that was posted a few pages back. Working lovely now.
Never had any issues with Bluetooth in my work van, and its connected for about 8 hours a day, music playing most of that and probably 2 hours of calls too.

Thanks! Yeah I went ahead and flashed that one. No problems so far

I think the BT issues are with my car more than anything else. Think it needs a software update
 

Adam3Sixty

Senior Member
Apr 23, 2011
1,891
762
Exeter
linktr.ee
OnePlus 7T
Thanks! Yeah I went ahead and flashed that one. No problems so far

I think the BT issues are with my car more than anything else. Think it needs a software update
Car BT systems are known to be *****y. Especially fron certain manifactures
I have a Renault Master LWB van, and the connection is perfect all day every day, 99.99% of the time. Only problem I ever have is if my wife calls me, the incoming call volume is kinda low, I call her back and its fine. I put that down to the networks tho.
 

Adam3Sixty

Senior Member
Apr 23, 2011
1,891
762
Exeter
linktr.ee
OnePlus 7T
Really stupid question here.....

My wife has an S4 Mini with CM12 running on it (thanks me for that flash) and has a thing called Android Beam to send files via NFC, now, where is that on KitKat???? I can't seem to find it anywhere.
Please help a silly old fool.
 

maxwen

Senior Member
Jun 10, 2012
8,068
10,287
Really stupid question here.....

My wife has an S4 Mini with CM12 running on it (thanks me for that flash) and has a thing called Android Beam to send files via NFC, now, where is that on KitKat???? I can't seem to find it anywhere.
Please help a silly old fool.

settings - more - nfc -> android beam
 

Adam3Sixty

Senior Member
Apr 23, 2011
1,891
762
Exeter
linktr.ee
OnePlus 7T
settings - more - nfc -> android beam
Hhmmmm.....
I have found the setting, and of course if NFC is turned on it is also, but on Lollipop there is actually a button on the share menu that says "Android Beam" and it is on pretty much all apps that have the ability to share something.
I guess this is just a feature of Lollipop, will see if I can figure out how to use it on KitKat when the wife gets home with her Lollipop S4 Mini.
Thanx for the reply :)
 

Wendigogo

Senior Member
Jun 14, 2010
614
327
Lyon
Samsung Galaxy Note 20 Ultra
I flashed the 1.2.5 KK file that was posted a few pages back. Working lovely now.
Never had any issues with Bluetooth in my work van, and its connected for about 8 hours a day, music playing most of that and probably 2 hours of calls too.

Well, there are 2 of them: "modem_125i.zip" and "modem_125_kk.zip" ... I guess you flash the second one right ?

Anyone had switch from unified ColorOS to OmniRom? Could he write how he does (I'm stuck in bootloop after flashing "omni-4.4.4-20140830-find7-HOMEMADE.zip")?

Enjoy!
 
Last edited:

leungclj

Senior Member
Feb 15, 2012
368
69
is there anyway to disable auto updates? Now that there are no more nwe code implanted in 4.4.4 omni, its annoying to keep seeing the "new update available" on the notification bar.
 

leungclj

Senior Member
Feb 15, 2012
368
69
Freeze/disable/uninstall/delete OpenDelta.
I have never used it, always update manually. Once u get rid of that app u won't get update notifications
Any other way to disable it easily? I have bought 2 Find 7 and flashed Omni on them and gave them to my sister and her boyfriend on thr other side of the world.

I need to give them some easy instructions.
 

Adam3Sixty

Senior Member
Apr 23, 2011
1,891
762
Exeter
linktr.ee
OnePlus 7T
Any other way to disable it easily? I have bought 2 Find 7 and flashed Omni on them and gave them to my sister and her boyfriend on thr other side of the world.

I need to give them some easy instructions.
Not that I know of, its an automatic system app, works just like standard updates, only way to remove it is root access to delete the app.
U can check and see if it can be disabled in Settings > apps > all > OpenDelta and see if the Disable button can be pressed, but I don't think this way is fool proof and sometimes things may still slip thru.
 

greivel2

Member
May 13, 2011
42
6
Hello pplz,

Had a hard reboot just a few minutes ago...
I'm on Omni 4.4.4-20150128-find7-nightly
Here is last_kmsg.txt

Can anyone tell me what happened?
But I dont think this is a rom related issue as I had hard reboots as well on other custom roms ...

(last_kmesg.txt is in zip attached because txt file is to big...)
Or here is a link for it --> click here
 

Attachments

  • last_kmsg.txt.zip
    119.1 KB · Views: 7

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
Hello pplz,

Had a hard reboot just a few minutes ago...
I'm on Omni 4.4.4-20150128-find7-nightly
Here is last_kmsg.txt

Can anyone tell me what happened?
But I dont think this is a rom related issue as I had hard reboots as well on other custom roms ...

(last_kmesg.txt is in zip attached because txt file is to big...)
Or here is a link for it --> click here
Weird. I've never seen SSR triggered for ADSP before.

If one of the coprocessors on an MSM appears to have an issue, there's code in the kernel to auto-restart the whole device (some of the coprocessors can't be restarted without a full device restart...)

Usually SSR watchdog hits are due to the baseband becoming unhappy for whatever reason, but this time it was the audio DSP... Were you listening to music?
 
  • Like
Reactions: greivel2

greivel2

Member
May 13, 2011
42
6
Weird. I've never seen SSR triggered for ADSP before.

If one of the coprocessors on an MSM appears to have an issue, there's code in the kernel to auto-restart the whole device (some of the coprocessors can't be restarted without a full device restart...)

Usually SSR watchdog hits are due to the baseband becoming unhappy for whatever reason, but this time it was the audio DSP... Were you listening to music?

No, as far as I remember I didn't listen to music in that moment . But I can say that I also had hard reboots when I was listening to music(but no logs right now) . Additionally sometimes when I'm listening to music, headphones or speakers, there are some kind of audio glitches. The sound is stuttering for a second and it seems for me to be something like a memory read problem just for a second
 

Adam3Sixty

Senior Member
Apr 23, 2011
1,891
762
Exeter
linktr.ee
OnePlus 7T
Have builds stopped for the ROM??
 

Attachments

  • 1423161282249.jpg
    1423161282249.jpg
    85.3 KB · Views: 131

Top Liked Posts

  • There are no posts matching your filters.
  • 60
    DO NOT post in this thread until you have read the first three posts and last two pages of this thread in their entirety!

    "Me Too" posts for known issues with no useful debugging information WILL BE REPORTED.


    This is the thread for Omni nightlies for the Oppo Find 7a and 7s

    3nIy01hl.png

    http://dl.omnirom.org/find7/

    Also, the nightlies support LVM for partition remapping, which allows the two internal data partitions (/sdcard and /data) to be merged into one that uses emulated storage for /sdcard (Android's standard method for ICS and later). Details can be found at http://forum.xda-developers.com/showpost.php?p=55081626&postcount=546 . LVM is significantly safer than other partition remapping solutions as it does not actually alter the underlying partition table. As a result, switching layouts is MUCH faster than methods which remap the partition table, and switching layouts is more reliable and doesn't fail in strange and difficult-to-repair ways (such as the frequent failures of another solution that can be seen in the ColorOS 2.0.2i beta thread). There's a good chance Oppo will be switching over to this method with a future ColorOS release, especially after their experiences with 2.0.2

    For historical reference, I will leave the pre-nightly test builds in the Downloads section of this thread. However, these are now obsolete.

    Gapps:
    http://forum.xda-developers.com/showthread.php?t=2397942
    (this isn't a nexus, use the modular releases, not full)

    Omni only supports TWRP recovery, use any alternate recovery at your own risk. Official TWRP for this device is:
    http://forum.xda-developers.com/showthread.php?t=2717916

    Anyone flashing this should know the usual installation drill... Flash in recovery, flash gapps, wipe data/factory reset. If you don't know how to do these things, this package is not yet ready for users like you.

    Thanks go to the following people for their help during bringup:
    Jake Whatley and Kristof Petho (Omni)
    Max Weninger for polishing the device up and getting it up to nightly readiness after I kind of burned out
    Andre Saddler and Hieu Nguyen of the Paranoid Android team

    XDA:DevDB Information
    Omni for Find 7a/7s, ROM for the Oppo Find 7

    Contributors
    Entropy512, maxwen, xplodwild, jerdog, jakew02
    ROM OS Version: 4.4.x KitKat
    ROM Kernel: Linux 3.4.x
    Based On: AOSP

    Version Information
    Status: Nightly

    Created 2014-05-21
    Last Updated 2014-09-02
    20
    Reserved

    Current status as of 05/20/2014:
    GPS works
    Wifi works
    Cellular radio works (data and voice calls)
    Basic camera/camcorder functions work
    Bluetooth works (tested with Google Glass and an OBDKey)
    Sensors work (except for Google Camera Photosphere - see below)
    Audio is flaky - Mic does not work in speakerphone calls (earpiece only) and headsets with microphones cause the audio HAL to barf. There are probably a number of other use cases where audio doesn't work well. Confirmed working are Google Play Music, Google Maps, earpiece calls, Bluetooth calls via Google Glass (Mic in speakerphone/headphones may be fixed in the 5/30 build - won't test until tomorrow.)

    Not yet implemented (need to get the basics done first, these shouldn't be too hard since maxwen did them all on N1)
    Screen-off gestures for music
    "Hey, Snapdragon" voice wakeup - gotta talk to xplodwild about this
    Superzoom mode (I'm about halfway there, it's in the 5/30 build but crashes when you take a shot, so effectively isn't really there...)

    Known issues:
    Rare spontaneous reboots due to the WCNSS firmware crashing (1-2 times/week for me)
    Magnetometer (compass) gets "Stuck" if you use Google Camera
    LPM (charging when device is off) is broken - device may charge but screen gets stuck on at the Oppo logo. (may sometimes happen when rebooting on charger)
    17
    Nightlies should start tomorrow morning. Nightlies will include LVM support but multiwindow will be gone.

    I chatted with xplodwild - he's decided that once he finishes his current project he's going to rewrite multiwin from scratch based on some recent discoveries that should make it work much better.

    Attached are new versions of the LVM setup ZIP, and an updated TWRP image.

    If you're already running LVM, don't flash the ZIP as it'll wipe your data again. If the spam about not being able to mount raw_sd and raw_data annoys you, you can flash this TWRP image to get rid of it.

    I won't work on cleaning up TWRP properly until I return from vacation - I'm leaving next Saturday and will be gone at least a week and a half. (Might occasionally check forums, but no haxxing anything.)

    Known issues remaining with TWRP:
    On LVM configurations, the raw_sd/raw_data stuff is hackish - but I wanted to make sure people had a way to return to a non-LVM configuration without a separate ZIP or flashing anything.
    On non-LVM configurations, there's now an "internal storage" mapped to /data/media that is very small. Don't use it - this is the thing blocking an official LVM-aware TWRP from happening and needs quite a bit of reworking TWRP code to fix.
    Before I leave I might make a small change to the non-LVM configuration to move the TWRP settings storage on non-LVM configs away from /data/media which is ugly.

    Honestly if you're not running LVM, it's probably best to just use the standard TWRP until it can properly be fixed. But the image here works for both configurations, it's just not quite optimal for non-LVM in terms of user interface.

    More info on LVM setup is at http://forum.xda-developers.com/showpost.php?p=55081626&postcount=546

    I plan on writing a tutorial in a separate thread that is developer-oriented later.
    13
    You can follow changes on omni gerrit if you like. maxwen has pushed a lot of oppo specyfic updates yesterday but they're still have status open. I can only guess he has a booting version by now, but it's up to devs when they will make anything public.
    I've been focusing on resolving remaining derps on my Nexus devices. I consider it a bad idea to move forward on non-Nexus devices until Nexus devices are working - since broken Nexus devices is usually a sign that we broke something somewhere.

    Once I finish that, I'm going to be assisting Max with the 7a. He has had some issues with bringup that we're trying to determine if they are 7s-specific. That dual-DSI stuff is a pain in the ass and always has been.

    Find7 is basically Omni's pilot device for non-Nexus 8974 support.