Related
Hey all,
As I don't develop CyanogenMod or work for their team, I didn't think it'd be right to make a post in the Development sub-forum. Anyway, I came across a post over on Android Police stating that CM 13 Nightlies are now availble for 'manta'. I've downloaded the latest Nightlie and flashed it on my Nexus 10 along with the lastest Gapps, and everything works great. You can find the Nightlies here. All credit goes to the CyanogenMod team for keeping our Nexus 10 alive!
In my case the gapps are too big (even micro and nano) while pico gets successfully flashed but then Google Play Services crash all the time.
Did you flash the very first nightly from Jan 9?
I have the same issues: nano gapps too large for system, can't install this way... any solutions?
Edit: pico gapps work, no issues so far
I can't even install the pico gapps. Which package did you use OP?
Edit: Tried again with a full wipe and it worked using the pico-apps. Have had no crashes of any Google services so far. I used the latest CM nightly to flash.
rxzlmn said:
I can't even install the pico gapps. Which package did you use OP?
Edit: Tried again with a full wipe and it worked using the pico-apps. Have had no crashes of any Google services so far. I used the latest CM nightly to flash.
Click to expand...
Click to collapse
Did it fail with the nightly from Jan 9 but then succeeded witht he nightly from today (Jan 10)?
Dimitris CH said:
Did it fail with the nightly from Jan 9 but then succeeded witht he nightly from today (Jan 10)?
Click to expand...
Click to collapse
I used the newer one both times. Only difference was full wipe.
I'm having zero luck on getting Google Play Services installed. Tried the nano, now the Pico. Same as above users, the install will go just fine but will give me crashes every second on screen.
I read here and there that this crash on CM13 (other devices) can also be caused by a) Privacy Guard settings for Google Play services, or b) allowing Google Play Services to access "Phone" and "Contacts" or something to that effect.
Still playing around trying to get this to install.......
Edit: Did a full wipe of everything, including System/Data, and it all works now. I'm all setup! I'm getting an error on Google "Now on Tap", saying "The app has stopped" everytime I try to use it. I remember seeing the fix somewhere about something in Accessibility settings. But I'm having no luck remembering what it was or finding the fix again.
DTB
Google play services were not working for me at first either. I decided to try and sideload the latest Google Play Services apk to see if would fix the problem. Thankfully, it did fix it. You can find the apk file here.
Install Opengapps nano or pico http://opengapps.org/ and full wipe before install.
http://review.cyanogenmod.org/#/c/127116/
Anyone tried enabling f2fs?
Good news, finally got "Now on Tap" working.
I went to settings. I searched for "Assist", and selected "Assist and Voice Input".
(I honestly can't find in the settings where it is, I can only find it by searching within settings.)
The "Assist App" was set to "Google App". I selected "None", then went back and set it to "Google App" again...and all was good!
So, looks like I am finally up and running. Another note; the Marshmallow apps restore didn't seem to restore for me. I even used my phone to setup my account, all was linked fine. It got my identity and set it, but did not restore any apps. Not a huge deal.
DTB
viruszzz said:
Install Opengapps nano or pico http://opengapps.org/ and full wipe before install.
Click to expand...
Click to collapse
I guess you did not read the part where we said that this is exactly what we did.
1GB RAM
I succesfully installed CM13 with Opengapps pico and its running very smooth so far. But in settings it's showing me that I only have 1GB of RAM instead of 2GB. Did anyone else notice this?
Edit: 1,1GB to be exact. Very strange.
Edit 2: I read in another thread that about 900MB is reserved for the GPU so that's probably why it is showing just 1,1GB for the system.
Hei, ref doing a full wipe, is that before doing the pico gapps install, and exactly what is meant by full wipe? Thanks
Cintra2 said:
Hei, ref doing a full wipe, is that before doing the pico gapps install, and exactly what is meant by full wipe? Thanks
Click to expand...
Click to collapse
Yes before installing Pico. I did a wipe after too, just to be sure. A full wipe means cache and system/data. If you have TWRP a normal wipe includes all of this.
MisterT200 said:
Yes before installing Pico. I did a wipe after too, just to be sure. A full wipe means cache and system/data. If you have TWRP a normal wipe includes all of this.
Click to expand...
Click to collapse
Many thanks for your quick reply, now I'll give it another go
Mvh
PS That did the job All working very well now!
Does CM13 support loop device?
I need to run linux chroot (via linux deploy); that requires that the ROM supports loop device. Request to those who have successfully install CM13 on N10: Could you install the free app "loop device checker" and check to see if loop device is supported?
THANKS!
ps. This app is free and useful but it has annoying loud music; mute the speaker first
After installing CM13, my Nexus10's rotation doesn't work.
When I used stock lollipop, rotation worked perfectly.
Even if I update to the newest version, it's the same here. (cm-13.0-20160129-NIGHTLY-manta)
Does anyone have the same problem?
Cintra2 said:
Many thanks for your quick reply, now I'll give it another go
Mvh
PS That did the job All working very well now!
Click to expand...
Click to collapse
Hey, down the page, you should be able to fit bigger packages than pico on there.
http://forum.xda-developers.com/nexus-10/development/rom-aicp-11-manta-t3280678/page18#post65047967
Youtube 1440p videos
For some reasons with the 02/09/2016 release I'm able to run YouTube video at 1440p, but after updating to newer releases it isn't the case anymore, instead I have the same problem as with Google's official releases the videos run for 1s then stops while the audio still runs normally.
I rooted my Moto E LTE 2015 from Virgin Mobile and installed CyanogenMod 13 Marshmallow. I have noticed a few problems.
1. Unable to write to internal or external storage.
2. Settings force close upon opening carrier settings in settings.
3. Performance settings don't always stick.
4. Battery settings sometimes force close in settings.
5. Random reboots.
When is a stable build going to be available? I'd like to know.
Meantime you can use
AICP 6.0 Rom
Chisty_143 said:
Meantime you can use
AICP 6.0 Rom
Click to expand...
Click to collapse
I've discovered why Battery Settings force close...
CM13 has bugs with it's builtin theme engine. Still have most of the other problems though.
Thanks for the suggestion, I'll check it out sometime.
Well cm13 is actually very stable and bugless for most users. I think something might have gone wrong with installation. The internal storage problem might be a kernel issue and not a cm13 one, I'd try updating the kernel and if that doesn't solve anything full wipe and install everything again.
Heyo, guys. I wanna show u my own ROM based on LineageOS 14.1.
Flash it as u flash another ROMs:
Wipe System, data, caches
Flash ROM
Flash Gapps
Flash SuperSu if u want
For update just do dirty flash.
Hope that u'll like this ROM.
Download link:
AFH
Big thanks to @romilparh who was the first man who helped me with beginning things.
Thanks to @jhalayashraj who taught me some things
Thanks to @amardeep434 who also helped me a lot
Thanks to @danieldmm who also helped me with a lot of things
Also thanks to @TechExhibeo my sensei who can help with ton of problems and advise smth
And thanks @jgcaap for some interesting things on github.
LineageOS
Kernel
Device
Have a good use and thanks
umm.. First?
EDIT: Hey Oleg, nice to see your CM. Will download asap.
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
thank u very much for this awesome rom.
Wow this ROM is awesome! I just saw LineageOS 14.1 for the OnePlus One yesterday. No bugs so far, It seems really stable and a great and probably the best daily driver ROM.
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
i'm not facing any problem with AdAway and viper in 20170109 build.
NeolWhyt said:
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
Click to expand...
Click to collapse
Probably u're doing smth wrong...
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
Doesn't have any problem. All is ok.
Okeys said:
Doesn't have any problem. All is ok.
Click to expand...
Click to collapse
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Sent from my A0001 using Tapatalk
nolsen311 said:
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Click to expand...
Click to collapse
Viper is still included. Just change SELinux mode. I'll change on needed later.
Have a good use
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
f2sf it's supported?
hyper_davide said:
f2sf it's supported?
Click to expand...
Click to collapse
Now not.
ppp99 said:
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
Click to expand...
Click to collapse
All in ext4?
Okeys said:
All in ext4?
Click to expand...
Click to collapse
Just checked, YES.
https://www.androidfilehost.com/?w=files&flid=132556
Thanks so much Okeys! this is the best ROM I could find so far, it works so perfectly!!
Summary of my attempts:
(1)I tried "lineage-14.1-20170130-nightly-bacon-signed.zip" from lineageos
* lower kernel: 3.4.112
* not support system root, need install supersu.
* System APP: "SoundRecorder" and "Screencast" were merged and replaced with "Recorder", I don't like the new "Recorder", the recorder file is much bigger than "SoundRecorder"
(2)I tried "RR-N-v5.8.1-20170131-bacon-Official.zip" from remix
* Same as lineage above
* Support system root option, not need supersu
(3)lineage-14.1-20170126-Okeys-bacon.zip
* new kernel: 3.4.113
* not support system root, need install supersu.
* keep the original "SoundRecorder" and "Screencast"
* The only problem I met is "Left Wipe" doesn't switch to "Google" with Pixel Launcher for Andriod 7.1, but I find a solution and fixed it.
** see my post: https://forum.xda-developers.com/oneplus-one/help/fix-left-wipe-doesnt-switch-to-google-t3549497
Please change to coloros blobs dude
20170202 Bacon Gesture Settings
lineage-14.1-20170202-Okeys-bacon flashed a few minutes ago. Noticed that the Gestures settings no longer allows control over music and camera gestures. They are on by default, and I guess can no longer be turned off.
Hope this helps,
E.
Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Shoury_Jain55 said:
Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Click to expand...
Click to collapse
This is caused due to franco kernel on an older patch. Nothing really worth worrying about.
MyNameIsRage said:
This is caused due to franco kernel on an older patch. Nothing really worth worrying about.
Click to expand...
Click to collapse
Umm okay, so what should I do now? By the way, thanks...
Shoury_Jain55 said:
Umm okay, so what should I do now? By the way, thanks...
Click to expand...
Click to collapse
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
greenys' said:
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
Click to expand...
Click to collapse
Wow. Thanks, I would definitely try those...
greenys' said:
I wouldn't trust my life (android device) on franco kernel for now. If I were you I'd download latest Lineage Rom, latest gapps, Magisk vcustom version that supports treble enabled roms, then kud kernel. Put them on an external sd or file storage, completely wipe my phone except the external part of it, then flash them in the said order. Franco kernel been updated quite a while ago. Since then lots of things have changed in the aosp based roms. The kernel might cause those problems of yours. Also first of all, before doing anything I'd flash latest Orange Fox Treble enabled recovery R6 beta, which solves some flashing issues. This is what I'd do to solve those problems of yours within 10 minutes. But it's just me, a purist being real and being safe than sorry.
Click to expand...
Click to collapse
Bro noting hepled me... What's should I do now, it was working fine for a few days but now I m back with the same problem...
Shoury_Jain55 said:
Bro noting hepled me... What's should I do now, it was working fine for a few days but now I m back with the same problem...
Click to expand...
Click to collapse
Did you try everything I wrote above? These steps should work in case you badly messed up your system. I mean, I fiddle and meddle with my OS all the time, often rendering my phone unusable. As much that I have to clean wipe and reinstall the whole OS following the steps I provided. There was no case when a whole, system wide wipe and a clean install wouldn't solve.
greenys' said:
Did you try everything I wrote above? These steps should work in case you badly messed up your system. I mean, I fiddle and meddle with my OS all the time, often rendering my phone unusable. As much that I have to clean wipe and reinstall the whole OS following the steps I provided. There was no case when a whole, system wide wipe and a clean install wouldn't solve.
Click to expand...
Click to collapse
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Shoury_Jain55 said:
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Click to expand...
Click to collapse
Perhaps I can give you one more tip that you can try.
First, if you have an external SD card make sure to copy latest stable global MiUi ROM, latest Lineage OS for mido, latest open gapps, kud kernel, Magisk 16.0 treble enabled and orange fox onto it. If not then download these to your pc or laptop.
1) Make a full wipe including system, data, vendor, cache, dalvik and internal storage.
2) From TWRP flash latest MiUi stable global rom.
(if you have external SD do it from there, if you don't, since you made a full wipe, your internal SD is empty. Through USB sideload copy MiUi onto your internal SD and flash it from there if you don't have an external SD with the flashable zips on it)
3) Boot up the system, make sure everything is working.
4) Reboot to TWRP and do a full wipe again.
5) Flash Lineage OS from your external SD or copy the required zip onto your internal SD through USB sideload.
6) Now flash latest gapps (pico is far enough)
7) Flash Kud Kernel
8) Flash Magisk 16.0 treble enabled or magisk vcustom, they are the same but more stable than 16.7 which is still beta.
9) Reboot to system and see for yourself if everything is working.
I hope this solves your problem. Sometimes if you flash back MiUi it solves some crash perhaps firmware related problems. I don't know but this helped me a few times. If you messed up something USB sideload is always an option to copy any flashable zip onto your internal SD, however I always use external SD for it's easy to trust and use.
In case your data/internal SD shows 0 kb/mb free space do a data wipe and a partition from special settings in TWRP with all sizes set to 0.
I don't have any more tips to help you. Sorry.
I would say get Orangefox or Redwolf recovery if you dont have them already. Try flashing any rom and see if your problem persists,if not flash magisk and custom kernels. With the process of elimination you should know the source of the problem which i think is francokernel as it was mentioned.
greenys' said:
Perhaps I can give you one more tip that you can try.
First, if you have an external SD card make sure to copy latest stable global MiUi ROM, latest Lineage OS for mido, latest open gapps, kud kernel, Magisk 16.0 treble enabled and orange fox onto it. If not then download these to your pc or laptop.
1) Make a full wipe including system, data, vendor, cache, dalvik and internal storage.
2) From TWRP flash latest MiUi stable global rom.
(if you have external SD do it from there, if you don't, since you made a full wipe, your internal SD is empty. Through USB sideload copy MiUi onto your internal SD and flash it from there if you don't have an external SD with the flashable zips on it)
3) Boot up the system, make sure everything is working.
4) Reboot to TWRP and do a full wipe again.
5) Flash Lineage OS from your external SD or copy the required zip onto your internal SD through USB sideload.
6) Now flash latest gapps (pico is far enough)
7) Flash Kud Kernel
8) Flash Magisk 16.0 treble enabled or magisk vcustom, they are the same but more stable than 16.7 which is still beta.
9) Reboot to system and see for yourself if everything is working.
I hope this solves your problem. Sometimes if you flash back MiUi it solves some crash perhaps firmware related problems. I don't know but this helped me a few times. If you messed up something USB sideload is always an option to copy any flashable zip onto your internal SD, however I always use external SD for it's easy to trust and use.
In case your data/internal SD shows 0 kb/mb free space do a data wipe and a partition from special settings in TWRP with all sizes set to 0.
I don't have any more tips to help you. Sorry.
Click to expand...
Click to collapse
Still didn't work
Maybe there is some hardware problem...
Well, thanks for the help! ?
Shoury_Jain55 said:
Still didn't work
Maybe there is some hardware problem...
Well, thanks for the help!
Click to expand...
Click to collapse
Oh, well. Perhaps you're right. I do this every week and works. I'm sorry I couldn't help you.
Shoury_Jain55 said:
Hello everyone!
Pls help me on this one...
I have:
- unlocked Boot loader
- installed Twrp 3.2.1 vendor patch
- installed Magisk 16.0
- flashed DotOs 2.4 treble ROM
- installed Franco kernel (fk6)
on my Redmi Note 4 (mido).
The problem is:
- whenever I reboot my device a message appears from DotOs System which says: There is an internal problem in your device. Please contact your manufacturer.
- whenever I play Pubg mobile, my phone usually reboots... And these random reboots occur not only in pubg but also in other apps if I try to multitask or click the buttons fastly or try to use my phone very quickly.
Please help me guys.
-Thank You:good:
Click to expand...
Click to collapse
Wrong forum.
Go to DotOs forum, and ask your question.
Mybe your rom not compatible for mido.
Shoury_Jain55 said:
Yep...
Installed lineage 15.1
Kud kernel
Magisk 16.7
Orange fox recovery
Still it redboots randomly sometimes...
Click to expand...
Click to collapse
Probably Cpu throttling service asks for increase in cpu frequency due to the requirement , but when the cpu frequency is scaled up high , but due to some internal problem (temperature sensor failure or faulty processor etc...) the temperature detected is too high that the phone reboots.
TBH I have no idea about how android devices work but this happens on PS4 due to burnt capacitors , this can be fixed sometimes.
Buddy I will help u...
Just download the build.prop editor from playstore and grant root permission and search for ro.treble.enabled line and change it to false:fingers-crossed:
rc chanu said:
Buddy I will help u...
Just download the build.prop editor from playstore and grant root permission and search for ro.treble.enabled line and change it to false:fingers-crossed:
Click to expand...
Click to collapse
Thank you bro, works for me.
Very nice!!!
Hi,
In the last few days, I've been testing several ROMs on my Mi Pad 4: MIUI, AOSP-based ROMs (such as LineageOS) and Mokee, which (for some reason) my unit came preinstalled with.
I've noticed that some things don't work on some custom ROMS, but do work on others. For example: encryption, MTP and the notification light work on Mokee but don't work on AOSP-based ROMs, and double tap to wake works on MIUI but doesn't work on any of the other ROMs.
I've seen some other problems fixed by tweaking build.prop, so maybe there's something in those ROMs' Vendor partitions that can be used to fix those issues in the other ROMs? I'd really like to get everything working when a 9.0 AOSP-based ROM comes out, so... what do you think?
MTP works on mokee? Going to try mokee next.
I think there's not much developers for this device because it's still new and it's not available worldwide.
I saw this on the treble forum, maybe can try.
How to fix mtp:
Enable developer settings (Please google to know if you don't know)
Scroll down to select Default USB Configuration
Select File Transfer
bradputt said:
MTP works on mokee? Going to try mokee next.
Click to expand...
Click to collapse
It does, you can try it here. https://download.mokeedev.com/?device=clover
bradputt said:
I think there's not much developers for this device because it's still new and it's not available worldwide.
Click to expand...
Click to collapse
Yeah, I know. But maybe we can try to make the most of what little we have.
bradputt said:
How to fix mtp:
Enable developer settings (Please google to know if you don't know)
Scroll down to select Default USB Configuration
Select File Transfer
Click to expand...
Click to collapse
That won't work, it just ignores the preference you set.
there's an update on Phh-Treble ROM!
i flashed this and MTP/SD card storage works now.
this is almost 99% working rom for me .... :highfive:
link:
https://github.com/phhusson/treble_experimentations/releases/tag/v23
bradputt said:
there's an update on Phh-Treble ROM!
i flashed this and MTP/SD card storage works now.
Click to expand...
Click to collapse
The last time I used that ROM Google apps (including the Play Store) would crash on me, leaving the device unusable, so I have to use LOS instead. Have they fixed that?
frandavid100 said:
The last time I used that ROM Google apps (including the Play Store) would crash on me, leaving the device unusable, so I have to use LOS instead. Have they fixed that?
Click to expand...
Click to collapse
i never have any problem with playstore or any apps..... did you install gapps separately?
i used this zip file, gapps and roots comes by default.
https://github.com/phhusson/treble_...wnload/v23/system-arm64-aonly-gapps-su.img.xz
bradputt said:
i never have any problem with playstore or any apps..... did you install gapps separately?
i used this zip file, gapps and roots comes by default.
https://github.com/phhusson/treble_...wnload/v23/system-arm64-aonly-gapps-su.img.xz
Click to expand...
Click to collapse
Yes, I always use that, and they always end up crashing.
frandavid100 said:
Yes, I always use that, and they always end up crashing.
Click to expand...
Click to collapse
That's strange, maybe you should try wipe everything and flash again.
Or wait for LOS to upgrade to latest version