Related
http://forum.xda-developers.com/showpost.php?p=56292388&postcount=15
http://forum.xda-developers.com/showpost.php?p=56292388&postcount=15
http://forum.xda-developers.com/showpost.php?p=56292388&postcount=15
:highfive: somebody test it & say howz it? will try then..
thanx @Ashwin Prabhunerurkar for CM
brother you a killer
finally feeding to dead devices
waited a long for this
thanks thanks thanks a lot
Finally CM
Thanks A Lot Developers
Sorry But I won't be Flashing It Until the Bugs gets Sorted Out.
I want to Use it as My Daily Driver
surely the best diwali gift for t2 owners
Great Job Man!!!! Big THANKS to ALL the developers!!!!:thumbup:
I would love to test it, but, unfortunately camera is a must for me. I'll wait till the bug gets sorted !!!
Sent from my D5322 using XDA Premium 4 mobile app
Camera Fix
Glad to see the first (nonstock) basec custom ROM. Couple of noob questions - does the bootloader needs to be unlocked for this. I have a rooted phone with dual recovery.
What are the camera files you have tried copying to this ROM from the Ultra Dual. I am presuming you have already done it but thought i could chime in. Have you copied libcameracustom.so and libcameraservice.so?
kan_ranga said:
Glad to see the first (nonstock) basec custom ROM. Couple of noob questions - does the bootloader needs to be unlocked for this. I have a rooted phone with dual recovery.
What are the camera files you have tried copying to this ROM from the Ultra Dual. I am presuming you have already done it but thought i could chime in. Have you copied libcameracustom.so and libcameraservice.so?
Click to expand...
Click to collapse
to have CyanogenMod you have to flash a custom kernal and to flash custom kernal you have to unlock the bootloader
this i my understanding
abt camera its my observation in CyanogenMod camera is always issue in early built but getting fixed later on
so i am sure in next built it will get fixed
THANK YOU SO MUCH FOR THIS!!! If not for the camera and led issues, I would gladly test it for you right away!
Super ninja edit: I think this belongs in original android development.
Sent from my D5322 using XDA Premium 4 mobile app
Can't Thank you enough for this...
P.S please fix the camera, and consider the feature request I have submitted in the panel, since that (feature request) is one the biggest flaws with the Stock ROM
Thanks again
This is not cool. You have published a ROM based on unmodified sources of other people's work, which is still incomplete, and is in fact worse than the current status of that work.
This is (probably) against the rules of XDA and has been reported.
Not only that but you explicitly state that you have no idea how to fix the issues present in this ROM. Anyone who installs this ROM risks damaging their device.
We didn't released the ROM for a reason. Do not use the sources to build the ROM without permissions and act like dev when you didn't contribute even one bit. These sources were not meant for a public release yet. AdFad did all the major work on this so atleast ask him before doing such stuff. Reported the thread, proper action will be taken soon.
Moreover you are asking for thanks for such kang
AJ
Thread closed. The OP of this thread hasn't taken part in the development and released it without credits. You should all wait for original developers to release it.
I'm really disappointed to see such situations on XDA.
Thank you,
Tom
Good day XDA!! This is my first ever post or thread on XDA, for about 5 years I have been a spectator to this site, and it has been an essential source for all things us android foondies want and need. But for the past month I have hit a blank when it comes to my new tab3 ve 7.0 sm-t116nq (goyave3g).
It started when I wanted to root it, little to no support for this model was available (at least through the search function) I managed to root through Kingo root on a pc. But now my dilemma is finding/porting rooms for this model. I have no problem with all my Mediatek androids, but I'm in the dark when it comes to samsung. I don't even know where to begin, for other popular Samsung's it's not a problem, obviously because they're popular.
SO, I need some help. I hate this abomination they call touchwiz, I want a vanilla aosp rom for this model, or even better CM or PAC-MAN rom!! I am prepaid to put a lot of time and effort into this. I have extremely limited experience, most of my past successes was actually the success of other xda members (you guys are awesome BTW.) Any info would be apriciated.
So let's revive this tablet and let's start a revolution for budget tablets.
Dudzzz576 said:
Good day XDA!! This is my first ever post or thread on XDA, for about 5 years I have been a spectator to this site, and it has been an essential source for all things us android foondies want and need. But for the past month I have hit a blank when it comes to my new tab3 ve 7.0 sm-t116nq (goyave3g).
It started when I wanted to root it, little to no support for this model was available (at least through the search function) I managed to root through Kingo root on a pc. But now my dilemma is finding/porting rooms for this model. I have no problem with all my Mediatek androids, but I'm in the dark when it comes to samsung. I don't even know where to begin, for other popular Samsung's it's not a problem, obviously because they're popular.
SO, I need some help. I hate this abomination they call touchwiz, I want a vanilla aosp rom for this model, or even better CM or PAC-MAN rom!! I am prepaid to put a lot of time and effort into this. I have extremely limited experience, most of my past successes was actually the success of other xda members (you guys are awesome BTW.) Any info would be apriciated.
So let's revive this tablet and let's start a revolution for budget tablets.
Click to expand...
Click to collapse
good news,i'm currently developing cm for this tab it might take a while depending on the device itself
Thunderoar said:
good news,i'm currently developing cm for this tab it might take a while depending on the device itself
Click to expand...
Click to collapse
Oh, such a good news, but tell me, will your cm support sm-t113 too bro?
x3m_zion said:
Oh, such a good news, but tell me, will your cm support sm-t113 too bro?
Click to expand...
Click to collapse
dont know, still testing
Thunderoar said:
good news,i'm currently developing cm for this tab it might take a while depending on the device itself
Click to expand...
Click to collapse
How is it going? Any news for us?
danny02 said:
How is it going? Any news for us?
Click to expand...
Click to collapse
i decided to suspend the project because of school though
Estamos presos no Android 4.4.4 =/
Maldito SM-T116BU
But is not there anyone interested in developing a rom with Lollipop for the SM t116? Hardware the device has, a Galaxy J1 mini has almost the same processed and less than 1gb of ram and it runs the Lollipop well
mmacedoc7 said:
But is not there anyone interested in developing a rom with Lollipop for the SM t116? Hardware the device has, a Galaxy J1 mini has almost the same processed and less than 1gb of ram and it runs the Lollipop well
Click to expand...
Click to collapse
hi! you can read here https://forum.xda-developers.com/galaxy-tab-3/development-7/rom-tab-3-lite-sm-t116-goyave-t3537793
pit file
Can anyone help me find pit file for galaxy sm-t116NU??????
OMG, Im also stuck here with SM-T116BU which was officially upgraded to Tab E (somehow) how it happened, i don't know since this was my son's Tab 3v originally.
lately. i have rooted tru inception (nice job for the rooting guys) then tried TWRP 3.1.1.0 but couldnt boot, down ver to TWRP 2.8.7.0 bcos the others are either not TAR for odin or files are missing to boot TWRP recovery.
so far, i have tried CM-13 but failed miserably, perhaps those files are corrupted as well
I enjoyed loading with my "Note3 with touchwiz" DO NOT TRY THIS UNLESS YOU KNOW HOW TO RECOVER, so i tried using the same ROM N9005_TouchWizMM_V4_16-04-2016. installation smoothly with TWRP into TAB E but could NOT make it BOOT.
I guess some files are missing while downloading those as well or those files have been corrupted thru the years.
N9005_TouchWizMM_V4_16-04-2016 not difficult to find but NEED an expert to cook a SM-116 version since this is best "complete" ROM (need kernel) in my Note3 now
I'll keep trying ROM N9005_TouchWizMM_V4_16-04-2016 into THIS TAB E and mixed with SM_116 kernels n I KNOW I MIGHT BRICK THIS SM-116 Tab E, what the HACK so let it be, NO VENTURE NO GAIN hahahaaa
deranche said:
OMG, Im also stuck here with SM-T116BU which was officially upgraded to Tab E (somehow) how it happened, i don't know since this was my son's Tab 3v originally.
lately. i have rooted tru inception (nice job for the rooting guys) then tried TWRP 3.1.1.0 but couldnt boot, down ver to TWRP 2.8.7.0 bcos the others are either not TAR for odin or files are missing to boot TWRP recovery.
so far, i have tried CM-13 but failed miserably, perhaps those files are corrupted as well
I enjoyed loading with my "Note3 with touchwiz" DO NOT TRY THIS UNLESS YOU KNOW HOW TO RECOVER, so i tried using the same ROM N9005_TouchWizMM_V4_16-04-2016. installation smoothly with TWRP into TAB E but could NOT make it BOOT.
I guess some files are missing while downloading those as well or those files have been corrupted thru the years.
N9005_TouchWizMM_V4_16-04-2016 not difficult to find but NEED an expert to cook a SM-116 version since this is best "complete" ROM (need kernel) in my Note3 now
I'll keep trying ROM N9005_TouchWizMM_V4_16-04-2016 into THIS TAB E and mixed with SM_116 kernels n I KNOW I MIGHT BRICK THIS SM-116 Tab E, what the HACK so let it be, NO VENTURE NO GAIN hahahaaa
Click to expand...
Click to collapse
What exactly are you trying to do?
Well. The TouchWiz works perfectly on my note3 so I'll try to cook a TouchWiz for Sm-t116 from the note3 platform. If u have ready ROM, do send them. Tks in advance !
Ps. Out of town next few days ??
deranche said:
Well. The TouchWiz works perfectly on my note3 so I'll try to cook a TouchWiz for Sm-t116 from the note3 platform. If u have ready ROM, do send them. Tks in advance !
Ps. Out of town next few days
Click to expand...
Click to collapse
Guys please give the firmware rom for TVRP on the TAB-3 Lite SM-T116 ! Cause when I for some reason flashed TVPP I realized that there are no custom firmwares for this device , But I need 100% working FI-WI, and cyanogen mod does not fit, cause Wi-Fi doesn't work there!
Need to rollback, or be advised of any custom ROMS that work..
Try Elite ROM from ROM section. it should work fine.
I personally would not recommend installing Elite ROM as it is more hassle than it is worth when you try to switch ROMs. It re/debrands your device and even after restoring a nandroid your audio will not work nor will your camera function properly. What files have bad keys? I put a lot of those up and the keys should work fine....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
@ghostair is your device bricked? IMO none of the ROMs for this phone are worth installing on a main phone because there is too much functionality lost, no disrespect to the devs. Elite ROM does have the least amount of bugs but it is a hassle as I mentioned earlier. My main gripe about it is when installing and uninstalling apps you must restart the device in order for the apps to be added or removed from the app drawer....its a major annoyance.
BLN-L24C567B110 Thanks to @Dazed No More
boot - https://mega.nz/#!ceRkHQoA!L8MECn8Ul...8JwO7ZuVEEr8mk
recovery - https://mega.nz/#!sOZAUJTZ!QKKROoWkI...UPNDwL79ZI1yQI
BLN-L24C567B360 Thanks to @Dazed No More
boot - https://mega.nz/#!hDQB3RCT!YTH2j1IhJ...y_prJHEgHdSrxg
recovery - https://mega.nz/#!Fa4DBbxS!XDIczpXcr...TApUtNvcOMEDnc
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
ghostair said:
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
Click to expand...
Click to collapse
Is your device bricked? You say you want to rollback, but have you started the process....what firmware are you on?
Dazed No More said:
....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
.
Click to expand...
Click to collapse
Let me check mate. Thanks for pointing that out.
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
ghostair said:
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
Click to expand...
Click to collapse
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Im assuming you did not make a full backup in TWRP before flashing any ROMs, in which case you have learned a valuable lesson....always have a backup. But since you dont we will get you back to EMUI which I assume is what you mean when you say roll back.
Dazed No More said:
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Click to expand...
Click to collapse
I understand, I probably should have just used, "go back," to EMUI. Since LOS 13 isn't usable in the least, as I can't make calls, and it drops LTE.
If they work then how? I followed everything, flashing vendor.img with fastboot, then flashing the respective zip?
I'd rather not go back to EMUI, it's why I haven't been able to actually "use it as a phone," since purchase.
Why would you not want to go back to EMUI? Its smooth and everything works. EMUI is the reason you havent been able to use it as a phone?? There is not one single ROM for this device that works entirely and has full functionality. You're always going to be missing something whether its the camera, LTE, calls, etc.
You're going to have to go back to EMUI so you can update to Anrdoid 7.0 (be sure to make a full backup) and then flash away all the ROMS you like and you will see they are all broken in some way. This is most definitely not the phone to use if you are looking for polished ROMs.
My last tip before departing......download the flashable vendor zip if you still want to mess around with the ROMs, it makes life much easier. Its in one of the threads in that forum I think AOKP
Long story short, I'm looking for the most stable and refined custom ROM for the MZP. I'm currently using Alberto97's AOSP 8.1 and while everything is working fine, it isn't really that refined. As it is ported from what I guess is the Google Pixel, the OS thinks that the device is a Google Pixel. For example, when I set up the device, it shows the banner "Finish setting up your Pixel". Also, when I register my fingerprint to unlock the device, the setup shows to use the index finger and touch the sensor located on the rear of the device (like the Pixel's). Charging with the phone powered off is also bugged, as it shows nothing but "Charging ??/100". I know these may seem like small things, but I'm a person with extreme attention to detail (almost borderline OCD) and things like these just bug the hell out of me, even though it isn't the devs fault at all (mad respect to Alberto).
Basically, I want a custom ROM that is MADE for the device, not ported. If you guys get what I mean. Polished is the word, I guess.
Seeing as LineageOS 14.1 is officially supported, do these cosmetic flaws exist? Can any LOS users confirm this? I apologize for bugging this sub with my stupid questions, I just want to settle with my phone once and for all.
Thank you to all for your help!
djdelarosa25 said:
Long story short, I'm looking for the most stable and refined custom ROM for the MZP. I'm currently using Alberto97's AOSP 8.1 and while everything is working fine, it isn't really that refined. As it is ported from what I guess is the Google Pixel, the OS thinks that the device is a Google Pixel. For example, when I set up the device, it shows the banner "Finish setting up your Pixel". Also, when I register my fingerprint to unlock the device, the setup shows to use the index finger and touch the sensor located on the rear of the device (like the Pixel's). Charging with the phone powered off is also bugged, as it shows nothing but "Charging ??/100". I know these may seem like small things, but I'm a person with extreme attention to detail (almost borderline OCD) and things like these just bug the hell out of me, even though it isn't the devs fault at all (mad respect to Alberto).
Basically, I want a custom ROM that is MADE for the device, not ported. If you guys get what I mean. Polished is the word, I guess.
Seeing as LineageOS 14.1 is officially supported, do these cosmetic flaws exist? Can any LOS users confirm this? I apologize for bugging this sub with my stupid questions, I just want to settle with my phone once and for all.
Thank you to all for your help!
Click to expand...
Click to collapse
Hi there,
None of the cosmetic flaws you said exist on the official LineageOS 14.1 ROM. I'm using it for several months now and it is certainly the most polished ROM created for this device.
By the way, I've tested weeks ago Alberto97's AOSP 8.1 and it was a weak experience. It wasn't optimized as I expected, some of the animations were jerky and I noticed multiple bugs.
I definitely recommend using LineageOS 14.1 ROM if you want a good experience. Also, I recommend using 7.1 ROMs instead of 8.0's/8.1's. They are way more stable and optimized.
If you have any question, feel free to ask.
Systemlessly said:
Hi there,
None of the cosmetic flaws you said exist on the official LineageOS 14.1 ROM. I'm using it for several months now and it is certainly the most polished ROM created for this device.
By the way, I've tested weeks ago Alberto97's AOSP 8.1 and it was a weak experience. It wasn't optimized as I expected, some of the animations were jerky and I noticed multiple bugs.
I definitely recommend using LineageOS 14.1 ROM if you want a good experience. Also, I recommend using 7.1 ROMs instead of 8.0's/8.1's. They are way more stable and optimized.
If you have any question, feel free to ask.
Click to expand...
Click to collapse
Sweet, thanks a lot man! I'm going to flash it right now.
Sadly, the flash failed It appears that it doesn't support the Oreo bootloader
djdelarosa25 said:
Sadly, the flash failed It appears that it doesn't the Oreo bootloader
Click to expand...
Click to collapse
What is the error?
Did you flash the official or soak test 8.0 rom before?
Systemlessly said:
What is the error?
Did you flash the official or soak test 8.0 rom before?
Click to expand...
Click to collapse
ERROR 7, my bootloader is not supported
I updated to official 8.0.0 Oreo by sideloading the OTA
djdelarosa25 said:
ERROR 7, my bootloader is not supported
I updated to official 8.0.0 Oreo by sideloading the OTA
Click to expand...
Click to collapse
Oh yeah, that's bad.
You should post a message regarding this issue on the Official Lineage 14.1 topic to make the developper aware. I think that's not hard to make the bootloader compatible, it should be some parameters to change
Systemlessly said:
Oh yeah, that's bad.
You should post a message regarding this issue on the Official Lineage 14.1 topic to make the developper aware. I think that's not hard to make the bootloader compatible, it should be some parameters to change
Click to expand...
Click to collapse
I've been trying to Google ways on how to contact the maintainer but I can't seem to find out how. Can you help me by sending a link on how to message the dev?
djdelarosa25 said:
I've been trying to Google ways on how to contact the maintainer but I can't seem to find out how. Can you help me by sending a link on how to message the dev?
Click to expand...
Click to collapse
According to this link: https://wiki.lineageos.org/devices/addison
It is said that it is mccreary the maintainer.
Here is his mail:
Sean McCreary: [email protected]
https://review.lineageos.org/#/q/owner:mccreary%40mcwest.org+status:merged
Systemlessly said:
According to this link: https://wiki.lineageos.org/devices/addison
It is said that it is mccreary the maintainer.
Here is his mail:
Sean McCreary: [email protected]
https://review.lineageos.org/#/q/owner:mccreary%40mcwest.org+status:merged
Click to expand...
Click to collapse
Holy cr*p, thanks so much, man! :laugh:
am also looking like dis , how smooth los 14.1? what is the present bug? in bootloader case, we can edit build prop instead zip folder
talktosam said:
am also looking like dis , how smooth los 14.1? what is the present bug? in bootloader case, we can edit build prop instead zip folder
Click to expand...
Click to collapse
I contacted the maintainer and he said it's not as simple as that, as there may be incompatibilities with a bootloader from a different Android version. We're messaging each other for the past few days and he sent me a test build. The flash succeeded, though we are unable to make it boot up.
djdelarosa25 said:
I contacted the maintainer and he said it's not as simple as that, as there may be incompatibilities with a bootloader from a different Android version. We're messaging each other for the past few days and he sent me a test build. The flash succeeded, though we are unable to make it boot up.
Click to expand...
Click to collapse
u ask any way to get LOS 15.1? any hope? how can i contact him?
talktosam said:
u ask any way to get LOS 15.1? any hope? how can i contact him?
Click to expand...
Click to collapse
I asked him yesterday but he said that it's against rules to ask for ETAs (even when I only asked him if it would come out, I didn't ask when :/)
Read the thread, one user already posted his email address here, though don't even try to ask him stuff like that again as surely he will link that to me.
djdelarosa25 said:
I asked him yesterday but he said that it's against rules to ask for ETAs (even when I only asked him if it would come out, I didn't ask when :/)
Read the thread, one user already posted his email address here, though don't even try to ask him stuff like that again as surely he will link that to me.
Click to expand...
Click to collapse
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
vbdss said:
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
Click to expand...
Click to collapse
Please see the post above you.
https://forum.xda-developers.com/showpost.php?p=76379057&postcount=16
---------- Post added at 07:06 PM ---------- Previous post was at 07:04 PM ----------
Happy to know that the developer fixed the issue @djdelarosa25. Well, it was a great idea to send him an e-mail.
vbdss said:
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
Click to expand...
Click to collapse
Lineage 14.1 is Nougat based and it will not flash as it will display bootloader error while flashing in twrp. Wait for Lineage 15 or as djdelarosa25 said [/COLOR]
djdelarosa25 said:
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
Click to expand...
Click to collapse
wait till 2nd may
---------- Post added at 05:47 PM ---------- Previous post was at 05:32 PM ----------
djdelarosa25 said:
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
Click to expand...
Click to collapse
Is there any news for Lineage 15? I am kinda use to Oreo so I am looking for an Oreo ROM. I like AOSP no doubt but I'd also like to try a ROM that is build from scratch for MZP only.
Systemlessly said:
Happy to know that the developer fixed the issue @djdelarosa25. Well, it was a great idea to send him an e-mail.
Click to expand...
Click to collapse
Yeah, thanks for helping me, man! The dev was really cool - replies, debugs, and compiles really quickly as well. Talk about pro.
Manish355 said:
Is there any news for Lineage 15? I am kinda use to Oreo so I am looking for an Oreo ROM. I like AOSP no doubt but I'd also like to try a ROM that is build from scratch for MZP only.
Click to expand...
Click to collapse
I already asked him if it was in the works and he said don't ask for ETAs. I asked him again today and told him I wasn't asking for a date, just a confirmation if LOS 15 is in the works. We'll see what he says.
EDIT: So it counts as an ETA then. He said we'll just see it come out (so I guess it is in the works). But I wouldn't worry that much, the dev works really fast.
and yeah, I like a ROM that was made for the MZP as well. As much as I like Alberto's ROM, a ROM built from scratch > a port (though LOS 14.1 is Alberto's work as well). It's a pity he quit development of it.
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