I've installed a variety of custom ROMs on my OP9 (EvolutionX, Nameless, Extended) and they all have the exact same problem: audio doesn't work properly, buggy, randomly would not connect to my Google account, etc. Since they all had the exact same issues, my guess is that it's a problem with my phone and not the ROMs themselves.
Does somebody know anything about the problem and what can I do to fix them? I'm fed up with OOS and would really like to use another ROM.
Ok everything you have listed is built from Lineage aosp. Therefore everything is gonna have same bug. If you notice the lemonade/p official lineage builds have stopped around the 12th and 14th of February .New ones are coming soon with merged patch that fixes all issues. Then devs from other roms will build on new fixed source and so on. Like throwing a pebble in a pond. Takes time for the ripple to get out. Watch lineage os website/downloads/op9
rodri_rebag5 said:
I've installed a variety of custom ROMs on my OP9 (EvolutionX, Nameless, Extended) and they all have the exact same problem: audio doesn't work properly, buggy, randomly would not connect to my Google account, etc. Since they all had the exact same issues, my guess is that it's a problem with my phone and not the ROMs themselves.
Does somebody know anything about the problem and what can I do to fix them? I'm fed up with OOS and would really like to use another ROM.
Click to expand...
Click to collapse
maybe you flashing over incompatible firmware
mattie_49 said:
Ok everything you have listed is built from Lineage aosp. Therefore everything is gonna have same bug. If you notice the lemonade/p official lineage builds have stopped around the 12th and 14th of February .New ones are coming soon with merged patch that fixes all issues. Then devs from other roms will build on new fixed source and so on. Like throwing a pebble in a pond. Takes time for the ripple to get out. Watch lineage os website/downloads/op9
Click to expand...
Click to collapse
That makes a lot of sense. I was wondering how the same issues presented with every ROM I installed. Thanks for the reply, I will wait for the new builds to start rolling out and then test them again.
Eric_Lev said:
In progress ... Be patient !
https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8350/+/349350
Workaround : https://forum.xda-developers.com/t/rom-official-lemonade-13-lineageos-20.4536697/post-88176351
Edit about workaround : 4 days of uptime without the binder issue.
Click to expand...
Click to collapse
Try the workaround until the fix is included.
downhere said:
Try the workaround until the fix is included.
Click to expand...
Click to collapse
This looks very promising, apparently it solves most of the issues I was experiencing. The only thing I'm scared of is that issues such as my Google account not loading would not be fixed.
rodri_rebag5 said:
This looks very promising, apparently it solves most of the issues I was experiencing. The only thing I'm scared of is that issues such as my Google account not loading would not be fixed.
Click to expand...
Click to collapse
That setup with cached_apps_freezer fixes the Google issues. No issues for me any more.
downhere said:
That setup with cached_apps_freezer fixes the Google issues. No issues for me any more.
Click to expand...
Click to collapse
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
rodri_rebag5 said:
That makes a lot of sense. I was wondering how the same issues presented with every ROM I installed. Thanks for the reply, I will wait for the new builds to start rolling out and then test them again.
Click to expand...
Click to collapse
It's binder issues
rodri_rebag5 said:
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
Click to expand...
Click to collapse
After you've installed build.
rodri_rebag5 said:
Then it's a miracle, I genuinely thought this was unfixable. Thanks a lot.
Just to clarify, do I run the command in stock OOS or once I've installed the ROM?
Click to expand...
Click to collapse
You can use Developer Options of the custom ROM.
Thanks for all the answers, I will flash a ROM probably later tonight and try the cached_apps_freezer fix.
Related
This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26
Thanks for keeping support for the Note 3 alive.
Great, good to see 12.1 back alive. Anything I can do to help, just say so.
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Straw poll whether to include root in the build here http://strawpoll.me/7191529
trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have
trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure
Cm14 nightlys / Lineage OS are officially available through your update setting or through www.get.cm!
Known Bugs:
Camera sometimes not working with third party camera apps (snap camera tested, works fine)
No Sim Card - resolved
Flashlight not turning on/off seemingly at random
CM 14 Nightlies changelog :
https://www.cmxlog.com/14.1/hiaeuhl/
https://www.cmxlog.com/14.1/hiaeul/
testing... firts bug, no sim card detected on A9 USA unlocked.
=(
What firmware does this require? And is force encryption still enabled? I haven't updated in months...
djsubtronic said:
What firmware does this require? And is force encryption still enabled? I haven't updated in months...
Click to expand...
Click to collapse
From 1.5x onwards. Encryption is enforced, the boot patcher to disable it still works.
ultramal said:
testing... firts bug, no sim card detected on A9 USA unlocked.
=(
Click to expand...
Click to collapse
Yes, i Suspect it has something to do with the modem firmware Hope it gets fixed in the next nightly,
presumably they will start occurring daily again?
The_scam said:
Yes, i Suspect it has something to do with the modem firmware Hope it gets fixed in the next nightly,
presumably they will start occurring daily again?
Click to expand...
Click to collapse
Intervigil compiled a couple earlier builds of cm 14/14.1 and the radio worked fine on both so I'm sure it's something fairly minor broke in this first official build.
Sent from my HTC One A9 using Tapatalk
The_scam said:
Yes, i Suspect it has something to do with the modem firmware Hope it gets fixed in the next nightly,
presumably they will start occurring daily again?
Click to expand...
Click to collapse
scott8281 said:
Intervigil compiled a couple earlier builds of cm 14/14.1 and the radio worked fine on both so I'm sure it's something fairly minor broke in this first official build.
Click to expand...
Click to collapse
Most likely because this was built by the bot, the one for hiaeuhl didn't even build.
Jenkins is not working quite well, no builds for a couple of days and stopped again now.
Ultramanoid said:
Most likely because this was built by the bot, the one for hiaeuhl didn't even build.
Jenkins is not working quite well, no builds for a couple of days and stopped again now.
Click to expand...
Click to collapse
Are you sure it has stopped? The last build was not 24 hours ago...
Does anyone know when the hiaeuhl version of 14.1 comes out ?
In the device wiki it already shows that 14.1 is supported, but there is no new nightly build to download.
The_scam said:
Are you sure it has stopped? The last build was not 24 hours ago...
Click to expand...
Click to collapse
It builds alphabetically, and it was stopped at bullhead. It seems to be building now again.
It's easy to check at any time : https://jenkins.cyanogenmod.org
It says no SIM for everyone apparently, I would wait to flash. Here's the strange thing: cell standby is using extreme amounts of battery
Update: I did a dirty backflash to an unofficial version, Cell DID not work. Hmm.
The Buildbot is back to work, but just in case, I'm gonna try to build, depends on how much space I have left.
Steve just posted this. I'm hoping he's simply referring to Cyanogen Inc. It looks as though CyanogenMod is progressing along just fine.
Sent from my HTC One A9 using Tapatalk
Why no love for the Sprint version? How hard is it to port it over from the GSM source? I've never tried building a ROM before but I'm willing to learn. Read this page: https://wiki.cyanogenmod.org/w/Doc:_porting_intro and plan on getting a VM set up and working through it this weekend.
The_scam said:
It says no SIM for everyone apparently, I would wait to flash. Here's the strange thing: cell standby is using extreme amounts of battery
Update: I did a dirty backflash to an unofficial version, Cell DID not work. Hmm.
Click to expand...
Click to collapse
Really? I used the unofficial build of cm14.1 for about a solid month without a sim error, how strange...
MGfusion said:
Really? I used the unofficial build of cm14.1 for about a solid month without a sim error, how strange...
Click to expand...
Click to collapse
Yes, but it was dirty.. and a backflash. so some components were most likely ineligible for downgrade
The_scam said:
Yes, but it was dirty.. and a backflash. so some components were most likely ineligible for downgrade
Click to expand...
Click to collapse
Ah, that makes sense. I read to quickly, missed the part that said "dirty flashback"
MGfusion said:
Ah, that makes sense. I read to quickly, missed the part that said "dirty flashback"
Click to expand...
Click to collapse
Yes,
Also, my own build got stopped so I'm gonna use the on being built through the Jenkins buildbot its about 95% done and then gonna upload later
The_scam said:
Yes,
Also, my own build got stopped so I'm gonna use the on being built through the Jenkins buildbot its about 95% done and then gonna upload later
Click to expand...
Click to collapse
I think I'm just going to wait until the builds become a bit more stable, and hang around on the stock sense ROM for a bit
I have nothing to do with the ROM.
I just happened to find it available to download at the usual Android file hosting spot.
I'm not a tester or affiliated in any way.
I will not post links out of respect for the dev's.
But if you've been around, then you know the usual places to look and how to find ROM's.
-----------------------------
Bootlegger's ROM
They usually base on GZOSP?
Placing a phone call reboots phone. I believe that's a known issue on all custom ROM's ATM.
Tried installing opengapps but while the zip doesn't have any errors during install, nothing got installed. I think that's another known issue across the board.
What's nice though is Bootlegger's already has a bunch of customization options built in. :good:
Center clock option obviously doesn't work too well (hello stoopid notch). :laugh:
Steps to install ROM
Boot to TWRP
Install ROM.zip
Install TWRP.zip (because ROM install removes it)
Reboot and play
CZ Eddie said:
Placing a phone call reboots phone. I believe that's a known issue on all custom ROM's ATM.
Tried installing opengapps but while the zip doesn't have any errors during install, nothing got installed. I think that's another known issue across the board
Click to expand...
Click to collapse
If you know the Dev, let them know about DU trees.
There's no such issues on dirty unicorn.
It kind of defeats the purpose of having a phone if every time you get a call the phone reboots! I'm grateful that work is being done on custom ROMs but at this time, at least to me is a no go if I can't receive a phone call on my phone. After all, that's why I have a phone. Also, is there a link? I don't see one on the OP.
No link because it's considered rude to post links to a devs work without their permission.
I'm sure when the ROM is ready for prime-time, they will post a thread for it over in the ROM section?
I read in another section that Hangouts phone works on these new ROM's devs are building/tinkering with right now.
Paradoxxx said:
If you know the Dev, let them know about DU trees.
There's no such issues on dirty unicorn.
Click to expand...
Click to collapse
I see that DU has been working on the Pixel 3(XL) for half a month now, any inclination as to why it isn't public yet?
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
I see that DU has been working on the Pixel 3(XL) for half a month now, any inclination as to why it isn't public yet?
Click to expand...
Click to collapse
Most maintainers don't like releasing a build until most important things work such as ril, volte, mms, etc etc.
superchilpil said:
I see that DU has been working on the Pixel 3(XL) for half a month now, any inclination as to why it isn't public yet?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
AnierinB said:
Most maintainers don't like releasing a build until most important things work such as ril, volte, mms, etc etc.
Click to expand...
Click to collapse
No idea.
I built it, everything was working perfectly. Did not find any issues at all, and was using it until yesterday's December images dropped.
Ahoi,
the guys from f(x)tec said they would send out some devices to developers of custom roms including lineage to help development of the rom. Did this already happen? Do lineage devs have the phone and did they start porting? Just curious if that happens at all. I'm hoping to put lineage on mine asap.
There are few developers who are making Lineage OS and Sailfish OS for Pro1. Chen showed some alpha build on Twitter previously. Also, devs has the source code since last month.
https://mobile.twitter.com/chenliangchen/status/1148357734204616704
https://mobile.twitter.com/tdmcode/status/1180553338389028865
http://talk.maemo.org/showpost.php?p=1560008&postcount=2235
chen said:
What I can confirm is that there are 2 senior developers has been working on Lineage OS since a while ago. And they've made some great progress. (All the credit goes to them)
They are awaiting for the official release and can move the porting project into the next stage I believe.
That's as far as I know, and again, it's a great work of Lineage community.
PS: When I tried to flash SFOS initial release onto Pro1 I need to flash a custom TWRP, which is I believe also from Lineage OS devs.
Click to expand...
Click to collapse
https://github.com/tdm?tab=repositories
With the email today confirming those who are in the first batch, we're getting close! What I think would be really nice would be working TWRP so can make stock backup on day zero. And of course for root, los, or sfos...
enigma9o7 said:
https://github.com/tdm?tab=repositories
With the email today confirming those who are in the first batch, we're getting close! What I think would be really nice would be working TWRP so can make stock backup on day zero. And of course for root, los, or sfos...
Click to expand...
Click to collapse
As a member of the proto guys, I can assure you that the fastboot images will get released quickly. We have the shipping firmware, maybe there'll be simply a website for that. A working TWRP exists, but keep in mind system-as-root limitations.
j1505243 said:
A working TWRP exists, but keep in mind system-as-root limitations.
Click to expand...
Click to collapse
Does backup work now? I'd heard the earliest port worked for flash but not backup.
Any chance you can share? I expect my phone any day now...
enigma9o7 said:
Does backup work now? I'd heard the earliest port worked for flash but not backup.
Any chance you can share? I expect my phone any day now...
Click to expand...
Click to collapse
Backups require decryption support, but since it's a stock msm8998 platform you can expect that rather quickly. Sharing is what I'll leave to the original creators, we're informed about the shipment progress.
j1505243 said:
keep in mind system-as-root limitations.
Click to expand...
Click to collapse
Don't suppose you have a link that could explain this to people who have no idea what you mean?
I think this has something to do with the fact that even as root in Android if you modify stuff in /system it doesn't stick after reboot. But I'm really only guessing and haven't bothered to read up on it yet.
enigma9o7 said:
Don't suppose you have a link that could explain this to people who have no idea what you mean?
I think this has something to do with the fact that even as root in Android if you modify stuff in /system it doesn't stick after reboot. But I'm really only guessing and haven't bothered to read up on it yet.
Click to expand...
Click to collapse
System-as-root means that /system is mounted as /, but it also means that recovery is a part of boot image, so flashing it as the whole boot partition won't let you boot the system. There'll be a need for TWRP installer script.
enigma9o7 said:
Don't suppose you have a link that could explain this to people who have no idea what you mean?
I think this has something to do with the fact that even as root in Android if you modify stuff in /system it doesn't stick after reboot. But I'm really only guessing and haven't bothered to read up on it yet.
Click to expand...
Click to collapse
https://source.android.com/devices/bootloader/system-as-root
https://twitter.com/tdmcode/status/1197945254906777600
Test builds are available:
- http://files.nwwn.com/android/pro1/lineage.html
Initial impressions?
Flash-A-Holic said:
Test builds are available
Click to expand...
Click to collapse
Thanks for posting this. I've been unable to find any impressions as to the stability of these ROMs. Yes, they are testing roms, but IME there are testing roms and then there are testing roms.
Are these the former (unsupported but mostly stable) or the latter (you don't want any of your real data on it, will crash at random times and missing core functionality)?
maplesteel said:
Thanks for posting this. I've been unable to find any impressions as to the stability of these ROMs. Yes, they are testing roms, but IME there are testing roms and then there are testing roms.
Are these the former (unsupported but mostly stable) or the latter (you don't want any of your real data on it, will crash at random times and missing core functionality)?
Click to expand...
Click to collapse
It's been stable for some time now. I'll be posting a thread here in the next day or two and making lineage official in the next week or two.
tdm said:
It's been stable for some time now. I'll be posting a thread here in the next day or two and making lineage official in the next week or two.
Click to expand...
Click to collapse
Great to hear it TDM.
Cannot give you enough kudos after lurking in the lineageOS test forum thread and seeing all the work you have been doing.
I may even give AOKP a try once you've had a chance to look at it. Lineage is great but it's been years since the Halcyon days of having _multiple_ viable on-stock Androids!
Anyone was aware about this ROM... Installed yesterday and as of now running smoothly... If anyone interested give a shot. Links are
Bliss ROM
boot.img
And no illustrations : không chắc::đảo mắtn)
Raj Pandiyan said:
Anyone was aware about this ROM... Installed yesterday and as of now running smoothly... If anyone interested give a shot. Links are
Bliss ROM
boot.img
Click to expand...
Click to collapse
Nice, who's building it?
Edmontonchef said:
Nice, who's building it?
Click to expand...
Click to collapse
Actually I was using their GSI on my previous device. I got notified from their blog regarding this... That's why shared...
Bliss Roms
Downloads
general question: what's the with move away from roms listing features or including screenshots these days? both blissroms and lineageOS have fancy websites with almost no details on what the roms offer and no screenshots. i get that they are free and owe me nothing but why on earth would i install any of them (and wipe my data) with no information on what i stand to gain?
c_tho said:
general question: what's the with move _away_ from roms listing features or including screenshots these days? both blissroms and lineageOS have fancy websites with almost no details on what the roms offer and no screenshots. i get that they are free and owe me nothing but why on earth would i install any of them (and wipe my data) with no information on what i stand to gain?
Click to expand...
Click to collapse
Exactly I was wondering about the same riddle... Even I came across while just surfing... There is no forum I can put this point up as the only discussion is through telegram and I'm least interested in that...
Raj Pandiyan said:
Exactly I was wondering about the same riddle... Even I came across while just surfing... There is no forum I can put this point up as the only discussion is through telegram and I'm least interested in that...
Click to expand...
Click to collapse
oh my goodness, telegram is an absolute nightmare, can you imagine trying to work out a list of rom features from a telegram channel? surely one of the worst places to get this kind of information.
anyway i don't like to complain, i'm sure the rom is very good, just a strange phenomenon i've been wondering about lately. i would have thought with stock android getting so much better over the years, rom devs would have had more reason to be more explicit about what their roms offer, rather than less. oh well.
New update guys!!!!!!!!
ROM
& same boot.img referred earlier....
This one is amazing..... June security patch...
c_tho said:
oh my goodness, telegram is an absolute nightmare, can you imagine trying to work out a list of rom features from a telegram channel? surely one of the worst places to get this kind of information.
anyway i don't like to complain, i'm sure the rom is very good, just a strange phenomenon i've been wondering about lately. i would have thought with stock android getting so much better over the years, rom devs would have had more reason to be more explicit about what their roms offer, rather than less. oh well.
Click to expand...
Click to collapse
Bliss Roms Blog
Bliss ROM Downloads
Cheers!!!!
edit: latest wont boot from clean flash... spinning boot logo ??
edit: previous version boots.. lets try update that..
badaas said:
edit: latest wont boot from clean flash... spinning boot logo ??
edit: previous version boots.. lets try update that..
Click to expand...
Click to collapse
Actually I downloaded the boot and used rom ( may release )... Got updated automatically... Working perfectly fine with no issues
boot doesnt work with june! can only install june via ota from may.....need new boot.img from payload.bin
June boot extracted:
Random reboots. Think it's location based as used to happen on my Xiaomi when going outside...
Still nags about update even though it's installed..
Auto brightness stopped working needs reboot.
But I do like the roms battery idle and usage, very good!
badaas said:
Random reboots. Think it's location based as used to happen on my Xiaomi when going outside...
Still nags about update even though it's installed..
Auto brightness stopped working needs reboot.
But I do like the roms battery idle and usage, very good!
Click to expand...
Click to collapse
I am using this ROM and as of now it's fine. Yes, there is some issue with auto brightness... Rest I hope it's sorted... It's smooth.... Battery optimization is also good...
Does it keep asking to update on reboot?
badaas said:
Does it keep asking to update on reboot?
Click to expand...
Click to collapse
No.... U update play store... that should fix that... Delete the ROM update that shows even after updating...
... Edit...
Same random reboot when going the shops. 2 different kernels, take phone out to check, soon as turn screen on, death.
badaas said:
Same random reboot when going the shops. 2 different kernels, take phone out to check, soon as turn screen on, death.
Click to expand...
Click to collapse
Pls post on official forum bro.... It's up now in ROMs forum XDA...