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.
Hi, today I'm bringing you a fix for the error 70 that will come up after installing google apps in TWRP because of system partition space problems.
You will have to follow this steps:
- Go to the recovery menu and do a factory reset.
- Search the ROM and install it.
- (This is a very important step for it to work). Go to TWRP recovery and select wipe.
- Then go to Advanced Wipe.
- Once you are there, select System partition and click repair or change file system.
- Some options will come up, and select Resize File System.
- Once you have followed all these steps you can nos install all google apps without problem.
If you still have any issue or problem dont hesitate to comment, and I will try to help you. Thanks!
Credits: @javiblader17 (Ak as JAVIX)
Fix Error 70 Gapps in TWRP (Marshmallow)
Hi, today I'm bringing you a fix for the error 70 that will come up after installing google apps in TWRP because of system partition space problems.
You will have to follow this steps:
- Go to the recovery menu and do a factory reset.
- Search the ROM and install it.
- (This is a very important step for it to work). Go to TWRP recovery and select wipe.
- Then go to Advanced Wipe.
- Once you are there, select System partition and click repair or change file system.
- Some options will come up, and select Resize File System.
- Once you have followed all these steps you can nos install all google apps without problem.
If you still have any issue or problem dont hesitate to comment, and I will try to help you. Thanks!:good:
Credits: @javiblader17 (Ak as JAVIX)[/QUOTE]
Thank you, good job.
Enviado desde mi XT1543 mediante Tapatalk
Thanks I had this problem with a friend's device. I installed pico gaaps and also It worked
thanks
This is muy video for fix error 70 TWRP
Link:http://www.dailymotion.com/video/x3sit55
Thanks a lot
It won't increase the size,
javiblader17 said:
Hi, today I'm bringing you a fix for the error 70 that will come up after installing google apps in TWRP because of system partition space problems.
You will have to follow this steps:
- Go to the recovery menu and do a factory reset.
- Search the ROM and install it.
- (This is a very important step for it to work). Go to TWRP recovery and select wipe.
- Then go to Advanced Wipe.
- Once you are there, select System partition and click repair or change file system.
- Some options will come up, and select Resize File System.
- Once you have followed all these steps you can nos install all google apps without problem.
If you still have any issue or problem dont hesitate to comment, and I will try to help you. Thanks!
Credits: @javiblader17 (Ak as JAVIX)
Click to expand...
Click to collapse
thnx . it worked now ...
thanku very much
Doesn't work for me, trying to update this phone for my girl. Followed your instructions, and the video. Still insufficient storage...
Hello
@javiblader17
I am using Xiaomi Redmi 1s (Armani) on Ressurection Remix.
When i am trying to install Mokee Rom (Marshmallow) the gapps (Pico version) fails saying error code 70.
I tried you method too..i get 31 mb left in the system partition after flashing just the mokee rom..Resizing doesn't work...plz help!!
nimesh.batra93 said:
@javiblader17
I am using Xiaomi Redmi 1s (Armani) on Ressurection Remix.
When i am trying to install Mokee Rom (Marshmallow) the gapps (Pico version) fails saying error code 70.
I tried you method too..i get 31 mb left in the system partition after flashing just the mokee rom..Resizing doesn't work...plz help!!
Click to expand...
Click to collapse
Even i am getting same problem installed Mokee and now cant even install pico gapps. error 70 tried the instructions in the video but no solution please help.
pkgoyal said:
Even i am getting same problem installed Mokee and now cant even install pico gapps. error 70 tried the instructions in the video but no solution please help.
Click to expand...
Click to collapse
i am searching for the solution..i will update this thread if i find one..
there is a way to increase system partition but its too complicated..
nimesh.batra93 said:
i am searching for the solution..i will update this thread if i find one..
there is a way to increase system partition but its too complicated..
Click to expand...
Click to collapse
Hi i have installed the latest nightly build of Mokee and Gapps Pico and it worked. Only the issue is batter is draining faster because of media server. downloaded the mediaserver killer app and it worked
Installed nightly today only..have you tried updating via OTA zip file?
Edit: it doesn't work!
nimesh.batra93 said:
Installed nightly today only..have you tried updating via OTA zip file?
Edit: it doesn't work!
Click to expand...
Click to collapse
installed mokee Marshmallow MK60.1-armani-160726-RELEASE and can't install gapps (redmi 1s 31MB free space)... it seems the developer didn't tested it before release.... Or we don't know how they can install it on their device LOL
joe200 said:
installed mokee Marshmallow MK60.1-armani-160726-RELEASE and can't install gapps (redmi 1s 31MB free space)... it seems the developer didn't tested it before release.... Or we don't know how they can install it on their device LOL
Click to expand...
Click to collapse
Thats what i was thinking too..we have the same device..same fioe to download.. but only few came up with this issue..
Too confused about it...eager to know the solution too
@javiblader17: thank you so much!! I did not know which way to turn, many thanks!
joe200 said:
installed mokee Marshmallow MK60.1-armani-160726-RELEASE and can't install gapps (redmi 1s 31MB free space)... it seems the developer didn't tested it before release.... Or we don't know how they can install it on their device LOL
Click to expand...
Click to collapse
I repartitioned System, Cache, Use data..increased system partition..the thing is you have to use twrp 2.8.7.0
http://en.miui.com/forum.php?mod=viewthread&tid=183258&extra=page=1&page=1&mobile=2
javiblader17 said:
If you still have any issue or problem dont hesitate to comment, and I will try to help you. Thanks!:good:
Credits: @javiblader17 (Ak as JAVIX)
Click to expand...
Click to collapse
[/QUOTE]
Hi i have really n issue to get the Problem solved.
When i try to resize my system memory nothing changes -.-' ist there another way to change it??
Hello,
after flashing the new CM13 snapshot cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J2-i9300 I keep receiving the following error over and over again:
"[CRASH] com.google.android.gms threw java.lang.securityException
java.lang.SecurityException: "gps" location provider requires ACCESS_FINE_LOCATION permission.
at android.os.Parcel.readException(Parcel.java:1620)
at android.os.Parcel.readException(Parcel.java:1573)
at android.location.ILocationManager$Stub$Proxy.addGpsStatusListener(ILocationManager.java:741)
at android.location.LocationManager.addGpsStatusListener(LocationManager.java:1537)
at aepg.acom.google.android.gms:1045)
at aelu.bcom.google.android.gms:7362)
at aelu.handleMessagecom.google.android.gms:262)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.os.HandlerThread.run(HandlerThread.java:61)"
Most of the apps doesn't work either. Most of the Gapps don't work, too, reffering to this error.
I granted the permission for Location but this does't help either.
I don't know what to do. Help would be much appriciated!
Thanks.
Mike
Same problem here....
I tried a clean flash and also tried to install gapps directly after installing cm13. But no success. I keep getting this error message...
I have the same problem with S4.
flash newest/oldest gapps ?
exe98123q said:
flash newest/oldest gapps ?
Click to expand...
Click to collapse
directly downloaded from open gapps:
open_gapps-arm-6.0-nano-20160821
try old or dont use, you can download apk from mirrors (google is yours uncle )
the newest have some bug or high demand on resurences imo
edit.
try pico only, you no need nothing else
exe98123q said:
try old or dont use, you can download apk from mirrors (google is yours uncle )
the newest have some bug or high demand on resurences imo
edit.
try pico only, you no need nothing else
Click to expand...
Click to collapse
Tried pico - same problem.
Tried whiping cash, fresh install CM13, fresh install GApps - same problem.
I did however find apk mirrors, but installing them didn't work ("Parsingfehler")...? How do I install the APK other then uploading it to the phone? Did I choose the wrong apk? Which one do I use for my S3 i9300? I tried this one:
http://www.apkmirror.com/apk/google...es-9-4-52-438-127739847-android-apk-download/
Does this problem maybe have anything to do with this patch?!
https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0
Sorry, but I'm not an expert so I'd need support what to do with it.
Please help. I'm starting to get sick of this problem and thinking about switching back to CM11 if this is even possible (tried to do so once after CM13 - phone went to bootloop) ...
Thanks.
that apk you can install normal, only gaps
exe98123q said:
that apk you can install normal, only gaps
Click to expand...
Click to collapse
???
i mean cant, gapps include files .jar, not only gsm core
Does anyone have a solution for the problem? Still not working. As soon as I start any gapp the message appears again.
Please help.
Thanks
Meanwhyle I managed to solve the problem. This gapps seem to work fine in combination with the CM13 snapshot:
http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
1) whype system partition & cash
2) flash room (I used cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J2-i9300.zip (296.87 MB)
3) install gapps (see above)
4) reboot
At first it seemed to cause further FC, but somehow they disappeared (maybe after updating the apps) and now everything works fine (except GPS location in Google Maps, but this is my least problem).
I also foudn another provider of gapps, but didn't test it.
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Apps
I had the same problem I gave up in the end and I downloaded aptoide has the same apps that you get from the play store
http://forum.xda-developers.com/showthread.php?t=3276606
Try this.
Sent from my GT-I9300 using XDA-Developers mobile app
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery - use my twrp
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
sometimes FC in camera
LineageOS Builds
3. 20180719: cleanup, update hwui\dalvik settings, add bt codecs (aptx, aptx-HD, ldac) https://drive.google.com/file/d/1EDIZPh5SOa36nUErAvFBREzRAhZCtHGa/view?usp=sharing
2. 20180713: https://drive.google.com/file/d/1sItey9421ml2QSyTNQKn5s1frvjASdCc/view?usp=sharing
1. 20180712: https://drive.google.com/file/d/1FWoBISUpbPozdlqkuJxBh7fdksEg-yP9/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM64
Android: 8.1
Variant: any
Sources
Sources: https://github.com/Lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Device: https://github.com/Valera1978/android_device_samsung_gtaxllte
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxllte
Thanks
Thanks to LineageOS team
Finally, I had time to check whether it's possible to build a 64bit firmware on the exynos7870. Yes, we have 64bit kernel, but all stock firmwares were 32bit, as result I need a lot of missed 64bit proprietary files.
This is fully 64bit firmware, missed files from a5'17 (it's on exynos7880) - gralloc, gps, ril, gles (mali).
Only own audio\camera still 32bit, but in any case it's working great in 64bit firmware.
I wrote own sensors HAL, because it's very specific for each device, it's still buggy, i'm continue work on it.
Right now I need understand - do we need 64bit at all? I don't see any huge improves.
Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery - use my twrp
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
buggy sensors (accelerator and light)
LineageOS Builds
1. 20180712: https://drive.google.com/file/d/1FWoBISUpbPozdlqkuJxBh7fdksEg-yP9/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM64
Android: 8.1
Variant: any
Sources
Sources: https://github.com/Lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Device: https://github.com/Valera1978/android_device_samsung_gtaxllte
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxllte
Thanks
Thanks to LineageOS team
Click to expand...
Click to collapse
Congrats! I am test it asap!:good::good::good:
new version.
now I can say - it's stable.
sensors - done (back to stock sensors.universal7870.so with prebuild 32bit service for sensors)
flip - done
it's still sometimes fc on camera - I'll check it later
I can confirm it works on SM-T580 (WiFi only) as well. Everything seems to work fine; buttons, WiFi + BT, camera, audio, video (youtube), sensors, smart cover etc.
OpenGApps 8.1 ARM64 installed with no errors.
The only thing I noticed is during first boot screen it says in the top-left corner in red text: 'Kernel is not seandroid enforcing'. Maybe this is on SM-T585 as well.
On the SM-T580 you get unusable sim-card icon in the notification bar and some other places, but that is to be expected.
sanchaz12 said:
I can confirm it works on SM-T580 (WiFi only) as well. Everything seems to work fine; buttons, WiFi + BT, camera, audio, video (youtube), sensors, smart cover etc.
OpenGApps 8.1 ARM64 installed with no errors.
The only thing I noticed is during first boot screen it says in the top-left corner in red text: 'Kernel is not seandroid enforcing'. Maybe this is on SM-T585 as well.
On the SM-T580 you get unusable sim-card icon in the notification bar and some other places, but that is to be expected.
Click to expand...
Click to collapse
Just installing on T585 now, I've flashed the rom and gapps fine.
Problem I have is first there was no keyboard, and now I can't sign in to Google account
It says checking and then screen goes black.
I've wiped cache and davlik but still won't work
Any help would be appreciated
Also, what's a full wipe in twrp?
Sent from my ONEPLUS A5010 using Tapatalk
tolerant said:
Just installing on T585 now, I've flashed the rom and gapps fine.
Problem I have is first there was no keyboard, and now I can't sign in to Google account
It says checking and then screen goes black.
I've wiped cache and davlik but still won't work
Any help would be appreciated
Also, what's a full wipe in twrp?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Those problems may be related to improper wipe, no worries.
Full wipe means in TWRP you go to 'Wipe' -> 'Advanced Wipe' -> Select all partitions except 'Micro SD card' and 'USB OTG'
In my case (SM-T580) that would be;
- Dalvik / ART cache
- System
- Data
- Internal Storage (Optional, but recommended to wipe)
- Cache
Don't forget to first make a backup via TWRP of the 'EFS' partition (on sd-card or USB-stick via OTG cable), just in case the SIM-card functions stop working due to lost IMEI.
Also, some issues may be related to the device still working on stuff when it shows the welcome screen after flashing. In general you should leave the device for around 5 minutes before doing anything after flashing and first boot to let everything finish properly.
sanchaz12 said:
Those problems may be related to improper wipe, no worries.
Full wipe means in TWRP you go to 'Wipe' -> 'Advanced Wipe' -> Select all partitions except 'Micro SD card' and 'USB OTG'
In my case (SM-T580) that would be;
- Dalvik / ART cache
- System
- Data
- Internal Storage (Optional, but recommended to wipe)
- Cache
Don't forget to first make a backup via TWRP of the 'EFS' partition (on sd-card or USB-stick via OTG cable), just in case the SIM-card functions stop working due to lost IMEI.
Also, some issues may be related to the device still working on stuff when it shows the welcome screen after flashing. In general you should leave the device for around 5 minutes before doing anything after flashing and first boot to let everything finish properly.
Click to expand...
Click to collapse
Thanks for that info, that worked brilliant, now fully working.
Thanks sanchaz12
Sent from my SM-T585 using Tapatalk
Rom is running smoothly, only problem I found so far is the camera app, it loads but the soft button only shows a half. It's like the screen is not big enough.
Is there a fix for this?
Sent from my ONEPLUS A5010 using Tapatalk
tolerant said:
Rom is running smoothly, only problem I found so far is the camera app, it loads but the soft button only shows a half. It's like the screen is not big enough.
Is there a fix for this?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Install another good camera. For example i am using Camera FV-5.
It's honestly WORRYING the fact the tablet runs at 10FPS when scrolling through the notification bar. Can't you disable the notification bar background alpha @Valera1978?
Hi. Thanks a lot @Valera1978 . Good job. Even GPS work now.:good:
Great work. I'm new there, i've just buy a T580 and watch your thread for 1 day.
Edit : "Install custom recovery - use my twrp" Where can i find it ? Thanks.
Steelskinz said:
Edit : "Install custom recovery - use my twrp" Where can i find it ? Thanks.
Click to expand...
Click to collapse
This for T585 only. You need install TWRP for T580 official or by @followmsi better from his RR threads.
repey6 said:
Hi. Thanks a lot @Valera1978 . Good job. Even GPS work now.:good:
Click to expand...
Click to collapse
Great! I can confirm that gps gets a fix in gps test app, just as can be seen in the screenshot. Also open camera app can take photos on both cameras and video on back camera. I couldn't record video with front camera, but that doesn't bother me anyway.
repey6 said:
This for T585 only. You need install TWRP for T580 official or by @followmsi better from his RR threads.
Click to expand...
Click to collapse
OK thanks.
Is this rom still OK for T580 ? I read someone flashed it already. Can anyone confirm ? Thanks.
I can't access the SD card in this ROM, maybe there are some leftover files from the previous ROM, that prevent the tablet from accessing it? Anybody has some advice if it's possible to fix that?
mnd123 said:
I can't access the SD card in this ROM, maybe there are some leftover files from the previous ROM, that prevent the tablet from accessing it? Anybody has some advice if it's possible to fix that?
Click to expand...
Click to collapse
External SD card?
Sent from my ONEPLUS A5010 using Tapatalk
tolerant said:
External SD card?
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Yes
mnd123 said:
Yes
Click to expand...
Click to collapse
Did you format it as internal storage on the last romyou had installed, if so it possibly will not work unless it's reformatted on the currently installed rom.
Does it actually show up in file manager?
Sent from my ONEPLUS A5010 using Tapatalk
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!!!