Hello, i'm new her, so i see that the oneplus one rom has been released in Find 7a android development, i was wondering how to install it and how to install the updates? thx...
http://phandroid.com/2014/05/14/you...d-7a-into-a-oneplus-one-with-cyanogenmod-11s/
We have prepared an easy to flash package over at xda.
Everything works fine except NFC and the camera (which works halfway).
Gesendet von meinem One mit Tapatalk
Related
I know cm12.1 has become official just a few days ago, but I wonder if the cm13 branch is planned. Many cyanogenmod supported devices are preparing cm13, is g4 joining them? A
antastik said:
I know cm12.1 has become official just a few days ago, but I wonder if the cm13 branch is planned. Many cyanogenmod supported devices are preparing cm13, is g4 joining them? A
Click to expand...
Click to collapse
If the lg 6.0 releases official maybe few day-week
As far as I am aware, whilst other supported devices are preparing cm13, none have been released yet. The two main devs working on cm12.1 are doing just that (I believe). You would have to ask them directly but I think the focus is to get 12.1 working properly (it's already close mind) before thinking about cm13.
I would hazard a guess that it's not days away but weeks or maybe a couple of months.
LG Android Marshmallow V20a source code on opensource.lge.com
Here: http://opensource.lge.com/osSch/list?types=ALL&search=h815
First fix the tree then we will working on mm
Sent from my LG-H815 using Tapatalk
genesixxbf3 said:
First fix the tree then we will working on mm
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Thank you, is timeline weeks or months?
By the way, does cm12.1 support raw images capture?
I appreciate your work so much
antastik said:
Thank you, is timeline weeks or months?
By the way, does cm12.1 support raw images capture?
I appreciate your work so much
Click to expand...
Click to collapse
No disrespect but you should know asking for an ETA is usually frowned upon.
In my opinion they do it right to end work on 12.1 first. And take a look at the 12.1 ROMs, that's an amazing work they're doing! Thanks for that.
Gesendet von meinem LG-H815 mit Tapatalk
Hello,
I am using an Elephone P8000.
My car is equipped with Android Auto/Mirrorlink.
Is it possible to get Android Auto working on the P8000 ?
What about Mirrorlink?
Thanks in Advance!
The radio must support Android Auto. If it does, then it automatically supports Mirrorlink. However, your phone must be MirrorLink compatible too. You will need to check with the manufacturer of your phone.
As described above my carradio is equipped with Apple CarPlay/Android Auto/Mirrorlink.
I installed the Android Auto -App on my P8000, connected it via USB with my Radio, searched for devices --> nothing happens.
Using a friends' S6 wasn't a problem, so it seems its a general problem with the P8000.
I guess that the stock rom (also ERAGON ROM) are not equipped with the necessary files.
BeneXVI said:
As described above my carradio is equipped with Apple CarPlay/Android Auto/Mirrorlink.
I installed the Android Auto -App on my P8000, connected it via USB with my Radio, searched for devices --> nothing happens.
Using a friends' S6 wasn't a problem, so it seems its a general problem with the P8000.
I guess that the stock rom (also ERAGON ROM) are not equipped with the necessary files.
Click to expand...
Click to collapse
I had the same issue the first time I connected my phone which is running the last Eragon 9.0.
Then I switched off USB-debug and played a bit with type of USB connection and the Android Auto setup started,
I got the black screen on my phone with the white label of Android-Auto but on the car it's just a black screen.... Nothing else.
It seems that many user experieced the same, even with stock or FlyMe:
http://bbs.elephone.hk/thread-9222-1-1.html
I'm wondering if the great @skeleton1911 has any idea or experience if something is missing in the ROM...
scaltro said:
I had the same issue the first time I connected my phone which is running the last Eragon 9.0.
Then I switched off USB-debug and played a bit with type of USB connection and the Android Auto setup started,
I got the black screen on my phone with the white label of Android-Auto but on the car it's just a black screen.... Nothing else.
It seems that many user experieced the same, even with stock or FlyMe:
http://bbs.elephone.hk/thread-9222-1-1.html
I'm wondering if the great @skeleton1911 has any idea or experience if something is missing in the ROM...
Click to expand...
Click to collapse
Hi.
The Problem is that the source of the p8000 is not released from elephone Side. . I know that this is a weird bug and the same could happen via Bluetooth..
Because the source is not released . me or the flyme dev or the Nexus rom dev ,can not compare it with Google's source , nor fix it...
But what I can try is. I have also an Elephone m2 . maybe there it works.. I will check it and if yes . I could try to port the necessary files....
Cheers
Gesendet von meinem Elephone P8000 mit Tapatalk
skeleton1911 said:
Hi.
The Problem is that the source of the p8000 is not released from elephone Side. . I know that this is a weird bug and the same could happen via Bluetooth..
Because the source is not released . me or the flyme dev or the Nexus rom dev ,can not compare it with Google's source , nor fix it...
But what I can try is. I have also an Elephone m2 . maybe there it works.. I will check it and if yes . I could try to port the necessary files....
Cheers
Gesendet von meinem Elephone P8000 mit Tapatalk
Click to expand...
Click to collapse
Super!!!
Let us know if you have any luck!
Maybe this can help http://forum.xda-developers.com/general/paid-software/android-4-1-headunit-android-auto-t3125252
Many thanks for being on top of it... as always
Another one here, I own an Elephone p7000, so I guess the solution could be the same
..
skeleton1911 said:
Hi.
The Problem is that the source of the p8000 is not released from elephone Side. . I know that this is a weird bug and the same could happen via Bluetooth..
Because the source is not released . me or the flyme dev or the Nexus rom dev ,can not compare it with Google's source , nor fix it...
But what I can try is. I have also an Elephone m2 . maybe there it works.. I will check it and if yes . I could try to port the necessary files....
Cheers
Gesendet von meinem Elephone P8000 mit Tapatalk
Click to expand...
Click to collapse
Did you find the necessary files in the M2 or Zopo?
skeleton1911 said:
Hi.
The Problem is that the source of the p8000 is not released from elephone Side. . I know that this is a weird bug and the same could happen via Bluetooth..
Because the source is not released . me or the flyme dev or the Nexus rom dev ,can not compare it with Google's source , nor fix it...
But what I can try is. I have also an Elephone m2 . maybe there it works.. I will check it and if yes . I could try to port the necessary files....
Cheers
Gesendet von meinem Elephone P8000 mit Tapatalk
Click to expand...
Click to collapse
it could be great mate!
Hi folks,
i just managed my P8000 (P8000_20160319 ROM) to work with Android Auto.
I manually installed Android Auto 1.6.226040 (2710411-release), my Elephone just stuck to the old 1.5.100945 (2462389-release) Version.
My P8000 also was stuck on the old android Auto version.
Installed your mentioned version, doesn't work for me with latest eragon version
Timmey22 said:
Hi folks,
i just managed my P8000 (P8000_20160319 ROM) to work with Android Auto.
I manually installed Android Auto 1.6.226040 (2710411-release), my Elephone just stuck to the old 1.5.100945 (2462389-release) Version.
Click to expand...
Click to collapse
Super, I was stuck at the old version as well.
After v. 1.6 was installed, I verified and Andorid Auto is now working
verified on CM12.1 build#6 by the great @BlueFlame4
Hi. I'm having a question before buying a note 7 if someone can help : knowing that it's still on stock ROM but updates were disabled vie package disabler so battery still at 100% will I be able to do the same after the phone will be restored as original by the seller ? Will I be able to disable the updates if I will find an old version of package disabler? Or I 'll be force to install a custom ROM ? Thx
Caius_Marius said:
Hi. I'm having a question before buying a note 7 if someone can help : knowing that it's still on stock ROM but updates were disabled vie package disabler so battery still at 100% will I be able to do the same after the phone will be restored as original by the seller ? Will I be able to disable the updates if I will find an old version of package disabler? Or I 'll be force to install a custom ROM ? Thx
Click to expand...
Click to collapse
Hi.
You can install the shield from the Alliance Note 7 or you can install an app that don't need root to disable packages...
Envoyé de mon SM-N950F en utilisant Tapatalk
Merci!
I just followed the solid explorer method and is working fine to stop the update.
So for now Im fine with it, discovering my new phone but I wont stay too long on stock 6.0.1. I guess there is a ROM with nougat ported from FE that I ll try someday. Can you confirm that is working fine? I dont care about iris, I wear glasses
Coming from note 5 the 7 is really nice, great phone that Samsung shouldnt kill. I compared it in a store with the 8 which is way too big although I am 6ft tall so I ll stay with 7 while it lasts. If FE will get oreo maybe someone will ported here.
A+
Envoyé de mon SM-N930F en utilisant Tapatalk
Does anyone know weather the Tech Gods will make the FE ROM available for the Snapdragon Note 7 variants? Or if they already have and I need to spend more then 2 hours reading through these forums?
Hi,
I have upgraded my Pixel2XL from the last P beta to final Pie by fastboot-flashing the factory image (without wiping) somes days ago. As I'm experiencing a problem with a specific app, I tried to downgrade to the last Android beta by flashing the beta image. But then my Pixel2XL was just bootlooping. Wiping cache didn't help. After reflashing final Pie, my Pixel2XL is running fine again.
So, isn't it possible to downgrade to the last Android beta? Or what have I done wrong?
Thanks in advance!
Gesendet von meinem Pixel 2 XL mit Tapatalk
if you havent previously done fastboot flashing unlock_critical you will need to do so in order to downgrade.
This will wipe your phone, there is no way around it.
Hm, I have done that the day I got my Pixel 2 XL some months ago...
Gesendet von meinem Pixel 2 XL mit Tapatalk
Hello everyone, just a two questions:
Is it possible to reduce minimal brightness without root?
Also, is it possible to install custom kernels without unlocking the bootloader? (i depend on a locked bootloader for a few apps)
Greets!
Gesendet von meinem Pixel 3 XL mit Tapatalk