Looks like our devices are finally dead. Time to Upgrade
I'll wait for a (stable) KK ROM before agreeing ;+)
Sent from my XT897 using XDA Premium 4 mobile app
lol, well the Nexus S 4G Developing Forum is pretty much dead except for the avatar rom really. I saw a couple people trying to get a stable 4.3 working but that was weeks ago. as for 4.4 i read that someone said you can use the Crespo version but you have to change a couple things and even with those changes it barely works
Yeah, this is a sad thing... If I had more time I'd try to build something...
Sent from my Nexus 5 using Tapatalk
rbeavers said:
I'll wait for a (stable) KK ROM before agreeing ;+)
Sent from my XT897 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm using a non stable version of kitkat rite now and I love it. It feels as fast as it was when i first got it two years ago. And when art is finally standard, it will go even faster
Sent from my Nexus S using xda app-developers app
I'm attempting to build CM11 for crespo4g right now.
We'll see how this goes.
I'm anticipating I'll run into at least as many issues as are plaguing the crespo. Plus WiMAX hasn't been working on any 4.3 builds, so I doubt we'll have it either. I'll post it here when I'm done, don't think I have enough cred on xda to post on the 4g dev section
nstant said:
lol, well the Nexus S 4G Developing Forum is pretty much dead except for the avatar rom really. I saw a couple people trying to get a stable 4.3 working but that was weeks ago. as for 4.4 i read that someone said you can use the Crespo version but you have to change a couple things and even with those changes it barely works
Click to expand...
Click to collapse
CM 10.2 is very active. Getting Nightly updates, but it runs a little slow.
CM10.3, KK, should be better.
Sent from my XT897 using XDA Premium 4 mobile app
rbeavers said:
CM 10.2 is very active. Getting Nightly updates, but it runs a little slow.
CM10.3, KK, should be better.
Sent from my XT897 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ummm kk is CM11 not CM10.3... Just an fyi
Sent from my Nexus 5 using Tapatalk
Wow
Sent from my Nexus 5 using xda app-developers app
the1dynasty said:
Ummm kk is CM11 not CM10.3... Just an fyi
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
That makes sense.
Can't wait.....
Sent from my XT897 using XDA Premium 4 mobile app
My build failed, trying to work from crespo cm11 sources and crespo4g cm10.2 solely for the radios. Anybody wanna try and help me figure this out? I've built for mako, but that's a whole different animal.
Sent from my Nexus 4 using Tapatalk
I forked CyanogenMod's CM10.2 crespo4g repo, and added a couple changes to update storage for KitKat, but most of the device specific stuff draws from the crespo tree, which is already at version 11.0 in CM's sources. I'm gonna try to start a build right now. I'll let you guys know how it goes. I'll also open a thread in the ns4g dev section as soon as I can.
If anyone wants to contribute code/tips/general know-how to this project it would be greatly appreciated. Also since I'm working from the 10.2 codebase, I expect the WiMax issue to carry over. That's something I'm willing to work on when I get it booting.
I also tried a dirty port from this discontinued crespo rom: http://forum.xda-developers.com/showthread.php?t=2526740. It just bootloops.
Here's my repo. Feel free to fork/make pull requests/etc...
https://github.com/jc4gavejc/android_device_samsung_crespo4g/tree/cm-11.0
jc4gavejc said:
I forked CyanogenMod's CM10.2 crespo4g repo, and added a couple changes to update storage for KitKat, but most of the device specific stuff draws from the crespo tree, which is already at version 11.0 in CM's sources. I'm gonna try to start a build right now. I'll let you guys know how it goes. I'll also open a thread in the ns4g dev section as soon as I can.
If anyone wants to contribute code/tips/general know-how to this project it would be greatly appreciated. Also since I'm working from the 10.2 codebase, I expect the WiMax issue to carry over. That's something I'm willing to work on when I get it booting.
I also tried a dirty port from this discontinued crespo rom: http://forum.xda-developers.com/showthread.php?t=2526740. It just bootloops.
Here's my repo. Feel free to fork/make pull requests/etc...
https://github.com/jc4gavejc/android_device_samsung_crespo4g/tree/cm-11.0
Click to expand...
Click to collapse
What's the error?
Sent from my SPH-L710 using XDA Premium 4 mobile app
jc4gavejc said:
I forked CyanogenMod's CM10.2 crespo4g repo, and added a couple changes to update storage for KitKat, but most of the device specific stuff draws from the crespo tree, which is already at version 11.0 in CM's sources. I'm gonna try to start a build right now. I'll let you guys know how it goes. I'll also open a thread in the ns4g dev section as soon as I can.
If anyone wants to contribute code/tips/general know-how to this project it would be greatly appreciated. Also since I'm working from the 10.2 codebase, I expect the WiMax issue to carry over. That's something I'm willing to work on when I get it booting.
I also tried a dirty port from this discontinued crespo rom: http://forum.xda-developers.com/showthread.php?t=2526740. It just bootloops.
Here's my repo. Feel free to fork/make pull requests/etc...
https://github.com/jc4gavejc/android_device_samsung_crespo4g/tree/cm-11.0
Click to expand...
Click to collapse
can't help with building it but i can be the first to try it when you're done...
My thoughts would be to edit the bootclass path in the kernel from the nexus s ROM to work for the nexus s 4g, as well as whatever else code is important in the kernel, then get it booting since in order to dirty port a ns ROM to the ns4g all you have to do is swap kernels and then you'll have basic functionality, but that's my two cents, I could be missing something important idk
Sent from my Sero 7 Pro using xda app-developers app
CM11 FTW
nstant said:
Looks like our devices are finally dead. Time to Upgrade
Click to expand...
Click to collapse
Just installed adityaxavier's unofficial CM11. Everything is working, including WiFi to 3G switchover (which wouldn't work in any CM10.2 build or Slimbean 4.3 build).
Wimax 4g is not yet working, but that is a minor issue for most.
I hope the Nexus S 4G development won't die out any time soon. This NS4G is my first smartphone, and I use it as a wifi only device. It was a friend's old phone, donated to me. I also have an original Motorola Droid (also from another friend's old phone stash), which I rooted and modded with custom ROMs and stuff. The Droid is now my little brother's first smartphone (also wifi-only). It's been a great learning experience, AND we get useful devices to use too! It's why I love it here at XDA so much.
NOT Dead! Because I found a few "newer", great ROMs to try out still. ROMs I tried and thoughts:
- adityxavier's unofficial CM 11, build 11 --> great, fast, smooth; but I get those errors prompts saying "process com.phone.android stopped working" after boot up. I tried a clean install, as well as a dirty install after factory reset. Still getting those errors.
- jc4gavejc's AOSP 4.4 for Nexus S 4G --> same as above, but also very simplistic, lean, and clean-looking, which I loved. I would've kept this ROM if not for the same error prompts "process com.phone.android stopped working"; or "process com.messaging.android stopped working". I'm beginning to think my phone can't handle 4.4 builds somehow.
- Slim Bean 4.3 --->fast, smooth, stable, minimalistic-looking, with none of the extra features that I'd likely not use anyways. I'm using it now as my stable ROM until I see a working android 4.4 that I can try out again.
- Helly Bean 4.3 -->Also a fast and stable ROM on my crespo4g device. Lots of extra features from Paranoid Android, which I don't really use. My stock battery charging animation disappears with this one. It seems to power on during charging, even after I turn it off.
- Official CM 10.2 --> easiest to install b/c of the cminstaller, but noticeably slower than the above custom ROMs.
Once I have enough posts, and clearance to do so, I'll post these comments, with more details, in their appropriate threads, to help give feedback on the ROMs I tried. Thanks to all the developers that spent time and efforts on these!
Trying to gather some momentum asking for official Omni on the LTE version...
Please make a comment if you're interested...
If there's enough people then maybe we can go start a petition page on the OmniROM forum.
I do know that there's already a very good unofficial build, but OpenDelta will only work on official Omni :/
Sent from my Nexus 7 using Tapatalk
According to XDA I am a noob and cannot post this in the comments of PA 4.4 M7 only because I haven't commented 10 times. I am, however, not a noob with rooting and have been rooted for about half a year. I wouldn't consider myself advanced, but you can use some technical talk.
I have used Paranoid Android before and I thought it was an awesome ROM. I switched to Insertcoin SixthSense when it came out for a change in looks. I just recently got bored of Sense and wanted to go back to stock. I used OmniRom for a few days and I now want to go back to Paranoid Android. When I try to flash it, it says E: Error executing updater binary in zip 'filepath of rom'. I am using the latest OmniRom 4.4.3 and my experience tells me that downgrading Android versions usually doesn't work. Am I stuck until PA upgrades to 4.4.3 or am I just doing something wrong.
Also, sorry for posting here, I haven't commented 10 times yet so I cannot post it in development where I would want to.
Phone - HTC One M7 ATT
ROM - Omni
Android Version - 4.4.3
Kernel - Stock
Recovery - TWRP 2.6.3.3
Current build of paranoid android is android version 4.4.4
#stayparanoid
Hey, sorry, could you link to your most recent version of Paranoid Android for the m7, please?. I don't see the m7 on your website and I'm not certain where it would be. Thank you
Sent from my One using XDA Free mobile app
markandyson said:
Hey, sorry, could you link to your most recent version of Paranoid Android for the m7, please?. I don't see the m7 on your website and I'm not certain where it would be. Thank you
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
We don't support anything that isn't a nexus, oppo, or 1+. You need to find the thread for your device in your device forum.
#stayparanoid
Do you guys think cyanogen will eventually add this phone to its official supported devices?
Coming from a Nexus 5 with endless rom development It'd be a shame if this phone didn't see as much. Especially since it has such potential
No I don't think that oneplus two will get official cyanogen support, as oneplus dropped cyanogen and started using there own OxygenOs. In fact, I think that even future devices from oneplus will also never get official cyanogen.
So, unfortunately we will need to stay at unofficial builds only.
Hit thanks If I helped!!!
kishan12345 said:
No I don't think that oneplus two will get official cyanogen support, as oneplus dropped cyanogen and started using there own OxygenOs. In fact, I think that even future devices from oneplus will also never get official cyanogen.
So, unfortunately we will need to stay at unofficial builds only.
Hit thanks If I helped!!!
Click to expand...
Click to collapse
yes cm13 will be officially available soon!And you are wrong ! one plus had a bad breakup with cyanogen but theirs a diiference between how people work on cynogenos and cyanogenmod !It depends on the devolepers of each community on how they work on devolepment on a particular device but one plus two devolepment is insane so cm13 is on the way and if u are still concerned look at the devs of HTC 826 they made thier device get official support and dont worry as far as i know the devolpement for this device will be booming shortly !And theirs already a thread on CM 13 !
Hope that your words come true. But still I don't think so that cm13 will be available OFFICIALLY.
Sent from my ONE A2003 using Tapatalk
kishan12345 said:
Hope that your words come true. But still I don't think so that cm13 will be available OFFICIALLY.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
lol bro if they get unofficial builds perhaps in a week ..then tell ME why wont they make it official after a month !what one plus one had is the cyanogen os and not cyanogenmod !To make a device official in cyanogenmod u have to have good devolpment for a particular device and the works for cm13 is already started for op2 !Check out cm12.1 thread garak is working on cm13 and threres another thread called cm13
As i understand, in order to get an official support from cyanogen to our device there must be unofficial CM build, witch can be sent to CM team for a review. If it passes, has most things working, then they add it to their device tree and officially supports it. In other words, anyone there can take CM vendor and framework codebase and then go and start adding the code necessary to make CM work properly on OPT device. When developer gets far enough along, he can then submit that code back to CM for inclusion into CM's github. If that code passes the checks that the CM team has, then the CM team will merge that code into its own device tree and add official support for that device.
Also there are chance of CM team taking this step by their selves .. but there is probably no hope for that. So the only hope is Grarak
This information is found in the official CM forum so i doubt it is false.
This is probably a dumb question..
But is it possible to flash the system.img from stock over a CM 13 rom and keep user data? Or a combination of the various IMG files?
I'm just having a lot of instability issues with the nightlies and don't want to have to download the 35gb of music again now that I'm on 2mbs internet :crying:
I had gone completely stock including relocking boot loader - agree - non stock ROMS are less stable.
Sent from my MI MAX using Tapatalk
BJNK said:
This is probably a dumb question..
But is it possible to flash the system.img from stock over a CM 13 rom? Or a combination of the various IMG files?
I'm just having a lot of instability issues with the nightlies and don't want to have to download the 35gb of music again now that I'm on 2mbs internet :crying:
Click to expand...
Click to collapse
Appears I may have found the answer in this excellent guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I am wondering if anyone can confirm if Google Music would still have all it's downloaded music? Or would flashing write over that, as they are protected/hidden/encrypted files?
Best guess
Going back stock will make it factory fresh
I.e. Bye bye downloads
Sent from my MI MAX using Tapatalk
Maybe don't use the nightlies and just use a more stable ROM? Your problem seems to be with nightlies being too unstable, well, that's the name of the game with nightlies. Maybe go for one of the other ROMs in the forum that offer much more stability? Won't be stock-stable but it will be pretty stable...
Sent from my LG-H900 using Tapatalk
CoNsPiRiSiZe said:
Maybe don't use the nightlies and just use a more stable ROM? Your problem seems to be with nightlies being too unstable, well, that's the name of the game with nightlies. Maybe go for one of the other ROMs in the forum that offer much more stability? Won't be stock-stable but it will be pretty stable...
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
You're probably right. I'm just a little surprised that the Redmi Note 3's unoffical version of CM 13 was 10x more stable than the unlocked Google Nexus phone. Not blaming anyone or thinking I am owed anything. I just assumed since it ran so well on the RN3 that it should be near perfect on the N6P.
Any ROMS you reccomend that? Any reason not to just go stock+root+xposed?
BJNK said:
You're probably right. I'm just a little surprised that the Redmi Note 3's unoffical version of CM 13 was 10x more stable than the unlocked Google Nexus phone. Not blaming anyone or thinking I am owed anything. I just assumed since it ran so well on the RN3 that it should be near perfect on the N6P.
Any ROMS you reccomend that? Any reason not to just go stock+root+xposed?
Click to expand...
Click to collapse
AFAIK last CM snapshot (release) for 6p was in April.
If you want a stable ROM for 6p, choose one that is based on AOSP and not to heavily modified.
I've been using Pure Nexus ROM for awhile now and I find it very stable, if you find a bug and report it correctly, the dev is sure to try his best to fix it.
He also releases an update every month at least to include the security patches.
Stock ROMs can have bugs too and sometimes fixed in custom ROMs, they're usually more optimized too
+1 for pure nexus rom and xposed
Sent from my Nexus 6P using XDA-Developers mobile app