[ROM][5.1/6.0][CM12.1/13][UBERTC][OPTIMIZED] Unofficial Build for i605

[Uuugh]

Playing with your new CM13... looks great so far. Thanks!

If anyone else has their phone crashing, check out the solution at this link. http://android.stackexchange.com/a/144858

 

[wilson3q]

Playing with your new CM13... looks great so far. Thanks!

If anyone else has their phone crashing, check out the solution at this link. http://android.stackexchange.com/a/144858

Thanks for testing.

Sent from my GT-N7105 using XDA-Developers mobile app

 

[Uuugh]

Btw. The cm13 requires SU to be installed in recovery after installation. http://forum.xda-developers.com/showthread.php?t=1538053

Very solid ROM. I threw xposed on top.

 

[xflbret]

Alright. Despite my aforementioned frustration toward the confusion of the definition of the word "solid", I am going to test this myself. I REALLY don't want to get another phone. But, development seems to be slowing down for this phone (don't understand why, a boot loader that can not be unlocked seems like a downgrade to me), and this is the only thread that has been touched for months.

Wish me luck.

 

[wilson3q]

Alright. Despite my aforementioned frustration toward the confusion of the definition of the word "solid", I am going to test this myself. I REALLY don't want to get another phone. But, development seems to be slowing down for this phone (don't understand why, a boot loader that can not be unlocked seems like a downgrade to me), and this is the only thread that has been touched for months.

Wish me luck.

Try the new version 0629...

Sent from my GT-N7105 using XDA-Developers mobile app

 

[xflbret]

Well, I am downloading the 6/29 version, but the download is slooooooooooooooooow. Is there anything that can be done about that?

 

[xflbret]

Well, I flashed it. I have made a phone call and received a phone call. So, right away I am much better off than I was with my last few attempts at CM. It is still early for me. I am waiting for TiBu to restore my apps. I'll check in either this evening or in the morning to inform of my progress, and any problems.

---------- Post added at 12:49 AM ---------- Previous post was at 12:19 AM ----------

Alright, first problem...the GPS won't lock. I am coming from a TW Rom and made sure I got a GPS lock right before flashing this ROM. In the first post of this thread there is mention of a fix. It says "(replace country SG to your own)". I don't know what "country SG" is. I click on the link and there's only one file offered. Can someone clear this up? I am going to need GPS if I stick with this ROM...

 

[wilson3q]

Well, I flashed it. I have made a phone call and received a phone call. So, right away I am much better off than I was with my last few attempts at CM. It is still early for me. I am waiting for TiBu to restore my apps. I'll check in either this evening or in the morning to inform of my progress, and any problems.

---------- Post added at 12:49 AM ---------- Previous post was at 12:19 AM ----------

Alright, first problem...the GPS won't lock. I am coming from a TW Rom and made sure I got a GPS lock right before flashing this ROM. In the first post of this thread there is mention of a fix. It says "(replace country SG to your own)". I don't know what "country SG" is. I click on the link and there's only one file offered. Can someone clear this up? I am going to need GPS if I stick with this ROM...

Sg is the country code of Singapore.

Open the zip file, edit system/etc/gps.conf, replace all sg.pool.ntp.org to xx.pool.ntp.org....xx is your country code.

Sent from my GT-N7105 using XDA-Developers mobile app

 

[xflbret]

Sg is the country code of Singapore.

Open the zip file, edit system/etc/gps.conf, replace all sg.pool.ntp.org to xx.pool.ntp.org....xx is your country code.

Sent from my GT-N7105 using XDA-Developers mobile app

I have the gps.conf open. There are several references to Asia in this. I am in the United States. What's the correct syntax for North America?

Or, is there just a pre-configured file for the US I can use to flash it in there?

 

[wilson3q]

I have the gps.conf open. There are several references to Asia in this. I am in the United States. What's the correct syntax for North America?

Or, is there just a pre-configured file for the US I can use to flash it in there?

Line begin with # is comment line...you can ignore. No reference to asia...

As i said, only need replace sg to us... you will be fine. But first lock still takes time.


Sent from my GT-N7105 using XDA-Developers mobile app

 

[xflbret]

I'll write my notes so far. I want to provide all the feedback I can because I really want Wilson to get this ROM right.

My first attempt didn't go so well, but I don't blame that all on the ROM. I attempted to restore all my apps with TiBu, and I guess this ROM didn't like that. I came from KitKat, so I'm guessing some of these apps liked being on KitKat but not Marshmallow. So, I reflashed again without restoring my app backups, and let them all download from Google Play. Huge pain in the ass, but with much better results.

Since my reflash, GPS is indeed working. I did have to reset my APN setting to default once already, and I really hope this is the last time. I am dumbfounded as to why this irritating problem hasn't been fixed yet. I mean, who is it that's using CM that doesn't want this fixed?!?!?!?!?

That problem aside, things are going okay so far. DirecTV doesn't want to start on this ROM, and the SiriusXM app is a bit shaky. I don't know if that's the fault of the apps or the ROM, but I thought I'd mention it.

I'll keep you updated with any more info I come up with. And, when I get a few minutes free, I'll edit in "US" to the GPS file even though it is working. Call it patriotism.

---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------

Oh, one more note...Bluetooth works okay if only one app wants the speaker. When two apps are competing for the speaker, some weird distorted sounds happen for a second or so. Not a huge deal, but this problem doesn't exist on the TW ROM so I thought I'd mention it.

 

[xflbret]

Well, for whatever reason the Bluetooth got worse. Very, very choppy. I remember this from last year when I tried this ROM. This happens regardless of whether I'm playing Poweramp, VLC, or Google music player. And, it isn't a distance thing because I was less than two feet away from the phone. I'll wait a day or so for someone to post a fix. If that doesn't happen, I'm out. I can make some sacrifices, but I'm afraid my music isn't one of them.

 

[jheide44]

Well, for whatever reason the Bluetooth got worse. Very, very choppy. I remember this from last year when I tried this ROM. This happens regardless of whether I'm playing Poweramp, VLC, or Google music player. And, it isn't a distance thing because I was less than two feet away from the phone. I'll wait a day or so for someone to post a fix. If that doesn't happen, I'm out. I can make some sacrifices, but I'm afraid my music isn't one of them.

Thanks for stopping by.

FWIW... The next time you "demand" a fix on a timetable perhaps submitting logs detailing your issue would be a value add to the dev/community in general...

If you want to add value, Google "logcat"... YMMV, but I run them over adb/USB debug... Good luck

Sent from my Nexus 6 using Tapatalk

 

[xflbret]

Thanks for stopping by.

FWIW... The next time you "demand" a fix on a timetable perhaps submitting logs detailing your issue would be a value add to the dev/community in general...

If you want to add value, Google "logcat"... YMMV, but I run them over adb/USB debug... Good luck

Sent from my Nexus 6 using Tapatalk

I was thinking that if this Bluetooth issue had been fixed, someone would post a link to it. But, I'm not going to go through the pain the ass of logcat files when I know full well nothing is going to come of it at this point.

I'm not demanding anything. In fact, I'm not expecting anything at all. For reasons I'm not understanding, the community abandoned this phone a long time ago. The APN issue has been baked in CM for well over a year now. So, too, has this Bluetooth issue. If someone was going to fix these issues it would have happened a long time ago. Not just the CM authors' fault, though. Samsung strung us along for a few months saying there would be a TW Lollipop release, and as we all know they pulled the rug out from under us at the last minute.

Truth be told: As of this morning I have officially given up. I don't WANT to buy another phone, but circumstances have dictated that I have little choice at this point. In fact, when I got the email about the response to my post coming in, I was googling for a more modern phone with an unlockable bootloader that I can run my long-desired-but-never-realized bug-free AOSP ROM on. So far, I'm leaning toward the Note 4 (which apparently was cracked about two months ago), but am exploring other choices, as well.

Thanks to Wilson and all others who made an effort to extend the life of the Note 2. Even though the results were never what I was looking for, and despite the negative tone of some of my posts based on three years of frustrations, I do indeed appreciate the efforts.

P.S. To whomever reads this post, we really need to all get on the same page concerning the definition of the word "solid" when describing a ROM.

 

[jheide44]

@xflbret
If you don't pull/provide a log you will never know, some of our devs have a similar note 2 from another carrier (not a i605) and have no way to test or bug fix on on VZW without log submissions. I hear what you are saying about activity winding down, but ultimately verizon is the real bastard for locking down our bootloader! i.e. Fewer unlocked BL phones fewer custom recovery/AOSP ROM folks less activity in the community for the i605. That said...

new device:
once you go nexus you will never go back. At least that was how it went down for me. (No more touchwiz or smali/baksali, just AOSP no bull****...)

The nexus 6, 5x and 6p have radios compatible with all US carriers... Check out the unlocked phones on swappa or VZW branded N6... With VZW, you may have to play the "shell game" to get VZW to activate your nano sim (i.e. borrow a VZW iPhone from a friend to get your account setup on sim, then pop sim in non VZW nexus 6 or newer and u r off to races). That said the last time I just got the customer support person on phone to setup my nonVZW imei & new sim, so maybe they got their heads out of their asses?

i605 official cm13 notes:
Fwiw I went back to the i605 as my daily driver for 2 weeks in early June. i found recent official cm13 nightlies to have no APN issues, good Bluetooth (to pebble watch and vehicle hands free)... There was a random reboot that may, or may not, have been fixed since then.

Next steps:
Have not played with this unofficial build ROM since early 2016. But prior to that it was my daily driver for over a year.

Today my note 2 Serves as a WiFi only remote control for my openHAB deployment...(OpenHAB is basically middleware for various home automation stuffs)

Maybe later next week I can test this current build for a few days and provide logs/comments if issues are noted.

Conclusion:
Like I said earlier, Good luck with however you choose to move forward.

Sent from my Nexus 6 using Tapatalk

 

[wilson3q]

Anyone to test the new build?

Sent from my GT-N7105 using XDA-Developers mobile app

 

[jheide44]

Anyone to test the new build?

Sent from my GT-N7105 using XDA-Developers mobile app

Ting GSM sim cards are on sale, just a buck. I just ordered 10 they should be here tomorrow. When they arrive I'll activate one and test your 7/13/16 i605 build on the T-Mobile network this weekend.

 

[amoot329]

Anyone to test the new build?

Sent from my GT-N7105 using XDA-Developers mobile app

Only using this phone as a gaming device with my v10 as a daily driver/hotspot. Don't have a sim card in there to test data. Bluetooth works fine with Bluetooth speaker, haven't noticed any choppiness. I do notice it has some memory leaks when I switch between multiple user profile for the game Underworld Empire. It lags immensely, even when pressing the home button, takes ~5s to drop back to home screen. Game would time out, would then have to restart game.

I do use the app Kernel Adiutor but haven't messed with the memory settings yet. Only changed the kernel governor from bfq to cfq.

Anyone to test the new build?

Sent from my GT-N7105 using XDA-Developers mobile app

Sent from my LG-H901 using Tapatalk

 

[xflbret]

As I stated in a post a week or two ago, I have given up on the Note 2. I chose the Note 4 as my next phone. After unlocking it and rooting it, I naturally set out to find a ROM I want to try out. So, I looked over CM13 for the Note 4.

Many people in that thread have also complained about a Bluetooth choppiness issue. So, I really don't think this is an issue with the Note 2, or any dev's compatibility with it. I think that this is a bug in the base code of CM that no one can or will fix.

I hope this helps someone.

 

[wilson3q]

Only using this phone as a gaming device with my v10 as a daily driver/hotspot. Don't have a sim card in there to test data. Bluetooth works fine with Bluetooth speaker, haven't noticed any choppiness. I do notice it has some memory leaks when I switch between multiple user profile for the game Underworld Empire. It lags immensely, even when pressing the home button, takes ~5s to drop back to home screen. Game would time out, would then have to restart game.

I do use the app Kernel Adiutor but haven't messed with the memory settings yet. Only changed the kernel governor from bfq to cfq.



Sent from my LG-H901 using Tapatalk

Multi user mode not working well with note 2. It is a high end smart phone. Single user should not lag.

Sent from my GT-N7105 using XDA-Developers mobile app