Samsung has posted the i500 source code up on their site today. Thanks to everyone who sent email's to samsung
You can find it here!:
Samsung Fascinate i500 source code
If someone could mirror this that would be great! Ill try to get one up tonight when im home.
I just sold my Nexus today on Ebay. this news has cheered me up.
Awesome, I can't download it through my phone though lol. (not that I will be able to make heads or tails out of it either way)
This should now lead to a kernel with integratedroot, correct?
I'll post a mirror once I finish downloading it.
Does Thu mean permanent root too? Seems like things a re quite different for fascinate than droids.
Dirk's root is permanent.
Heres a mirror link, not sure if it will be any faster than source though.
Eh, guess I can't post links yet.
tats_06 said:
Does Thu mean permanent root too? Seems like things a re quite different for fascinate than droids.
Click to expand...
Click to collapse
You're right. At this point on the original Droid, we were about three weeks away from the first, highly cryptic, nerve wracking root procedure. We were also still a couple of months away from Koush showing up and compiling the first Droid port of CyanogenMod.
I'm personally highly impressed with how quickly this community is getting going!
Here's one:
http://zennmaster.com/mirror/SCH-I500_OpenSource.zip
Have fun!
This mirror has been updated to the new (9/16) version.
Zennmaster said:
You're right. At this point on the original Droid, we were about three weeks away from the first, highly cryptic, nerve wracking root procedure. We were also still a couple of months away from Koush showing up and compiling the first Droid port of CyanogenMod.
I'm personally highly impressed with how quickly this community is getting going!
Click to expand...
Click to collapse
Oh I meant like different root process and etc. I am not complaining about pace of things
Good news for those of us in Vibrant section trying to port certain items like the puzzle lockscreen!
Can someone please explain what custom kernel is and what would it bring for this phone? Thanks in advance
Apparently there is something wrong with the source code samsung released, as kernels built with the code do not boot.
fallingup said:
Apparently there is something wrong with the source code samsung released, as kernels built with the code do not boot.
Click to expand...
Click to collapse
Even unmodified they just don't boot? Time for some more emails to samsung!
Turns out they changed the package between last night and this morning. The MD5 hashes are different.
Last Night:
[email protected]:~/fascinate$ md5sum SCH-I500_OpenSource.zip
05a5eadc5f859bf385d202d738dfcfe6 SCH-I500_OpenSource.zip
This morning:
[email protected]:~/fascinate$ md5sum SCH-I500_OpenSource.zip 771c9a5745637887db257e6c94ae7ade SCH-I500_OpenSource.zip
fallingup said:
Turns out they changed the package between last night and this morning. The MD5 hashes are different.
Last Night:
[email protected]:~/fascinate$ md5sum SCH-I500_OpenSource.zip
05a5eadc5f859bf385d202d738dfcfe6 SCH-I500_OpenSource.zip
This morning:
[email protected]:~/fascinate$ md5sum SCH-I500_OpenSource.zip 771c9a5745637887db257e6c94ae7ade SCH-I500_OpenSource.zip
Click to expand...
Click to collapse
I was just downloading to check that. I know I got an 'official' email earlier this morning, about 5 hours after we found the code last night.
They even have a version field in that table.. Come on Sammy, work with us here.
so has anyone confirmed that the new source works? I'm really excited to start mucking around in the code now that we've got odin restores ready.
sonofskywalker3 said:
so has anyone confirmed that the new source works? I'm really excited to start mucking around in the code now that we've got odin restores ready.
Click to expand...
Click to collapse
source is the same as far as we can tell now that we have messed with it
sorry for the mix up
So I've asked this question in other threads. Is there any long term ill side effects to the lag fix? I've had the captivate, and now the fascinate back on my favorite network so I've used it for a few days on both phones and never kept it. Just curious if someone who knows could answer this for me.
Sent from my SCH-I500 using XDA App
The only upside I've seen from the lag fix is boosting the Quadrant scores. Doesn't do much else on my phone and I'm actually thinking about removing it and waiting to screw it up some more when CM gets ported.
Related
They haven't been heavily tested, but IRC seems relatively content with them. Mind you, these were never meant for the Fascinate, but the Mesmerize.
Voodoo
ec10_voodoo.zip
or
http://adbdev.com/danknub/ec10_voodoo.zip
Nonvoodoo
ec10_nonvoodoo.zip
or
http://adbdev.com/danknub/ec10_nonvoodoo.zip
Once again, thanks jt1134 for his scripts.
adrynalyne said:
They haven't been heavily tested, but IRC seems relatively content with them. Mind you, these were never meant for the Fascinate, but the Mesmerize.
Voodoo
ec10_voodoo.zip
Nonvoodoo
ec10_nonvoodoo.zip
Once again, thanks jt1134 for his scripts.
Click to expand...
Click to collapse
ill give it a go . thank you .
Downloading now. Any notable differences over your eb16 kernel?
Hi Adrynalyne!
Just installed. Everything's looking good so far. Will need more time with it though. Thanks.
Installing now. Hopefully no explosions =P
EDIT: I've played with it for 5 or 10 minutes now. Seems quite nice. I'll test the battery and all that fun stuff tomorrow.
Thanks adrynalyne.
Curious about this, however my battery is just settling in on EB01 so ill wait and see what everyone thinks...
Sent from my SCH-I500 using XDA App
A description of features would be nice, thanks!
Downloading and installing
Sent from my SCH-I500 using XDA App
Same here, but since i'm still getting only 30hrs max on light usage I figure what the heck.... give it a try.
chargerfn909 said:
Curious about this, however my battery is just settling in on EB01 so ill wait and see what everyone thinks...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
What is different from the [KERNEL][3.15.2011]EB16 Kernels?
Can we flash EC10 right over the EB16 Kernel?
Hotspot monitoring dummy kernel in both versions?
fitti28 said:
Can we flash EC10 right over the EB16 Kernel?
Hotspot monitoring dummy kernel in both versions?
Click to expand...
Click to collapse
I wiped both caches (dalvik+ regular) and then flashed right over EB16. No issues here.
I don't know about the monitoring dummy kernel but I'd be surprised if it wasn't in here.
MaskaMage said:
Same here, but since i'm still getting only 30hrs max on light usage I figure what the heck.... give it a try.
Click to expand...
Click to collapse
That's excellent! I never go easy, between texting, this place, and the web in general in lucky to get 17 or so hours lol.. I can charge all day at work or whenever I need if I'm not going to be home though..
Sent from my SCH-I500 using XDA App
fitti28 said:
What is different from the [KERNEL][3.15.2011]EB16 Kernels?
Can we flash EC10 right over the EB16 Kernel?
Hotspot monitoring dummy kernel in both versions?
Click to expand...
Click to collapse
You should be fine flashing over eb16 but adrynalyn would have said they have the dummy file if they did. Plus they are very new (ec10 is code for march 10th 2011), so I doubt they have any mods yet.
Sent from my SCH-I500 using XDA Premium App
They have the dummy file.
There, I made you honest.
Not that it matters, but for those interested Quadrant scores (voodoo):
1470, 1593, 1659, 1641
So don't use your precious Quadrants as a reason to not install this
So an average quadrant of 1600??
Sent from my SCH-I500 using XDA App
Flashed over SC 2.9.1 w/ stock EB01 kernel ... (non-voodoo here)
> Wifi still works! Already major improvement over the EB16s for me.
> *228/2 PRL update worked
> Still holding a wakelock on Gps Location Provider on boot, don't know if that has anything to do with the Kernel or not. Running a GPS app clears the lock just as it did before.
> Quadrant (non-voodoo): 946
So far so good. Will see how the battery is tomorrow.
cat /proc/version:
Linux version 2.6.32.9 ([email protected]) (gc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #1 Thu Mar 10 12:52:44 KST 2011
Many thanks as always Adrynalyne!!
kuronosan said:
A description of features would be nice, thanks!
Click to expand...
Click to collapse
fitti28 said:
What is different from the [KERNEL][3.15.2011]EB16 Kernels?
Click to expand...
Click to collapse
Description:
It does mostly everything EB16 does, in mostly the same way.
Unfortunately, Verizon isn't nice enough to include a changelog in their leaked beta internal release software.
There seems to be a misunderstanding about what happens when stock beta kernels are leaked. Maybe people are coming from devices that have custom compiled kernels, where the kernel dev actually helped modify the source code. In this case, yes, a dev will know most everything about said kernel.
This is not the case with leaked stock kernels (or any leaked data). The person who posts the leaked data is rarely an active part of development with the pre-compiled source code. They usually can only see exactly what you see: a compiled binary file. They usually install them on their phone, do some general testing to make sure basic functionality is intact, then they give them to the public.
That's where the public comes in. There are virtually infinite amounts of configurations on everyones' phones. The leaker usually only has one phone. If they are thorough, they MAY test it in a few different environments. Everyone has something unique about their set up or something that they really care about and notice about the behavior of their phone. However, no dev or even a small group of beta testers have the time or resources to test every single application/configuration/feature.
On top of this, the public wants immediate leaks ("You've been running something newer than me?! I WANT IT NOW"). They want the bleeding edge, without any of the bleeding edge problems. This creates a conflict between someone sitting on a leak for too long vs. thoroughly testing a kernel.
So if that's too long of a story, or I haven't made myself clear, I offer this summary: You are the beta testers. You are the changelog writers. You find out the description of features. The leaker merely leaks. Someone who actually cares a bit about public safety/performance (like Adryn) will take an additional step and optimize/mod/lightly test. But after that, the public is just one giant test group, and this is the way it is supposed to be.
If that scares anyone, they are welcome to wait a while and read through people's reports of their experiences with the kernel. If that is still too scary, then I hear that Verizon might be releasing this software on the 12th of Never.
And just in case I hurt anyone's feelings, I'm not singling you two out, and I'm not flaming you. This is a general public post aimed at addressing the overall concern behind this issue that comes up in every new dev thread. You both seem genuine and non-confrontational, but there is a wide range of people who come into these types of threads and whine and complain. So it's nearly guaranteed that someone else will enter and be like "OMG guize my phone iz broked how come you didnt say phone is broked???!!!!!" Then, everyone can point to this post.
GizmoDroid said:
Description:
It does mostly everything EB16 does, in mostly the same way.
Unfortunately, Verizon isn't nice enough to include a changelog in their leaked beta internal release software.
There seems to be a misunderstanding about what happens when stock beta kernels are leaked. Maybe people are coming from devices that have custom compiled kernels, where the kernel dev actually helped modify the source code. In this case, yes, a dev will know most everything about said kernel.
This is not the case with leaked stock kernels (or any leaked data). The person who posts the leaked data is rarely an active part of development with the pre-compiled source code. They usually can only see exactly what you see: a compiled binary file. They usually install them on their phone, do some general testing to make sure basic functionality is intact, then they give them to the public.
That's where the public comes in. There are virtually infinite amounts of configurations on everyones' phones. The leaker usually only has one phone. If they are thorough, they MAY test it in a few different environments. Everyone has something unique about their set up or something that they really care about and notice about the behavior of their phone. However, no dev or even a small group of beta testers have the time or resources to test every single application/configuration/feature.
On top of this, the public wants immediate leaks ("You've been running something newer than me?! I WANT IT NOW"). They want the bleeding edge, without any of the bleeding edge problems. This creates a conflict between someone sitting on a leak for too long vs. thoroughly testing a kernel.
So if that's too long of a story, or I haven't made myself clear, I offer this summary: You are the beta testers. You are the changelog writers. You find out the description of features. The leaker merely leaks. Someone who actually cares a bit about public safety/performance (like Adryn) will take an additional step and optimize/mod/lightly test. But after that, the public is just one giant test group, and this is the way it is supposed to be.
If that scares anyone, they are welcome to wait a while and read through people's reports of their experiences with the kernel. If that is still too scary, then I hear that Verizon might be releasing this software on the 12th of Never.
Click to expand...
Click to collapse
Very nicely said. But i think most of the time when people ask they are not trying to be rude or annoying. They are just not aware or hoping the person who leaked it might have the changelog as well.
Thanks adrynalyne...
Hi
I saw a post in the dev section titled "Source code (Android kernel, Ubuntu) now available".
I saw it here and downloaded it in case it disappears:
https://opensource.motorola.com/sf/sfmain/do/go/rel1543?selectedTab=files
What does this mean for the Atrix now? Is this anything special or won't help us at all? Will it be easier for the devs to crack the bootloader?
I'm still up in the air on whether to buy this phone or not and I'm just waiting to see if more development is made on it to choose.
Bell has lowered the price of the phone by $100 until March 31st so I would like to make my decision before that time. Nexus S and Incredible S are also coming to Bell in April so I'm not sure what to do! But Atrix with unlocked bootloader is like unlimited potential!
Thanks,
Elliott
I too would like to know as well what his could mean to the Atrix. ANy one care reply?
please.
Here are the words from another member at this thread Source code (Android kernel, Ubuntu) now available
ikenley
It will make it easier for tweaks and optimization to occur without access to the bootloader.
It could also mean that there is a possibility for custom Roms for the truly gifted Developers who can do it without modifying the Kernel. Has happened for the Milestone and is currently being undertaken for the Milestone 2 (Droid 2)
Click to expand...
Click to collapse
Thanks I saw that too...
Ahhh I want to wait until the Incredible S and even the Nexus S but the thought of having a dual core proc that is very fast is tempting to me...knowing that these devices only have single cores they're not as future proof...but neither is the Atrix if no development is done on it.
I'm fairly sure the source wont disappear for android that is... the kernel stuff maybe? I think android is GPL'd so it has to be released after modification as part of the license.
Starholdest said:
Thanks I saw that too...
Ahhh I want to wait until the Incredible S and even the Nexus S but the thought of having a dual core proc that is very fast is tempting to me...knowing that these devices only have single cores they're not as future proof...but neither is the Atrix if no development is done on it.
Click to expand...
Click to collapse
I'm in the same boat as you. Even in Canada.
But I guess I'm going to take the plunge and get this phone I'm getting it tomorrow or the day after.
My reasoning is that there will be a new nexus by the end of the year. But I agree fully to what you said above. I wish Motorola made the Nexus S. I wish it was the atrix but an official google device. If only that happened.
Source Code : OSHWT_U1_4.257.14
Starholdest said:
Hi
I saw a post in the dev section titled "Source code (Android kernel, Ubuntu) now available".
I saw it here and downloaded it in case it disappears:
https://opensource.motorola.com/sf/sfmain/do/go/rel1543?selectedTab=files
What does this mean for the Atrix now? Is this anything special or won't help us at all? Will it be easier for the devs to crack the bootloader?
I'm still up in the air on whether to buy this phone or not and I'm just waiting to see if more development is made on it to choose.
Bell has lowered the price of the phone by $100 until March 31st so I would like to make my decision before that time. Nexus S and Incredible S are also coming to Bell in April so I'm not sure what to do! But Atrix with unlocked bootloader is like unlimited potential!
Thanks,
Elliott
Click to expand...
Click to collapse
I see this is the source code for the original retail version (OLYFR_U4_1.2.6). I noticed on there website they also released the source code for what looks like the newest build they have out getting beta tested right now (OSHWT_U1_4.257.14) I might be wrong on that, but if it is, it seems Motorola might be getting easier to work with.
Motorola Website source code >> OSHWT_U1_4.257.14 <<
**Edit** Looks like this is the Source Code for the 'Atrix Webtop'. My bad...
We are starting a new thread as we enter a new phase of development.
We are beyond confident @ this point that we are where we need to be. We are now working on new init.rc and init.mapphone_cdma.rc that will be able to boot a cm7 atrix nightly.
As of now we only have aceoyame working on these and wish to solicit ideas from those who may be more experienced or who have a keen eye for the obvious.
We will be test flashing this first run shortly. Lets keep this thread clean. We are expecting only comments relating to the new .rc's or pointing out obvious shortcomings of our method.
Expect a test flash to be posted here shortly so others can try along.
So without further ado... here are the initial versions of the inits as modified by aceoyame..
init.mapphone_cdma.rc http://pastebin.com/N3CFNrBX
init.rc http://pastebin.com/KdpL6eKC
Help and comments are welcome...
If you apprecieate our work please hit THANKS on the appropriate post to let us know you guys care and to keep the thread un-cluttered. So far with the other threads it seems we only have about 20 or so users who are looking forward to this.
There is an excellent thread here.. http://forum.xda-developers.com/showthread.php?t=1372293 started by ashclepdia that can be used for speculation, thanks, etc...
Thanks again to the many users here for helping during the sbf flashing phase.. we may need your help again soon.
And last but not least thanks again to dragonzkiller for taking the time from his busy schedule to get us past the last hurtle.
So fu$king excited! Thanks guys!
Sent from my DROID X2 using XDA App
While reading init.mapphone_cdma.rc i noticed like 3 mount points referencing yaffs2. From what I understood, yaffs2 isn't supported by the X2. That was the only glaring thing I saw so far.
Keep up the great work
Edit: Everyone, Please lets keep on topic. If you have any questions or you want to say thanks please use this thread http://forum.xda-developers.com/showthread.php?t=1372293
We need to keep this topic clean for the sake of development.
Thanks
can someone explain whats this for and what it does?
Does it improve something?
Makes my phone faster?
Last longer?
Took better photo and video?
Better sound quality?
Tnx
raclimja said:
can someone explain whats this for and what it does?
Does it improve something?
Makes my phone faster?
Last longer?
Took better photo and video?
Better sound quality?
Tnx
Click to expand...
Click to collapse
Well in an EXTREMELY broad overview, all this work that these fine gentleman are doing will take the lid off the jar of the x2. And when they are finished we will finally be able to port over miui and cm7 and many other roms for the x2. I super excited for miui... love u ace
kpkacts238 said:
Well in an EXTREMELY broad overview, all this work that these fine gentleman are doing will take the lid off the jar of the x2. And when they are finished we will finally be able to port over miui and cm7 and many other roms for the x2. I super excited for miui... love u ace
Click to expand...
Click to collapse
STATUS UPDATE
Well after numerous tries with variations on those inits we still have no sucessfull boot. Gonna try again tomorrow with some new inits.
Gonna keep @ this till we get somewhere..
raclimja said:
Click to expand...
Click to collapse
Put the phone down and back away! Haha I'm extremely excited about this I'm desiring to see a cyan droid spinning on my boot screen I only wish I knew more so I could be of some help top make this happen like yesterday. Im very thankful to all that are making this happen this forum will explode once this comes out LIKE BOOM
To the ones who like to clutter the thread (over half of this thread isn't relevant) and you know who you are please just only hit the thanks button. Even the OP has a link for people who can't stay on topic. This is necessary
Sent from my DROID X2 using XDA App
This is me asking for all of the x2 devs to pitch in and help with CM now that we have 2nd init going. The thing holding us back atm is our init scripts, the one were using bombs out shortly before boot animation (before adb runs) any help would be awesome!
Do you have link to CM7 including 2nd init you are testing with?
I want to push it into my phone when I get a chance this weekend and see whether I can help.
Thanks.
Well its a new day.. and i begin my holliday break.. Gonna spend a good bit of it working on this. I have some new approaches I am going to try today. Hopfully we can get some good information from the upcoming tests.
Do you have link to CM7 including 2nd init you are testing with?
I want to push it into my phone when I get a chance this weekend and see whether I can help.
Thanks.
Click to expand...
Click to collapse
We intend to release a testing package shortly, once it is logging some sort of usefull data for us. In its current conditions it is not very informative. Rather then spending time getting people up to speed on it.. i am gonna try to get it to a point that it is more useful and self explanatory.
Ideally someone with more experience booting on second init devices will come along and give us a nudge to speed things up
In the meantime i have re-written our hijack to work along side our current X2 bootstap so that will save us some sbf time.
Hang in there.. We are getting close. Thanks for everyones support.
Probably should've posted this earlier, but I have a fairly powerful system. I could compile for you guys.
(I'd need to know what to install, since I haven't compiled a ROM before)
Sent from my DROID X2 using XDA App
mastafunk said:
Well its a new day.. and i begin my holliday break.. Gonna spend a good bit of it working on this. I have some new approaches I am going to try today. Hopfully we can get some good information from the upcoming tests.
We intend to release a testing package shortly, once it is logging some sort of usefull data for us. In its current conditions it is not very informative. Rather then spending time getting people up to speed on it.. i am gonna try to get it to a point that it is more useful and self explanatory.
Ideally someone with more experience booting on second init devices will come along and give us a nudge to speed things up
In the meantime i have re-written our hijack to work along side our current X2 bootstap so that will save us some sbf time.
Hang in there.. We are getting close. Thanks for everyones support.
Click to expand...
Click to collapse
So I take it the script I sent you over helped a lot? It's good to see that! If you're guys' init script works I can patch them into an actual CM7 build for the X2 (So that we can have a device config, and eventually nightlies for it).
fortune82 said:
Probably should've posted this earlier, but I have a fairly powerful system. I could compile for you guys.
(I'd need to know what to install, since I haven't compiled a ROM before)
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Don't worry about trying to compile anything yet. For a few reasons:
They're only patching an ATRIX build, not compiling yet
We don't have a full device setup for the X2 (i'm working on that now)
My computer is more than powerful enough to start releasing office DX2-Dev-Team betas from the repo, so don't worry about compiling yet
I will be on irc @ #X2-AOSP all night for the specific discussion of this thread.
So after a late night in IRC we managed to past 1 of the 2 hurdles we were trying to solve. Thanks to all that helped.
We were able to get some logcat action going!!
One more hurdle to pass and we are going to be VERY CLOSE.
Thanks again for those that were up late night working on this..
Which hurdle?
Tapped from my tweaked out DX2
Which hurdle?
Click to expand...
Click to collapse
answered in the post above yours..
mastafunk said:
We were able to get some logcat action going!!
Click to expand...
Click to collapse
Duh moment lol,
Tapped from my tweaked out DX2
is this the lockboot loader you guys are trying to crack?
If so, would this allow people to install or port ics? or copy the fix for blue tint on camera on droid 3?
Tnx
Hello XDA,
As you may or may not know, the official CM9 Project for the HTC Amaze has not died at all. It is being worked on by developers like +Max Krivonos.
I am making this post mainly in hope of educating myself in regards to the development process and things realted to it.
I've been following the project since the day they released the video of what Max got working on the Amaze already. Over the course of many months, cable detection, SD card, and "wifi" was fixed. There are only problems like GSM and the Camera left. Now I understand that Max has been busy with a lot of things considering his comments on his update posts seem to say that, but I am just curious as to how long does it really take to get things like that fixed?
My HTC Amaze is only my second Android device to my HTC Sensation which I only had for about 2 months. I have never really followed a project exclusively so I have no idea as to what the average timeframe is. However, my main concern is that Max "opened the repo", and a leak for the ICS update already came out. Shouldn't this help a lot? There are already many developers who are pushing out very clean ROMs based off of the leak, and there's only around 2 problems with more than 1 developer working on the issues. How long does it really take?
I didn't want to bother Max and other devs by asking them because I'm sure they have a lot of things on their hands anyways. Like I said before, this is not meant to be negative in any way. I simply want to learn about this, because I have been very eager waiting for CM9 like everyone else.
bri.kwong94 said:
Hello XDA,
As you may or may not know, the official CM9 Project for the HTC Amaze has not died at all. It is being worked on by developers like +Max Krivonos.
I am making this post mainly in hope of educating myself in regards to the development process and things realted to it.
I've been following the project since the day they released the video of what Max got working on the Amaze already. Over the course of many months, cable detection, SD card, and "wifi" was fixed. There are only problems like GSM and the Camera left. Now I understand that Max has been busy with a lot of things considering his comments on his update posts seem to say that, but I am just curious as to how long does it really take to get things like that fixed?
My HTC Amaze is only my second Android device to my HTC Sensation which I only had for about 2 months. I have never really followed a project exclusively so I have no idea as to what the average timeframe is. However, my main concern is that Max "opened the repo", and a leak for the ICS update already came out. Shouldn't this help a lot? There are already many developers who are pushing out very clean ROMs based off of the leak, and there's only around 2 problems with more than 1 developer working on the issues. How long does it really take?
I didn't want to bother Max and other devs by asking them because I'm sure they have a lot of things on their hands anyways. Like I said before, this is not meant to be negative in any way. I simply want to learn about this, because I have been very eager waiting for CM9 like everyone else.
Click to expand...
Click to collapse
i may be wrong so don't hold me to it. but i believe they need the wifi drivers which htc has not released yet to fully remove sense and get everything working. like i said i'm not positive but i think i read that somewhere else.
I think someone said Max quit working on it, and has posted his build online somewhere. As the poster above me said, it is because of the lack of source code atm. Once the ICS leak becomes "official", HTC should release the code. Keep in mind we're not really supposed to have this leak at the moment.
Max posted over a week ago that he was stopping his work on it as "he is just too busy" and released the repo.
jimczyz said:
Max posted over a week ago that he was stopping his work on it as "he is just too busy" and released the repo.
Click to expand...
Click to collapse
Gosh, I had no idea because I couldn't find anything like that on Google+
Who will be working on it? I guess another thing i'm trying to ask is if it's impossible to derive the source-code from the leak.
Well I definitely understand were your coming from but I think we just have to be patient like its hard trying to pull the drivers that are specifically made for the sense it takes time to try and rework those drivers for an aosp rom so I guess it would be wise to just be patient and wait to see what spot or xboarder is doing. I know xborarder is on android-dev.us and he's working with a couple of ppl on a Tom so just be patient man.
Sent from my HTC_Amaze_4G using xda premium
Sportsman is working on cm9 for us, we he has a alpha build already. Go to the development thread to see it.
Sportstar* I guess my autocorret got me.
Over 10000!!! You bet I am.
xndabox said:
Sportsman is working on cm9 for us, we he has a alpha build already. Go to the development thread to see it.
Over 10000!!! You bet I am.
Click to expand...
Click to collapse
Is it any good?
bri.kwong94 said:
Is it any good?
Click to expand...
Click to collapse
Its good only this the radios are broke so he is working know getting them fixed its a kernal this so we have to wait
Sent from my HTC_Amaze_4G using xda premium
ryuken11221 said:
Its good only this the radios are broke so he is working know getting them fixed its a kernal this so we have to wait
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Yeah I remember reading his thread a while back. Kernels rely on official releases? Can't someone build their own kernel? Does it take a long time?
bri.kwong94 said:
Yeah I remember reading his thread a while back. Kernels rely on official releases? Can't someone build their own kernel? Does it take a long time?
Click to expand...
Click to collapse
Well it all depends on how many devs are working on it so yes kernals are very difficult if you don't know what your doing or if your just new period but just keep looking out for it I think it will come sooner than you think
Sent from my HTC_Amaze_4G using xda premium
Hi everyone,
I am taking a poll to guage interest in the S4 Community for donating to and obtaining Carbonrom on the Verizon Galaxy S4.
CarbonRom is an aftermarket firmware based on the Android Open Source Project. I am not affiliated with any of the development of this rom. I am just a huge fan of their work and would love to see this rom come to our beloved S4. Having a device in hand to develop provides better success in providing a quality product. I am hoping this poll will help convince Carbonrom to purchase an S4 and begin development of it.
Here is a link to their goo.im developer page!
http://goo.im/devs/carbon
So what say ye!
UPDATE 5/28/13
There is now a secondary Carbon paypal link located here:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=T447T4BPVX2TY
THIS LINK IS STRICTLY FOR DONATIONS TO HELP FUND THE PURCHASE OF A VERIZON GALAXY S4 FOR TEAM CARBON.
This link will remain open until the goal (cost of a used S4) is reached. Should the goal not be obtained, or one is obtained by Team Carbon by another method, the monies will be refunded. All donations will be recorded and added to the OP, so there is full transparency on our way to the goal. Let's help Team Carbon get this device so our beloved S4 can get some lovin!
DONATION LIST:
1. David M. -$10
2. Thomas S -$8
Yeee
Sent from my Galaxy S4
I had some problems on the S3 and went to Liquid / I do think that the developer has some talent and even lended some support ($$) but eventually went to Liquid prior to selling the S3. On the Touchwiz side, ScottsRoms always worked for me.
Thanks for the support guys. If enough is raised, I'd definitely like to support this device. I'm convinced that like the s3, this is going to be as close as we get to a nexus on Verizon.
justreboot, i'm not sure when you had your issues, but 1.7 is very solid, and in my opinion the nightlies even more so. Either way, 4.3 is going to be a complete rebase. We've got some exciting ideas in store.
I would do dirty, unforgivable things for Carbon on the GS4.
jumpinghooligans said:
I would do dirty, unforgivable things for Carbon on the GS4.
Click to expand...
Click to collapse
I'll take that as a yes! Lol
Sent from my SCH-I545 using Tapatalk 2
jumpinghooligans said:
I would do dirty, unforgivable things for Carbon on the GS4.
Click to expand...
Click to collapse
Oh. Oh my.
Looking at loki, the new bootloader unlock, I can say we'll definitely need to have a test unit to dev with. I'm not willing to blind dev on such a nice device anyway - you end up with a substandard rom in my opinion - but this one in particular will need more attention, since the bootloader unlock isn't a released tool so much as something we would need to integrate into the build process. On the plus side, it looks like we'd be able to do so fairly easily so we should be able to still have nightlies and the like.
dg4prez said:
Oh. Oh my.
Looking at loki, the new bootloader unlock, I can say we'll definitely need to have a test unit to dev with. I'm not willing to blind dev on such a nice device anyway - you end up with a substandard rom in my opinion - but this one in particular will need more attention, since the bootloader unlock isn't a released tool so much as something we would need to integrate into the build process. On the plus side, it looks like we'd be able to do so fairly easily so we should be able to still have nightlies and the like.
Click to expand...
Click to collapse
Speaking of loki. I just was able to install twrp on my vzw s4 and made my first nandroid! Things are definitely progressing!
Sent from my SCH-I545 using Tapatalk 2
what do you think of the hardware itself? is it a worthwhile upgrade from the s3?
dg4prez said:
Oh. Oh my.
Looking at loki, the new bootloader unlock, I can say we'll definitely need to have a test unit to dev with. I'm not willing to blind dev on such a nice device anyway - you end up with a substandard rom in my opinion - but this one in particular will need more attention, since the bootloader unlock isn't a released tool so much as something we would need to integrate into the build process. On the plus side, it looks like we'd be able to do so fairly easily so we should be able to still have nightlies and the like.
Click to expand...
Click to collapse
Patching boot.img with Loki...
[+] loki_patch v1.2
[+] Detected target Verizon build JDQ39.I545VRUAMDK
[+] Output file written to /home/cordell/slim/out/target/product/jfltevzw/repack.d/loki/boot.img
MODVERSION: Slim-jfltevzw-4.2.2.build.5.6-UNOFFICIAL-20130525-1259
Zipping package...
Signing package...
Cleaning up...
Package complete: /home/cordell/slim/out/target/product/jfltevzw/Slim-jfltevzw-4.2.2.build.5.6-UNOFFICIAL-20130525-1259.zip
2c5c02174cdabc90db85e6365179c39a Slim-jfltevzw-4.2.2.build.5.6-UNOFFICIAL-20130525-1259.zip
pretty simple to integrate right into squishier...
cordell12 said:
Package complete: /home/cordell/slim/out/target/product/jfltevzw/Slim-jfltevzw-4.2.2.build.5.6-UNOFFICIAL-20130525-1259.zip
2c5c02174cdabc90db85e6365179c39a Slim-jfltevzw-4.2.2.build.5.6-UNOFFICIAL-20130525-1259.zip
Click to expand...
Click to collapse
So....when? That build was hours ago! Seriously glad to see the top flight devs get behind this!
brizey said:
So....when? That build was hours ago! Seriously glad to see the top flight devs get behind this!
Click to expand...
Click to collapse
dude i put a thread in Q n A asking for a tester, 107 people read the damn thing, but nobody took me up on it
cordell12 said:
dude i put a thread in Q n A asking for a tester, 107 people read the damn thing, but nobody took me up on it
Click to expand...
Click to collapse
Damn, I didnt see it or else I would have stepped up.
cordell12 said:
dude i put a thread in Q n A asking for a tester, 107 people read the damn thing, but nobody took me up on it
Click to expand...
Click to collapse
I almost never go in Q & A, lol. I am not sure I can do testing if it is alpha-ish or if you need technical feedback, but I can run a beta that boots through its paces...basically like UAT. Edit: and i can do logcats, heh.
Agreed. Still something that should be tested and used if it is to be properly maintained.
dg4prez said:
Agreed. Still something that should be tested and used if it is to be properly maintained.
Click to expand...
Click to collapse
was a reply to Cordell's earlier post about integrating it into squisher. Didn't notice the page 2. I suck at mobile browsing.
I used carbon on my note 2, i would definitely be interested.
We're cooking up some ridiculous new stuff. I think everyone is going to be VERY happy.
Carbon rom was probably the sexiest thing I ever ran on my bionic. I would donate a few bucks if it helped get us support for an S4.
by the way, the experimental halo releases tonight were not the interesting things i'm referring to...