Will the i9500 ever get an aokp rom? I would ask developers to please make an aokp rom for it since that is an amazing rom.
If anyone knows any information about this please do but without spamming
Stay Cool
Samsung doesnt release the source code for its exynos processor. So, till now there hasnt been a cyanogenmod rom yet. But it is in progress. First cm, then aokp because aokp is based on cm roms.
Sent from my GT-I9500 using Tapatalk 4 Beta
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!
i have seen that omni rom is not supporting legacy devices like galaxy s,etc..
why is it so....
why there are not included in their mainfesto??
will they include these devices in future...
anurag.dev1512 said:
i have seen that omni rom is not supporting legacy devices like galaxy s,etc..
why is it so....
why there are not included in their mainfesto??
will they include these devices in future...
Click to expand...
Click to collapse
So the thing is, omni as a whole does support legacy devices. However developers may not have legacy devices as a high priority, so support for them will be slow.
They will be added in the future if a developer does bring them up
Sent from my Nexus 7 using Tapatalk
ok.....just answer one more thing..
cybojenix said:
So the thing is, omni as a whole does support legacy devices. However developers may not have legacy devices as a high priority, so support for them will be slow.
They will be added in the future if a developer does bring them up
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
if any other developer brings omni to legacy device by himself will that get treated as official rom from omni developer side...
anurag.dev1512 said:
if any other developer brings omni to legacy device by himself will that get treated as official rom from omni developer side...
Click to expand...
Click to collapse
Amy developer can contribute any patch they/feel suitable to omni, including legacy patches, as long as the quality is to a good standard, it works, and it doesn't break anything else
Sent from my Nexus 7 using Tapatalk
...???
cybojenix said:
Amy developer can contribute any patch they/feel suitable to omni, including legacy patches, as long as the quality is to a good standard, it works, and it doesn't break anything else
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
i m asking that now omni is not supporting legacy devices if any other non-omni developer creates rom for legacy device then will that be recognised as official rom from omni..
If they are experienced enough to maintain it, then I guess yes it will be official.
However it is my opinion that many people who "bring up" a rom on a device are not experienced enough to be a maintainer for a team such as omni or cyanogenmod.
Sent from my Nexus 7 using Tapatalk
Yes legacy devices will be supported if the ROM runs well enough on them. They will definitely not be kept out of having official builds.
Support Samsung Galaxy S2 I9100
tilal6991 said:
Yes legacy devices will be supported if the ROM runs well enough on them. They will definitely not be kept out of having official builds.
Click to expand...
Click to collapse
Can we just make a poll or something to ask to support Samsung Galaxy S2 I9100.
tilal6991 said:
Yes legacy devices will be supported if the ROM runs well enough on them. They will definitely not be kept out of having official builds.
Click to expand...
Click to collapse
So Why i9100(not g version) doesn't have official support? Below is list of unofficial builds:
http://forum.xda-developers.com/showthread.php?t=2533946
http://forum.xda-developers.com/showthread.php?t=2494127
Karls0 said:
So Why i9100(not g version) doesn't have official support? Below is list of unofficial builds:
http://forum.xda-developers.com/showthread.php?t=2533946
http://forum.xda-developers.com/showthread.php?t=2494127
Click to expand...
Click to collapse
Encourage your dev to push his changes to gerrit so we can get official builds set up. It's up to him though.
http://forum.xda-developers.com/showpost.php?p=47606886&postcount=79
@nims11 posted link to his github in "Developers - Merging Your Working Device" thread. Something more is needed? I'm not dev and i don't know how exactly gerrit work. Can you add i9100 to gerrit basing on it or something else is needed?
Edit:
I asked both i9100 developers of OmniRom - they can't do anything as long as admin doesn't create directory for i9100 in OmniRom github. Maybe someone with permission to do this will read this post
Karls0 said:
http://forum.xda-developers.com/showpost.php?p=47606886&postcount=79
@nims11 posted link to his github in "Developers - Merging Your Working Device" thread. Something more is needed? I'm not dev and i don't know how exactly gerrit work. Can you add i9100 to gerrit basing on it or something else is needed?
Edit:
I asked both i9100 developers of OmniRom - they can't do anything as long as admin doesn't create directory for i9100 in OmniRom github. Maybe someone with permission to do this will read this post
Click to expand...
Click to collapse
It took a while to get i9100 forked due to the fact that it was a holiday for many of us.
It's forked and the 4.4 bringup patches are on gerrit for review. Rather than forking one of the trees out there, we started from the same origin point as n7000/i777 as I want the commit history for those devices to be similar.
Right now, the holdup for i9100 is that no one who actually owns the device and knows how to apply/review Gerrit patches has reviewed and tested them yet.
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.
I am really close to tossing the M9 out the window and finally coming back to CM and rooted phones on verizons network. Is there not an official Cyanogenmod thread for the Nexus 6p? Cyanogens site has recent nightlys and snapshots. Also I see SlimGapps is no more, whats the set of Gapps everyone is using now?