Hello fellas
I was just looking around for device trees and latest work done on VK810 to see if i could contribute and i came across this. Removed link in case someone really is stupid. See attachment! I also found GITHUB and saw very recent device tree changes so we are just weeks away from CM12.1
Now the foolish people would immediatel try to contact the developers and ask for ETA and bother the very few developers who want to work on this device. If you piss the developer, they won't touch your device again and trust me it would be a great loss to community because this promises us stable device tree and kernel sources which means that all next android versions released by google could be easily worked on. As device tree is base for all development. Please don't f*** it up for others !
The wise ones would wait PATIENTLY because it's just few weeks away to have all the love for our device. Another member is in contact with another developer and he promised CLEANROM in very near future for Verizon Vk810 G PAD LTE.
Update CLEANROM released.
http://forum.xda-developers.com/lg-...-4-4-2-24a-smooth-clean-t3105587#post60673234
I am glad to be bearer of good news.
Update
I and another user tried CM12.1 and only the data is not working. So once the data is fixed. We'd have working tree with CM with other Roms to follow.
I tether from my phone so data is a non issue for me. Excited to see what's to come
Sent from my vk810 using XDA Free mobile app
juggamonkey said:
I tether from my phone so data is a non issue for me. Excited to see what's to come
Sent from my vk810 using XDA Free mobile app
Click to expand...
Click to collapse
New commits have been merged today for data and LTE so I would test the new build and report back here. We are all excited actually!
Hnk1 said:
New commits have been merged today for data and LTE so I would test the new build and report back here. We are all excited actually!
Click to expand...
Click to collapse
Data working?
w0rdie said:
Data working?
Click to expand...
Click to collapse
Not yet. Even new commits from lollipop rom for Vk810 have been merged today but still GPS and data do not work.
Rest is fine!
Hnk1 said:
Not yet. Even new commits from lollipop rom for Vk810 have been merged today but still GPS and data do not work.
Rest is fine!
Click to expand...
Click to collapse
Damn, I could live without GPS but data is the reason I keep the thing. Keep us updated -- thanks!
w0rdie said:
Damn, I could live without GPS but data is the reason I keep the thing. Keep us updated -- thanks!
Click to expand...
Click to collapse
Sure mate. I am working on a Root for our device at the moment for 35A. I have succeeded in it as well. Just need to make default app as SuperSU
Hnk1 said:
Sure mate. I am working on a Root for our device at the moment for 35A. I have succeeded in it as well. Just need to make default app as SuperSU
Click to expand...
Click to collapse
Any update?
w0rdie said:
Any update?
Click to expand...
Click to collapse
Yes, I plan to update the my thread in general section by tomorrow. I succeed in doing everything but I needed confirmation if it works or not for others as well. That's all.
Are you in a hurry ?
w0rdie said:
Any update?
Click to expand...
Click to collapse
Here. I thought you couldn't wait for it so did it for you now.
Visit my threads. All instructions have been posted.
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-altev-complete-root-recovery-t3108260
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-downgrade-required-t3116336#post60921535
Hnk1 said:
Here. I thought you couldn't wait for it so did it for you now.
Visit my threads. All instructions have been posted.
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-altev-complete-root-recovery-t3108260
http://forum.xda-developers.com/lg-g-pad-83/general/vk810-downgrade-required-t3116336#post60921535
Click to expand...
Click to collapse
Is there actually a cm12.1 for vk810? No links.
713brianp27 said:
Is there actually a cm12.1 for vk810? No links.
Click to expand...
Click to collapse
It is still in development. Data and GPS does not work.
At the moment, he's (developer) still trying to sort out blobs
Hnk1 said:
It is still in development. Data and GPS does not work.
At the moment, he's (developer) still trying to sort out blobs
Click to expand...
Click to collapse
Last time someone ported CyanogenMod they never got data working. I tried to make adjustments, modem, build.prop, tore kernel apart, several wasted attempts. Figured it was a caf issue and different commits. So I bought a Nexus 7 LTE, slapped my sim in and ran. I like my GPad just not the limitations set upon me by a locked down Boot loader. To be honest my signal is stronger w N7. So I don't even use data on it. Do wish I could get rid of that annoying "no sim" alert.
Subscribed.....
Tried the ROM... VIK is much smoother, can't speak of data. SIM is in N7
713brianp27 said:
Tried the ROM... VIK is much smoother, can't speak of data. SIM is in N7
Click to expand...
Click to collapse
The baseband being "Unknown", which is what I got too with a Verizon SIM in, means it doesn't even recognize that you have a modem,so you can tell already it wouldn't work even with your SIM in it.
Sent from my VK810 4G
roirraW "edor" ehT said:
The baseband being "Unknown", which is what I got too with a Verizon SIM in, means it doesn't even recognize that you have a modem,so you can tell already it wouldn't work even with your SIM in it.
Sent from my VK810 4G
Click to expand...
Click to collapse
Yeah, I didn't have my sim in. I may try with sim. Not sure its worth trouble though. This N7 sim tray is a pain. But its probably going to be same issue as with the cm11 port. The 12.1 doesn't impress me. Locked bootloader puts so many limitations. GPad in general is nice, better with L, but I get better data reception on the N7?
Related
Hi Guys,
Today i have installed the latest version of OMNIROM Kitkat 4.4.1 and still Wi-fi tethering is not working.
Any ideas how can i fix the same.
Thanks in advance
Anuroop
anuroopkoka2012 said:
Hi Guys,
Today i have installed the latest version of OMNIROM Kitkat 4.4.1 and still Wi-fi tethering is not working.
Any ideas how can i fix the same.
Thanks in advance
Anuroop
Click to expand...
Click to collapse
Indeed, the Wi-Fi and BlueTooth tethering is not working here either. It worked well on the Stock ROM though, so I don't believe it's caused by the provider.
I hope this can be fixed, I read somewhere else I might have to do with the tether_dun_required setting in settings.db -> global.
OK, this is useful info. It was not working on I9300 and I had no way at all to test that (the only 4412 device I have is wifi-only) - but later this week I can investigate tethering issues on N7000 if it's also problematic. Just need to find my microsim adapter...
Entropy512 said:
OK, this is useful info. It was not working on I9300 and I had no way at all to test that (the only 4412 device I have is wifi-only) - but later this week I can investigate tethering issues on N7000 if it's also problematic. Just need to find my microsim adapter...
Click to expand...
Click to collapse
Would be great if the hotspot works on my i9300. Thanks for all your effort!
Entropy512 said:
OK, this is useful info. It was not working on I9300 and I had no way at all to test that (the only 4412 device I have is wifi-only) - but later this week I can investigate tethering issues on N7000 if it's also problematic. Just need to find my microsim adapter...
Click to expand...
Click to collapse
Hi Guys,
Any update on the tethering issues on N7000..
Regards,
Anuroop
I was tracking down some other issues over the weekend... I might not be able to play with this at all until the holidays.
This is rom is awesome but only a,wifi tethering prob plz fix this..
this is just a awesome rom but only a prob plz fix the wifi tethering prob otherwise there is no prob evry thing is excellent..if any one know how to fix plz reply as soon as possible...
thnks in advnce...
+1
Sent from my Nexus 5 using XDA Premium 4 mobile app
Entropy512 said:
I was tracking down some other issues over the weekend... I might not be able to play with this at all until the holidays.
Click to expand...
Click to collapse
Any luck with this yet? Really keen to know what this problem is caused by no pressure and thanks either way
infrag said:
Any luck with this yet? Really keen to know what this problem is caused by no pressure and thanks either way
Click to expand...
Click to collapse
I was going to work on it over the holidays, but among the things I forgot to bring with me was the SIM adapter for my N7000. Tethering works fine on all of the other devices I own.
I've got a number of ideas why, although the fact that BT tethering is ALSO failing indicates it's something different from what I'm used to in the past... That's new information.
Entropy512 said:
I was going to work on it over the holidays, but among the things I forgot to bring with me was the SIM adapter for my N7000. Tethering works fine on all of the other devices I own.
I've got a number of ideas why, although the fact that BT tethering is ALSO failing indicates it's something different from what I'm used to in the past... That's new information.
Click to expand...
Click to collapse
BT tethering works for me
Sent from my GNote
yanix said:
BT tethering works for me
Sent from my GNote
Click to expand...
Click to collapse
Odd, someone else claimed it was not working... They might be on one of the providers where tethering is blocked. (There's a commit going through review to remove a bunch of those blocks...)
So it seems to be something odd with all of the Samsung Exynos4 devices, not sure what yet... Every change that SHOULD be required seems to be there, but we're obviously missing something.
Entropy512 said:
Odd, someone else claimed it was not working... They might be on one of the providers where tethering is blocked. (There's a commit going through review to remove a bunch of those blocks...)
So it seems to be something odd with all of the Samsung Exynos4 devices, not sure what yet... Every change that SHOULD be required seems to be there, but we're obviously missing something.
Click to expand...
Click to collapse
Btw, I'm not sure if this would help but this fixed a wifi tethering issue back in PA-JB.
http://forum.xda-developers.com/showpost.php?p=42205316&postcount=2279
Sent from my GNote
yanix said:
Btw, I'm not sure if this would help but this fixed a wifi tethering issue back in PA-JB.
http://forum.xda-developers.com/showpost.php?p=42205316&postcount=2279
Sent from my GNote
Click to expand...
Click to collapse
Just found herna CM11 beta7 wifi-tethering is working ... hope that would help
yanix said:
Btw, I'm not sure if this would help but this fixed a wifi tethering issue back in PA-JB.
http://forum.xda-developers.com/showpost.php?p=42205316&postcount=2279
Sent from my GNote
Click to expand...
Click to collapse
Thanks for the tip - I knew there was some stuff in frameworks/base related to tethering, I just hadn't had the time to look into it in detail.
https://gerrit.omnirom.org/#/c/4215/ might fix things for people, not sure.
Was able to get a ROM built and running based on LRX21V straight from source. Just trying to get a feel on how many people would want to run AOSP. There are some bugs present such as video recording causing the camera to stop working. I think there are binaries missing that Google didn't include in the binaries that are available. Same problem happened on the Nexus 5. Didn't test it much as I just purely wanted to see if it booted.
Also there is a lack of gapps available so I won't be rushing to get anything out. Let me know what y'all think and I'll try to tackle this to get some other options out for us.
Here is the test build for those that want to have a look. This is just a test build so bugs are to be expected. Video recording does not work. Haven't tested it completely as I need a fully working device this weekend. This is for those that have free time to just nit pick and find all bugs in this. Please report back after you are done and let me know what else you may have found that is broken or not working right.
Stock Google kernel (so if you flashed the kernel image to remove encryption your phone WILL be encrypted again)
Built off 5.0.0_r7 from AOSP
Flash ROM, flash gapps and flash SU that is linked below. This will allow root access on the stock kernel.
You can also optionally flash the custom boot image after flashing the ROM, gapps and SU by rebooting to bootloader and fastboot flash boot the custom encryption kernel. That is optional. Be sure to go back in to recovery after flashing the kernel to reflash the SU to make sure it was not overwritten.
Download Rom:AFH Mirror
Download Gapps for Lollipop:http://forum.xda-developers.com/showthread.php?p=56810851#post56810851
Download latest SU: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I'm tuned in!
Sent from my Nexus 6 using XDA Free mobile app
The development section is kind of depressing me right now (no offense to devs) so bring it!
the.emilio said:
Was able to get a ROM built and running based on LRX21V straight from source. Just trying to get a feel on how many people would want to run AOSP. There are some bugs present such as video recording causing the camera to stop working. I think there are binaries missing that Google didn't include in the binaries that are available. Same problem happened on the Nexus 5. Didn't test it much as I just purely wanted to see if it booted.
Also there is a lack of gapps available so I won't be rushing to get anything out. Let me know what y'all think and I'll try to tackle this to get some other options out for us.
Click to expand...
Click to collapse
Any gapps should work. It can be downloaded from the nexus 5 section
---------- Post added at 09:37 AM ---------- Previous post was at 09:34 AM ----------
Its only been a couple days. And the phone is really scarce. Give it time
estallings15 said:
The development section is kind of depressing me right now (no offense to devs) so bring it!
Click to expand...
Click to collapse
That is pretty offensive. It is a new device and isn't in the developers hand so releasing work without testing their work leads to quality problems.
I don't see you doing any development work and developers don't owe anyone anything as they do all this work as a hobby pretty much.
Sent from my Nexus 6 using Tapatalk
zephiK said:
That is pretty offensive. It is a new device and isn't in the developers hand so releasing work without testing their work leads to quality problems.
I don't see you doing any development work and developers don't owe anyone anything as they do all this work as a hobby pretty much.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I know the reasons behind it, which was the point of the "no offense." I wasn't whining. I was trying to help motivate and encourage OP. He, as well as others, are working on making things happen and I'm excited for it and waiting eagerly for the kernel source to drop.
You took what I said the wrong way, so step off of your soap box, zephiK.
Edit: That reminds me. If any devs need testers, PM me. I'll be happy to help the community out.
Smallsmx3 said:
Any gapps should work. It can be downloaded from the nexus 5 section
---------- Post added at 09:37 AM ---------- Previous post was at 09:34 AM ----------
Its only been a couple days. And the phone is really scarce. Give it time
Click to expand...
Click to collapse
Lol. I know this. Just came from the N5 I guess what I meant is that there isn't a complete package yet. There's a minimal yes that does work. But I prefer the full. Just lazy and hate downloading apps or pushing apps lol
the.emilio said:
Lol. I know this. Just came from the N5 I guess what I meant is that there isn't a complete package yet. There's a minimal yes that does work. But I prefer the full. Just lazy and hate downloading apps or pushing apps lol
Click to expand...
Click to collapse
Ha! That's funny. does r 7 have any significant commits over our revision
Smallsmx3 said:
Ha! That's funny. does r 7 have any significant commits over our revision
Click to expand...
Click to collapse
No. Minor bug fixes for the particular device it was made for but that's it. I did notice on the N5 that there was a significant "miscellaneous" battery drain on r7. Might roll back to r3 if its present since r3 is the one for us (its also the same build for the N5).
zephiK said:
That is pretty offensive. It is a new device and isn't in the developers hand so releasing work without testing their work leads to quality problems.
I don't see you doing any development work and developers don't owe anyone anything as they do all this work as a hobby pretty much.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
We are working on something [emoji6]
the.emilio said:
No. Minor bug fixes for the particular device it was made for but that's it. I did notice on the N5 that there was a significant "miscellaneous" battery drain on r7. Might roll back to r3 if its present since r3 is the one for us (its also the same build for the N5).
Click to expand...
Click to collapse
Miscellaneous bug again? I wonder if they broke the same thing they already fixed, or if this is something else that is just falling into miscellaneous as well.
Thanks for the work on this!
In for the long haul! Tired of the plethora of gapps on this phone. Somehow I managed to break photos once by removing some google app... Weird.
Sent from my Nexus 6 using Tapatalk
I uploaded the ROM for testing purposes. Please re-read the OP for more info. :good:
the.emilio said:
I uploaded the ROM for testing purposes. Please re-read the OP for more info. :good:
Click to expand...
Click to collapse
Sweet, thanks.
What the Christ is this new file layout?! System.new.dat o.0
Sent from my Nexus 6 using Tapatalk
Rauch said:
Sweet, thanks.
What the Christ is this new file layout?! System.new.dat o.0
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's lollipop for ya..
the.emilio said:
That's lollipop for ya..
Click to expand...
Click to collapse
As I wanted to attempt to pre-root and make some changes... Ugh.
Simply installing the SuperSU apk is enough for root, correct? I don't have to re-run CF... Especially since I'm not near a PC
Sent from my Nexus 6 using Tapatalk
Rauch said:
As I wanted to attempt to pre-root and make some changes... Ugh.
Simply installing the SuperSU apk is enough for root, correct? I don't have to re-run CF... Especially since I'm not near a PC
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes just use the one I linked to. Be sure to flash it in the same session so you don't lose the custom recovery.
Rauch said:
As I wanted to attempt to pre-root and make some changes... Ugh.
Simply installing the SuperSU apk is enough for root, correct? I don't have to re-run CF... Especially since I'm not near a PC
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Remember its just a test so I recommend waiting until you have access to a PC. Just in case lol
Well, I bit the bullet. Only lost a few downloads.... But anyway.
Sound quality seems.... Different? Also network says its connected to LTE, but its beyond slow. Not sure why exactly.
I'm on the correct APN.
Closing apps, I hear a slight buzz/tap three tomes when hitting the home button.
Sent from my AOSP on Shamu using Tapatalk
carloscibrian4 said:
Did anyone's storage decreased afterwards? My nexus says that there is only 23gb of storage despite being a 64 gb
Click to expand...
Click to collapse
I have a 32gb and that's what I have.... I didn't check before.... Anyone have any idea what storage should be out of the box?
Rauch said:
Well, I bit the bullet. Only lost a few downloads.... But anyway.
Sound quality seems.... Different? Also network says its connected to LTE, but its beyond slow. Not sure why exactly.
I'm on the correct APN.
Closing apps, I hear a slight buzz/tap three tomes when hitting the home button.
Sent from my AOSP on Shamu using Tapatalk
Click to expand...
Click to collapse
I was getting weird audio sounds at first... I don't know if it was the update when I got home that fixed it but it's been non existent since the first couple of hours I had the phone
New build MPA44G is latest developer preview firmware of Android M. Maybe the last, too.
Download it here.
Source here
I haven't noticed anything so far
is there a new radio?
joeyddr said:
is there a new radio?
Click to expand...
Click to collapse
I don't think so. I did a dirty flash and everything is working
There is a thread for this
Sent from my Nexus 6 using Tapatalk
Just flashed via fb and the radio now ends in 24r
how is navigation read lte devices have a location bug
kornklown69 said:
how is navigation read lte devices have a location bug
Click to expand...
Click to collapse
Saw that as well. This is a huge bug since majority of the people use LTE while using navigation.
Is now on tap working with the newest build?
Having issues connecting to my wifi network. It connected and couple of seconds later disconnects. It says connection failure.
wera750 said:
Is now on tap working with the newest build?
Click to expand...
Click to collapse
Nope. Seems like it was all under the hood changes apart from the new boot up screen. Still no easter egg,
akhan47 said:
Nope. Seems like it was all under the hood changes apart from the new boot up screen. Still no easter egg,
Click to expand...
Click to collapse
Can someone please share the new boot animation? I have started a thread here http://forum.xda-developers.com/nexus-6/themes-apps/android-marshmellow-boot-animation-t3180825 if someone is willing to provide it...it doesn't have to be a flash-able zip, just copy paste will do...
Thank you
Someone check stagefreight detector
Enhanced data switch is back when on Project FI. Its not there in the current 5.1.1 builds.
Permissions check is working. What I mean is that an app will ask you to allow or deny permissions when if first attempts to do something. Example: I went to download something on Chrome and I received a prompt asking me to allow or deny chrome access to my music, videos, and files.
How many threads do we need for this? There is already a discussion thread.
Sent from the Nodes of Ranvier
eep2378 said:
How many threads do we need for this? There is already a discussion thread.
Sent from the Nodes of Ranvier
Click to expand...
Click to collapse
3 is the golden number.
jodvova said:
3 is the golden number.
Click to expand...
Click to collapse
Owned
Lets keep it neat, tidy and in one place
http://forum.xda-developers.com/nexus-6/general/android-m-discussion-thread-t3120782
Thread closed
So, I got a small update just now for my N900T. The changelog says OS 5.1.1.
I'm installing now. Will update when it's finished.
Edit: Added screenshot.
Build number is N910TUVU2DOK2
I have a update downloading as well, lets see how this goes. You meant to type N910T I presume?
blindskater39 said:
I have a update downloading as well, lets see how this goes. You meant to type N910T I presume?
Click to expand...
Click to collapse
Yes, I know the N910T3 has had 5.1.1 for a while, but no, this is for the N910T.
Unfortunately I am not rooted, so I can't provide any firmware dump or anything else that would be of help to devs.
Techngro said:
Yes, I know the N910T3 has had 5.1.1 for a while, but no, this is for the N910T.
Unfortunately I am not rooted, so I can't provide any firmware dump or anything else that would be of help to devs.
Click to expand...
Click to collapse
I have the N910T as well. I am not rooted either for now... How did you view the changelog?
blindskater39 said:
I have the N910T as well. I am not rooted either for now... How did you view the changelog?
Click to expand...
Click to collapse
When the install finished downloading, it asked me to confirm the install. That's when it showed the changelog. I should have taken a screenshot of it. Probably had good info. Oh well, too late for that now.
Techngro said:
When the install finished downloading, it asked me to confirm the install. That's when it showed the changelog. I should have taken a screenshot of it. Probably had good info. Oh well, too late for that now.
Click to expand...
Click to collapse
I got you I hope this doesn't cause any troubles for rooting.
My phone just started downloading an update as well. Couldn't find what update it was downloading until I came here. Hopefully no issues?
twister99403 said:
My phone just started downloading an update as well. Couldn't find what update it was downloading until I came here. Hopefully no issues?
Click to expand...
Click to collapse
Haven't played with it enough yet. Time for bed. Have to go to work in a few hours. But the install went smoothly, and the first boot was fine.
Let's hope it stays that way.
blindskater39 said:
I got you I hope this doesn't cause any troubles for rooting.
Click to expand...
Click to collapse
Thanks. Security update. Yaaaaaaay!
As for rooting, I'm sure the usual suspects from XDA will be on it in no time. They'll probably have root before I get home from work.
Techngro said:
Thanks. Security update. Yaaaaaaay!
As for rooting, I'm sure the usual suspects from XDA will be on it in no time. They'll probably have root before I get home from work.
Click to expand...
Click to collapse
I hope this leads to a fix for the finger print bug in ROMs. This is my first device that has a finger print scanner and I don't like giving out passwords lol.
Just got the update as well on a non-rooted N910T.
Really hoping for some improvements in speed.
Finally. I've noticed better reception so far. I'm at the Dr's office which I never get signal in the waiting room but I got 2 bars. Hopefully it fixed reception that 5.0.1 messed up for me
NogaroS4 said:
Finally. I've noticed better reception so far. I'm at the Dr's office which I never get signal in the waiting room but I got 2 bars. Hopefully it fixed reception that 5.0.1 messed up for me
Click to expand...
Click to collapse
Bars don't mean anything. What's the change in dBm under settings/about phone/status/signal strength?
Sent from my SM-N910T using Tapatalk
vprasad1 said:
Bars don't mean anything. What's the change in dBm under settings/about phone/status/signal strength?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Might not mean much but having any signal vs no signal is an improvement.
My antutu score went down from 52000 to 49000 (COG2-DOK2), gps is not any better, copy and paste clipboard is gone, and the handwriting input has changed.
blindskater39 said:
My antutu score went down from 52000 to 49000 (COG2-DOK2), gps is not any better, copy and paste clipboard is gone, and the handwriting input has changed.
Click to expand...
Click to collapse
ugh clipboard gone??
I guess I will find out soon - this is a big update 677.68 Megs!
w8wca said:
ugh clipboard gone??
I guess I will find out soon - this is a big update 677.68 Megs!
Click to expand...
Click to collapse
And so many wonder why the general public bemoans updates. Not that I used it much but it was nice to have if it is in fact gone. I hope they didn't change much else.
The real update I see is that the Stagefright exploit is fully patched.
Most of you on this thread might not care but if you install this update, there's no going back to KK or Lollipop.
tsdsbrk said:
Most of you on this thread might not care but if you install this update, there's no going back to KK or Lollipop.
Click to expand...
Click to collapse
This is Lillopop 5.1.1 right?
Hey folks , title says it all. I switched to cm13 from chroma , performed a full system wipe including sd card. So far so good but the only problem is , gsm doesn't work. I can't switch to it. Not from the settings and not from the dialer hidden menu. When i select gsm , it immediately switches back. It's always "Wdcma Only". Is this a known bug ? I scoured xda but haven't been able to find anything.
Thanks in advance.
Edit : Flashed the stock radio from 5.1.1 to no avail , also tried the 33-1.07 hybrid modem again doesn't switch. Using the latest December 27th build.
There was a bug report in the mako CM13 thread about being unable to switch between 2G and 3G, perhaps this is the same issue?
I think someones written a patch and just waiting for it to be merged.
Can you explain to me why you want to switch between them? My phone automatically switches, if 3G is available, it uses that, if its not, it drops back to the best available 2G signal automatically. Why would you choose not to use 3G if its available and just let the phone automatically switch?
Aragorn84 said:
There was a bug report in the mako CM13 thread about being unable to switch between 2G and 3G, perhaps this is the same issue?
I think someones written a patch and just waiting for it to be merged.
Can you explain to me why you want to switch between them? My phone automatically switches, if 3G is available, it uses that, if its not, it drops back to the best available 2G signal automatically. Why would you choose not to use 3G if its available and just let the phone automatically switch?
Click to expand...
Click to collapse
What you're talking about is wcdma preferred mode. Mine is stuck on wcdma only. Which means i don't have gsm so it won't switch automatically. That and the fact that i rarely use 3g because i'm always on wi-fi somewhere , using gsm saves battery. also on lollipop 3g modem took horribly long wake locks that lasted for %70 of the idle time so i hate msm.hsic.wakelock. But if it is a known bug , i'm relieved because that should be patched soon. Without me having to restore my backup. Thanks.
Sent from my Nexus 4 using Tapatalk
boltthrower56 said:
What you're talking about is wcdma preferred mode. Mine is stuck on wcdma only. Which means i don't have gsm so it won't switch automatically. That and the fact that i rarely use 3g because i'm always on wi-fi somewhere , using gsm saves battery. also on lollipop 3g modem took horribly long wake locks that lasted for %70 of the idle time so i hate msm.hsic.wakelock. But if it is a known bug , i'm relieved because that should be patched soon. Without me having to restore my backup. Thanks.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I just flashed CM13 on my wife's nexus 4 and I realized LTE wasn't enabled. Googled it and it seems there was an app for lollipop to enable it but it didn't work out for me.
Is it a CM13 bug thing or am I missing something?
pcaseiro said:
I just flashed CM13 on my wife's nexus 4 and I realized LTE wasn't enabled. Googled it and it seems there was an app for lollipop to enable it but it didn't work out for me.
Is it a CM13 bug thing or am I missing something?
Click to expand...
Click to collapse
It doesn't work for me too. I think it might be a bug
Sent from my Nexus 4 using Tapatalk
boltthrower56 said:
It doesn't work for me too. I think it might be a bug
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
It's a known bug. We have to wait for this patch to be merged. Keep an eye on it!
ht_tp://review.cyanogenmod.org/#/c/125897/
Thanks to Streetwalker for finding the bug.
TigTex said:
It's a known bug. We have to wait for this patch to be merged. Keep an eye on it!
ht_tp://review.cyanogenmod.org/#/c/125897/
Thanks to Streetwalker for finding the bug.
Click to expand...
Click to collapse
Thanks for the heads-up. I checked it , i think it hasn't been merged yet. So we gotta wait for tomorrow's release i guess.
Can anyone get their Nexus 4 running a recently nightly (like Jan 8th 2016) successfully switch to LTE? The fix in question was merged a few days ago.
Even though I can go into the *#*#4636#*#* service menu and successfully switch to LTE/GSM auto, or LTE/CDMA auto, and the radio *does* appear to power-cycle, it still says on 3G/H+ (so the status bar icon says). Never had this issue with CM12.
My build.prop also says my preferred network mode is 9, even after rebooting, which should keep it on LTE. Any ideas?
The only way to have LTE is to change that patch to include LTE instead of only GSM and WCDMA but since LTE isn't fully supported on nexus 4, a patch like that will never be merged.
Probably someone will make one "lte enabler" for cm13, just wait (or help)
Build with that patch
TigTex said:
The only way to have LTE is to change that patch to include LTE instead of only GSM and WCDMA but since LTE isn't fully supported on nexus 4, a patch like that will never be merged.
Probably someone will make one "lte enabler" for cm13, just wait (or help)
Click to expand...
Click to collapse
i saw this and since i wanted to figure out how to build cyanogenmod anyways, i went and built cm13 with the LTE included in where the patch discussed here should have added it. I have yet to test it on my device but thought people here might be interested in it.
let me know if it works out.
i would post a link, but since this is my first post it won't let me. i guess message me directly for it? or maybe someone can and then post the link here?
zachron said:
i saw this and since i wanted to figure out how to build cyanogenmod anyways, i went and built cm13 with the LTE included in where the patch discussed here should have added it. I have yet to test it on my device but thought people here might be interested in it.
let me know if it works out.
i would post a link, but since this is my first post it won't let me. i guess message me directly for it? or maybe someone can and then post the link here?
Click to expand...
Click to collapse
Shoot me a PM and I'll post it for you, assuming that's allowed (mods?).
zachron said:
i saw this and since i wanted to figure out how to build cyanogenmod anyways, i went and built cm13 with the LTE included in where the patch discussed here should have added it. I have yet to test it on my device but thought people here might be interested in it.
let me know if it works out.
i would post a link, but since this is my first post it won't let me. i guess message me directly for it? or maybe someone can and then post the link here?
Click to expand...
Click to collapse
lannister80 should be posting a link to it shortly, but i thought i would give an update that i did test it on my device last night and LTE does work with it. the normal issues of making sure you have the right modem and then changing it in the *#*#* thing. i had to change mine to LTE only first and then it would work when i changed it to LTE /gsm auto... but it does work.
zachron said:
lannister80 should be posting a link to it shortly, but i thought i would give an update that i did test it on my device last night and LTE does work with it. the normal issues of making sure you have the right modem and then changing it in the *#*#* thing. i had to change mine to LTE only first and then it would work when i changed it to LTE /gsm auto... but it does work.
Click to expand...
Click to collapse
https://www.amazon.com/clouddrive/s...D4HdJg40yFjrvcAwWa?ref_=cd_ph_share_link_copy
There's the link. Can I ask which commit this CM13 build is based on? Is this a nightly, something older, etc?
lannister80 said:
URL REDACTED BECAUSE I CANNOT POST LINKS
There's the link. Can I ask which commit this CM13 build is based on? Is this a nightly, something older, etc?
Click to expand...
Click to collapse
its a nightly, i might update it on a weekly basis maybe, i have not decided. i can only use the machine i am building it on sometimes.
zachron said:
lannister80 should be posting a link to it shortly, but i thought i would give an update that i did test it on my device last night and LTE does work with it. the normal issues of making sure you have the right modem and then changing it in the *#*#* thing. i had to change mine to LTE only first and then it would work when i changed it to LTE /gsm auto... but it does work.
Click to expand...
Click to collapse
Confirmed that this build does enable LTE. I did have to, as zachron mentioned, set the radio to "LTE only" first (which enabled LTE), and then "LTE/GSM auto", (which kept LTE enabled, and will hopefully jump down to HSPA+ or 3G when necessary). Switching to "LTE/GSM auto" first did not work (radio turned off, but came back on in HSPA+/3G mode).
I'll roam around today and see if I lose data at any time (when LTE isn't available).
Thanks @zachron!!
zachron said:
its a nightly, i might update it on a weekly basis maybe, i have not decided. i can only use the machine i am building it on sometimes.
Click to expand...
Click to collapse
@zachron: Can you show me what source changes you made? Maybe I can set up a github account and do a merge request with these changes. I can't fathom why this isn't included in CM13 for the N4xus 4 when it was in CM11, CM10 etc.
https://github.com/CyanogenMod/android_device_lge_mako/tree/cm-13.0
lannister80 said:
@zachron: Can you show me what source changes you made? Maybe I can set up a github account and do a merge request with these changes. I can't fathom why this isn't included in CM13 for the N4xus 4 when it was in CM11, CM10 etc.
https://github.com/CyanogenMod/android_device_lge_mako/tree/cm-13.0
Click to expand...
Click to collapse
sure.
https://github.com/CyanogenMod/andr...orks/base/core/res/res/values/config.xml#L234
i changed "<string translatable="false" name="config_radio_access_family">GSM|WCDMA</string>" to
"<string translatable="false" name="config_radio_access_family">GSM|WCDMA|LTE</string>"
as someone else mentioned, earlier in this thread though, they may not change it because the nexus 4 does not "officially" support lte
zachron said:
as someone else mentioned, earlier in this thread though, they may not change it because the nexus 4 does not "officially" support lte
Click to expand...
Click to collapse
Which is insane, because they absolutely allowed this in the last several major CM versions (12, 11, probably 10 and 9). Enabling LTE was one of the first things I did after getting my Nexus 4 in March 2013, and I was on an official CM build for years.
The "enabler" just messes with build.prop and makes some database changes to make the setting "stick" after reboot, so it must have been an allowed option when it was built (the enabler can't change that).
I don't know what the deal with the sudden change of heart is...
lannister80 said:
Which is insane, because they absolutely allowed this in the last several major CM versions (12, 11, probably 10 and 9). Enabling LTE was one of the first things I did after getting my Nexus 4 in March 2013, and I was on an official CM build for years.
The "enabler" just messes with build.prop and makes some database changes to make the setting "stick" after reboot, so it must have been an allowed option when it was built (the enabler can't change that).
I don't know what the deal with the sudden change of heart is...
Click to expand...
Click to collapse
yeah i dont disagree
zachron said:
yeah i dont disagree
Click to expand...
Click to collapse
Pull/merge request created:
https://github.com/CyanogenMod/android_device_lge_mako/pull/6
Hope I didn't screw it up, I'm new to git.
---------- Post added at 01:15 PM ---------- Previous post was at 01:12 PM ----------
lannister80 said:
Pull/merge request created:
https://github.com/CyanogenMod/android_device_lge_mako/pull/6
Hope I didn't screw it up, I'm new to git.
Click to expand...
Click to collapse
Oh damn it, I have to do it via this site (they won't merge anything submitted directly on the repository):
http://review.cyanogenmod.org/