Related
Code:
/*
** Your warranty is now void.
**
** We are 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 us for messing up your device, we will laugh at you.
**
**/
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
IMPORTANT INFORMATION
Root is not included by default on LineageOS 14.1. You need to install an add-on via recovery. You only need to install this once. You can download the SU add-on here
After installation go to Settings>Developer Options>Root access and set to Apps only or Apps and ADB.
LineageOS comes with LineageOS Recovery by default, if you don't like it (like me ) you can flash alternative recoveries using IsoRec. You really need 1GB /system partition. The smallest build-configuration is larger than 512mb. You can use ODIN, but you can also use Lanchon's REPIT.
If you're interested in BLN, check this thread for a complete support of this feature.
If you're interested to go to emulated-storage, check this thread.
Official LineageOS Wiki: http://wiki.lineageos.org/
Changelog: https://www.lineageoslog.com/14.1/i9100
LineageOS official nightly builds
https://download.lineageos.org/i9100
Google Apps:
http://opengapps.org/
XDA:DevDB Information
Lineage OS 14.1, ROM for the Samsung Galaxy S II
Contributors
rINanDO, lysergic acid, serenitys
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-02-13
Last Updated 2017-04-20
Reserved
gapps link dead
[i9100] Useful fixes for LineageOS 14.1 [7.1.2]
[i9100] Useful fixes for LineageOS 14.1 [7.1.2]
I am very glad that you are here!
It may be helpful to you:
Scripts moved here ...
BatyuS said:
gapps link dead
Click to expand...
Click to collapse
I think ist is just a mistake and should mean "open gapps"
http://opengapps.org/
Sent from my ME173X using XDA-Developers Legacy app
In General forum? Why not in Original Android Development?
Which GApps exactly?
Just to prevent from questions like "which GApps architecture and version do I need?"
This link will show you the minimal OpenGapps variant independently of your last visits (cookies never forget you)
http://opengapps.org/?download=false&arch=arm&api=7.1&variant=pico
(so only the variant needs to be changed if you prefer bigger packages)
Edit: Check this post to see how to create a customizable config that allows you to control the OpenGApps installer, e.g. to downsize bigger GApps packages for flashing Pixel Launcher while skipping other components you don't want. Included a sample config-file there as well.
I have questions:
FM Radio?
upgrade of CM 13?
TWRP emuled storage installation and new repit procedure?
from cm-13.0-20161218-nightly to lineageOS 14.1
shkedov said:
In General forum? Why not in Original Android Development?
Click to expand...
Click to collapse
Hi everyone, I am a low-average level user so I wonder if there is a step-by-step guide to upgrade my I9100-international from cm13 to lineageOS 14.1
bepcan said:
Hi everyone, I am a low-average level user so I wonder if there is a step-by-step guide to upgrade my I9100-international from cm13 to lineageOS 14.1
Click to expand...
Click to collapse
Only if you're coming from cm13 without losing data (i.e. your apps installed). Otherwise - wipe clean and install the recent nightly only (and gapps if you wish).
-3. Get a good cup of coffee.
-2. You must have at least 1GB partition of /system. If not, first repartition your storage (see OP) and then come back to here to proceed.
-1. Proceed to oficial download site: "https://download.lineageos.org/i9100 for the current build, https://www.androidfilehost.com/?w=files&flid=154035 for the experimental build, thanks to @ale5000 for uploading this for us.
0. Download the latest 2 following files: Nightly and Experimental (as for now lineage-14.1-20170208-experimental-i9100-signed.zip and lineage-14.1-20170208-nightly-i9100-signed.zip). Verify their md5 checksum to prevent errors, it is vital to do so.
Optional - download gapps from [url]http://opengapps.org/[/URL] for android 7.1, ARM (the nano is fine for me).
1. Boot into recovery. Install the "experimental" zip (Dirty flash! No wipes!).
1.5. You can reboot now into system, just to get a systemUI crash errors and a blank screen. Pretty useless. If you got to here then force reboot to recovery and proceed to step 2.
2. Reboot into recovery! Install the "Nightly" zip and gapps.
3. Wipe cache and boot to system.
There you go kiddo'.
Good luck! :fingers-crossed:
Whats Working Nd Not Working Tell Pls
rowdykumar786 said:
Whats Working Nd Not Working Tell Pls
Click to expand...
Click to collapse
It is relatively very stable to me, most is working! Phone and RIL, audio, GPS, BT, and a lot more!
I believe battery has improved too. Performance is very well.
This is my only phone, I rely on this phone, and on my daily use no problems so far! And yeah this ROM rocks!:good:
Go for it dude!
I experience a problem with libUMP making my own build. Is this : https://forum.xda-developers.com/showthread.php?p=69920779 still a working solution?
Verstuurd vanaf mijn GT-P7500 met Tapatalk
shkedov said:
Without losing data (i.e. your apps installed).
-3. Get a good cup of coffee.
-2. You must have at least 1GB partition of /system. If not, first repartition your storage (see OP) and then come back to here to proceed.
-1. Go to https://download.lineageos.org/i9100.
0. Download the latest 2 following files: Nightly and Experimental (as for now lineage-14.1-20170208-experimental-i9100-signed.zip and lineage-14.1-20170208-nightly-i9100-signed.zip). Verify their md5 checksum to prevent errors, it is vital to do so.
Optional - download gapps from http://opengapps.org/ for android 7.1, ARM (the nano is fine for me).
1. Boot into recovery. Install the "experimental" zip (Dirty flash! No wipes!).
1.5. You can reboot now into system, just to get a systemUI crash errors and a blank screen. Pretty useless. If you got to here then force reboot to recovery and proceed to step 2.
2. Reboot into recovery! Install the "Nightly" zip and gapps.
3. Wipe cache and boot to system.
There you go kiddo'.
Good luck! :fingers-crossed:
Click to expand...
Click to collapse
Do you don't include TWRP emu 3.03 https://forum.xda-developers.com/showpost.php?p=71009597&postcount=88 Interesting
Yes I would like to know upgrade path to official using twrp3.0.3 for emulated storage too please
todonormal said:
Do you don't include TWRP emu 3.03 https://forum.xda-developers.com/showpost.php?p=71009597&postcount=88 Interesting
Click to expand...
Click to collapse
People asked for a simple migrating guide from CM13 to LOS14.1, if someone isn't heading to switch to emulated I don't see a reason to send people to install an emu-recovery while they don't wish to.
It should be a decision for users.
Therefore I don't see a reason to include special addtional options besides the basics (exp+nightly+gapps). Whoever wants to expand more should simply read the OP and the links.
As for myself yes, I'm on emu now.
shkedov said:
People asked for a simple migrating guide from CM13 to LOS14.1, if someone isn't heading to switch to emulated I don't see a reason to send people to install an emu-recovery while they don't wish to.
It should be a decision for users.
Therefore I don't see a reason to include special addtional options besides the basics (exp+nightly+gapps). Whoever wants to expand more should simply read the OP and the links.
As for myself yes, I'm on emu now.
Click to expand...
Click to collapse
Could we have a short video to show how to switch to emulated storage?
Regards.
New build lineage-14.1-20170213-nightly-i9100-signed.zip is up
https://www.lineageoslog.com/14.1/i9100
laptopu said:
Yes I would like to know upgrade path to official using twrp3.0.3 for emulated storage too please
Click to expand...
Click to collapse
Hmm, because this phone is my main and only phone, I won't be able to test that soon (reverting recovery and ROM to cm13, reverting repartitioning too, then starting to trial and error).
But I believe that the safest way is to start from the moving to LOS14.1 - flashing the experimental and nightly first, as I guided. Then later flash emu-twrp recovery and proceed with rINanDO's instructions.
I'm afraid doing opposite (emu'ing first and then flash exp+nightly) might not work since Lanchon and the guys warned us that this emu-kernel might not work even with cm13 and maybe even affect it! Maybe repiting manually with Lanchon's magic REPIT would do, then migrate ROM, then change to new emu-recovery.
PLEASE:
- don't direct-link to recoveries that will brick your phone if installed too early.
- read the linked threads in the opening posts to understand the complexity of any of the changes
- if understood the consequences and you still want to do them all at once: know your limits
- if still feeling comfortable until here: go ahead *but do it in the correct order* or your phone will bootloop as all the newer test-recoveries were built with a Nougat ramdrive and thus will very very likely bootloop on your phone if installed on non-Nougat ROMs!
So my advice for your own safety: stay in your lane and read everything first.
EDIT: And by the way: please keep emulated storage discussions in the appropriate thread until it is officially tested and documented to be kind of noob-proof.
Lineage is a free, community built, aftermarket firmware distribution of Android 7.1.1 (N), which is designed to increase performance and reliability over stock Android for your device.
Code:
#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.
*
*/
Lineage is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. Lineage does still include various hardware-specific code, which is also slowly being open-sourced anyway.
We'll not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our intructions word by word
are unfriendly
And most important: DON'T READ THE OP
What's working:
Everything except in BUGS/Not working list
BUGS/Not working :
Offline charging doesn't work
STK hangs after choosing a subscription in the menu
Front camera displays 0,3MP instead of 2MP
First time installing LineageOS 14.1 to your Galaxy Core Prime, or coming from another ROM:
Install TWRP Recovery
Reboot into Recovery using 3-button-combo (Vol-up+Home+Power)
Do a Nandroid backup! (Optional and only if you weren't running TouchWiz before)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)*
Install the ROM from sdcard using TWRP Recovery
Optionally install the Google Apps ( get it here: https://opengapps.org ) (pico GAPPS recommended) (*)
NOTE: First boot might take long time, due to deodexed build, so don't consider bootloop!!
Upgrading from an older build of this ROM
Wipe system partition, wipe dalvik-cache but not data partition
Optionally install Google Apps (GAPPS) (link above)
(*) NOTE: If you're about going to install GAPPS with ROM, install it right after you've installed the ROM, else you have to do a factory reset if you've booted the ROM first
DOWNLOADS:
Click to expand...
Click to collapse
BETA-4: Drive link
Want some screenshots? Get them in Screenshot tab above
XDA:DevDB Information
LineageOS 14.1, ROM for the Samsung Galaxy Core Prime
Contributors
remilia15
Source Code: https://github.com/remilia15/android_device_samsung_core33g/tree/cm-14.1
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock 4.4.4
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 3
Beta Release Date: 2017-04-08
Created 2017-04-08
Last Updated 2018-06-15
CHANGELOG
BETA-1:
Initial LineageOS 14.1 release
BETA-2: Post #25
BETA-3: Post #230
BETA-4: Post #365
Frequently Asked Questions
Taken originally from @doesntexits
Q: ROM startup too slow?
A: Nope, just because you haven't done a factory reset before installing the ROM
Q: Dead touchscreen?
A: Wrong installation method leads to this problem. Before restoring to stock through Odin, go to recovery mode (TWRP highly recommended), wipe everything in the Wipe section >> Advanced wipe (tick all system, data, cache, but not other storages, no need wiping dalvik/ART cache, as it already done by wiping data), then go to Download mode, restore stock, install custom recovery again and then, install the ROM you want
Q: ETAs?
A: See here: Link
Q: Anymore models supported?
A: SM-G360HU
Q: Is init.d supported on this ROM?
A: Every CyanogenMod ROMs support init.d, so be free at scriptings
Q: Can you include ABCXYZ feature / Samsung Apps here?
A: NO!
Q: Can I use your ROM as a base for portings?
A: Yes, you can
Q: Server error in Google Play Store?
A: Install latest Google Play Services manually first (might take long time, due to Lollipop's nature), then you can install apps from GG Play as usual
Q: How to use adoptable storage feature? I see it's new in Marshmallow, and now it's Nougat
A: Go to Settings >> Storage & USB >> Tap on the SD card label (not the eject icon) >> 3 dots menu on the top right >> Settings >> Format as internal and done!
Q: Where's the MTP option in this ROM? I don't see it in Storage settings
A: This feature has been moved to Developer settings since Marshmallow, and will reset to default (Charging) after everytime you unplug your USB (due to security reasons). Enable developer options first by tapping 7 times on Build number in About phone section >> Go to Developer settings >> Select USB configuration. The fastest way to do this is plug in your USB with your PC, scroll down notification bar and tap on "USB for Charging" or "USB is connected"
Q: Where's the "running" section in Apps settings?
A: It has been cut off separately to Memory setting and "Running services" in Developer settings. You can see the memory used by apps for a period of time and closing apps too, but they won't disappear in the menu, and in "Running services", still same as old-fashioned running apps section
Q: My phone is slow as snail after installing ROM. I've tried restoring stock and do formattings but no help?
A: I have answered this question. See this post: Link
Thanks @remilia15
Thread bookmarked
Thanks
Awesome @remilia15 thanks
WOW we have got a LOS 14.1
you are awesome
Finally N for our device. Yay. Thanks OP
Fix for home button not working
So I managed to fix the home button not working bug.
Extract the contents of the attached zip file into your /system/usr/keylayout and change the permissions of each file to 644 if they are not 644 already. Then a reboot should fix the problem.
Now searching for quick fix of camera.
For older releases, use patch below by [email protected] for those bug fixes.
Or flash newer release like Beta-2.
Any custom kernel works?
FIX for bugs
listed things are fixed
camera [photo&video]
Flac audio codec
home button
volume [increased]
flash the zip and do a factory reset
DOWNLOAD
[email protected] said:
listed things are fixed
camera [photo&video]
Flac audio codec
home button
volume [increased]
flash the zip and do a factory reset
DOWNLOAD
Click to expand...
Click to collapse
Why still do factory reset? I just flashed and reboot works fine.
mmmmmmm Thanks for it
What about battery drain ????
Nice! Downloading, will test tonight.
Sent from Vietnam
Thank you
Q: How to use adoptable storage feature? I see it's new in Marshmallow
Q: Where's the MTP option in Marshmallow? I don't see it in Storage settings @remilia15
Lol !
we are here in Nougat Not Marshmallow
Thanks to all Contributor to build this Lineage Os For G360H, At least we got it :good:@[email protected] fixed the many bugs of Beta-1 so Please update Beta Version and Bug list @remilia15
Whats about Battery drain issue? Who already Install this Rom please review it,
Thanks you
adamh.ayyad said:
Q: How to use adoptable storage feature? I see it's new in Marshmallow
Q: Where's the MTP option in Marshmallow? I don't see it in Storage settings @remilia15
Lol !
we are here in Nougat Not Marshmallow
Click to expand...
Click to collapse
Mtp is currently having problems.
Sent from my SM-G360H using Tapatalk
---------- Post added at 07:00 AM ---------- Previous post was at 07:00 AM ----------
noman6999 said:
Thanks to all Contributor to build this Lineage Os For G360H, At least we got it [emoji14] :good:@[email protected] fixed the many bugs of Beta-1 so Please update Beta Version and Bug list @remilia15
Whats about Battery drain issue? Who already Install this Rom please review it,
Thanks you
Click to expand...
Click to collapse
Battery drain is common so just ignore it lol.
Sent from my SM-G360H using Tapatalk
SupulEdirisinghe said:
Mtp is currently having problems.
Sent from my SM-G360H using Tapatalk
Its working with me
Click to expand...
Click to collapse
@remilia15
Nice job my little sister
Anyway, I hope @AtomR saw this thread
It has been a very long time since my last post on XDA. I've been so busy with my job, and haven't got time to visit here
How are you guys all going?
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!!!
HAVOC 3.0 ROM V2 2019-12-06
Project ended.
This is BETA version, USE STABLE crDroid or GoogleDroid ROMs.
Your warranty is now void.
There's no guarantee, don't use it if you don't know what you're doing!
Android quota removed. (Easy back 7.x-9.x ROMs)
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery) My TWRP: LINK
Boot into recovery
Wipe dalvik, system, data, cust (vendor), cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy SD)
Flash Google Apps package (Optional) LINK
Flash Magisk Root (Optional) LINK
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 40 sec to 1 minutes.
Boot time 30 sec.
There are many tiny, unpleasant bugs in Havoc system, NOT recommended for daily use, maybe just for fanatics.
DOWNLOAD V2 ROMDon't need wipe data if upgrade previous Havoc 3.
NEW: FM radio fixer LINK (If not working FM radio, install this fixer in TWRP)
NEW: dt2w fixed : LINK (Install in TWRP.)
V2 Changelog:
Power off (offline) charging bug fixed
Some camera bug fixed
Many system bug fixed
Energy consumption is very good
The Android system seems stable and fast (Havoc Os not so much )
Know bugs: - no double touch wake up (?)
- FM radio
- power off charge
Update: I found some permission issues.
I'm trying to fix it.
The camera app does not save images to the SD card...
Gallery Go does not handle SD card properly...
They don't even ask for permission...
Workaround: USE INTERNAL STORAGE for photography, and sometimes move images to SD.
*
Screenshots: LINK
ROM source xda: LINK
Havoc-OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.x
ROM info: mido OFFICIAL port, Q10 system_root partition
Created 2019-11-26 V0 version
Last Updated 2019-12-06 to V2 version
It looks like I have solved two serious problems.
(dex2oat didn't work and neither did ashmem)
The system boot is twice as fast, etc.
I soon publish the new ROM.
Upgrade Out. More stable, fast.
Reboots into fastboot mode
My device automatically reboots into fastboot mode after I flashed this.
---------- Post added at 09:48 AM ---------- Previous post was at 09:45 AM ----------
I am using pixel experience ROM currently. When I flashed this my device end up in bootloop. Do I have to be in miui for installing this..??
Redminote5a8 said:
My device automatically reboots into fastboot mode after I flashed this.
I am using pixel experience ROM currently. When I flashed this my device end up in bootloop. Do I have to be in miui for installing this..??
Click to expand...
Click to collapse
Thank you your response, ROM V1 fixed, downloadable.
(The system partition on my phone was slightly disintegrated, I had to fix it.)
Pixel E. ROM is on 4PDA, downloadable.
Use a suitable TWRP, pls.
If anybody have downloaded V1, delete it because it is defective.
ROM named *V1fix.img works.
Sorry. I apologize for the inconvenience.
Hahaha, the camera bug very funny: LINK
The camera app save images to folder: sdcard - /Android/data/org.lineageos.snap/files
Thnx ****ing org.lineageos.snap app, and i suck...
offline charging bug
Hafitz Setya said:
offline charging bug
Click to expand...
Click to collapse
Thank you your responde, i know this bug, i will deal with it, i hope soon.
HAVOC 3.0 ROM V2 2019-12-06
V2 out.
I ended this job for the time being here, I don't got much feedback and thnx (respect the exceptions), and a lot of time goes with it. Sry, bye.
that is a great work
hey szanalmas we all on ugglite telegram appreciate your hard and excellent work for bringing stable Q to ugglite
thanks is few for you on Xda beacuse almost ugglite useres are on telegram groupe
they all ask you to join the group on telegram
:good::good::good::good:
szanalmas said:
I ended this job for the time being here, I don't got much feedback and thnx (respect the exceptions), and a lot of time goes with it. Sry, bye.
Click to expand...
Click to collapse
i told u to use telegram, people most activates in therre they report bug in telegram
FM radio fixer out. LINK
Dt2w fixer placed out.
According to Hafitz Setya, he also works with the my dt2w fixer on Havoc OS. Use it gladly: LINK (Install in TWRP.)
Is this rom work in ugg?
szanalmas said:
Dt2w fixer placed out.
According to Hafitz Setya, he also works with the my dt2w fixer on Havoc OS. Use it gladly: LINK (Install in TWRP.)
Click to expand...
Click to collapse
It don't work. Only for ambition display. Rom is good, but sometimes slowly. Not work gestures If someone can fix it, I will be happy.. Bluetooth works unstable
Manager_of_Gulag said:
It don't work. Only for ambition display. Rom is good, but sometimes slowly. Not work gestures If someone can fix it, I will be happy.. Bluetooth works unstable
Click to expand...
Click to collapse
Try execute 10goodix & turn on emulate init.d in kernel adiutor and reboot and turn off this
Sent from my Xiaomi Redmi Note 5A using XDA Labs
Manager_of_Gulag said:
It don't work. Only for ambition display. Rom is good, but sometimes slowly. Not work gestures If someone can fix it, I will be happy.. Bluetooth works unstable
Click to expand...
Click to collapse
1. workaround dt2w: download Ravenge OS (TWRP save) and restore ONLY VENDOR. I integrated dt2w to vendor, but only for PE and subsequent ROMs.
2. workaround (full ROM installer): change the vendor.transfer.list and vendor.new.dat.br files from PixelE to HavocOS (or Arrows, or crDroid) in to the installer zip file. After no need patch for dt2w. Only copy two files to ROM installer zip file.
If you want dt2w, you have to disable the double tap on ambient display because two identical functions cannot be interpreted at the same time.
Dt2w will be good in every new ROM.
I have already stated that Official ROM development is chaotic.
The Havoc bug to this day:
- no flashing LED for missed calls
- Doesn't work with two buttons navigation back sweeping
- there is a problem with the bluetooth call
- applications are chaotic and inconsistent, with each developer trying their own solutions
- etc
- developers do not receive meaningful feedback
The situation is similar for all AOSP-based ROMs, which may be due to the lack of an official Lineage 17.
Google ****ed up sd card permissions.
I don't know when a stable AOSP ROM will be available, just wait now...
Hey.
After flashing the system asks for a password ??
What the hell?
Repixel said:
Hey.
After flashing the system asks for a password ??
What the hell?
Click to expand...
Click to collapse
1. If your phone data was encrypted, you may need to format the data partition. Save all your data first.
2. If a quota was applied to the data partition, it must be removed or formatted.
To remove a quota from TWRP:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
(If you then install a ROM that uses a quota, you will need to uninstall it again to use the quota-free ROM.)
3. Or, put the previous ROM from your backup on your phone and keep using it.
crDroid 6.0 -V2 2019-12-06
Project ended.
This is BETA version, USE STABLE crDroid or GoogleDroid ROMs.
(Original rosy OFFICIAL ROM is BETA.)
My favorite custom ROM!
Your warranty is now void.
There's no guarantee, don't use it if you don't know what you're doing!
Android quota removed. (Easy back 7.x-9.x ROMs)
Make sure you have a custom recovery installed (TWRP is the preferred recovery)
Boot into recovery
Wipe dalvik, system, data, cust (vendor), cache partitions
Flash ROM (sideload or copy SD)
Flash Google Apps package (Optional)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to ~40 sec to 1 minutes.
Boot time ~30 sec.
There are many tiny, unpleasant bugs in it, NOT recommended for daily use, maybe just for fanatics.
DOWNLOAD STABLE ROMDon't need wipe data if upgrade previous 6.0 version.
V2 Changelog:
Power off (offline) charging bug fixed
Some camera bug fixed
Many system bug fixed
Energy consumption is very good
The Android system seems stable and fast
Know bugs: no double touch wake up (?)
Fm radio
power off charge
Update: I found some permission issues.
I'm trying to fix it.
The camera app does not save images to the SD card...
Gallery does not handle SD card properly...
They don't even ask for permission...
Read more: LINK
Workaround: USE INTERNAL STORAGE.
Built-in screenrecord not working good for me.
SCREENSHOTS: LINK
crDroid source: LINK
ROM source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.x
ROM info: rosy OFFICIAL port, Q10 system_root partition
Created 2019-11-28 V0
Last Updated 2019-12-06 V2
could you try build Pixel Experences android 10 ?
viethoang18 said:
could you try build Pixel Experences android 10 ?
Click to expand...
Click to collapse
Pixel E. ROM can be found on 4PDA.
(It worked for me.)
Working fine
Working fine my phone performance doubled nice work.. But can u suggest me gapps please..?
Redminote5a8 said:
Working fine my phone performance doubled nice work.. But can u suggest me gapps please..?
Click to expand...
Click to collapse
This or this but i did a little testing, i don't like gapps, it drains the battery. (I used to make a gapps ROM backup (data) and sometimes restore it when needed.)
"The camera app does not save images to the SD card...
Gallery does not handle SD card properly..."
Read this: LINK
The built-in camera app save the pictures to sdcard: /Android/data/org.lineageos.snap/files/
This bug in software or/and developer (in Pie9/Q10? any phones?). Unfortunately, they are not very interested. (LINK)
If someone in the gallery does not see the DCIM folder on sdcard, rename it (i use Total Commander) e.g.: DCIM0, then rename back to DCIM, and works fine after. (for me working) (it can be used in any folders on sdcard)
thanks man
please go ahead and join tele group redminote_5a
we need expert developer like you
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
thanks man
please go ahead and join tele group redminote_5a
we need expert developer like you
Please test this dt2w fixer on crDroid 6: LINK
And please feedback, working or not. Thnx.
szanalmas said:
Please test this dt2w fixer on crDroid 6: LINK
And please feedback, working or not. Thnx.
Click to expand...
Click to collapse
work :good::good::good: