I haven't any results searching "scanning"...and after a dirty flash all my apps have begun to crash continuosly. I'm returned on 5.1.1 for the despair
Your problem is that you dirty flashed from 5.1.1 to 6.0. Try a clean flash, mane.
I haven't any results searching "scanning"...and after a dirty flash all my apps have begun to crash continuosly. I'm returned on 5.1.1 for the despair
Hey guys if you want to use the menu button/recents button as you normally would, aka long press and short press. Download this app: https://goo.gl/tgOiie and set the buttons accordingly under hard keys and it will allow complete customization of your hardware buttons. Hope this helps some people!
Sent from my A0001 using Tapatalk
how do i use now on tap? does it work with the hardware buttons? *I've turned on now on tap from the Google app setting
I feel sorry for the devs who work for OPO.
People in this forum do exact opposite of what XDA is.
A little reading or using search would help you a lot.
Wait wait wait...I dirty flashed from the same build (18th) because I couldn't find wifi scanning advanced settings in the search menu.Your problem is that you dirty flashed from 5.1.1 to 6.0. Try a clean flash, mane.
I don't know what device's you have used in the past but there is Bergius on every forum that is popular and of interest. Having said that it is good to have good developers doing good work.
You can look at my signature for device list.
I feel OPO forums are the most stupid ones.
You can look at my signature for device list.
I feel OPO forums are the most stupid ones.
Hey guys if you want to use the menu button/recents button as you normally would, aka long press and short press. Download this app: https://goo.gl/tgOiie and set the buttons accordingly under hard keys and it will allow complete customization of your hardware buttons. Hope this helps some people!
Sent from my A0001 using Tapatalk
Wait wait wait...I dirty flashed from the same build (18th) because I couldn't find wifi scanning advanced settings in the search menu.
Thanks for your message, and sorry for the delay.
We looked at the stack traces that you provided, and this seems extremely strange:
D/AndroidRuntime(20763): Shutting down VM
E/AndroidRuntime(20763): FATAL EXCEPTION: main
E/AndroidRuntime(20763): Process: com.keramidas.TitaniumBackup, PID: 20763
E/AndroidRuntime(20763): java.lang.StringIndexOutOfBoundsException: offset=0 length=48 string.length()=47
E/AndroidRuntime(20763): at android.util.SeempLog.seemp_println_native(Native Method)
E/AndroidRuntime(20763): at android.util.SeempLog.record_str(SeempLog.java:68)
E/AndroidRuntime(20763): at android.app.Instrumentation.execStartActivity(Instrumentation.java:1485)
E/AndroidRuntime(20763): at android.app.Activity.startActivityForResult(Activity.java:3951)
E/AndroidRuntime(20763): at android.app.Activity.startActivityForResult(Activity.java:3911)
E/AndroidRuntime(20763): at com.keramidas.TitaniumBackup.MainActivity.ˊ(Source:2660)
E/AndroidRuntime(20763): at com.keramidas.TitaniumBackup.MainActivity.onOptionsItemSelected(Source:2115)
E/AndroidRuntime(20763): at android.app.Activity.onMenuItemSelected(Activity.java:2942)
E/AndroidRuntime(20763): at com.android.internal.policy.PhoneWindow.onMenuItemSelected(PhoneWindow.java:1151)
E/AndroidRuntime(20763): at com.android.internal.view.menu.MenuBuilder.dispatchMenuItemSelected(MenuBuilder.java:761)
E/AndroidRuntime(20763): at com.android.internal.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:152)
E/AndroidRuntime(20763): at com.android.internal.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:904)
E/AndroidRuntime(20763): at com.android.internal.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:894)
E/AndroidRuntime(20763): at android.widget.ActionMenuView.invokeItem(ActionMenuView.java:616)
E/AndroidRuntime(20763): at com.android.internal.view.menu.ActionMenuItemView.onClick(ActionMenuItemView.java:141)
E/AndroidRuntime(20763): at android.view.View.performClick(View.java:5198)
E/AndroidRuntime(20763): at android.view.View$PerformClick.run(View.java:21150)
E/AndroidRuntime(20763): at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(20763): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(20763): at android.os.Looper.loop(Looper.java:148)
E/AndroidRuntime(20763): at android.app.ActivityThread.main(ActivityThread.java:5417)
E/AndroidRuntime(20763): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(20763): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
E/AndroidRuntime(20763): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
W/ActivityManager( 9660): Force finishing activity com.keramidas.TitaniumBackup/.MainActivity
It doesn't seem to be something that Titanium Backup does. Are you sure it's not a bug in the ROM?
Thanks,
Regards,
Titanium Track / Android support team
Download Google keyboard from the Playstore.What about gesture typing with the aosp keyboard. does that work ? or rather how can we get it to work ?
MMS can be fixed by going to the developers options and turn data always on.If anybody was curious MaxxAudio worked with this rom while I was running it. I was having problems downloading mms so I restored my nan. But I really liked running this rom! Well done.
Sent from my A0001 using Tapatalk
OK for some reason I'm getting a LOT of SODs out of no where! I had to reflash the rom cause my camera wasn't working and now every few hours I get an SOD or the phone freezes. Anything to fix this as most of u guys don't have this prob
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
(maybe I should get a monospace font in Firefox)Feature - Working on Stock camera - OppoCamera port - CameraNextMod?
Switching front/back cam - No - Yes - Yes
Camcorder <=1080p - No - Yes - Yes
4K Recording - No - No - Yes
1. Kernel Compatibility
The kernel of this ROM is based on CM12.1, but not exactly the same. You can not use kernels built for CM12.1 with this ROM. Marshmallow requires new features like updated SELinux, uid_cputime, etc, but CM12.1 source does not contain these features. You can take a look at commits and it will be clear.
2. Recovery Compatibility
I am using TWRP 2.8.7.0 with MultiROM support (TWRP_multirom_bacon_20150803-00.img from MultiROM thread). If you can not get the ROM installed properly, please try updating your recovery.
3. Rooting
Since this is a experimental build,I have turned off SELinux completely.SELinux is permissive. Just flash SuperSU 2.50 zip in the recovery and it will be fine.
4. F2FS Support
The kernel has F2FS driver builtin and corresponding entries in fstab file (as CM does). Vold has F2FS files as well, so you can give it a try. But I can not guarantee that it will work flawlessly.
EDIT: Some people tested and reported it not working. Make a backup before you try.
5. GApps
I'm using DeltaGapps with SetupWizard removed (yes it is the one that keeps force closing. you can disable that via adb as well). I think the lack of permissions(appops_whitelist.xml I guess) caused this failure. After allowing every permission required by Google apps and adding the account manually, Sync and Store works as expected. Now on Tap seems broken. Maps is working, and gets a lock in secs..
There are some other GApps package links in the first few pages. Some people say Now on Tap works with them, you can have a try.
6. Disabling HW Keys and Enabling Softkeys - The Easy Way
Code:echo qemu.hw.mainkeys=0 >> /system/build.prop reboot # enables soft keys echo 0 > /proc/touchpanel/keypad_enable # disables hw keys, need to do this on every boot
7. Where Is The App Switcher?
If you are comfortable with softkeys, goto 6.
If you are not,goto 3 and take a look at http://xdaforums.com/showpost.php?p=63313126&postcount=115double tap the home key.
8. LCD Density
Above will lead to corrupted pics.Code:wm density 440 # if you want 440 wm density reset # self-explanatory
Change
toCode:ro.sf.lcd_density=480
(Note: I did this before installing GApps, not sure if this is related to Google Now Launcher FCs)Code:ro.sf.lcd_density=VALUE_YOU_WANT
9. DT2W WorkaroundDT2W has been added into settings since 20151027.
Then add this line to /system/usr/keylayout/Generic.kl:Code:echo 1 > /proc/touchpanel/double_tap_enable # do this on every boot
Code:key 255 POWER
10. Apps Not Working
Settings -> Apps -> YOUR_APP -> Permissions -> Turn on everything
11. Fixing random freezes
http://xdaforums.com/showpost.php?p=63378883&postcount=682
Thanks @The Dork Knight Rises
I am in the process of testing a modified zip. Mods include:
-All assert type lines removed from updater-script. Hence you can flash on any firmware (OR EVEN ON ANY DEVICE. MAKE SURE YOU FLASH ON ONEPLUS ONE ONLY)
-Removed verification AFTER flashing hence the zip is directly flashable as secondary in MultiROM
-Enables software Navigation Bar automatically. (If you don't want it, delete 'qemu.hw.mainkeys=0' line in /system/build.prop or set value to 1)
If it flashes successfully (should take a while, ama wipe caches and all), it should be up within half an hour. :good:
EDIT: Modified zip without build.prop hack worked, but second version failed. Probably cuz edited on phone. Will try on PC.
(Sad news: I still have freezes :crying