• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[7.1.1] Omni for Oppo Find7

Search This thread

iNaruX

Senior Member
Jun 29, 2012
195
120
Hey guys, I am currently on RR 6.0.1 Marshmallow with LVM (!)

Do I need to update my Kernel / vendor or remove LVM etc. before flashing 7.1.1 OmniRom ?
Answer is appreciated. Thank you for keeping this phone alive.

Greetings.
 

Yashraj Chawla

Senior Member
Dec 13, 2014
111
40
25
Ahmedabad
Hey guys, I am currently on RR 6.0.1 Marshmallow with LVM (!)

Do I need to update my Kernel / vendor or remove LVM etc. before flashing 7.1.1 OmniRom ?
Answer is appreciated. Thank you for keeping this phone alive.

Greetings.

No need to do anything of that sort, just flash the ROM with latest gapps and reboot.
If you face connectivity issues then just flash the 2.1.5i modem ?
 
  • Like
Reactions: iNaruX

beton87

Senior Member
Jan 7, 2013
481
116
Wrocław
Do you have official TWRP? First make sure you have LVM working. Then to check if everything is ok flash just rom without gapps and root. If it works, factory reset, flash gapps and root.
 

javier.pc

Senior Member
Mar 23, 2010
248
74
Valencia
Hey guys, what files do I need to flash in which order?

Coming from crDroid Marshmallow LVM I did use a clean flash,

Omni Nougat weekly zip
LVM (before or after nougat, which file to use exactly?)
Gapps
Supersu

I only get bootloops so far :(

can anyone help me here quickly?

Thanks in advance!

Do you have LVM already installed? If so, you don't need to flash LVM script again (in fact you should not do it). If you don't, then you need to flash LVM script before the rom.
As @beton87 explained, it's better to flash only ROM to verify that everything works, then you can flash gapps and SuperSU.
 

gluffs

New member
Dec 29, 2008
2
1
When we had homemade build so I could connect my huawei watch and android wear. After the official build came so I can not connect. Wrong PIN code or wrong password appears. What is wrong?
 

maxwen

Senior Member
Jun 10, 2012
8,052
10,284
When we had homemade build so I could connect my huawei watch and android wear. After the official build came so I can not connect. Wrong PIN code or wrong password appears. What is wrong?
There was a version of wear app that refused to work on userdebug builds but newer version works fine again for me. But you can try changing in build.prop from userdebug to user that was the workaround in the past
 

beton87

Senior Member
Jan 7, 2013
481
116
Wrocław
Max, what is the sqare that appeared in camera app video preview?
 

Attachments

  • unnamed.jpg
    unnamed.jpg
    21.1 KB · Views: 248

andriman

Senior Member
Feb 11, 2013
195
169
@maxwen: This is probably related to the problem with playlists after reboot.

I flashed the latest weekly version of the ROM yesterday and it messed up my alarm.
- no song was selected (<unknown>) (a song from ext SD card was selected before)
- it resulted in no alarm being triggered/played
- I almost overslept

Suggested solution: when OmniClockCS cannot find a song after reboot, show an ongoing notification... Or simply assign the default one.
 
Last edited:

maxwen

Senior Member
Jun 10, 2012
8,052
10,284
Hello everybody.

Does anyone know which file systems are supported on the external sdcard?

I know from my tests with earlier builds, that f2fs was not supported. Is this still true?

Can I use ext4 instead, as I really don't like FAT.

Thanks in advance.

Benjamin
Portable: exfat vfat ext4
Adopted: ext4

This is my kingdom - I make the rules
 
  • Like
Reactions: Benni:)

maxwen

Senior Member
Jun 10, 2012
8,052
10,284
@maxwen: This is probably related to the problem with playlists after reboot.

I flashed the latest weekly version of the ROM yesterday and it messed up my alarm.
- no song was selected (<unknown>) (a song from ext SD card was selected before)
- it resulted in no alarm being triggered/played
- I almost overslept

Suggested solution: when OmniClockCS cannot find a song after reboot, show an ongoing notification... Or simply assign the default one.

For such cases there is a fallback sound already in place
and yes that works fine - please test again!

Its a very annoying peep peep compiled into the app so
there is no way that this can fail AFAIKT - tested this
multiple times myself - ending up in a few near
heard strokes :cowboy:

IF you can reproduce it I would be very interessted in logs

This is my kingdom - I make the rules
 
Last edited:

Top Liked Posts