Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
kpmohamedhussain said:
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
Click to expand...
Click to collapse
really ...anyone who gets a brick because of not reading a thread certainly shouldnt be xda or even messing around with the phone in the first place. just stay stock if you wont read
We survived finely when Nougat was still new, so what makes Oreo special?
There's simply no good point to making a whole section for a particular version of Android. The same thing can be done simply with a proper thread title.
The problem isn't purely on the lack of separation of sections — It's the 5 seconds attention span that most seems to have because they can't read the first post of the thread they're in or they're too busy looking at butterflies and they ended up destroying their device and/or data inside the device.
I know we can't fix people, but that doesn't make for a good argument for creating a new section.
kpmohamedhussain said:
Dear Admins,
Can we have a separate section for oreo related moda, apps and themes... This will ensure users from installing unsupported stuffs as wells as to avoid getting bricked/boot loop. This can also be used as a one stop place to look for oreo related stuffs...
Click to expand...
Click to collapse
As stated. This is not gonna happen. If you cant do the proper research needed for what you are doing then you shouldnt be doing it in the first place.
I disagree with OP - there shouldn't be separate section for Oreo stuff. Ask yourself - what would happen, if released mod would be compatible with Marshmallow, Nougat and Oreo?
Okay, now that's not going to happen. But what can happen is in every thread the op can state the supported android versions first or the rom's android version first and then state what is the thread for (rom, mod, source code...). Something like "[7.1.1][ROM] Resurrection Remix 5.8.4 SomethingTweaks Edition" and not "[OH YEAH BABY WE SUPPORT COLOR ENGINE] CrazyManiacLunatic Tweaks". All the OPs should first give the supported android version or the rom android version then state what is the thread about and then write the rom that they are based on then write the name that they've given. But they MUST write the android version and the thread's reason to exist at first. Because this way when you are looking for an oreo rom you just have to look inside the first bracket and find it quickly instead of checking each thread's name to first find out where is the version and then looking at the version.
charackthe said:
Okay, now that's not going to happen. But what can happen is in every thread the op can state the supported android versions first or the rom's android version first and then state what is the thread for (rom, mod, source code...). Something like "[7.1.1][ROM] Resurrection Remix 5.8.4 SomethingTweaks Edition" and not "[OH YEAH BABY WE SUPPORT COLOR ENGINE] CrazyManiacLunatic Tweaks". All the OPs should first give the supported android version or the rom android version then state what is the thread about and then write the rom that they are based on then write the name that they've given. But they MUST write the android version and the thread's reason to exist at first. Because this way when you are looking for an oreo rom you just have to look inside the first bracket and find it quickly instead of checking each thread's name to first find out where is the version and then looking at the version.
Click to expand...
Click to collapse
Yeah that is not gonna happen either. This gets brought up every few years and the answer is always the same. The devs can name their threads anything and any way they want. Heck they don't have to encludes any info at all.
People seem to forget that this is a developers site. Not a rom site or a support site. You are expected to do your own homework and have all the info you need before flashing. That encludes how to use command line to recover from something bad happening.
zelendel said:
Yeah that is not gonna happen either. This gets brought up every few years and the answer is always the same. The devs can name their threads anything and any way they want. Heck they don't have to encludes any info at all.
People seem to forget that this is a developers site. Not a rom site or a support site. You are expected to do your own homework and have all the info you need before flashing. That encludes how to use command line to recover from something bad happening.
Click to expand...
Click to collapse
Well, developers love mentioning how they won't take responsibility if anything happens in every single thread over a million times but they seem to forget that people are looking for most basic info in the OP post. Developing can only be achieved if you acknowledge something and share it with others. The progress can not be achieved without information. I'm not going to flash a rom just to see if it is a Nougat or an Oreo rom. And I'm not going to flash all versions of modems to see which is the right one. Developers and maintainers must inform casual users or other developers about what is they are looking at. Sharing is caring. Not everybody likes to use something they don't know.
charackthe said:
Well, developers love mentioning how they won't take responsibility if anything happens in every single thread over a million times but they seem to forget that people are looking for most basic info in the OP post. Developing can only be achieved if you acknowledge something and share it with others. The progress can not be achieved without information. I'm not going to flash a rom just to see if it is a Nougat or an Oreo rom. And I'm not going to flash all versions of modems to see which is the right one. Developers and maintainers must inform casual users or other developers about what is they are looking at. Sharing is caring. Not everybody likes to use something they don't know.
Click to expand...
Click to collapse
And that is what a Gerrit is for.
To be honest. Causal users are not the focus here.
zelendel said:
And that is what a Gerrit is for.
To be honest. Causal users are not the focus here.
Click to expand...
Click to collapse
I see you all over the place! You are retired? You post on here like its full time lol
ZVNexus said:
I see you all over the place! You are retired? You post on here like its full time lol
Click to expand...
Click to collapse
I am a retired mod. My job allows for me to always be lurking around. Every couple of hours or so I check my email and catch up.
Been that way for as long as I can remember. Heck I used to be on far more in the early years.
Related
1. I think it's really stupid forcing captcha before every post,
2. Stopping legitimate questions about a specific ROM from being posted directly on the specific ROMs thread until you have 10 post is also stupid,
3. I know it's pointless asking this question here SINCE THE DEV WILL NEVER SEE IT!!!!!!!, but have you ever considered incremental updates? The download site is slow and it seem pointless downloading the full ROM when only minor changes have been made.
mdhowes said:
1. I think it's really stupid forcing captcha before every post,
2. Stopping legitimate questions about a specific ROM from being posted directly on the specific ROMs thread until you have 10 post is also stupid,
3. I know it's pointless asking this question here SINCE THE DEV WILL NEVER SEE IT!!!!!!!, but have you ever considered incremental updates? The download site is slow and it seem pointless downloading the full ROM when only minor changes have been made.
Click to expand...
Click to collapse
I fully agree with Ypur first and second point.
Yeah, any idiot can get past a captcha.
There should be a test:
"you've flashed a ROM, but not the boot.img, should you:"
a) ask in the ROM thread why phone is broken
b) ask in Q&A section why phone bootloops
c) ask if flashing boot.img is required
d) tell everybody it's easier with Samsung
e) flash boot.img
I've been caught out by the 10 post restriction on the Developer threads, but usually found the answer after a quick search or just waiting a day or so to see if the same query gets raised.
As for incrementals, good idea for those that are coming from that base ROM, but not much for those that are flashing it for the first time.
Unless you want a new base ROM, and the incrementals? In which case poor Mr Dev does enough work already!
ARHD on my One X is working fine so far. I have the odd issue with not seeming to be able to connect over mobile data, but it is WAAAY less often than when it was stock. Pretty poor from HTC to release their flagship with so many radio based problems.
Meh. Mondays
Phew, glad I'm not alone with my frustration about captcha and post limits. Thought I might have seemed agro.
Incremental only on same base. Ie; 9.0.0 to 9.1.0. Seems silly downloading the whole 500mb for minor changes.
BenPope said:
Yeah, any idiot can get past a captcha.
There should be a test:
"you've flashed a ROM, but not the boot.img, should you:"
a) ask in the ROM thread why phone is broken
b) ask in Q&A section why phone bootloops
c) ask if flashing boot.img is required
d) tell everybody it's easier with Samsung
e) flash boot.img
Click to expand...
Click to collapse
Hahaha, made my night
Yeah, i also hated the unreadable Captcha o_0
Sent from my HTC One X / Desire HD using xda premium
Yep, just a pointless post to get my count up...
mattspew said:
1. I think it's really stupid forcing captcha before every post,
2. Stopping legitimate questions about a specific ROM from being posted directly on the specific ROMs thread until you have 10 post is also stupid,
3. I know it's pointless asking this question here SINCE THE DEV WILL NEVER SEE IT!!!!!!!, but have you ever considered incremental updates? The download site is slow and it seem pointless downloading the full ROM when only minor changes have been made.
Click to expand...
Click to collapse
I´ve got the "Point-2-Problem" too
Well, after reading nearly 300 sites in the ARHD Thread, i sometimes saw the same Questions by many Users with XXX Posts.
This let me doubt the 10-Post-Regulation, but i can also understand that the developers are herried about noob Spam...
Anyway... i think every noob can get a custom rom on a HOX by reading the Thread, just some Time is needed.
But it would be really nice when a newbie could also ask or share some experience, even on a brand new ROM like ARHD 9.1.0.
It is just to keep the thread clean is what I feel. Don't forget that everyone isn't a techie and might just post a dumb question upon registering.
BTW, I have never had to post a question since same is posted atleast once. If not, combining a couple of posts definitely answers my question :laugh:
Trust me, I am on 9.0.0 and it's worth waiting.
We finally have PE treble thanks tobthe devs.
My main concern is regarding the stock kernel with new treble update. All i want to know is the best setup for the new PE rom. I am on non treble version and here i am using PE+heliox+boostv7+ubercool and the performance is unbeatable.
So i was thinking what will be the best setup for the latest treble update..?
I've tried treble kernels but kronic is still best. Wait for next update, i hope many problems would get fixed.
#3
Failed to update vendor image
Rahil4321 said:
I've tried treble kernels but kronic is still best. Wait for next update, i hope many problems would get fixed.
Click to expand...
Click to collapse
The battery backup is very poor and the phone gets heat up a lot and all game are lagging.
What about ar beast??
rince4 said:
Failed to update vendor image
Click to expand...
Click to collapse
First flash -Factory to vendor zip
Then flash treble twrp
And finally flash the rom.
Shouldn't this question be asked in the PE thread it self?
Anyways, just for information, I too have this same question. Myself a big fan of the old PE, indeed it has given me the best performance so far.
Presently waiting on AiCP 13.1 and I am following the PE thread to note down who is suggesting what and known good setups.
I guess reading the thread is better idea rather expecting everyone to contribute in a seperate section. Many may not simply come to see this thread or take the extra hassle to pen down twice !!
NaXal said:
Shouldn't this question be asked in the PE thread it self?
Anyways, just for information, I too have this same question. Myself a big fan of the old PE, indeed it has given me the best performance so far.
Presently waiting on AiCP 13.1 and I am following the PE thread to note down who is suggesting what and known good setups.
I guess reading the thread is better idea rather expecting everyone to contribute in a seperate section. Many may not simply come to see this thread or take the extra hassle to pen down twice !!
Click to expand...
Click to collapse
No one is sharing the best setup. Everyone is asking about their problems in the thread. So i made a different thread itself.
gunavat said:
No one is sharing the best setup. Everyone is asking about their problems in the thread. So i made a different thread itself.
Click to expand...
Click to collapse
I wonder if that means no one has found a satisfactory setup yet.
At least I concluded that and stayed on AiCP for the time being till all the answers about these common questions and solutions for those problems are found.
NaXal said:
I wonder if that means no one has found a satisfactory setup yet.
At least I concluded that and stayed on AiCP for the time being till all the answers about these common questions and solutions for those problems are found.
Click to expand...
Click to collapse
Maybe yes. Let's wait and watch
Anything??
https://download.lineageos.org/bacon
Currently Maintained by jrior001/
https://www.cyanogenmods.org/forums/topic-tag/jrior001/
Install instructions
https://wiki.lineageos.org/devices/bacon/install
Upgrade from official Lineage OS 14.1 possible but as usual clean install is better. Good time to wipe that phone clean.
Please update TWRP to the latest. If you have this device and don't know how to install please follow above procedure.
If you have device encryption enabled, consider removing as its a bit touch and go. As usual always have a full backup and separate copy of your data/pictures.
And the caveat you are responsible for what you do with your device applies and no one else is responsible for your action. People may be able to help if you ask kindly.
Official channel released finally on the 18th of July 2018.
Super effort by Devs specially jrior001, so please donate if you can.
PS I am just making this thread as there is none and it was released atleast 6 days ago and in no way taking any credit for the ROM or the work done by DEVS.
which is d stable twrp version???
jokermithun said:
which is d stable twrp version???
Click to expand...
Click to collapse
3.2.1-0
jokermithun said:
which is d stable twrp version???
Click to expand...
Click to collapse
I am sure you are joking but for those who dont know its 3.2.1-0
https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
Please select appropriate file and upgrade as image. If you dont know which file to use it means you need to read up more.
Is that cyanogenmods website some kind of fan site? It doesn't look official.
Kernel
Is anybody working on the included Kernel?
The background of my question is that I am experiencing spontaneous reboots when physically leaving a Wi-Fi connection, particularly my home Wi-Fi.
This defect was present in LineageOS 14.1 as well. There I could solve the problem completely by installing the latest Franco Kernel. However, in LineageOS 15.1 the Franco Kernel leads to very frequent soft reboots, like 5 in one hour, so I am now back on the stock kernel.
The only workaround I know is to disable Wi-Fi before leaving a Wi-Fi area, then re-enabling it.
Before other users jump in and state that they don't have this defect, not everybody has it. It is not clear under which conditions the defect shows up. It may depend on certain apps being present. But obviously it is not the apps' fault, as the fact proves that the Franco Kernel resolved it in LineageOS 14.1. Not to mention that no app has the right to reboot the system.
sn809 said:
I am sure you are joking but for those who dont know its 3.2.1-0
https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html
Please select appropriate file and upgrade as image. If you dont know which file to use it means you need to read up more.
Click to expand...
Click to collapse
No sir....actually im nt frequent user of xda forums these days
NetGuard via VPN is not working for me. Under 14.1 was everything ok.
Hardware buttons backlighting is very dim for me even when set up to 100% brightness.
sn809 said:
PS I am just making this thread as there is none and it was released atleast 6 days ago and in no way taking any credit for the ROM or the work done by DEVS.
Click to expand...
Click to collapse
The Development section is for users to post their own development work, not links to the development work of others. Please refer to the sticky posted here and be sure to follow the forum rules.
THREAD CLOSED
Hi
I have a Honor 5X (kiwi / KIW-L21) as my daily driver and as its nearing the end of it warranty (2 years) its starting to run slower (good job, Huawei). Given this and the fact that during these two years i never received ANY update apart from an update to android 6.0.1 from android 5, im considering switching to LOS 16.
The thing is im completely new to custom ROMs, recovery, phone rooting and that jazz and im a bit scared.
I wanted to know if there is a way I can try out LOS 16 (say for example on a VM) to be sure that i like it before installing.
If not, would I be able to restore my phone back to its current OS in case i dont like LOS and want to fall back to EMUI ?
PS : I wanted to try it out on an older phone I have and for which i dont care as much, but its not supported :'( Its an Asus Zenfone go ZB552KL
Thanks in advance !
The oldphone approach is a good idea. Go to a recycling place and grab some old Motorola or Samsung phones. Broken screen is OK.
kurtn said:
The oldphone approach is a good idea. Go to a recycling place and grab some old Motorola or Samsung phones. Broken screen is OK.
Click to expand...
Click to collapse
My local trash collecting place isn't very open to people who want to take stuff (yes, what a nonesense) but i'll try that i guess. The thing is we have like 3 or 4 old phones but none of them are listed as compatible on the LOS website
IamGron. said:
My local trash collecting place isn't very open to people who want to take stuff (yes, what a nonesense) but i'll try that i guess. The thing is we have like 3 or 4 old phones but none of them are listed as compatible on the LOS website
Click to expand...
Click to collapse
You don't need official. Search XDA and you will find unofficial lineageOS for many old phones. https://twrp.me/Devices/ is a good place to find the phone's code name. With that you can check stats.lineageos.org for popular ROM versions.
Will give it a look, thanks.
If nothing usefull comes out of this investigation and I end up doing it on my 5X, is there a way for me to backup the whole phone (i mean not just data, like the whole OS) that way I can fall back to its current state if something goes wrong / i dont like LOS ?
IamGron. said:
Will give it a look, thanks..........
Click to expand...
Click to collapse
To be honest, there's various ways for backing up a whole device but, there's limited (possibly no) choices that all depends upon the device itself and the capabilities of said device. So there's no real way of answering this question without, also, taking under consideration that what works for one may/may not work for another.
With that stated...
I've always found that the only way to know if I like something as huge as updating the Custom Android version Firmware, is to "Hope for the Best and Prepare for the Worse".
I've been successful with Restoring TWRP Backups made but, have always had an (approximately) 50% +/- of a restoration working without any issues (a chance of requiring a fresh installation in the end).
In another words...
The only "recommended" way to upgrade/downgrade the LineageOS Android Versions is to make sure you have everything on hand for performing a fresh installation for both the upgrading and the downgrading of both Android Versions.
For anyone to guide you any other way should (ethically) be able to provide you with guidance in case something goes wrong in the process (of said guidance) with your specific device.
You should also ask for support and guidance within the LineageOS thread and, if needed, somewhere within the Device Dedicated Area of the forum that's specific to your device. This will help locate assistance from those who has your device as well.
For example...
[ROM][9.0.x] LineageOS 16.0 Official (kiwi) [NO VoLTE] by BadDaemon
[ROM] [9.x] LineageOS 16.0 Pie Unofficial for Honor 5x (kiwi) by coldhans
https://forum.xda-developers.com/honor-5x
I hope that I had explained this okay via text... :thumbup:
I wish you the best of luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Ibuprophen said:
To be honest, there's various ways for backing up a whole device but, there's limited (possibly no) choices that all depends upon the device itself and the capabilities of said device. So there's no real way of answering this question without, also, taking under consideration that what works for one may/may not work for another.
With that stated...
I've always found that the only way to know if I like something as huge as updating the Custom Android version Firmware, is to "Hope for the Best and Prepare for the Worse".
I've been successful with Restoring TWRP Backups made but, have always had an (approximately) 50% +/- of a restoration working without any issues (a chance of requiring a fresh installation in the end).
In another words...
The only "recommended" way to upgrade/downgrade the LineageOS Android Versions is to make sure you have everything on hand for performing a fresh installation for both the upgrading and the downgrading of both Android Versions.
For anyone to guide you any other way should (ethically) be able to provide you with guidance in case something goes wrong in the process (of said guidance) with your specific device.
You should also ask for support and guidance within the LineageOS thread and, if needed, somewhere within the Device Dedicated Area of the forum that's specific to your device. This will help locate assistance from those who has your device as well.
[...]
Click to expand...
Click to collapse
Hi there, thanks for the answer and sorry for the delayed reaction, I was busy
I will investigate on the linked threads and see what I want to do after that. My main concern being fingerprint sensor gestures (I know, stupid habits lol) asking on the kiwi forum is definitely a good idea. Same things for installing TWRP and the recovery, someone there would probably be able to help.
Thanks a lot for your time
I've been around a while so I'm not new to Android or to tech in general but I am new to this Slot A/B stuff and also new to using Verizon 5G/LTE.
After soft-bricking my new phone by flashing TWRP and crDroid 8.2 based on Android 12, everything seems to be working well except I noticed that I'm not receiving MMS. I went to APN settings but I'm not able to edit the existing ones and if I add a new one, I can't change any settings there except the APN field. I also noticed that my build.prop identifies my phone as LE2123. I confirmed before I modified anything that I have LE2125. Any thoughts on this?
Resolution:
It looks like All LOS based roms as well as TWRP and crDroid recovery are going to show a model of LE2123. It also looks like my MMS issues were caused by YAATA. It's either not compatible with Android 12 or with 5g/VoLTE etc. I ended up restoring back to factory using MSM tools and then installed one thing at a time until I narrowed it down to YAATA. Uninstalled and problem resolved
If I'm not mistaken crDroid is
LOS based where Derpfest is AOSP based
Why would you post an issue with crDroid in a separate post instead of reporting it in the actual rom's thread?
ive had that happen on occasion. the latest bug i seem to have acquired is that during the phone connection where and when the person making the call (me) in said scenario wait's for the other party to answer does not hear anything until either some one answers or their voicemail does.
I've got the same issue with the no ringing during a call on Derpfest rom but doesn't really bother me much I've gotten used to it
Elrey567 said:
I've got the same issue with the no ringing during a call on Derpfest rom but doesn't really bother me much I've gotten used to it
Click to expand...
Click to collapse
i have noticed that whenit says LE2125, and not 2123, both issues do not exist.
oneszero said:
i have noticed that whenit says LE2125, and not 2123, both issues do not exist.
Click to expand...
Click to collapse
just now read your previous post. DERP!
djsubterrain said:
Why would you post an issue with crDroid in a separate post instead of reporting it in the actual rom's thread?
Click to expand...
Click to collapse
I actually did post in the crDroid thread and got no response so then I made a separate thread
0siribix said:
I actually did post in the crDroid thread and got no response so then I made a separate thread
Click to expand...
Click to collapse
upon further testing,it only happens after cRDroid is flashed. Think it might have to do with the boot..img? Under the Model tab, I'm curious, what Platform does your phone say your is?
oneszero said:
upon further testing,it only happens after cRDroid is flashed. Think it might have to do with the boot..img? Under the Model tab, I'm curious, what Platform does your phone say your is?
Click to expand...
Click to collapse
It says lahaina
0siribix said:
I actually did post in the crDroid thread and got no response so then I made a separate thread
Click to expand...
Click to collapse
Opening multiple threads like this won't help but make this place worse. Did you try contacting the Developer in the device group chat? The majority of the devs nowadays use Telegram groups for communication between users/devs. Also, without providing proper LOGS, don't expect any kind of support or reply from a developer. Friendly advice.
ekin_strops said:
Opening multiple threads like this won't help but make this place worse. Did you try contacting the Developer in the device group chat? The majority of the devs nowadays use Telegram groups for communication between users/devs. Also, without providing proper LOGS, don't expect any kind of support or reply from a developer. Friendly advice.
Click to expand...
Click to collapse
In my defense, I opened a single thread, not multiple. When I didn't get a response for two days in the crDroid thread, I assumed that if I was going to get any support that a dev would ask for the logs or other info they need. I mean, what's the point of going through the trouble of obtaining logcat and uploading it just to be ignored
Also, FWIW, I searched around this forum and google for a while before I started this thread precisely to avoid this situation.
Anyway from what I'm gathering, it sounds like maybe LOS 19 for this phone is not quite ready. I think I'll flash TWRP and go back to crDroid 7 for a bit. I might try one of the AOSP variants but I've always leaned toward the LOS flavors in the past
It looks like All LOS based roms as well as TWRP and crDroid recovery are going to show a model of LE2123. It also looks like my MMS issues were caused by YAATA. It's either not compatible with Android 12 or with 5g/VoLTE etc. I ended up restoring back to factory using MSM tools and then installed one thing at a time until I narrowed it down to YAATA. Uninstalled and problem resolved