Related
Hey There,
I've just installed this fine ROM today, and it seems great,
but for some reason, the wifi reception is BAD now.
It works fine if I seat near my router, but if I move 3 meters away
it looses the connection ... and says the reception is POOR.
Any1 else has this problem?
Which version of CM10 did you flash, if it's anything older than beta 1 try flashing Beta 1 ? if you still have problems after Beta1
Try flashing a different kernel and see if that resolves your problem. (if i can spare you some time, try faux123's kernel)
http://forum.xda-developers.com/showthread.php?t=1647993
And then if you still have problems.
Try running the Viper ROM 2.6.0 with the Butter hacks runs very smooth.
http://forum.xda-developers.com/showthread.php?t=1745176
Thanks for the quick replay
I flashed the "[08-09] [ROM] CyanogenMod 10 - Endeavor Unleashed" rom.
I don't think this is the same cm10 everyone's using.
and I don't really understand, doesn't the Kernal comes with the rom?
Can I change it without changing a rom ?
alexx_za said:
Which version of CM10 did you flash, if it's anything older than beta 1 try flashing Beta 1 ? if you still have problems after Beta1
Try flashing a different kernel and see if that resolves your problem. (if i can spare you some time, try faux123's kernel)
http://forum.xda-developers.com/showthread.php?t=1647993
And then if you still have problems.
Try running the Viper ROM 2.6.0 with the Butter hacks runs very smooth.
http://forum.xda-developers.com/showthread.php?t=1745176
Click to expand...
Click to collapse
I notice the same problem a few days ago (I think is since I have install CM10). I have switched on OrDrost since 2 days, I tried the Faux kernel and finally I just revert to full stock rom and my wifi signal haven't change :/
// Edit : after more search, it's a hardware fault :
XDA news
XDA thread
Thesalan said:
// Edit : after more search, it's a hardware fault :
XDA news
XDA thread
Click to expand...
Click to collapse
But on the stock rom WIFI was ok.
Update: Ok I did the "Squeeze" test. Wifi is great whn I squeeze
So it is a hardware problem?? How it only started after I put CM10?
Have you reinstalled the stock rom since you have the problem?
I don't know if CM10 is the cause, or it's a coincidence..
there's an UNOFFICIAL release at the moment which may fix some issues, though I've not noticed anything and I've had every release since A10 installed, so it could be a hardware issue.
I'm on the newest build of cm10 and my WiFi network is fine. I can from leedroid and so far just the same. I do have a tiny bit of earphone cable between my back and hard case which gives me my full bar due to the hardware fault.
Couldnt be bothered sending it back. So this works. Bit did recorded it with HTC so they know I have the fault.
Sent from my HTC One X using xda app-developers app
Thesalan said:
Have you reinstalled the stock rom since you have the problem?
Click to expand...
Click to collapse
Not yet, I really hate the stock rom.
tgcp, Where can I get this rom?
(Although it really seems like an hardware problem,
I heard the latest stock update helps a little so there
might be a software solution)
Rodbouy said:
I'm on the newest build of cm10 and my WiFi network is fine. I can from leedroid and so far just the same. I do have a tiny bit of earphone cable between my back and hard case which gives me my full bar due to the hardware fault.
Couldnt be bothered sending it back. So this works. Bit did recorded it with HTC so they know I have the fault.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
But if you use Cm10 without that little earphone cable, the wifi won't work good?
BTW, what does htc support ask to fix the problem? Do they care you rooted and unlocked the device?
The cable is about 3mm in lengh and as i have a hard case, its enough to compress the connection inside the phone where the fault is.
Htc would of course fix it, but whats the point if the phone is working and its not noticeable.
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Rodbouy said:
The cable is about 3mm in lengh and as i have a hard case, its enough to compress the connection inside the phone where the fault is.
Htc would of course fix it, but whats the point if the phone is working and its not noticeable.
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
but it is noticeable!
I can't move more then 2 meters from my router or it disconnects.
Does your wifi issue not that bad? (without the cable's help)
With out my fix the signal is a joke. 1 bar when 3 feet away. Wasnt usable.
Sent from my HTC One X using xda app-developers app
Rodbouy said:
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Problem is I can't get back to stock! from what I understand the Stock RUU for my phone wasn't released ...
Do you think HTC will be "understanding" and fix the wifi issue even with a custom rom?
(they'll know anyway that I opened bootloader)
Try flash the Rom with the stock kernel, that will surely solve the WiFi problem.
Sent from my HTC Desire C using xda premium
Did you not do a backup before installing custom rom. Im positive that even if you relock the bootloader they can see that if they went in to recovery. But unlikely. So if you flash stock rom and re lock bootloader, remove root you should be fine
Sent from my HTC One X using xda app-developers app
Hi, try using tbaldens CM10. It can be found under HTC ONE X ORIGINAL ANDROID DEVELOPMENT. I found this to be the best CM10
I have been chasing this problem ever since installing CM10 on my Evo 4g LTE. I was getting 4 times the wifi distance on the stock rom. I go about 30 ft. outside the office and wifi drops. Also, what is the most annoying... I stream over our LAN, and when the screen is off, it turns wifi off after a few minutes. (and yes, the check box is checked to keep wifi alive). I've also tried all of the wifi fix apps and none work. If I leave the screen on and stream........ it is good anywhere from 1/2 hour to an hour, then it will just stop. This kills my battery of course. The problem 1st occured when I first bought my OEM 4g lte, but there was an option in the advanced menu "best wifi performance", after checking that, it worked great, then I switched to CM10 and I now have the wifi issue, and there is no option for "best wifi performance". I've tried a couple other jellybean roms and they have the issue as well. This is driving me nuts. I hope someone finds a solution. I don't think the average person would find this as a problem, but when I stream over the net and move all about the shop, it is unacceptable.
I faced the same issue but not on any other ROM. It was specifically with Cyanogenmod 10. I was upset because it gave me the best results but the wifi result was really poor.
However, since I work with wireless networks often, I decided to explore Cyanogenmod's wifi settings. I noticed that if you go in the Advanced Wifi functions (which you can find in the Wifi options menu) you will notice that there is an option called "Wi-Fi Region Code".
Apparently, this option allows you to select the frequency bands your device can operate and is subject to the different world regions. It is quite possible that your Access Point follows the regulatory body of your country and you should know which frequency bands they allow the AP to operate. Due to this it may be just that the Cyanogenmod, by default, put you in a different regulatory domain and limits your frequency band to a subset offered by the AP. Hence, this effectively limits your wifi reach even if you are sitting right next to the AP.
I chose "Japan" since I remembered that their regulatory domain allowed for quite a large subset of frequencies that are allowed on the WIFI spectrum. This immediately increased my received signal strength and I did not have any problem since.
I suggest you play with this, it is likely that your android device will start functioning correctly. However, if you are facing this limited frequency issue on more than one device and that too running different operating systems and different wifi hardware...chances are that your wifi router is malfunctioning. In that case, replacement or repair of the Access point is the best alternative.
Good luck. I hope this solves your problem.
rectorfury said:
I faced the same issue but not on any other ROM. It was specifically with Cyanogenmod 10. I was upset because it gave me the best results but the wifi result was really poor.
However, since I work with wireless networks often, I decided to explore Cyanogenmod's wifi settings. I noticed that if you go in the Advanced Wifi functions (which you can find in the Wifi options menu) you will notice that there is an option called "Wi-Fi Region Code".
Apparently, this option allows you to select the frequency bands your device can operate and is subject to the different world regions. It is quite possible that your Access Point follows the regulatory body of your country and you should know which frequency bands they allow the AP to operate. Due to this it may be just that the Cyanogenmod, by default, put you in a different regulatory domain and limits your frequency band to a subset offered by the AP. Hence, this effectively limits your wifi reach even if you are sitting right next to the AP.
I chose "Japan" since I remembered that their regulatory domain allowed for quite a large subset of frequencies that are allowed on the WIFI spectrum. This immediately increased my received signal strength and I did not have any problem since.
I suggest you play with this, it is likely that your android device will start functioning correctly. However, if you are facing this limited frequency issue on more than one device and that too running different operating systems and different wifi hardware...chances are that your wifi router is malfunctioning. In that case, replacement or repair of the Access point is the best alternative.
Good luck. I hope this solves your problem.
Click to expand...
Click to collapse
I've tried changing my Region Code, but for some reason it keeps defaulting back to Europe... Any ideas? I've tried changing it numerous times, same result.
Howdy Folks!
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
DarkBlaidd said:
Howdy Folks!
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
Click to expand...
Click to collapse
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
I will likely switch back as I have a new hands free stereo for my car that I would like to legally take advantage of
let us know if you run into issues you will need to do a few searches.
sbiricuda said:
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
Click to expand...
Click to collapse
I'm a poor boy, so I am probably going to try and save a few bucks by using this method, which requires root.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
Click to expand...
Click to collapse
What was the GPS issue? Can you link to the fix please?
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
Click to expand...
Click to collapse
Cool, thanks for giving your opinion. How good is your battery life?
yohan4ws said:
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
Click to expand...
Click to collapse
Sounds like a good idea, I will do that.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
Click to expand...
Click to collapse
Noted, I will stay away from fastgsm. I think I am going to do this or GalaxSim Unlock.
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
Click to expand...
Click to collapse
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out. There is also a chance that Samsung will update us to Jellybean, they just released an update for the Galaxy S2, so it's possible.
let us know if you run into issues you will need to do a few searches.
Click to expand...
Click to collapse
Thanks! I believe I have done enough research to do what I want, so hopefully I won't make any dumb mistakes.
DarkBlaidd said:
Update from 2.3.6 to 4.0.4
Click to expand...
Click to collapse
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
Click to expand...
Click to collapse
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
DarkBlaidd said:
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out.
Click to expand...
Click to collapse
I'm in same boat here I guess. Just ordered a Glide, looking forward to having a physical keyboard again since my TP2 days. I was checking out the ROM options, found the link for "Stock UCLJ3 Rom" and it looks like that is the way go, other than maybe just staying stock... I need Bluetooth, Camera, GPS, and Tethering to work, so I guess I won't be messing around with anything fancy.
So don't do any OTA upgrade at all when I first get it out of the box? Just back it up, then root, and install UCLJ3 via CWM? Is this the best choice?
roothorick said:
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Click to expand...
Click to collapse
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
idenlover said:
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
Click to expand...
Click to collapse
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
roothorick said:
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
Click to expand...
Click to collapse
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
idenlover said:
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
Click to expand...
Click to collapse
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
roothorick said:
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
Click to expand...
Click to collapse
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
idenlover said:
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
Click to expand...
Click to collapse
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
roothorick said:
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
Click to expand...
Click to collapse
Awesome, thanks for the help!:good:
roothorick said:
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
Click to expand...
Click to collapse
Damn it, that really sucks. Thank you so much for letting me know that, you saved me some headaches.
Edit: I did some digging around to get a technical explanation of this issue and stumbled across some unexpectedly good news, I can use HSPA+ on T-MO, well halfway at least, I'm going to make a new post as a public service.
Hello, I would like to preface this post by saying I'm a complete noob to XDA Forums and custom ROMs as well. I've know about XDA Developers for years, just never been much of a tinkerer when it comes to Android, I just prefer stock.
Well recently, I bought a used LG G3 because the deal was just to good to pass up. It was my first time using a ROM other than stock and it was utterly disgusting in comparison. I hated it so much I installed my first ROM ever, and it was Candy5 for I heard CynogenMod stopped supporting the LG G3 is some capacity. Well, I've been using it for a while now and made it look as close as I could to stock, there's just one problem.
I recently enabled Wi-Fi calling on Ting. The device was a Verizon model, but I purchased it unlocked, and activated it on the MNVO Ting. Well, it wasn't working so I was wondering what's up. I read that you had to enable it within the devices settings, but all guides were not specific to the custom ROM I had installed, and even following along as closely as I could, the option for Wi-Fi calling wasn't there. I've read that if Wi-Fi calling doesn't appear, your device doesn't support it. But, everywhere I've read, has been consistent that Wi-Fi calling is supported on the LG G3.
So, I ask you long time tinkerers, do you know how to enable Wi-Fi calling within the Candy5 ROM? Does it just not support it? I even used the neat search feature within the settings app and couldn't find a switch for it. Please help!
NeatAndClean said:
Hello, I would like to preface this post by saying I'm a complete noob to XDA Forums and custom ROMs as well. I've know about XDA Developers for years, just never been much of a tinkerer when it comes to Android, I just prefer stock.
Well recently, I bought a used LG G3 because the deal was just to good to pass up. It was my first time using a ROM other than stock and it was utterly disgusting in comparison. I hated it so much I installed my first ROM ever, and it was Candy5 for I heard CynogenMod stopped supporting the LG G3 is some capacity. Well, I've been using it for a while now and made it look as close as I could to stock, there's just one problem.
I recently enabled Wi-Fi calling on Ting. The device was a Verizon model, but I purchased it unlocked, and activated it on the MNVO Ting. Well, it wasn't working so I was wondering what's up. I read that you had to enable it within the devices settings, but all guides were not specific to the custom ROM I had installed, and even following along as closely as I could, the option for Wi-Fi calling wasn't there. I've read that if Wi-Fi calling doesn't appear, your device doesn't support it. But, everywhere I've read, has been consistent that Wi-Fi calling is supported on the LG G3.
So, I ask you long time tinkerers, do you know how to enable Wi-Fi calling within the Candy5 ROM? Does it just not support it? I even used the neat search feature within the settings app and couldn't find a switch for it. Please help!
Click to expand...
Click to collapse
Yeah WiFi calling won't be an option on AOSP ROMs... Its cooked into the stock software (for at least t mobile) and only works on stock based ROMs. There was a developer that tried to use the code from I BELIEVE the nexus 6 and adopt it to our devices but it never got pushed through. If you want WiFi calling/VolTE, stick with stock ROMs.
yanowman said:
Yeah WiFi calling won't be an option on AOSP ROMs... Its cooked into the stock software (for at least t mobile) and only works on stock based ROMs. There was a developer that tried to use the code from I BELIEVE the nexus 6 and adopt it to our devices but it never got pushed through. If you want WiFi calling/VolTE, stick with stock ROMs.
Click to expand...
Click to collapse
Ah, I see. Hopefully some day it would be available on custom ROMs. Using the stock ROM is not even worth the gloriousness of Wi-Fi calling, and that's really saying something, because my room is a complete dead zone for reception. I have to walk out on my porch every time I want to place / receive phones calls or SMS texts.
NeatAndClean said:
Ah, I see. Hopefully some day it would be available on custom ROMs. Using the stock ROM is not even worth the gloriousness of Wi-Fi calling, and that's really saying something, because my room is a complete dead zone for reception. I have to walk out on my porch every time I want to place / receive phones calls or SMS texts.
Click to expand...
Click to collapse
Yeah I completely feel your problem. Over at my house (which is in the maybe 10 minutes from the main bay area) there is NO reception, only when you walk down the street is there reception. When I was on Verizon I got their WiFi booster thing... Now that I'm on T mob, I use WiFi calling bakdd info their ROMS
Anyone seen the firmware for the M9 that supports Marshmallow ? It's definitely out there as some users are running Marshmallow ROMs....
Any leaks ? Any news on official release ?
Is this what you are looking for?
http://www.htc.com/us/support/htc-one-m9/news/
No, that's not for Verizon plus it's a full ROM/RUU.
Sent from my HTC6535LVW using Tapatalk
Yeah, I have been wondering the same thing. I figured something would have got leaked by now. Or at least some info...
Sent from my HTC One M9
The Marshmallow ROM for Verizon's M9 is still in the testing stages. Based upon my current build, I'd guess late testing stages, but don't quote me.
hgoldner said:
The Marshmallow ROM for Verizon's M9 is still in the testing stages. Based upon my current build, I'd guess late testing stages, but don't quote me.
Click to expand...
Click to collapse
Oops! Sorry...
I believe Marshmallow firmware is only out for the dev / WWE devices.
VZW will most likely be the last variant to the update to MM, so don't hold your breath waiting on it.
FYI - I'm running the latest Candy6 (an AOSP-based Marshmallow ROM) on the most recent VZW firmware and it is running flawlessly. I actually thought I was enjoying sense until i went back to AOSP!
PrizmaticSmoke said:
FYI - I'm running the latest Candy6 (an AOSP-based Marshmallow ROM) on the most recent VZW firmware and it is running flawlessly. I actually thought I was enjoying sense until i went back to AOSP!
Click to expand...
Click to collapse
Is there a thread for that here at XDA, in the VZW section ? I've used CM-based ROMs for years but the only one I've seen for the M9 didn't have VZW support (yet).
The Venom team, and a few others, do have a test build for Verizon from HTC. However sharing this build would mean violating an agreement between said testers and HTC/Verizon. This, in turn, would mean no more early test builds would be released to them. This is not what any of us want.
You, and I, have Verizon M9's. We understand our devices are not the same as International/Developer... and thus we wait, patiently. Our turn will come.
hallstevenson said:
Is there a thread for that here at XDA, in the VZW section ? I've used CM-based ROMs for years but the only one I've seen for the M9 didn't have VZW support (yet).
Click to expand...
Click to collapse
Yep there's an XDA thread, but it's over in the general M9 section, here ya go: http://forum.xda-developers.com/one-m9/development/rom-t3265048
The thread title still states it's CM based, but they recently rebased on AOSP for Marshmallow. Most recent build is labeled as an alpha, but it's working great for me.
So to confirm, Verizon is actually testing a marshmallow build?
Aganar said:
So to confirm, Verizon is actually testing a marshmallow build?
Click to expand...
Click to collapse
Of course. Have been for a while. No release date though.
PrizmaticSmoke said:
The thread title still states it's CM based, but they recently rebased on AOSP for Marshmallow. Most recent build is labeled as an alpha, but it's working great for me.
Click to expand...
Click to collapse
I'm working my way through that thread. When it was first started, it appeared that there were a few critical things not working properly, like non-system apps being unable to read the external SD card. When they switched to AOSP, it seemed to improve things, but it's still not clear from that thread.
So..... since you're using it and also on Verizon, what doesn't work ? I've seen people release ROMs with non-working cameras, can't make phone calls, and other crazy s**t. I'm all for helping if I can, but I still need a functioning phone !!
I've got the ROM zip and GAPPS downloaded on my phone ready to go....
hallstevenson said:
I'm working my way through that thread. When it was first started, it appeared that there were a few critical things not working properly, like non-system apps being unable to read the external SD card. When they switched to AOSP, it seemed to improve things, but it's still not clear from that thread.
So..... since you're using it and also on Verizon, what doesn't work ? I've seen people release ROMs with non-working cameras, can't make phone calls, and other crazy s**t. I'm all for helping if I can, but I still need a functioning phone !!
I've got the ROM zip and GAPPS downloaded on my phone ready to go....
Click to expand...
Click to collapse
Honestly everything is working great for me on the build from 01-08, nothing is broken that i can tell. Data, wi-fi, gps, bluetooth, camera, flashlight, SD card, calls, texts, all are good to go. I haven't tested IR blaster as I don't use it for anything. And you will not have advanced calling/VoLTE available as far as I'm aware. But all good otherwise. :good:
I did see another VZW user reporting some issues on the same build like not getting a GPS lock, and their network incorrectly showing as Sprint and losing service whenever they drop to 3g or 1x coverage. But I have not had any GPS issues myself, and can't speak to the coverage issue as I live and work in an area with pretty solid LTE coverage and have had no problems.
I saw the one report of a GPS issue but multiple people saying they have no problem, so I brush off that "issue". I do have advanced calling enabled but no one I call does, so it doesn't matter. If I'm not mistaken, both ends need it enabled (?). Either way, it won't stop me.
Sent from my HTC6535LVW using Tapatalk
The 01/08 build is the one I have downloaded too.
Sent from my HTC6535LVW using Tapatalk
hallstevenson said:
I saw the one report of a GPS issue but multiple people saying they have no problem, so I brush off that "issue". I do have advanced calling enabled but no one I call does, so it doesn't matter. If I'm not mistaken, both ends need it enabled (?). Either way, it won't stop me.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I never had a gps lock when I went from sense to aosp. That was my problem. Switching from LTE to 3g and 1x because of fringe coverage , and having it read sprint pcs was just odd. Other than that, it's a great rom
No problem with GPS here. I just tried it for the first time with Google Maps and it showed my location spot-on. I also tried GPS Status and got a fix on 15/20 satellites (inside).
hallstevenson said:
No problem with GPS here. I just tried it for the first time with Google Maps and it showed my location spot-on. I also tried GPS Status and got a fix on 15/20 satellites (inside).
Click to expand...
Click to collapse
locks super quick too. Once i went and flashed a sense rom, got my lock, then went back to aosp, all was good. Do me a favor, download 4g switcher from the play store (its got a red power button logo). Since your in good 4g coverage. in this app, goto the dropdown menu that lists the radio bands (CDMA/EVDO/GSM/WCDMA/LTE Auto is set by default) select CDMA auto (PRL) (this will force you into 3g mode). Then see if you see either 3107 or sprint PCS as your coverage. Then try to browse to a webpage or something on the 3g, i couldnt get data to work in that mode whatsoever. Then at least ill know if im sane. Thank you
Don't need an app for that - just dial "*#*#4636#*#*"
It shows "Sprint PCS" when I switch to 3G mode. I'm not going to chance any data roaming charges though... Sorry
Did you toggle Settings, Cellular Networks, Data roaming to 'on' ? It's off by default. That could be why you couldn't browse on 3G.
Hello all. I admit to being a noob in terms of installing custom ROM's but have installed CM 12 to my m919 (Tmobile) S4 which works well - except for no audio during calls...
I have roamed the internet and tried various things like installing Sound About, as well as disabling the 'OK Google' feature, with no success. I have Vonage extensions app on my phone and can make calls fine with that - that is of course, voip, but does establish mic and earpiece work ok.
Is this something to do with the modem? I see mention of installing an updated baseband though I have no idea. I also read somewhere about someone flashing stock lollipop first, then CM 12 to fix it? All a bit bewildering to me at present.
Wondered if anyone had any info. Thanks in advance