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

Search This thread

Adam3Sixty

Senior Member
Apr 23, 2011
1,891
762
Exeter
linktr.ee
OnePlus 7T
well 4.4 will not change - so just use what you have :)
Happy exactly where I am for the time being :)
OmniROM has been my daily driver since the nightlies started on the Galaxy S3, and was one of the main reasons for me buying a Find 7, and with more and more apps and modules coming along with the material style, I can make it look different every week if I wanted to, lol.
Thanx for everything u have done for the device in the past.
I take it u r now working on Lollypop??
 

greivel2

Member
May 13, 2011
42
6
he it's me again posting a new last_kmsg :(

just this morning my phone was next to me on my charger but it was not in use. Suddenly it just hard rebooted...

Still on the nightly as the last time.

Link for last_kmsg or zip as attachment.
Anyone who can explain what happened?

Just fyi I had lots of reboots but didn't bother to post them but slowly it starts to getting on my nerves!:eek:
 

maxwen

Senior Member
Jun 10, 2012
8,068
10,287
he it's me again posting a new last_kmsg :(

just this morning my phone was next to me on my charger but it was not in use. Suddenly it just hard rebooted...

Still on the nightly as the last time.

Link for last_kmsg or zip as attachment.
Anyone who can explain what happened?

Just fyi I had lots of reboots but didn't bother to post them but slowly it starts to getting on my nerves!:eek:

...
[19152.349205][28098,kworker/0:1 ]Watchdog bite received from ADSP!
[19152.355689][28098,kworker/0:1 ]ADSP subsystem failure reason: SFR Init: wdog or kernel error suspected.
[19152.365716][28098,kworker/0:1 ]subsys-restart: subsystem_restart_dev(): Restart sequence requested for adsp, restart_level = SYSTEM.
[19152.379003][28098,kworker/0:1 ]Kernel panic - not syncing: subsys-restart: Resetting the SoC - adsp crashed.
...

Something @Entropy512 like a lot :)
Actually thats a SOC watchdog hard reboot - so something terrible went wrong with the SOC
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
...
[19152.349205][28098,kworker/0:1 ]Watchdog bite received from ADSP!
[19152.355689][28098,kworker/0:1 ]ADSP subsystem failure reason: SFR Init: wdog or kernel error suspected.
[19152.365716][28098,kworker/0:1 ]subsys-restart: subsystem_restart_dev(): Restart sequence requested for adsp, restart_level = SYSTEM.
[19152.379003][28098,kworker/0:1 ]Kernel panic - not syncing: subsys-restart: Resetting the SoC - adsp crashed.
...

Something @Entropy512 like a lot :)
Actually thats a SOC watchdog hard reboot - so something terrible went wrong with the SOC
I think watchdog bites can be caused by a software problem on a subsystem.

Up until grievel2's first log, I've never seen an SSR watchdog bite for anything other than the modem, and we've had the modem occasionally go out to lunch on us since the very beginning.

grievel2's issues are the first (and only) times I've seen ADSP watchdog bites. Either his device is starting to fail, or he's running some app that uses the Hexagon SDK and is doing Bad Things. https://developer.qualcomm.com/mobi...-hardware/multimedia-optimization-hexagon-sdk - I admit I know very little about exactly how that works, but it APPEARS that it allows app developers to create code chunks that get uploaded to the ADSP if I'm understanding things correctly.

ADSP = Audio Digital Signal Processor, it's a separate core on the Snapdragon 801.
 

greivel2

Member
May 13, 2011
42
6
I think watchdog bites can be caused by a software problem on a subsystem.

Up until grievel2's first log, I've never seen an SSR watchdog bite for anything other than the modem, and we've had the modem occasionally go out to lunch on us since the very beginning.

grievel2's issues are the first (and only) times I've seen ADSP watchdog bites. Either his device is starting to fail, or he's running some app that uses the Hexagon SDK and is doing Bad Things. https://developer.qualcomm.com/mobi...-hardware/multimedia-optimization-hexagon-sdk - I admit I know very little about exactly how that works, but it APPEARS that it allows app developers to create code chunks that get uploaded to the ADSP if I'm understanding things correctly.

ADSP = Audio Digital Signal Processor, it's a separate core on the Snapdragon 801.

I dont think that I am running any app that uses the Hexagon SDK (as far as I am informed myself)

So what would you suppose to do? Is there any chance that I can get it fixed somehow or should I just use my warranty and get replacement phone?
 

theevilworm

Senior Member
Oct 2, 2011
137
29
I know this 4.4 ROM is mostly dead, but I cannot make the switch to 5.0 because of missing XPosed modules.
Entropy or maxwen, I cannot estimate how big of a task this is, but would it be possible to upload the kernel modules for NFS filesharing or build it directly into the kernel? I would really appreciate this, I don't understand why Android doesnt support NFS out of the box. However, if it takes more than a couple of minutes of your busy schedule, I can understand if you deny my request.
 
Last edited:

prashantfind7

Member
Feb 6, 2016
21
2
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.

can you please tell me what should I do to setup LVM? I have the latest TWRP recovery for find 7.
What I did was kept the zip folder (setuplvm_find7_FULL_WIPE_09012014.zip) in external sdcard. Then from TWRP recovery mode, I tried to install that zip, nothing happened. The process failed. Am I missing something?
I'm using Oppo Find 7 with colorOS 2.1.5i (lollipop)
 

Cookie Ninja

Senior Member
Jan 21, 2010
2,043
700

Yup. That guy's a regular troll. Crossposted in all live find7 forums....
All you gotta do is go into settings>storage and delete some files to regain ownership of the partition. Had similar problems about missing internal SD card, not seen on ES explorer, PC but visible in settings storage....maybe something to do with some orphan files hijacking chown settings for internal SD....

Dead Cookies leave no trails...
 
Sep 17, 2009
26
2
Great ROM. Thank you!
One thing though: with Opera Mobile the phone not able to play vp9 encoded videos. I've no idea why. It was ok on ColorOS. The other thing is charging. The screen stays on, won't go black. I read the original post. It there anything can be done about it?
 

Cookie Ninja

Senior Member
Jan 21, 2010
2,043
700
Great ROM. Thank you!
One thing though: with Opera Mobile the phone not able to play vp9 encoded videos. I've no idea why. It was ok on ColorOS. The other thing is charging. The screen stays on, won't go black. I read the original post. It there anything can be done about it?

Check "stay awake" in developer settings...

Dead Cookies leave no trails...
 
  • Like
Reactions: [email protected]

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.