Related
Hi guys,
I tried to flash the Franco kernel with the CM11 snapshot M9, for some reason i get pixel distortion top right. Where the cell bars show, sometimes over the complete right side of the screen.
Thereafter i re-flashed the rom directly following with the franco kernel, same result though.
Any ideas?
Thanks!
Its known issue. Graphics overlay on screen touch.
Workaround: Goto 'Developer Options' and disable Hardware Overlays.
U have to do this every time u reboot the phone.
Update your ROM, you're using a outdated ROM thats lacking the commits. Easier to update your ROM than to do a workaround on every reboot.
zephiK said:
Update your ROM, you're using a outdated ROM thats lacking the commits. Easier to update your ROM than to do a workaround on every reboot.
Click to expand...
Click to collapse
You're saying there is an update for stable version?
Or do you mean flashing the latest nightly?
Thanks for the answers guys!
Waanzin said:
You're saying there is an update for stable version?
Or do you mean flashing the latest nightly?
Thanks for the answers guys!
Click to expand...
Click to collapse
Latest nightly.
What samflorin said, M10 is out for some phones. OnePlus One is still being worked on so they didn't push M10 yet. When it does, it should be very close to the OTA.
M9 was a very old build that lacked the commits causing conflict on the kernel side of things. Once you update, all should be good
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
Hello, everyone, is there anyone ever tried Xposed on HTC U11?
Earlier today, I saw there's someone posted pics showing Xposed working on HTC M9 and 10 with Nougat 7.1.2 on Weibo (A Chinese social media), and someone replied it also worked on HTC U11. I searched on XDA and found the following thread for the unofficial Xposed released for Nougat, saying the available versions are：
-Xposed SDK25 ARM64
-Xposed SDK25 ARM
-Xposed SDK25 X86
Here is the original thread:
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
So I just wanna know if anyone tried it on HTC U11, is there any bugs or bootloop problems?
If nobody ever tried, I would try it these two days, and anyone who ever used Xposed, please give some advise to me to avoid potential risk since I've been not using android for a long time and never sideloaded any Xposed frame.
@altimax98 had and didn't seem to be too fond about it
altimax98 said:
Tried Xposed
Don't do that
It installs fine, but soon you get random reboots and random FC's on applications. It works though
Click to expand...
Click to collapse
starkdon said:
Hello, everyone, is there anyone ever tried Xposed on HTC U11?
Earlier today, I saw there's someone posted pics showing Xposed working on HTC M9 and 10 with Nougat 7.1.2 on Weibo (A Chinese social media), and someone replied it also worked on HTC U11. I searched on XDA and found the following thread for the unofficial Xposed released for Nougat, saying the available versions are：
-Xposed SDK25 ARM64
-Xposed SDK25 ARM
-Xposed SDK25 X86
Here is the original thread:
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
So I just wanna know if anyone tried it on HTC U11, is there any bugs or bootloop problems?
If nobody ever tried, I would try it these two days, and anyone who ever used Xposed, please give some advise to me to avoid potential risk since I've been not using android for a long time and never sideloaded any Xposed frame.
Click to expand...
Click to collapse
Yeah I wouldnt use it. It started with random apps I was not even using force closing, like the dialer, FB Messenger, and Sync for Reddit. Then I rebooted and it kept rebooting from the lockscreen, but only back to the boot logo. It did that 3 times and then ran fine for a while, then the FC's started again.
Uninstalled it and all is back to normal.
altimax98 said:
Yeah I wouldnt use it. It started with random apps I was not even using force closing, like the dialer, FB Messenger, and Sync for Reddit. Then I rebooted and it kept rebooting from the lockscreen, but only back to the boot logo. It did that 3 times and then ran fine for a while, then the FC's started again.
Uninstalled it and all is back to normal.
Click to expand...
Click to collapse
Thanks for such info bro, in this case I'd better wait for a stabler version.
velimirchek said:
@alimax98 had and didn't seem to be too fond about it
Click to expand...
Click to collapse
Emmm, maybe because of different rom, which rom are you using, HTC official RUU or 3rd party? I'm on viper 1.4.0.
starkdon said:
Emmm, maybe because of different rom, which rom are you using, HTC official RUU or 3rd party? I'm on viper 1.4.0.
Click to expand...
Click to collapse
Emmm, I didn't install it just pointed you to someone that did
velimirchek said:
Emmm, I didn't install it just pointed you to someone that did
Click to expand...
Click to collapse
Yeah thx man, he also replied, I saw his reply and maybe should just wait.
Hmm anyone else tried to see if this working? I know it's still not stable.
installed in ViperU 1.5 rom and all of the things is worked.
No force close and not rondom reboot.
Use the last update and enjoy it.
No need to wait for rovo89 release.
Sent from my HTC U11 using Tapatalk
marvi0 said:
Hmm anyone else tried to see if this working? I know it's still not stable.
Click to expand...
Click to collapse
Actually I'm using it now, I go to the thread I mentioned, chose the latest arm 64 sdk 25 version.
I'm using viper 1.5.0 and it works fine, I didn't get too much FC only magisk manager FC sometimes. Some modules are not compatible with Android N yet, you can search the list in Xposed forum.
But also remember to backup your data before flashing.
Good luck.
arianat said:
installed in ViperU 1.5 rom and all of the things is worked.
No force close and not rondom reboot.
Use the last update and enjoy it.
No need to wait for rovo89 release.
Click to expand...
Click to collapse
Yep, I also tried it just yesterday not too much problems only some modules not compatible and no FC except magisk manager. Hope we will have more modules on magisk soon.
Hmm so those on viper seem to be in luck. Has anyone else used xposed on stock rom?
Still no one here with stock ROM trying Xposed mode?
any update on this? Is it usable now?
xposed for Oreo is released and now work in oreo u11
i intalled and tested but a module like luckyPatcher dosnt work now
That's a link to Lowes.com!
Currently rooted and xxxnolimits installed and magisk and twrp installed and working fine.
Now getting notified about updating but I'm hesitant. Doesn't seem to be many Roms for android 11 and not sure if Magisk compatible with 11
So for any 7 pro users is it best to stick with 10 until more roms come on board and more app compatible
Cheers
Here are a few things that I will consider before upgrading;
Changelog of the new vendor update.
Any specefic feature that I am in desperate need off and vendor finally relased it.
Magisk support as a rooting method. Modules, meh..
Obviously kernel patches.
You mentioned xXx NoLimit ROM, as per my knowledge it is OTA independent. If I were you, I wouldn't just upgrade, why?
Magisk support for new oos11 is limited.
It's probably early builds, lot of bugs ready to jump out in the wild.
Wait for a while, let 1 or 2 roms surface, let vendor fix ___ glitch in ___ iface. And what do you know, a quick google query brings up some nice corpses from vendor's closet..!
Yeah seems the scales tip to the remain as is
If it ain't broke no need to fix it
Still getting notifications to update
Is there a compatible version of twrp and Magisk for os11
Also any os11 roms worth keeping an eye on any posts or updates
Cheers
No don't update to Android 11.. Its too buggy and eating battery life
Twrp is not available for android 11, but magisk is.
If you're rooted, freeze the system update app so that you stop getting notifications.
And, most people are waiting to upgrade since 11 and 11.0.2 aren't quite perfect or way different yet.
nabril15 said:
Twrp is not available for android 11, but magisk is.
If you're rooted, freeze the system update app so that you stop getting notifications.
And, most people are waiting to upgrade since 11 and 11.0.2 aren't quite perfect or way different yet.
Click to expand...
Click to collapse
Cheers looking through apps on titanium to freeze system update app.. Any ideas what's it called as can't seem to see it
funkyirishman said:
Cheers looking through apps on titanium to freeze system update app.. Any ideas what's it called as can't seem to see it
Click to expand...
Click to collapse
It's called System Update 2.1.3.2010...........(more numbers....) on mine.
Ben81 said:
It's called System Update 2.1.3.2010...........(more numbers....) on mine.
Click to expand...
Click to collapse
Cheers see it now thanks
funkyirishman said:
Cheers looking through apps on titanium to freeze system update app.. Any ideas what's it called as can't seem to see it
Click to expand...
Click to collapse
It's called System Updates
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.