Related
LETS GET THIS LIST GOING!!
I know there are several threads on this allready, but finding the actual information of which roms work and which don't is very hard, so I've decided to make this thread to have a centralized place to list and discuss roms that work with the patch.
First things first:
The verizon patch and information about it can be found here. http://forum.xda-developers.com/showthread.php?t=2055218
Things to remember:
Do Not flash modems from any rom that doesn't have a Verizon Base.
Always make a backup before testing the patch with new roms.
(not sure if kernels are harmfull, or if you need to flash specific verizon kernel after flash, will update when I gather more info, for now this is a list of known working roms and how you got there.
Now the Good Stuff.
I thought since I was making this thread I would jump in and test first. here's what I have so far.
1) Ok, my first attempt wasn't so good. I installed the whompasaurus rom from the sprint forum. Device booted fine, but upon boot I got an Ecryption Failed screen with no way to go any further (to my knowledge anyway) I feel this is stll relevant to the thread. So post your experiences and I will update the op accordingly. I have seen a few roms on the at&t forum that say "no device check" therefore I assume they will work. Time will tell.
Please feel free to list roms that you have succesfully got working with the vzw patch and if you used build prop edits to achieve this as well then please be specific and I will add them to the op as they come in.​
Ive got all the DLL1 and DLL4 roms to work in the att & tmobile forums.
The caveat with Scott's patch is that it is only designed to get TW roms from other carriers working on our devices. While most TW roms will boot fine after the patch, they will more than likely require some build.prop modification to get them completely up to snuff. In the case of porting AOSP roms, the patch isn't entirely useful, save for a few vzw specific system applications, as AOSP doesn't use CSC files. AOSP porting can be done with build.prop adjustments.
Can you elaborate on which build prop edits need to be done, ro.product.model, etc. As I stated above I tab into an encryption problem, would a stock Verizon build pro fix that?
Sent from my SCH-I605 using Tapatalk 2
Jsminnis please add me on gtalk. [email protected]
Background:
Ant+ and Health/Sport accessories are not very widespread among smartphone users, but it was one of the major reasons a which I moved from the Nexus 4 to Galaxy S4.
While S4 on 4.3 works great with my Garmin Heart Rate Monitor(HRM), I'm not satisfied with Touchwiz and Knox.
My S4 feels laggy, slow and I want to use stock android, or even any of those KitKat releases.
Many Xperia devices have Ant+ support, and it seems that they manage to cook it into custom roms successfuly.
Target:
Assemble a flashable zip which would allow anyone with an S4 already flashed to 4.3 to use the Ant+ receiver.
Research:
I've spent some time embeddint the Ant+ files (com.dsi.ant.antradio_library.jar and .xml, and the AntHalService.apl) on MakTail's 4.3 GE but ran into an issue that blocked further investigation:
The AntHalService tries to enable bluetooth, can't find the method and reboots the device.
The version is 3.0.0 which is supplied on Stock ROM, and there is already a 3.1.1 available from Ant Alliance which removes the requirement for enabling bluetooth.
I got the source code and compiled the apk, but I can't run it as a System App, so I got stuck. Spent some time trying to workaround it, but no success.
I guess that even when I get hold of a working 3.1.1, there will be new issues, and I'm a complete newbie on ROM cooking.
So I would like help from others, maybe suggesting next steps or getting hands on with me on this project.
XDA:DevDB Information
Ant+ Support for Non-Stock ROMs, a Tool/Utility for the Samsung Galaxy S 4
Contributors
AdrienC
Version Information
Status: Testing
Created 2013-11-25
Last Updated 2013-11-25
Attached is a file with the system files required for ant which I could find after some investigation.
Links:
Here is the source code for the AntHalService.apk which I couldn't run as System service.
https://github.com/ant-wireless/Android_ANTHALService
And the slooow forum:
http://www.thisisant.com/forum/viewforum/30/
to run as system app if you are rooted just manually copy apk to /system/apk
lgkahn said:
to run as system app if you are rooted just manually copy apk to /system/apk
Click to expand...
Click to collapse
won't work due to the signature I guess. Even when I signed with debug keys didn't work. Maybe due to SELinux?
Code:
I/PackageManager( 707): /system/app/AntHalService.apk changed; collecting certs
W/PackageManager( 707): Signature mismatch for shared user : SharedUserSetting{42a56d98 android.uid.system/1000}
W/PackageManager( 707): SELinuxMMAC.assignSeinfoValue
E/PackageManager( 707): Package com.dsi.ant.server has no signatures that match those in shared user android.uid.system; ignoring!
I am going to flash 4.4 GE edition by Jamal http://forum.xda-developers.com/showthread.php?t=2544474 and will try to survive with my Suunto USB Ant+ stick on OTG to allow me to spend more time trying to make this work.
Will update with any progress/issues.
Well, I send a cry for help to @broodplank1337 and got his awesome reply showing availability and this was my reply, which I decided to share as while I waited for help I made some pretty good advance!
While I was waiting for your reply I made some progress....
I replaced the classes.dex from my compiled apk(from java source) into the samsung apk and that was enough to bypass the cert check ( I was pretty sure I tried that before, but must've done something wrong).
I found out the source code is referencing a kernel module that doesn't exist for Galaxy S4, so I ran Dex2Jar and Java Decompiler and I'm now analysing the source code and I think that it somehow passes the instructions directly to the chip.
I'm thinking about trying to change the bluetooth methods it uses to the ones available on AOSP, which is why the 3.0.0 was failing initially.
It'll probably still take some work, but it might be feasible.
The main issue is that I'm new to android coding, and not a java expert, but used to be a programmer and I'm finding my way (and some joy) hacking thru all this code.
Click to expand...
Click to collapse
I'm attaching the source code for AntHalService.apk from Samsung stock roms (version 3.0.0).
I guess I'll have to work over it, as the 3.1.1 I got from AntWireless references an antradioservice.so which Sammy don't have and causes a bootloop.
I am now comparing the smali code between the 3.0.0 and the 3.1.1 to see if I can do an easy patch, but it's not looking very likely...
Lets see how this goes.
Awesome work guys! I'm really looking forward to be able to finally use my AOSP ROM (Paranoid Android at the moment) with Ant+ support! Just broke the Selfloops OTG dongle... I know many people are looking for a solution in the various fitness and sports communities...
Thanks in advance for your work!
Please please get this to work! I'm rooting for you on my side over here! It would make me one very happy s4 user.
Wouldnt it be nice if cyanogenmod one day supported ant+?
We can only dream.
Any luck? Or is there anything people who cannot code can do to help? This is the one thing I want on my android phone currently.
Guys, an update. I kinda gave up for a while. ANT Forums are helpless, and I got kinda tired of looking around. I'll need to have some free time and motivation to dissect the code and try to make it work on the AOSP bluetooth stack.
A good workaround I found is to have a dual boot solution, so you can switch to the Touchwiz ROM for a training.
karimero said:
Awesome work guys! I'm really looking forward to be able to finally use my AOSP ROM (Paranoid Android at the moment) with Ant+ support! Just broke the Selfloops OTG dongle... I know many people are looking for a solution in the various fitness and sports communities...
Thanks in advance for your work!
Click to expand...
Click to collapse
blue6800user said:
Please please get this to work! I'm rooting for you on my side over here! It would make me one very happy s4 user.
Wouldnt it be nice if cyanogenmod one day supported ant+?
We can only dream.
Click to expand...
Click to collapse
blue6800user said:
Any luck? Or is there anything people who cannot code can do to help? This is the one thing I want on my android phone currently.
Click to expand...
Click to collapse
Thanks, hope to eventually come with good news, got kinda sad to hit a wall. But meanwhile, use your favourite rom and dual boot a Touchwiz ROM.
I'm now back to the last released version of 4.3 for Brasil to soon extract the libs and apk's to build a slim TW ROM just for dualbooting.
It'll be an easier workaround. For those with 32GB S4's don't even need to go down this path, just dual boot and be happy!
Thanks for working on this, got the S4 the other day coming from a Bionic that was had ANT+ chipset, but they never turned it on. I too would love a CM 11 with ANT+ support. I will happen, eventually.
ant+ apps on the app store
Hi I'm running 4.4.2 Echoerom on my S4 and just discovered that I'm lacking ANT support despite installing the ant service and apps from the store. Did you try these apps, were you able to make any progress?
Any updates on this ?
I'd like to use ANT+ on my s4 running AOSB.
Any updates for ant+ support in CM11?
The solution of dual boot seems very messy for only that
any news with that?
I'm super late with this, but if anyone is still looking at building ANT+ in to custom ROMs, I have had success building from the ANT Wireless source: check the ANT hardware thread
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
DavM said:
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
Click to expand...
Click to collapse
When you say vanilla I'm assuming you mean AOSP, in that case we do have cm12.1, but I don't know if that's what you mean when it comes to "frequent ROM updates"
But if you're asking as to why we don't have a stock 5.1 ROM, that would be because LG hasn't released a base for it yet
6NomoN6 said:
When you say vanilla I'm assuming you mean AOSP, in that case we do have cm12.1, but I don't know if that's what you mean when it comes to "frequent ROM updates"
But if you're asking as to why we don't have a stock 5.1 ROM, that would be because LG hasn't released a base for it yet
Click to expand...
Click to collapse
CM is not aosp based, it's cm based.
Yes, the argument could be made that everything starts with aosp, but AFAIK there is little true aosp left in cm, and mostly custom cm code.
As for the op,
You get what devs decide to build. Your question is borderline offensive.
DavM said:
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
Click to expand...
Click to collapse
Well, you could always start a stock rom, root it, and use Titanium Backup to remove any feature you don't want and arrive to a "vanilla ROM". The ROM development is a hobby for the dev, so of course there are "frequent ROM updates". By the way, LG has not released the 5.1 yet, they are still on 5.0.1 (23c).
DavM said:
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
Click to expand...
Click to collapse
Been using validus for days. Works great. No freezes. Don't use the features if you don't want em.
This rom is a port of the Stock Touchwiz Marshmallow beta build
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
I'm searching for Contributors, if you are interested, please send me a PM
Current Status: Released first Alpha (v0.1a)
Next Release ETA: ~ January 2016
Known Issues:
Stuck On Boot Logo
Click to expand...
Click to collapse
Install Guide:
Download the compressed file
Decompress the file
Reboot phone in download mode
Open the folder called "Odin + flash files"
Open Odin, flash the pit file (i9100-3GB) and the kernel (i9100-kernel)
Copy the continuingM flashable zip file into an sd card
Insert the SD card in the phone
reboot the phone in recovery mode
Wipe data/factory reset
Flash the continuingM Zip
Fix permission
reboot phone
Click to expand...
Click to collapse
Changelog:
v0.1a
Initial Release
Click to expand...
Click to collapse
Downloads:
Alpha 1
Click to expand...
Click to collapse
XDA:DevDB Information
ContinuingM Touchwiz Edition, ROM for the Samsung Galaxy S II
Contributors
firepenguin
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2015-12-29
Last Updated 2015-12-29
Interesting project. Keep it up!
I'm having troubles with the Note 5 Update zip, it have only patch files, Someone have a dump, not update zip of the Note 5 / S6 Marshmallow beta?
firepenguin said:
I'm having troubles with the Note 5 Update zip, it have only patch files, Someone have a dump, not update zip of the Note 5 / S6 Marshmallow beta?
Click to expand...
Click to collapse
hi,
something like this ?
http://forum.xda-developers.com/showpost.php?p=63855358&postcount=122
http://forum.xda-developers.com/showpost.php?p=63854846&postcount=113
wel wel wel... rely intersting project keep up
Interesting,
I am waiting to test your rom.You know if we gonna have this function available ?
Call record
Code:
Voice call uplink + downlink audio source
Constant Value: 4 (0x00000004)
Interesting .......
Note 5 ported to s2 but with marshmallow.. interesting one.
@Senthil360 Maybe you have note 4 but check it.
GreekDragon said:
Note 5 ported to s2 but with marshmallow.. interesting one.
@Senthil360 Maybe you have note 4 but check it.
Click to expand...
Click to collapse
Yes bro but I guess device needs official marshmallow, Because i don't have much faith in Touchwiz when it comes to updates
And personally i believe stockis better than port in Touchwiz ROMs
Placeholders aren't allowed on XDA.
edi194 said:
Placeholders aren't allowed on XDA.
Click to expand...
Click to collapse
Actually, since this thread is clearly labeled "WIP" this is allowed. Ongoing development.
Thanks for your concern.
The_Merovingian
Forum Moderator
I will test to help development
I'm currently deodexing the dump and removing all arm64 libs/binaries. I think that the first alpha will be ready for the 2nd January
I've done the first build, Now i'm uploading it. It won't boot, it gets stuck on Galaxy SII logo, I don't know why. To flash it you need to repartition the phone. The file i will upload is a 7z file, so you need to decompress it to flash. The file contains odin, the pit file and the rom
Clean CM13 kernel can't boot TouchWiz rom. You need to modify it.
Wow nice & interesting Rom. Waiting for some screenshots!
But is this based on CM13 or a port from original TouchWiz FW?
I mean if this is a real port and would really boot you as a dev would have done the impossible to be possible. So i am a bit unsure if this rom will really boot. @arter97 and @Blekota gave already their best to get the newest touchwiz (4.4.4) feeling for our S3, but they could not get a port from a newer device running android 5 or 6, as there is no device with similar hardware. So I think there is no chance for a port to the Galaxy S2.
firepenguin said:
I've done the first build, It won't boot, it gets stuck on Galaxy SII logo, I don't know why.
Click to expand...
Click to collapse
This shows me that the rom will never boot. See my upper explanation.
But still good luck in this project, will keep following it, as when you would make this really possible you would have made a really big thing in the Galaxy S2 Android Life!
i confirm , no boot , sorry for s2.
I think S2 would be ported on S3 JB 4.3 stock firmware rather than this.
This is almost impossible... 64bit firmware is not compatible with 32bit device.
FaserF said:
Wow nice & interesting Rom. Waiting for some screenshots!
But is this based on CM13 or a port from original TouchWiz FW?
I mean if this is a real port and would really boot you as a dev would have done the impossible to be possible. So i am a bit unsure if this rom will really boot. @arter97 and @Blekota gave already their best to get the newest touchwiz (4.4.4) feeling for our S3, but they could not get a port from a newer device running android 5 or 6, as there is no device with similar hardware. So I think there is no chance for a port to the Galaxy S2.
This shows me that the rom will never boot. See my upper explanation.
But still good luck in this project, will keep following it, as when you would make this really possible you would have made a really big thing in the Galaxy S2 Android Life!
Click to expand...
Click to collapse
I don't own I9100 but porting stock firmware (like official JB 4.3 or ported FW like KK TW 4.4.4) from international I9300 should be possible and with good results.
Why? Of course because its similar hardware (Exynos/GPU Mali etc.)
But I'm not talking about porting with AOSP base like CM, this is long, long way to changing smali code in framework etc. Just trying adapt kernel (exactly ramdisk) to be able boot this official firmware, and changing device blobs - Mali libs/egl/audio libs/camera/av decoders and encoders libs/ril libs...this is possible.
I don't know if you will get "useful" ROM, but you should be able to boot it.
Like I ported just for fun one of official JB for S2 to Ace 2 (where hardware is really different), audio, video, camera wasn't working but ROM booting anyway...
Maybe it does not may any sense (I spent on this 2 hours), but I just wanna say its possible and results are good as hardware is close.
Good luck.
PolishVodka said:
I don't own I9100 but porting stock firmware (like official JB 4.3 or ported FW like KK TW 4.4.4) from international I9300 should be possible and with good results.
Why? Of course because its similar hardware (Exynos/GPU Mali etc.)
But I'm not talking about porting with AOSP base like CM, this is long, long way to changing smali code in framework etc. Just trying adapt kernel (exactly ramdisk) to be able boot this official firmware, and changing device blobs - Mali libs/egl/audio libs/camera/av decoders and encoders libs/ril libs...this is possible.
I don't know if you will get "useful" ROM, but you should be able to boot it.
Like I ported just for fun one of official JB for S2 to Ace 2 (where hardware is really different), audio, video, camera wasn't working but ROM booting anyway...
Maybe it does not may any sense (I spent on this 2 hours), but I just wanna say its possible and results are good as hardware is close.
Good luck.
Click to expand...
Click to collapse
Thank you so much. I will try your method
*** This project is now abandoned in favor of the LineageOS variant ***
This is a port of Cyanogenmod 14.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. Cyanogenmod needs no introduction, it is one of the most popular aftermarket ROM distributions around.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
As this is the first CM-14.1 release, I don't recommend you use this as a daily driver, but it should be good enough for some. Make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on Cyanogenmod 14.1 sources which is based on Nougat 7.1.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Update Dec 3, 2016
===============
Fixed GPS, Wifi Hotspot, Graphics issues, Calls, Camera,sdcard is now marked as adoptable.
Works:
- Wifi/SMS
- Audio
- Graphics with glitches (minor screen tearing, blank screen showing up on overlays)
- GPS
- Wifi Hotspot
- Incoming/Outgoing Calls
- MTP
Does not work:
- Bluetooth
- Camera
- LTE (Due to APN issues)
- Battery Meter not updating
Bugs/Known Issues
* Problems recording video
Other Notes:
- selinux permissive
Most of the issues are fixable, I just need more time and encouragement
SM-T280 Users: Unfortunately this rom would probably not work on it since the SM-T285 and SM-T280 have different kernels and slightly different hardware. I don't have access to this device so it would be hard for me to port it over. However I believe there are a lot of similiarities in the device tree that can be shared. If a dev with the SM-T280 is interested I can probably help.
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty, Samsung representatives will probably not be able to help you as they are still stuck at 5.1.1 land as of now and have no idea how to handle a SM-T285 that is running 7.1.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section.
BUILD12032016
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
CM-14.1 Samsung Galaxy Tab A 7.0 LTE (SM-T285), ROM for the Samsung Galaxy Tab A series
Contributors
jedld
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-12-03
Last Updated 2017-01-31
Nice job!!!
Great job! The ROM is impressively fluid, and I particularly love the way it renders fine text, which I appreciate because I prefer DPIs of 140 to 160. Unfortunately, just like in the early iterations of OmniROM 6.0, the tablet will not connect to the internet over cellular networks no matter how much I tinker with APNs. It's a great build, nevertheless, and I look forward to future releases.
Thank you !! Will give it a try.
posting here too (as did on omni - realized this is the cm 14.1 board)...
"briefly tried the cm14.1....much better very fast response-on the omni the pull down was an issue (would also ask me to format the sd card)
noticed here too the signal tends to drop in and out (wonder if it is some power saving going on-it goes to full strength during a call)...speakerphone also does not work here but must say this is better than the omni even though data does not work"
keyboard much better here too
on both cm14.1 and the omni, the dialer tends to be have some lag when pressing the numbers (do it too fast and can get many errors)-minor thing understand this is an alpha and the omni is a beta
thanks
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
mazmorbid said:
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
Click to expand...
Click to collapse
needs some xml changes that needs to be compiled into the framework for that I believe. Though there are more critical bugs I need to fix with this 7.1 rom.
I wish I could help in some way, appreciate your work.
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
khanhpt said:
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
Click to expand...
Click to collapse
Try using an older gapps package like from october, recent versions seem to have issues.
jedld said:
Try using an older gapps package like from october, recent versions seem to have issues.
Click to expand...
Click to collapse
Thank Jedld, i has tried 27th,october version and it WORKS, thank.
I used the version as recommended in the Omni ROM, which was from the 9th of November, no problems with the app store or downloading apps either.
Any closer to another release ?
Nougat will take a while unfortunately
jedld said:
Nougat will take a while unfortunately
Click to expand...
Click to collapse
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
mac231us said:
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
Click to expand...
Click to collapse
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
jedld said:
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
Click to expand...
Click to collapse
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
mac231us said:
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
Click to expand...
Click to collapse
Those patches didn't help unfortunately Though I've fixed network type selection in CM-14.1 already, unfortunately data connection still won't come online due to errors related to APNs. Seeing as this was working perfectly in CM-13 this could be a CM-14 or Nougat related change, it will take a while to figure out what that is. As for bluetooth I was able to get it to turn on, however it is still unable to detect/pair to any device, this is also something that was working in CM-13.
any hope on porting this to t280?
klemen241 said:
any hope on porting this to t280?
Click to expand...
Click to collapse
I don't have the T280 so I wouldn't know. There are devs that are trying or have tried to work on it, not sure about their progress.