Related
OK.guys I have a stock n1 running 2.3.6 but I am tired of the wifi issue my question is if I root does this fix the issue and also what are the benefits of rooting and which is the best method and rom
Thanks in advance
Can't answer for certainty because we don't know if your problem is software or hardware related.
Sent from my Transformer TF101 using Tapatalk
my wifi keep on droping off when i google it i see its a problem with the n1
hope this helps
I haven't run stock since Froyo came out, but I haven't had any issues with my wifi, so if it is an issue with software, it doesn't seem like it exists in CyanogenMod. But as baseballfanz mentioned, it is too difficult to determine whether your issue is hardware or software. If it is software, it should be fixed. The two most popular custom ROMs are CyanogenMod and MIUI. I know CyanogenMod covers a lot of the additional features on their website, I am not sure about MIUI, but both probably include better perfomance and battery life, along with a ton of extra features.
Never had any WiFi issues myself or heard of anyone else having any with the N1. I suppose you could TRY another rom but I'm not sure if that would work. If you do I would recommend a cyanogenmod simply because theres so many people using that if anyone else has had this issue its probably been reported and solved if it was a software problem. Always worth a hot and if nothing else theres more to do with a rooted phone anyway.
Good luck, hope you'll let us know how you get on.
addam360 said:
Never had any WiFi issues myself or heard of anyone else having any with the N1. I suppose you could TRY another rom but I'm not sure if that would work. If you do I would recommend a cyanogenmod simply because theres so many people using that if anyone else has had this issue its probably been reported and solved if it was a software problem. Always worth a hot and if nothing else theres more to do with a rooted phone anyway.
Good luck, hope you'll let us know how you get on.
Click to expand...
Click to collapse
There are many people reporting Wi-Fi issues on the Nexus One on a stock ROM after the 2.3.6 update. Many threads in this forum, as well as google's support forum...
Root anyway
Too many benefits and too much fun not to--
Full image backups
Better app managemet
Faster Updates
Ability to run Sense roms
Overclocking
etc
etc
ok ok you guys twisted my arm lol i am going to install cm7.1 let you know how this runs
If you are not rooted yet back up phone with an app like MyBackUp Pro and copy sdcard to pc
Include System Wipe as part of wiping phone before flashing new rom
Best Recovery--latest non-beta Amon_Ra
Wiki has good root info--
not worried about apps all free app can download so not going to back up lol
Your Brave
It backs up more than apps--does System/Home Screens/Bookmarks/SMS/MMS/Playlists etc
Def do your sdcard
Good Luck
brave you say lol
its a new phone so i dont have anything i want to keep in it new as in new to me but a used phone
hey guy sorry took long to report i sucessfully rooted my n1 rubbing cm7 are there any good sense roms i could try i really like the sense interface thanks alot
Check in the Nexus One Android Development forum, or look at the Nexus One wiki, which lists more roms as well. I just went to the Development forum myself and did a search for "sense", there's multiple Sense roms in that forum.
Good luck.
I loaded a runnymedemod007 v007 ROM RUNNING GREAT SO FAR
Hey where Is my manners THANK YOU ALL FOR ALL THE ASSISTANCE !!!
Sent from my HTC Nexus One using XDA App
Hello everyone. I was planning to buy a used HTC Nexus One but I read about all the problems it has and had second thoughts. I had researched and found the following:
*To solve the broken power button- Download "Any unlock" from Google play
*To solve the inactive screen during calls- Download "Call Delay Patch" from Google play (can someone please verify this?)
I have also read about :
(i) camera not working(I saw a topic about clearing the camera's data which worked for some ppl and didn't work for other ppl)
(ii) X- screen problem(I have no knowledge about this) ,and
(iii) Wifi not connecting(I read about using "wifi fix" but not sure if it fixes this)
which are the problems that I couldn't find a solution to.
All of the above is considering it's on 2.3.6 official.
Basically I want to buy a N1 after selling my Samsung Galaxy Ace but I'll only do that if I have a solution to the major problems (such as the wifi and call problem) the N1 has. Is it worth it? Thank you
Ajayr64 said:
Hello everyone. I was planning to buy a used HTC Nexus One but I read about all the problems it has and had second thoughts. I had researched and found the following:
*To solve the broken power button- Download "Any unlock" from Google play
*To solve the inactive screen during calls- Download "Call Delay Patch" from Google play (can someone please verify this?)
I have also read about :
(i) camera not working(I saw a topic about clearing the camera's data which worked for some ppl and didn't work for other ppl)
(ii) X- screen problem(I have no knowledge about this) ,and
(iii) Wifi not connecting(I read about using "wifi fix" but not sure if it fixes this)
which are the problems that I couldn't find a solution to.
All of the above is considering it's on 2.3.6 official.
Basically I want to buy a N1 after selling my Samsung Galaxy Ace but I'll only do that if I have a solution to the major problems (such as the wifi and call problem) the N1 has. Is it worth it? Thank you
Click to expand...
Click to collapse
Well, you are kinda late on the N1 bandwagon aren't you mate? All things said and done, the N1 is a great, unique phone. I've had it for the past 3 years and it has never given me any problems. If you plan on sticking to the stock 2.3.6 ROM, you will not encounter any problems other than maybe the power button problem ( which if you are lucky/careful you might not have to face)
There are no problems with WiFi or Calls ( I think these are problems faced by users who have gone the Custom ROM route and have put a heavily modded JB or ICS ROM on their phones). If you were to flash, say stable CM 7.2, then you will rarely come across any such issues.
They don't make 'em like these anymore
Cheers
Ajayr64 said:
Hello everyone. I was planning to buy a used HTC Nexus One but I read about all the problems it has and had second thoughts. I had researched and found the following:
*To solve the broken power button- Download "Any unlock" from Google play
*To solve the inactive screen during calls- Download "Call Delay Patch" from Google play (can someone please verify this?)
I have also read about :
(i) camera not working(I saw a topic about clearing the camera's data which worked for some ppl and didn't work for other ppl)
(ii) X- screen problem(I have no knowledge about this) ,and
(iii) Wifi not connecting(I read about using "wifi fix" but not sure if it fixes this)
which are the problems that I couldn't find a solution to.
All of the above is considering it's on 2.3.6 official.
Basically I want to buy a N1 after selling my Samsung Galaxy Ace but I'll only do that if I have a solution to the major problems (such as the wifi and call problem) the N1 has. Is it worth it? Thank you
Click to expand...
Click to collapse
I have two N1.
One is stock (GB 2.3.6) The other (JB Rom) is my backup and toy for taking advantage of the great work of the dev.
None of them have the issues you mention.
I enjoyed very much this phone until I got the Galaxy Nexus.
I intend to keep my N1 backup for the foreseeable future (I mean my future).
Yes, for me, it is a keeper.
sphinxcs898 said:
Well, you are kinda late on the N1 bandwagon aren't you mate? All things said and done, the N1 is a great, unique phone. I've had it for the past 3 years and it has never given me any problems. If you plan on sticking to the stock 2.3.6 ROM, you will not encounter any problems other than maybe the power button problem ( which if you are lucky/careful you might not have to face)
There are no problems with WiFi or Calls ( I think these are problems faced by users who have gone the Custom ROM route and have put a heavily modded JB or ICS ROM on their phones). If you were to flash, say stable CM 7.2, then you will rarely come across any such issues.
They don't make 'em like these anymore
Cheers
Click to expand...
Click to collapse
Haha yeah very late Oh that's good to hear I saw a lot of posts in these forums about these problems and some were old and some were new so I wanted some clarity. Thanks for the info! I was planning not to root the phone also so that's good. I'm tired of the samsung interface on my phone so i wanted a change.
gunner1937 said:
I have two N1.
One is stock (GB 2.3.6) The other (JB Rom) is my backup and toy for taking advantage of the great work of the dev.
None of them have the issues you mention.
I enjoyed very much this phone until I got the Galaxy Nexus.
I intend to keep my N1 backup for the foreseeable future (I mean my future).
Yes, for me, it is a keeper.
Click to expand...
Click to collapse
Oh that's cool. I 'm more encouraged to buy it now. Is JB rom stable? I was planning to not root it but if i get bored might give it a shot.
Ajayr64;38062419
Oh that's cool. I 'm more encouraged to buy it now. Is JB rom stable? I was planning to not root it but if i get bored might give it a shot.[/QUOTE said:
The JB is stable. I will update it this w.e. to the latest nightly (Evervolv-Perdo-3.2.0).
Good luck
Click to expand...
Click to collapse
gunner1937 said:
I have two N1.
One is stock (GB 2.3.6) The other (JB Rom) is my backup and toy for taking advantage of the great work of the dev.
None of them have the issues you mention.
I enjoyed very much this phone until I got the Galaxy Nexus.
I intend to keep my N1 backup for the foreseeable future (I mean my future).
Yes, for me, it is a keeper.
Click to expand...
Click to collapse
I have two N1 too. One is AOKP ICS as my daily driver and the other is JB CM 10. Indeed, I just bought a brand new N1 (got a good deal) and upgraded to AOKP ICS and gave to my father to use. I like the N1 because it fits nicely in the pocket and reasonable size.
taodan said:
I have two N1 too. One is AOKP ICS as my daily driver and the other is JB CM 10. Indeed, I just bought a brand new N1 (got a good deal) and upgraded to AOKP ICS and gave to my father to use. I like the N1 because it fits nicely in the pocket and reasonable size.
Click to expand...
Click to collapse
Oh so you haven't had any of the problems I mentioned above? That's my only concern with buying the N1.
Again, as long as it's stock or a stable Custom ROM, no need to worry about any problems. It's a reliable phone.
Okay thanks. Btw on the N1 wiki it says super one click works only up till 2.3.3 . So if the android version is 2.3.6 i'll have to root it without using Super one click?
either u can downgrade it to 2.3.3 n root or else try www.unlockroot.com
but a simple solution is to unlock the bootloader...
Sent from my Nexus One using Tapatalk
Ajayr64 said:
Okay thanks. Btw on the N1 wiki it says super one click works only up till 2.3.3 . So if the android version is 2.3.6 i'll have to root it without using Super one click?
Click to expand...
Click to collapse
n1newbie said:
either u can downgrade it to 2.3.3 n root or else try www.unlockroot.com
but a simple solution is to unlock the bootloader...
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Yea, actually, the simplest one is to unlock the boot loader and flash the su.zip file to gain root access. There are numerous tutorials on the web which let you do that.
To summarize, the steps would be:
a) Unlock bootloader
b) Flash the recovery image. (CWM or AmonRA)
c) Copy the su.zip onto the SD card.
d) Reboot into recovery to flash that zip file and voila, root access.
OKay thanks a lot !
I'm using a 3 year old nexus one I bought on these forums over 7 months ago. It looks really beat up but has never needed any repairs including the power button. I've had stock 2.3.6 then cm7 then 4.1 for a couple months then cm7 again. It's always been pretty good. Only issue is occasional digitizer going nuts which is common but only a minor annoyance.
Sent from my Nexus One using xda app-developers app
None on the Vivid Roms are anywhere close to stable, and all the dev's are leaving :crying:
I may be misinformed, but there is not a single rom that works flalessly on our devices...
So, this brings me to my question. Is there a UNIVERSAL ROM for ANY ANDROID DEVICE?
No, there is no universal Rom
Why?
-because every android device is completely different from each other...even similar devices have quite a bit of differences-chipsets, manufacturers, drivers, mount points...etc, they all very from device to device
Sent from my HTC PH39100 using Tapatalk 2
get a new phone
Sent from my HTC PH39100 using Tapatalk 4 Beta
skyrocketeer said:
get a new phone
Sent from my HTC PH39100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Just wondering... Would you want to donate one? The only way I got a Vivid is coz I got one in one of those charity secret santa things.
Mihir1997 said:
Just wondering... Would you want to donate one? The only way I got a Vivid is coz I got one in one of those charity secret santa things.
Click to expand...
Click to collapse
Do you dev? considering you just asked for Universal rom, I'm going to assume you don't.
So no
Mihir1997 said:
None on the Vivid Roms are anywhere close to stable, and all the dev's are leaving :crying:
I may be misinformed, but there is not a single rom that works flalessly on our devices...
So, this brings me to my question. Is there a UNIVERSAL ROM for ANY ANDROID DEVICE?
Click to expand...
Click to collapse
i suggest flashing some roms instead of putting dow the forum. some ppl have put alot of work into these roms
Try albinoman's CyanogenMod 10.1 ROM. It's Jellybean 4.2.2 and is stable. Only problem I have is reception bars are inaccurate, but that is a rare problem.
Only other bug I have encountered is reception drops on first boot. Easy fix in the development thread.
KarlKognition said:
Try albinoman's CyanogenMod 10.1 ROM. It's Jellybean 4.2.2 and is stable. Only problem I have is reception bars are inaccurate, but that is a rare problem.
Only other bug I have encountered is reception drops on first boot. Easy fix in the development thread.
Click to expand...
Click to collapse
Hi,
I flashed this Rom, but it seems that the in-call and speaker volume is still very low.
I started from the stock ICS rom, unlocked, rooted, flash boot.img and flash the rom. The volume issue in CM10 is solved in this Rom?
Thanks
friedenhe said:
Hi,
I flashed this Rom, but it seems that the in-call and speaker volume is still very low.
I started from the stock ICS rom, unlocked, rooted, flash boot.img and flash the rom. The volume issue in CM10 is solved in this Rom?
Thanks
Click to expand...
Click to collapse
No its going to plauge this device forever. I am going to try one thing to see if I can make it work .. I found something.. But It most likely wont work and this is sorta off topic to what this started out to be. If you have any questions go ask em in the Development section
KarlKognition said:
Try albinoman's CyanogenMod 10.1 ROM. It's Jellybean 4.2.2 and is stable. Only problem I have is reception bars are inaccurate, but that is a rare problem.
Only other bug I have encountered is reception drops on first boot. Easy fix in the development thread.
Click to expand...
Click to collapse
This is the first Rom that I've flashed and its my daily driver its good enough the call volume is annoying but when I call someone they can't hear me but I can hear them from time to time any idea on why that is?
Sent from my Vivid 4G using xda app-developers app
swordmastr54 said:
This is the first Rom that I've flashed and its my daily driver its good enough the call volume is annoying but when I call someone they can't hear me but I can hear them from time to time any idea on why that is?
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
It is a bug in all of the AOSP based roms. Albinoman released a new build which kinda fixes it. I haven't tested it yet but according to the posts on the thread seems to be working well.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
WildfireDEV said:
It is a bug in all of the AOSP based roms. Albinoman released a new build which kinda fixes it. I haven't tested it yet but according to the posts on the thread seems to be working well.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
Click to expand...
Click to collapse
I would like to ask: do you mean the low in-call volume is fixed? I am going to try this rom!
Thanks
friedenhe said:
I would like to ask: do you mean the low in-call volume is fixed? I am going to try this rom!
Thanks
Click to expand...
Click to collapse
its more like "medium" in call volume now.
i m making one!!
a universal rom seems pretty impossible right!! i ll make one fr sure and u all will get that for free right here on xda i jst need time so u jst wait n watch people!!
I need a coustom rom for allwinner a23 it is a chinese tablet
is there have any rom for Walton primo s5. if anyone know plzzz
An old instinct brought me here? Why? Because its possible!
Mihir1997 said:
None on the Vivid Roms are anywhere close to stable, and all the dev's are leaving :crying:
I may be misinformed, but there is not a single rom that works flalessly on our devices...
So, this brings me to my question. Is there a UNIVERSAL ROM for ANY ANDROID DEVICE?
Click to expand...
Click to collapse
What an interesting post that relays something I've been noticing about XDA, it's development and far too many post of someone who asserted they had no problems putting such and such ROM into his device, "Here's the Tutorial" issue I'm having at present.
I have even openly complained about the only thing I was learning how to do here was how to brick devices in every possible way. And the way I found out how to recover from it properly, sure wasn't from them here. A lot of times you can get the official firmware straight from the manufacturer, online. I've been gone 8 to 10 years and what happened? Most of the posts are Ghost-Town status! Back to the point.
I don't see why they can't be universal, really. And it seems as though, that this was overlooked by every single so-called developer out there. How do you make a 64 bit processor with a dual core would be the first clue. You got your phone(modem) and a split partition that the modem may control sometimes but, can be modified. They seem to have decorated the tree, so to speak rather than actually "build" something. Oh it looks nice and all with the tinsel and shinny stuff. But they're in a hurry I guess and missing the reality of it. You can see it with the source code. The story will go that they got a source code, let's say, Android 4.0. Did this, this, this and that and here you go. Woohooo, look what I did. But what did they do? It wasn't really building if you look at it the right way, it's just, decoration. In the beginning you had to stack things, like boxes. one on top of the other. It's kinda like that. Or sideways. Remember the basics. Two core, four core, soon eight. It doesn't really matter when all it is, is some kind of partitioning. What is it all? 64 one way or another. But seperate the two is the first issue. The phones gonna be the phone regardless. Put a switch in for control. Then you're left with the other part to do as you wish. Run a whole different program, on top of the phone program. Eventually you're gonna reach the end of what the phone is capable of. That's a givenIt was remembering the days of TV/VCR repair and how a basic motherboard works. This part controls audio, this part controls video thing. Now you see it? It's the same in an Android isn't it, just smaller of course. And when it dawned on me that this was more than possible and everyone went the other way? Oh boy things are about to get silly around here at XDA. I'm most definately going to take a different look at this now. It wasn't a problem ten years ago once you got the hang of it to flash in a ROM. Everything I see now is. So what happened? Everyone went decorating I guess...
---------- Post added at 03:19 PM ---------- Previous post was at 02:50 PM ----------
mg2195 said:
No, there is no universal Rom
Why?
-because every android device is completely different from each other...even similar devices have quite a bit of differences-chipsets, manufacturers, drivers, mount points...etc, they all very from device to device
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Riiiight chipsets are more about how many GHz the device may use which is usually around 1 to 1.65 GHZ, we want our devices fast. Manufactures? Well they just put the same stuff together in a different way. Drivers and mounts can be put together, same ol USB (with maybe different serials) and even sd card mounts. Really there's not much difference when you look at it as a whole. Refrence
https://www.androidauthority.com/fact-or-fiction-android-apps-only-use-one-cpu-core-610352/
Long time Android user here. I'm debating on whether or not I'd like to pull the trigger and root/flash a custom ROM to my brand new Nexus 6 (seriously, still has that new-phone smell). My girlfriend and I both got these beauties the same day and love them to pieces.
However...
Coming from a rooted/customized S3 and M7 I'm already missing the customization features that rooting devices allowed. Although I wouldn't have any issues doing so, I'm a bit concerned with potential bugs that could occur while using custom ROMs.
For instance, when I bought my M7, before I rooted it, the call quality was phenomenal. Then after rooting/flashing a custom OS, the quality seemed to drop substantially. No matter which ROM/kernel sets I used, there were always data and/or performance issues including, but not limited to, Pandora app skipping even when data (LTE) was at max reception.
I'm not asking which custom ROM is better as that would be a "to each their own" situation. I've, personally, been a fan of Liquid Smooth and ran it as a daily driver for my S3 (and ViperOne for my M7), but from what I've seen in the development pages there are quite a few ROMs I'd like to try out.
I wanted to see what people who've already rooted and flashed custom ROMs thought of their Nexus 6 post-awesomizing. Did the call quality change? Other than listed ROM bugs, were there any frequent issues that continued through various ROMs and kernel combinations?
Thanks, in advance, to anyone and everyone who replies!
Cheers,
Blue
bb2si said:
Long time Android user here. I'm debating on whether or not I'd like to pull the trigger and root/flash a custom ROM to my brand new Nexus 6 (seriously, still has that new-phone smell). My girlfriend and I both got these beauties the same day and love them to pieces.
However...
Coming from a rooted/customized S3 and M7 I'm already missing the customization features that rooting devices allowed. Although I wouldn't have any issues doing so, I'm a bit concerned with potential bugs that could occur while using custom ROMs.
For instance, when I bought my M7, before I rooted it, the call quality was phenomenal. Then after rooting/flashing a custom OS, the quality seemed to drop substantially. No matter which ROM/kernel sets I used, there were always data and/or performance issues including, but not limited to, Pandora app skipping even when data (LTE) was at max reception.
I'm not asking which custom ROM is better as that would be a "to each their own" situation. I've, personally, been a fan of Liquid Smooth and ran it as a daily driver for my S3 (and ViperOne for my M7), but from what I've seen in the development pages there are quite a few ROMs I'd like to try out.
I wanted to see what people who've already rooted and flashed custom ROMs thought of their Nexus 6 post-awesomizing. Did the call quality change? Other than listed ROM bugs, were there any frequent issues that continued through various ROMs and kernel combinations?
Thanks, in advance, to anyone and everyone who replies!
Cheers,
Blue
Click to expand...
Click to collapse
The problem with HTC and Samsung devices, is that they are not truly open source. For a "dev" to get an AOSP ROM built for those devices can be quite an ordeal and can require many hacks to be made and many bugs will be found trying to get the AOSP source code to fit that device... The Nexus does not have this problem as AOSP is designed for it. Even a monkey could compile a bug free AOSP rom for the nexus, so don't worry about that sort of thing.
rootSU said:
The problem with HTC and Samsung devices, is that they are not truly open source. For a "dev" to get an AOSP ROM built for those devices can be quite an ordeal and can require many hacks to be made and many bugs will be found trying to get the AOSP source code to fit that device... The Nexus does not have this problem as AOSP is designed for it. Even a monkey could compile a bug free AOSP rom for the nexus, so don't worry about that sort of thing.
Click to expand...
Click to collapse
That's quite a relief to read. So there hasn't been any known issues with the call quality suffering? That is my biggest concern as with my HTC (post root/flash) the call quality was horrendous! It sounded like the person on the other line was constantly mumbling. The quality on the Nexus 6, as of now, is so crisp and clear it sounds as if they're sitting right next to me.
I'll definitely be looking forward to trying out the various ROMs available.
bb2si said:
That's quite a relief to read. So there hasn't been any known issues with the call quality suffering? That is my biggest concern as with my HTC (post root/flash) the call quality was horrendous! It sounded like the person on the other line was constantly mumbling. The quality on the Nexus 6, as of now, is so crisp and clear it sounds as if they're sitting right next to me.
I'll definitely be looking forward to trying out the various ROMs available.
Click to expand...
Click to collapse
Yep, with a nexus those sort of issues should be a thing of the past. HTC are particularly bad as on teh M7, they themselves couldn't even get GPE to run properly (Speaker quality took a tumble).
Also, you may not know but Xposed framework just came out with an Alpha. In a short while, it wil get more stable and modules will get updated for Lollipop, meaning you will probably be able to add much of that customisation without changing from the stock rom.
rootSU said:
Yep, with a nexus those sort of issues should be a thing of the past. HTC are particularly bad as on teh M7, they themselves couldn't even get GPE to run properly (Speaker quality took a tumble).
Also, you may not know but Xposed framework just came out with an Alpha. In a short while, it wil get more stable and modules will get updated for Lollipop, meaning you will probably be able to add much of that customisation without changing from the stock rom.
Click to expand...
Click to collapse
I've heard of the manufacturer UI's getting in the way of performance with devices. I'm glad I went with the pure Google goodness this time! I'll keep an eye on Xposed, but I think you've helped my decision in rooting today.
Now to impatiently wait for work to be over and rush home to my laptop!
bb2si said:
I've heard of the manufacturer UI's getting in the way of performance with devices. I'm glad I went with the pure Google goodness this time! I'll keep an eye on Xposed, but I think you've helped my decision in rooting today.
Now to impatiently wait for work to be over and rush home to my laptop!
Click to expand...
Click to collapse
Good luck.
It is also my personal recommendation that you don't use a toolkit and you use fastboot natively..
rootSU said:
Good luck.
It is also my personal recommendation that you don't use a toolkit and you use fastboot natively..
Click to expand...
Click to collapse
Always do! Already have links saved to my email for how-to's and how-not to's.
Thanks for your input!
bb2si said:
Long time Android user here. I'm debating on whether or not I'd like to pull the trigger and root/flash a custom ROM to my brand new Nexus 6 (seriously, still has that new-phone smell). My girlfriend and I both got these beauties the same day and love them to pieces.
However...
Coming from a rooted/customized S3 and M7 I'm already missing the customization features that rooting devices allowed. Although I wouldn't have any issues doing so, I'm a bit concerned with potential bugs that could occur while using custom ROMs.
For instance, when I bought my M7, before I rooted it, the call quality was phenomenal. Then after rooting/flashing a custom OS, the quality seemed to drop substantially. No matter which ROM/kernel sets I used, there were always data and/or performance issues including, but not limited to, Pandora app skipping even when data (LTE) was at max reception.
I'm not asking which custom ROM is better as that would be a "to each their own" situation. I've, personally, been a fan of Liquid Smooth and ran it as a daily driver for my S3 (and ViperOne for my M7), but from what I've seen in the development pages there are quite a few ROMs I'd like to try out.
I wanted to see what people who've already rooted and flashed custom ROMs thought of their Nexus 6 post-awesomizing. Did the call quality change? Other than listed ROM bugs, were there any frequent issues that continued through various ROMs and kernel combinations?
Thanks, in advance, to anyone and everyone who replies!
Cheers,
Blue
Click to expand...
Click to collapse
It's Nexus man The best dev support is available for Nexus devices All ROMs has bugs and you'll have to bear with it. But the ROMs for Nexus devices meet stable version sooner than others. Taking Parandroid Android as an example. Visit their website and you'll be able to find that the main team focus on the Nexus line and they've legacy team to support other devices. I was also an user of S3 (Exynos variant) and PA used to be a great custom ROM for me
SAW_JOK3R said:
It's Nexus man The best dev support is available for Nexus devices All ROMs has bugs and you'll have to bear with it. But the ROMs for Nexus devices meet stable version sooner than others. Taking Parandroid Android as an example. Visit their website and you'll be able to find that the main team focus on the Nexus line and they've legacy team to support other devices. I was also an user of S3 (Exynos variant) and PA used to be a great custom ROM for me
Click to expand...
Click to collapse
Yes I suppose a caveat to what I have already said, there will still be bugs on roms due to devs making customisations and you will see their bugs potentially. When I say bug free, I'm just talking about a clean AOSP rom affecting the fundamentals of the device.
rootSU said:
Yes I suppose a caveat to what I have already said, there will still be bugs on roms due to devs making customisations and you will see their bugs potentially. When I say bug free, I'm just talking about a clean AOSP rom affecting the fundamentals of the device.
Click to expand...
Click to collapse
Yeah. The awesome dev support is the only thing which made me to ditch Note 4 And I'm evidencing that custom ROMs has less Major bugs than stock ROM LOL :silly:
bb2si said:
That's quite a relief to read. So there hasn't been any known issues with the call quality suffering? That is my biggest concern as with my HTC (post root/flash) the call quality was horrendous! It sounded like the person on the other line was constantly mumbling. The quality on the Nexus 6, as of now, is so crisp and clear it sounds as if they're sitting right next to me.
I'll definitely be looking forward to trying out the various ROMs available.
Click to expand...
Click to collapse
I'm currently running Euphoria OS on my N6. It is based on CM12, and offers a lot of customization options without actually having to enable root. I've been running it for almost a month now, and I have yet to feel a need to go into Developer Options and flip the switch for root access.
From a call quality standpoint, we are all running the same radio versions, so it will come down to your area. I work in an area where T-Mobile is spotty (my building specifically, LTE is stupid fast outside of it) and so I'm eagerly awaiting the update which adds WiFi Calling to AOSP. As it stands now, my phone does activate HD Voice and show an indicator icon in the dialer when I'm on with another T-Mobile user.
Maybe I can use this to convince my girlfriend to let me root hers, as well. She's never had an unlocked device before and she's very cautious about it, but I'm sure I could convince her.
Thanks again, all!
Quick question, does any one have a good recommendation on a guide to root my n6 I don't want to use a tool kit because I'm hearing its better to do root through fastboot if that's correct. I've been rooting phone for some time now but I've only dealt with fastboot once before with an HTC device. All my other devices where s2 to s5. And I usually used chainfires tool kits. So could someone please set me in right direction as far as guides go? Thanks
beachbum40 said:
Quick question, does any one have a good recommendation on a guide to root my n6 I don't want to use a tool kit because I'm hearing its better to do root through fastboot if that's correct. I've been rooting phone for some time now but I've only dealt with fastboot once before with an HTC device. All my other devices where s2 to s5. And I usually used chainfires tool kits. So could someone please set me in right direction as far as guides go? Thanks
Click to expand...
Click to collapse
If you already have TWRP installed, just flash SuperSU. It used to require an insecure boot image due to Lollipop's security features removing root on each boot, but now the new SuperSU injects root each time.
beachbum40 said:
Quick question, does any one have a good recommendation on a guide to root my n6 I don't want to use a tool kit because I'm hearing its better to do root through fastboot if that's correct. I've been rooting phone for some time now but I've only dealt with fastboot once before with an HTC device. All my other devices where s2 to s5. And I usually used chainfires tool kits. So could someone please set me in right direction as far as guides go? Thanks
Click to expand...
Click to collapse
Its pretty simple.
Use fastboot to unlock bootloader (wipes device]
use fastboot to flash TWRP recovery
Put SuperSU zip on sdcard and flash that via TWRP recovery.
There are guides in general. The main thing is understanding using fastboot. I have a thread on that.
Go to general > all in one thread > question 28
Thank you for quick response guys? Rooting today can't take it anymore.
NotATreoFan said:
I'm currently running Euphoria OS on my N6. It is based on CM12, and offers a lot of customization options without actually having to enable root. I've been running it for almost a month now, and I have yet to feel a need to go into Developer Options and flip the switch for root access.
From a call quality standpoint, we are all running the same radio versions, so it will come down to your area. I work in an area where T-Mobile is spotty (my building specifically, LTE is stupid fast outside of it) and so I'm eagerly awaiting the update which adds WiFi Calling to AOSP. As it stands now, my phone does activate HD Voice and show an indicator icon in the dialer when I'm on with another T-Mobile user.
Click to expand...
Click to collapse
Why do you need a specific custom ROM for many customization when there is Xposed available now?
---------- Post added at 12:48 AM ---------- Previous post was at 12:45 AM ----------
beachbum40 said:
Quick question, does any one have a good recommendation on a guide to root my n6 I don't want to use a tool kit because I'm hearing its better to do root through fastboot if that's correct. I've been rooting phone for some time now but I've only dealt with fastboot once before with an HTC device. All my other devices where s2 to s5. And I usually used chainfires tool kits. So could someone please set me in right direction as far as guides go? Thanks
Click to expand...
Click to collapse
This thread can help you further
bb2si said:
Maybe I can use this to convince my girlfriend to let me root hers, as well. She's never had an unlocked device before and she's very cautious about it, but I'm sure I could convince her.
Thanks again, all!
Click to expand...
Click to collapse
Tell her no sex if you can't root her phone!
SAW_JOK3R said:
Why do you need a specific custom ROM for many customization when there is Xposed available now?
Click to expand...
Click to collapse
Well xposed is Alpha - not ready for public consumption.
Also, xposed module features are never as good as ones compiled directly into the ROMs. They're just not as efficient. Xposed doesn't replace the need for custom ROMs.
rootSU said:
Well xposed is Alpha - not ready for public consumption.
Also, xposed module features are never as good as ones compiled directly into the ROMs. They're just not as efficient. Xposed doesn't replace the need for custom ROMs.
Click to expand...
Click to collapse
Well, Xposed is working flawlessly on nexus 5 and 6 without causing any issue That's why suggested Yeah, that doesn't replace the need of custom ROM but that actually add more feature of user's choice
Hi guys,
My knowledge of ROMs and rooting isn't the best so please bare with me if this question seems dumb. And before anyone says, I have read this thread (and countless others) but would like some clarification.
I've always wanted to install CyanogenMod to my Z3 Compact because my car, an E46 BMW has not been able to pair with my phone since 4.2.2 when a change to bluetooth.default.so was made - Cyanogenmod has the fix.
I have seen recent posts on this forum that suggest if the phone is rooted and a custom ROM is installed, I'm still able to maintain my camera quality which previously was limited (fish-eye effect and low light poor quality) due to the loss of DRM'd software due to a DRM restore fix created by one of the forum members. Is this correct? This was the only thing that ever stopped me rooting my Z3 as camera quality is of high importance to me.
I've been using an iPhone 5s since my screen smashed last month and I planned to buy an iPhone 6s this weekend but if it seems I can use the Z3 Compact for all purposes ( In-car Bluetooth, stable Android, good camera and battery life) then I will definitely get the screen repaired tomorrow!
Thanks in advance.
This is a link explaining the Bluetooth issue I'm talking about.
tsmr said:
Hi guys,
My knowledge of ROMs and rooting isn't the best so please bare with me if this question seems dumb. And before anyone says, I have read this thread (and countless others) but would like some clarification.
I've always wanted to install CyanogenMod to my Z3 Compact because my car, an E46 BMW has not been able to pair with my phone since 4.2.2 when a change to bluetooth.default.so was made - Cyanogenmod has the fix.
I have seen recent posts on this forum that suggest if the phone is rooted and a custom ROM is installed, I'm still able to maintain my camera quality which previously was limited (fish-eye effect and low light poor quality) due to the loss of DRM'd software due to a DRM restore fix created by one of the forum members. Is this correct? This was the only thing that ever stopped me rooting my Z3 as camera quality is of high importance to me.
I've been using an iPhone 5s since my screen smashed last month and I planned to buy an iPhone 6s this weekend but if it seems I can use the Z3 Compact for all purposes ( In-car Bluetooth, stable Android, good camera and battery life) then I will definitely get the screen repaired tomorrow!
Thanks in advance.
This is a link explaining the Bluetooth issue I'm talking about.
Click to expand...
Click to collapse
It is true, I am using DRM fix for my Z3c because I didn't backup my DRM keys (duh!) and the camera quality seems perfect, although the fix says it also restores X-Reality and whatnot but I haven't got to get the engine working, I fixed that with Color Control to match my saturation and colors needs...
As for the Bluetooth issues, I've kinda experienced problems with it too, I have a Bluetooth gamepad, and whenever I'm playing an Android game that supports controllers, it disconnects, but when I play on emulators it doesn't happen... I don't know if there's a fix for that but oh well.
DRM fix works only on stock based roms and on Concept roms.
It doesn't work on custom roms like Cyanogenmod.
istux said:
DRM fix works only on stock based roms and on Concept roms.
It doesn't work on custom roms like Cyanogenmod.
Click to expand...
Click to collapse
Thanks for the reply. I don't actually need CyanogenMod, I just need to be able to edit the bluetooth.default.so file as per the thread I linked so that in-car Bluetooth works with my handset. Is this possible whilst maintaining camera quality?
Also when you say 'only works on stock based ROMs' - does this mean that I could install stock Android 6.0 to my device with a custom bluetooth.default.so file, then install the DRM fix and it will work as normal? This would be amazing!
PS. What is a Concept ROM?
I'm so sorry for asking what are most probably stupid questions but I'm fairly new to the Android scene thus still learning.
Of course its possible, you don't need unlocked bootloader to edit system files lol. Unlock bootloaders are used to install custom kernels or firmwares not made by Sony, like CyanogenMod or AOKP and etc.
Concept, is the "Alpha" Edition of Marshmallow that Sony plans to ship out within the next few months, they let a select a number of people to test out the rom and help them debug it. I don't recommend installing it as it is near beta stage and the number of bugs really don't make it suitable as a daily driver for you phone, stick with Lollipop until we get the official stable update unless you know what you're doing.
Good luck!
Revontheus said:
Of course its possible, you don't need unlocked bootloader to edit system files lol. Unlock bootloaders are used to install custom kernels or firmwares not made by Sony, like CyanogenMod or AOKP and etc.
Concept, is the "Alpha" Edition of Marshmallow that Sony plans to ship out within the next few months, they let a select a number of people to test out the rom and help them debug it. I don't recommend installing it as it is near beta stage and the number of bugs really don't make it suitable as a daily driver for you phone, stick with Lollipop until we get the official stable update unless you know what you're doing.
Good luck!
Click to expand...
Click to collapse
Thanks for explaining what Concept is. I guess that's not something that I need right now! To clarify; are you saying that to be able to edit system files, I don't need to unlock my bootloader? I was under the impression that to do this I'd need to:
a) Unlock bootloader.
b) Root device.
c) Access/edit the bluetooth system files.
Any advice on the steps I need to take to have my Z3 Compact work with my car whilst maintaining original camera quality would be much appreciated!
PS. Due to the prompt, positive responses in this thread, I've just taken my Z3 to a local to store so the screen can be repaired. Thanks all for the help - such good folk!
tsmr said:
Thanks for the reply. I don't actually need CyanogenMod, I just need to be able to edit the bluetooth.default.so file as per the thread I linked so that in-car Bluetooth works with my handset. Is this possible whilst maintaining camera quality?
Also when you say 'only works on stock based ROMs' - does this mean that I could install stock Android 6.0 to my device with a custom bluetooth.default.so file, then install the DRM fix and it will work as normal? This would be amazing!
PS. What is a Concept ROM?
I'm so sorry for asking what are most probably stupid questions but I'm fairly new to the Android scene thus still learning.
Click to expand...
Click to collapse
If you need only the root in order to work on that bluetooth file, you can do it without unlocking the bootloader.
Follow this tutorial: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
You will be able to get root without losing DRM keys and else you will make a backup of DRM keys So, if in the future you need/want to unlock the bootloader, you have a safe copy of your keys. :good:
istux said:
If you need only the root in order to work on that bluetooth file, you can do it without unlocking the bootloader.
Follow this tutorial: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
You will be able to get root without losing DRM keys and else you will make a backup of DRM keys So, if in the future you need/want to unlock the bootloader, you have a safe copy of your keys. :good:
Click to expand...
Click to collapse
Thank you so much. Will try this in the morning and hopefully I will be able to use Bluetooth in my car once again!
tsmr said:
My knowledge of ROMs and rooting isn't the best[...]I have seen recent posts on this forum that suggest if the phone is rooted and a custom ROM is installed, I'm still able to maintain my camera quality[...]camera quality is of high importance to me
Click to expand...
Click to collapse
My suggestion (solely based on the points your described):
Either get a Z3c and stick to stock ROM
Or get an iPhone (seriously)
Now don't get me wrong, I am not being against custom ROMs. I am running CM myself and the first think I do before buying any android phone is to check if it has official CM support But you need to know that custom ROMs come with their own cost, and it depends whether you're willing to pay the price.
Reasons for my suggestion to you is that the road to unlocked bootloader and custom ROMs is a rough one. You'll be adding more mods and flashing more updates and you quickly end up with a phone which gets into the way and needs constant maintenance. Then there are issues with warranty, security, bugs, etc. Checking the forums for changelogs, kernels and ROMs will become a normal routine.
If you're regular user who wants his/her phone to just work, accept one of my suggestion and save yourself some pain. However, you might choose to be adventurous, then welcome to the community
PS: I'm myself exploring Z3c and iPhone 5s for my next phone.
Honestly, the road to rooting and properly running a rooted software is really not that long and rocky if you follow the linked thread perfectly. You also don't NEED to unlock the BL to get most of the advantages (there are many pre-rooted customized ROMs available without needing an unlocked BL). Follow the thread, stick to a good stable ROM or customization (I'm on Max Fury right now and she did some amazing work, check it out), and you'll be just fine. My BL is not even unlockable, doesn't bother me one bit. You can use Nova for a more Google-ish feel, and Sony's 5.1.1 is already pretty good at not being "Sony-fied".
Anyhow, this is the best phone I've ever owned, not looking back (I've had MANY more than just in my signature).
hv6478 said:
NOTE: annotated snippets from original comment
- if you follow the linked thread perfectly
- you also don't NEED to unlock the BL to get most of the advantages (it's upto you to figure out that just which advantages follow under that "most" category)
- follow the thread
- stick to a good stable ROM or customization (it's upto you to figure out whether you need a rom or customization)
Click to expand...
Click to collapse
Thanks. This proves my point even more! Now just compare this to getting a phone that just works
Although ROM customization is a beautiful and powerful idea, it's not for everyone, and comes at a cost (read: complexity). If anyone is ready to handle the complexity, please dive right in
Please don't mistake me. I'm not trying to disrespect the devs or offend custom ROM users, I'm both. I'm just trying to list down the pros and cons.