ADVANCED USERS ONLY.
MAKE A BACKUP. THESE BUILDS COULD MAKE THE PHONE USELESS AS A PHONE!
SERIOUSLY. This is an unofficial CM7 build with cherry picks (from CM's Gerrit) of unfinished mods and/or broken code that is continually changing. New users should STAY AWAY FROM HERE. There is NO SUPPORT for this build, by myself or anyone else, so don't expect it. Do not file bug reports on the CM issue tracker from these builds. If you have to ask about compatibilities (which HBOOT version is needed, if A2SD scripts work, etc) you SHOULDN'T BE HERE. Don't PM me with silly questions, because they probably won't be answered.Rebased to CM source @ 8/1/11
I understand there is no support provided, and I will brick my phone by flashing this! OLD 3/31 BUILD
md5sum: 2d66e2e72e775ef736b0daa49ab22b6b
SHA1: dce98e947a08b52726fb0a2bf324e05ef2581b12
All credit goes to cyanogen & #teamdouche, I'm just a guy with a spare computer that learned how to compile and install Ubuntu without breaking Windows 8....
Credit to @RyanMacG for #Euroskank hosting!Some recent device related CM7 commits since last build:
None. At least on the official CM git.
Items from CM's Gerrit I have manually cherry-picked:
Not seeing any good ones. Look and suggest some!
If I stop using certain cherry picked commits all of a sudden, it's either: because they were merged, or the mod is based on older code than what is in CM currently and merge fails.
Known Bugs:
None apart from what the latest official slayher build has AFAIK
Build Status
Getting source for mecha related stuff and finding code to cherry pick. Should be built and uploaded by 9:30AM 8/2/11 CST
Please visit @cmsrc or CM's Gerrit for a complete list of commits.
Style of thread kanged from fitsnugly's Nexus One thread with permission.
So there are still a lot of issues with the gb build then? Or are they nearing a final working version? And by no means am i asking for an eta or anything just curious as to the progress being made.
Right now it runs. That's all I can say. But it is a lot better of a first build than other devices.... If I can get a working vendor built this weekend,we may see some progress(wifi working maybe....)
Sent from my ADR6400L using XDA Premium App
Same thing that was with my builds guys. Not worth it. Compile on your own for now if you really want this. There is no data, no calls, nothing. Until RIL is figured out, then CyanogenMod 7 is useless. I will be building full time once RIL is sorted but for now, these are useless other than having bragging rights. Not trying to discourage the OP but rather letting the masses know what's up.
otto888 said:
Right now it runs. That's all I can say. But it is a lot better of a first build than other devices.... If I can get a working vendor built this weekend,we may see some progress(wifi working maybe....)
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Might be able to get some help from @gearheadcustoms and @gridlock (Twitter) in fixing some of the issues you mentioned. A running CM7 nightly is progress. Sure this will be all fixed up within due time. Thanks to Euroskank, with corpses
ProTekk said:
Same thing that was with my builds guys. Not worth it. Compile on your own for now if you really want this. There is no data, no calls, nothing. Until RIL is figured out, then CyanogenMod 7 is useless. I will be building full time once RIL is sorted but for now, these are useless other than having bragging rights. Not trying to discourage the OP but rather letting the masses know what's up.
Click to expand...
Click to collapse
What's the issue with RIL?
i have a build from another dev that runs and i have gapps but no data so you cant sign in and wifi throws you into a bootloop...we needa kernel and i think we will finally have GB for the TB!
RIL: Radio Interface Layer.
The only reason that we have no data/text/calling/etc for CM 7. These threads are beating a dead horse. Wait until we have a working test build. I'll start building again once we have that.
The issue is, it's not open source.
ProTekk said:
RIL: Radio Interface Layer.
The only reason that we have no data/text/calling/etc for CM 7. These threads are beating a dead horse. Wait until we have a working test build. I'll start building again once we have that.
The issue is, it's not open source.
Click to expand...
Click to collapse
Right I thought RIL was made open source, guess not. But like all development, it starts with baby steps. Thank ProTekk
Man i cant wiat till yous figure this out...Im jonesin for sum GB
I think the title needs changing, and I really wish these builds were not posted if no one was willing to support them.
We end up getting the questions on irc, people don't read the disclaimers/warnings. The howto stealing sites (thats you A.T.) remove the warnings.
Maybe change title to "CM Builds - DATEHERE - NON-FUNCTIONAL" so less ppl will mess with it.
So we need to find the RIL files leaked? Or how do you get them?
andrew53517 said:
So we need to find the RIL files leaked? Or how do you get them?
Click to expand...
Click to collapse
You give the devs time to RE them, and write new ones.
jcase said:
You give the devs time to RE them, and write new ones.
Click to expand...
Click to collapse
Oh gotcha. So they have to make them compatible. That makes more sense. Now the closed source comment makes sense.
Thunderbolt Rooted!
This is absurd. Mods should lock this thread until we get a working rom.
No offense... but why? This thread is misleading, this thread will cause noobs too eff up their sh*t (despite your clearly stated warnings, they will not take them seriously), this thread is utterly useless because CM7 is not working, CM Parts are not working, RIL is not working...
Flashing this will make your phone useless (just like this thread).
Besides, there are already threads dedicated to compiling daily builds of CM7. Those threads have been put on hold (like they should) until CM7 is ready to be compiled. Even then, many people will flash extremely early builds of CM and wonder why certain functionality is missing or why x,y, and z does not work.
The underlying point is that this thread is going nowhere fast and will only cause problems. At least wait until the RIL is re-engineered and working.
Thank you.
Prrrooo sup d; ?
Sent from my ADR6400L using XDA Premium App
nerogold said:
Prrrooo sup d; ?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Not much back full time again
Sent from my ADR6400L using XDA Premium App
Good to see .anxious to flash cm7.
Sent from my ADR6400L using XDA Premium App
Related
I'm no longer working on this. I've tried, failed, and moved on. It seems that some other folks have had some success. Maybe they will continue on. Between work, family, college, etc. it's obvious that I'm getting nothing done on this.
This is an attempt at taking the work being done for the heroc here - http://forum.xda-developers.com/showthread.php?t=911828 and porting it to the Eris.
Honestly, I know enough to be dangerous and that's about it. The HeroC (sobe and those thanked in the post linked to above) folks and those upstream from there are doing most of the work. So, thank you to them.
If anyone would like to help, please do. That's the main reason that I'm posting this now. The kernel doesn't even compile at this point, much less boot. (It's hard to boot something that doesn't exist. )
Source: https://github.com/gnarlyc/cm-kernel
So far, here's what I've done.
1) forked sobe's repo
2) copied the heroc board files, renamed the copies to *desirec*, and changed all instances of HEROC to DESIREC and heroc to desirec inside the files
3) started removing heroc touchscreen stuff and adding desirec touchscreen stuff
Why am I doing this?
1) learn more about kernels
2) use some that programming knowledge that I'm supposedly learning in class
3) get an updated kernel for the Eris
very nice, i do wish you luck.
Very good. Glad to see you working on this.
Powered by: GSB CM7
For those who don't follow the front page news, the Heroc 2.6.35 Kernel is now good enough to be considered a Release Candidate. Same link as in first post.
roirraW "edor" ehT said:
For those who don't follow the front page news, the Heroc 2.6.35 Kernel is now good enough to be considered a Release Candidate. Same link as in first post.
Click to expand...
Click to collapse
Those guys are awesome. I have an exam on Wednesday and homework due on Sunday, but I'll take a look as soon as I can. If someone else wants to give it a shot, it won't hurt my feelings.
Got any screenshots ?
Can I run Flash on this ?
hallstevenson said:
Got any screenshots ?
Can I run Flash on this ?
Click to expand...
Click to collapse
ROFL!!!
I said ROFL, dangit! (10 char...)
hallstevenson said:
Got any screenshots ?
Can I run Flash on this ?
Click to expand...
Click to collapse
Reboot your phone and look at the splash screen. Now imagine seeing your phone stuck right there. There's your screenshot!
I'll send you a flashable zip, if you want it.
Flash doesn't work because they don't want to support our proccesors architecture.
Sent from my GSBv2.2-ERIS using XDA App
It IS Lupus said:
Flash doesn't work because they don't want to support our proccesors architecture.
Sent from my GSBv2.2-ERIS using XDA App
Click to expand...
Click to collapse
They were joking.
roirraW "edor" ehT said:
They were joking.
Click to expand...
Click to collapse
I was half asleep when i posted. So I didn't realize that.
gnarlyc said:
Reboot your phone and look at the splash screen. Now imagine seeing your phone stuck right there. There's your screenshot!
I'll send you a flashable zip, if you want it.
Click to expand...
Click to collapse
This worked I hav e flash now
Sent from my ADR6400L using XDA App
tazzpatriot said:
This worked I hav e flash now
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
10 char...
Sent from my FroyoEris using XDA Premium App
Any work still going on n with this?
This is what we would need to port over the new Hero Sensable Gingerbread right? Man if we could get this working, I would be about the happiest guy in the world
My final exam is on Wednesday of next week. So, I can promise that I will put much more effort into after that. I can't promise to get it working, but I'll definitely put a lot more time in. As I said before, if anyone wants to jump in and help, feel free. There's already one other person (breber) helping, but I think he's been in the same boat as me. So... Hopefully, he'll be able to help more after classes are over too.
Kernel updates are pretty much the only updates I ever care about.
Just an update. This hasn't been worked on as much as I hoped. However, I've had help from breber. Actually, he's made much more progress than I did. The kernel not only compiles, but it boots too! As soon as we can get the touchscreen working, it might even be usable.
Here's the current source.
https://github.com/breber/cm-kernel
If anyone else wants to take a stab at it, feel free. Our time is somewhat limited.
I've played around with adding the capella 3602 stuff back in, but it didn't seem to help with the touchscreen issue. The TS is one of the few components that are different between the HeroC and Eris.
gnarlyc said:
Just an update. This hasn't been worked on as much as I hoped. However, I've had help from breber. Actually, he's made much more progress than I did. The kernel not only compiles, but it boots too! As soon as we can get the touchscreen working, it might even be usable.
Here's the current source.
https://github.com/breber/cm-kernel
If anyone else wants to take a stab at it, feel free. Our time is somewhat limited.
I've played around with adding the capella 3602 stuff back in, but it didn't seem to help with the touchscreen issue. The TS is one of the few components that are different between the HeroC and Eris.
Click to expand...
Click to collapse
So your moving on from this?
http://forum.xda-developers.com/showthread.php?t=1073930 - the original thread
https://github.com/doixanh/X8Features - the github source
Are there any DEVs willing to compile this in there ROM (lookin at you ACS) lol I have wanted this so badly, but am unwilling to take the performance hit that ee03 causes compared to SRF 1.1.1.
Dont take the dive to gb
Even though the devs try hard some things just cannot be
Like taking the crap**** gb leak and turn it into gold
Sent from my Nexus S 4G using XDA Premium App
gtuansdiamm said:
Dont take the dive to gb
Even though the devs try hard so things just cannot be
Like taking the crap**** gb leak and turn it into gold
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
This makes no sense? The developer dioxanh got this to work perfectly on froyo and put the source on github for other DEVS to compile for there ROMs. It can be because he has done it
I meant that the gb link is über slow and it probably wont get better till the next leak
Sent from my Nexus S 4G using XDA Premium App
All the Epic ROM's with the exception of MIUI and CM7 are NOT compiled from source code.
They are merely customizations and hacking based off of the compiled libraries. It would likely be impossible to reverse engineer this into any of the ROM's. It would need to be done in Smali... if that's even possible..
Syndicate is in fact compiled from source if I'm not mistaken, that's why they always wait for a few days source leaks to release.
TheDub said:
They are merely customizations and hacking based off of the compiled libraries. It would likely be impossible to reverse engineer this into any of the ROM's. It would need to be done in Smali... if that's even possible..
Click to expand...
Click to collapse
Look all I know is that this DEV made it possible to implement into custom ROMs for froyo. It says so clearly in the forum I posted if you had bothered to read it at all.
Actually read it .. Good work on dev for doing this! .. But it must be cooked into roms only and only works for a few roms
Sent from my SPH-D700 using XDA Premium App
I know Impaler and Mystery and others are busy workin on 1.2, and It would be cool if they lookd into implementing this into it.
jspsuperman said:
Look all I know is that this DEV made it possible to implement into custom ROMs for froyo. It says so clearly in the forum I posted if you had bothered to read it at all.
Click to expand...
Click to collapse
I did "bother" to read it. It's Froyo source code to implement this feature. We don't have 100% of Samsungs source code for Froyo/Eclair/Gingerbread, they don't release it.
We only receive the kernel source code. This could only be baked into a Froyo based AOSP ROM which other then the very dated CM6 we do not have.
The kernel source code and the entire operating system (AOSP) are two completely different things, and the code to make this work isn't in the Kernel it's in the Framework.
ACS's ROM is not AOSP.
AOSP: Android Open Source Project - I'm using it to reference having the entire operating system's source code available, not just the kernel.
I wasnt aware that only the kernal source was released. What a bummer if a sony X8 can do this but our epic cant without gingerbread
Yeah just the way it is...
Most phones don't have 100% complete source drops, the popular two phones that do of course are the Nexus One and Nexus S, this is why the Nexus phones so easily get ROM's like CyanogenMod working. With the Epic and Galaxy S developers are forced to "rewrite" lots of code to get things interfacing with the Samsung proprietary drivers properly.
If we had 100% of the source code I don't doubt ROM's would be very different today, there would have also been a official CyanogenMod by now I'm sure.
If you want to see for yourself what Samsung releases you can go to:
https://opensource.samsung.com/
Do a search for I9000 for example and download one of the releases (I looked at I-9000-Opensource.zip)
You will see a few files in there.. one labeled kernel, the other eclair.
The kernel one is obvious, the eclair one contains only the hardware libraries.
So unfortunately, this really isn't possible in any of our existing Froyo ROM's, except CM6.
PS: I9000 is the model number for the European Galaxy S.
jspsuperman said:
I wasnt aware that only the kernal source was released. What a bummer if a sony X8 can do this but our epic cant without gingerbread
Click to expand...
Click to collapse
Don't mess with TheDub
qbking77 said:
Don't mess with TheDub
Click to expand...
Click to collapse
Apparantly lol That sucks but I guess gingerbread will be official soon enough then we will have somthin else kickass from U ACS folk lol
063_XOBX said:
Syndicate is in fact compiled from source if I'm not mistaken, that's why they always wait for a few days source leaks to release.
Click to expand...
Click to collapse
This is not true, just so you know.
Sent from my SPH-D700 using XDA App
Thread was created in order to move discussions from this development thread here http://forum.xda-developers.com/showthread.php?t=1054254 to this general thread since our conversations had little to do about contributing to Development. As always keep it clean, no flaming, etc.
Sent from my SPH-D700 using XDA App
Can't wait for a gb source code so I can use miui at its greatest
Sent from my super awesomely amazing
Generation
Unsubdued
Nuclear
Drive
Assault
Module
gtuansdiamm said:
Can't wait for a gb source code so I can use miui at its greatest
Sent from my super awesomely amazing
Generation
Unsubdued
Nuclear
Drive
Assault
Module
Click to expand...
Click to collapse
I think everyone is waiting for MIUI and CM7. Can't seem to get here soon enough lol we seem to have some Devs looking into making the current MIUI version we have more "useable" hopefully they can get us a descent release where the basic features are stable enough to be use as a 'daily driver' if not, GB will be here shortly in a couple weeks n we'll get things rolling
Sent from my SPH-D700 using XDA App
Miui +epic=miepicui
Sent from my SPH-D700 using XDA App
I'm currently using miui 1.3.5. The only problem for me is battery drain and some other minor things.
Sent from my Samsung-SPH-D700 using Tapatalk
lynyrd65 said:
I'm currently using miui 1.3.5. The only problem for me is battery drain and some other minor things.
Sent from my Samsung-SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Really? For me battery was great, but bad 3G and no 4G killed it for me. If I would have at least had ok 3G, I would keep it, but otherwise when I leave my house, I have no internet, which is not the case on stock (or close) Roms.
The MIUI we have has great features and all, but let's face it, it's not the most attractive looking rom.
I can't wait until we have the newest MIUI, I've used it on my old Evo and trust me it blows away the one we have now. You guys are going to be so happy once we have it.
I'd use it as my daily and never change it EVER if we had it.
Unless the sense port was finished, in that case I would use that. But otherwise new MIUI is great.
erikkWTF said:
The MIUI we have has great features and all, but let's face it, it's not the most attractive looking rom.
I can't wait until we have the newest MIUI, I've used it on my old Evo and trust me it blows away the one we have now. You guys are going to be so happy once we have it.
I'd use it as my daily and never change it EVER if we had it.
Unless the sense port was finished, in that case I would use that. But otherwise new MIUI is great.
Click to expand...
Click to collapse
It's not until you use theme manager to download themes. You can customize boot animation, wallpaper, icons, ringtones, with one click. Also, if you don't like those, you can get newer ones online at miuithemes.com, but those may not use all their features on froyo.
I'm really feeling the excitement build in the Epic community and I think its great. Things have been much more positive around here lately as well. I can't wait to try out miui and cm7 after GB source comes out, and hopefully be able to help out finding bugs and testing.
A couple months ago I was ready to ditch this phone for just about anything (even considered downgrading to an EVO) but now I think I'll be happily running the Epic for a good while to come.
For anyone who is fed up waiting for the latest and greatest, try running SFR 1.2 (froyo) with clean kernel. I am very nit picky about my daily driver and this has been flawless. Performance is much better than stock, and everything works so well I just don't feel rushed to upgrade (phone or OS) like I used to.
Right now I'm using marcusants ACS Bamboozle, but will definitely switch when (maybe if) we get GB Miui.
I have also seen an improvement in our community. The useless flaming and bickering has been toned down to a minimum, if not, just completely stopped. Its great to finally be one big happy community like before. I can say SRF 1.2 is def my favaorite ROM and daily driver at the moment, but I'm definetly looking towards CM7 and MIUI. It'll still be a while to get some stable builds done even after source is released so I hope SRF 1.3 is dropped a bit before then so I can totally leave froyo with a bang! and according to qbking77 in the SRF 1.2 development thread, SRF 1.3 is still being worked on, as well as a possible new kernel thanks to their hard work, it'll be a lot easier to wait a bit longer for MIUI/CM7 lol
Sent from my SPH-D700 using XDA App
MIUI just looks like a Chinese iOS knockoff. :\
Since I'm also probably going to be waiting for the next Nexus (if I can resist the SGSII) I'm also looking forward to CM7 and MIUI. I've never used either before or any iteration, but the reports on them are always great.
I'm gonna go to CM7 and set everything up, make a Nandroid Backup, then go to MIUI and set everything up with a Nandroid Backup after, because those are gonna be the only 2 ROMs I'll use.
Do any of you know how to build a kernel? I've made files to test, but don't know how to compile. I combined some files from GS CM Kernel and Epic stock kernel. Just need to know how to make a zimage. I can post the files if you want to compile.
xboxfanj said:
Do any of you know how to build a kernel? I've made files to test, but don't know how to compile. I combined some files from GS CM Kernel and Epic stock kernel. Just need to know how to make a zimage. I can post the files if you want to compile.
Click to expand...
Click to collapse
You might want to PM thomasskull666 or Rodderik for that. They're the "kernel gurus". Just make sure u know what your doing and dnt hard brick ur phone. I wish I could help more but so far I'm looking for an extra computer to load a linux only OS since I hate to dual boot. Also, I haven't read too much into compiling yet so no help there either :\ sorry
Sent from my SPH-D700 using XDA App
xboxfanj said:
Do any of you know how to build a kernel? I've made files to test, but don't know how to compile. I combined some files from GS CM Kernel and Epic stock kernel. Just need to know how to make a zimage. I can post the files if you want to compile.
Click to expand...
Click to collapse
Crack one open in notepad and see
Sent from my SPH-D700 using Tapatalk
Testers needed for a new AOSP Build.
Based off AdamG's DevNull build.
I do not have this device so I am doing this blind folded.
I only need 2 Testers
Sent from my PG86100 using xda premium
may you be more precised please, and give a link to the ROM ?
I'll happily test this for you as I much prefer generic Android to a manufacturer version. I ended up sticking with Nexus 1 builds on my HD2 and I miss it.
One thing I would say though, I did try installing the DevNull build and my phone never booted, so I ended up restoring my backup. I never looked into it any further, so if you've based this quite heavily on his build then I may be of no use to you.
Feel free to PM me if you want to keep the details off the public forum for now.
I would be interested if you can provide a change log or is it devnull themed? A bit more info would be great.
@John noticed your from Northampton too
daleski75 said:
@John noticed your from Northampton too
Click to expand...
Click to collapse
Yes mate - small world (or big xda!)
I'll test for you
hi
was the development for the slim ics port stopped? because the thread just vanished and i can't find it again. Am i too stupid or did somebody really delete it?
the thread about the sd version is still there: http://forum.xda-developers.com/showthread.php?t=1763112
the thread was here: http://forum.xda-developers.com/showthread.php?t=1759815
cu
I haven't been following it lately, but I saw a dispute whether the developer should have made a slim version of an already available ROM or not. So it is likely that the original ROM developer asked to cease the slim port and sought a thread closure.
Marvlesz said:
I haven't been following it lately, but I saw a dispute whether the developer should have made a slim version of an already available ROM or not. So it is likely that the original ROM developer asked to cease the slim port and sought a thread closure.
Click to expand...
Click to collapse
if the thread would have been simply closed like others i would agree, but this thread vanished completely. the dispute was on the first two pages. how can a rom-cooker demand that his android rom doesn't get ported? credits where given where they where due and apart of that aosp is oss.
Screemi said:
if the thread would have been simply closed like others i would agree, but this thread vanished completely. the dispute was on the first two pages. how can a rom-cooker demand that his android rom doesn't get ported? credits where given where they where due and apart of that aosp is oss.
Click to expand...
Click to collapse
Fully agree wirh you.
What was wrong with porting rom and giving credits to original Dev?
For me it was the fastest, smallest ics rom for hd2.
Sent from my SlimICS using xda premium
Post deleted. But i have links. Long live Google Cache
From slim ics site:
"Supported Devices here, no extra devices for now ( and NO PORTS of Slim ICS)"
"http://source.android.com New versions will also be announced through this site."
"Fully built from AOSP sources with some cherry picks from CM and AOKP team, Easy to customize features (thanks to AOKP team)"
Atm trying to be calm but... Lets just say it piss me off this kind of thing.
This guy need to look at Miui team, they have right set of mind.
Sent from my SlimICS using xda premium
Where is @zorua BTW? Has him have deleted too?
Traukoman said:
Where is @zorua BTW? Has him have deleted too?
Click to expand...
Click to collapse
Hope not!
It would be nice if a moderator (or someone that knows and is objective about it) can tell us what happened. If it ended up in a heated argument I wouldn't want someone telling us only his half of the story - but I really would like to know.
DeeinSouthAfrica said:
Hope not!
It would be nice if a moderator (or someone that knows and is objective about it) can tell us what happened. If it ended up in a heated argument I wouldn't want someone telling us only his half of the story - but I really would like to know.
Click to expand...
Click to collapse
Same here. Btw dev of original Slim ics rom seems had allergy reaction on porting his rom. As i allready posted. What i dont get it, how in open source community is it possible? Isn't whole point to be open, share with ofc giving credits to ppl which contributed?
Sent from my SlimICS using xda premium
maneken25 said:
Same here. Btw dev of original Slim ics rom seems had allergy reaction on porting his rom. As i allready posted. What i dont get it, how in open source community is it possible? Isn't whole point to be open, share with ofc giving credits to ppl which contributed?
Sent from my SlimICS using xda premium
Click to expand...
Click to collapse
If it was pulled by a moderator upon request personally I think it's within reason. The thread wasn't stated as being Unofficial, which it should have been, and with a system partition of 130MB it can hardly even be called a slim OS (other full fat ROMs are 150); nevermind comparable to SlimICS which are half that size (54 - 70). And besides the last post I seen on the thread was from the OP who said he wasn't happy with the build and wanted to change the ROM he was porting from, and it was only an alpha.
On a similar note, if a small ICS rom is to come along, I personally thing it would be benificial if we could utilise squashfs. This would require kernel support, the toggles are there to turn on squashfs support in dorimanx, but it may require a module from somewhere, I'll PM dori tomorrow concerning this unless someone here know if squash can/can't be used with our bootloaders / device. Only problem I can for see is in module compatibility, and if it works should allow for smaller versions of our current ROMs.
Your position is legit but non of the slim ics roms include gapps and trebucht as launcher. It was comparable to other full roms with about 50-100mb less memory. And for me it's totally legit to port a ROM from one to an other device if you give credit and state which Tom was ported. Would be different if there was some own coding for tools and drivers was done. Don't distribute my tools without my permission is different than don't share something i picked up somewhere else and used it for my own work. That's not how the gold licence works.
Sent from my HTC HD2 using xda app-developers app
HypoTurtle said:
If it was pulled by a moderator upon request personally I think it's within reason. The thread wasn't stated as being Unofficial, which it should have been, and with a system partition of 130MB it can hardly even be called a slim OS (other full fat ROMs are 150); nevermind comparable to SlimICS which are half that size (54 - 70). And besides the last post I seen on the thread was from the OP who said he wasn't happy with the build and wanted to change the ROM he was porting from, and it was only an alpha.
On a similar note, if a small ICS rom is to come along, I personally thing it would be benificial if we could utilise squashfs. This would require kernel support, the toggles are there to turn on squashfs support in dorimanx, but it may require a module from somewhere, I'll PM dori tomorrow concerning this unless someone here know if squash can/can't be used with our bootloaders / device. Only problem I can for see is in module compatibility, and if it works should allow for smaller versions of our current ROMs.
Click to expand...
Click to collapse
Most of ics roms are from 150 to 220m(miui).
This rom without gapps was around 85mb.
I have atm slim ics with trimmed gapps and some media files that fit in less then 120mb, if i compare to other ics rom which i used as trimmet down, they were from 140 to 190mb imho it was really Slim version of rom
Edit: Maybe it was beta version but worked without problems and it was the fastest ics i tried and i tried them alot
Sent from my SlimICS using xda premium
maneken25 said:
Most of ics roms are from 150 to 220m(miui).
This rom without gapps was around 85mb.
I have atm slim ics with trimmed gapps and some media files that fit in less then 120mb, if i compare to other ics rom which i used as trimmet down, they were from 140 to 190mb imho it was really Slim version of rom
Edit: Maybe it was beta version but worked without problems and it was the fastest ics i tried and i tried them alot
Sent from my SlimICS using xda premium
Click to expand...
Click to collapse
Fair point, the last zip I downloaded had a system folder of 130MB thats where I got my sizes from,have had a play with squashfs and have shrunk this down from 130 to 92MB. Will try tomorrow to get a kernel to compile properly and see if squash works here. Haven't tried slim myself, currently running PA and can't see how it can be faster. Have you had any issues when trying to make a call /pressing the call button?
Screemi said:
Your position is legit but non of the slim ics roms include gapps and trebucht as launcher. It was comparable to other full roms with about 50-100mb less memory. And for me it's totally legit to port a Tom from one to an other device if you give credit and state which Tom was ported. Would be different if there was some own coding for tools and drivers was done. Don't distribute my tools without my permission is different than don't share something i picked up somewhere else and used it for my own work. That's not how the gold licence works.
Sent from my HTC HD2 using xda app-developers app
Click to expand...
Click to collapse
Tom who?
The thread is not in the trash-can subforum (Confirmed)
It was serious then
+ Que PPC said:
Tom who?
The thread is not in the trash-can subforum (Confirmed)
It was serious then
Click to expand...
Click to collapse
Tom is dictionary suggestion for ROM, it happens often to my SwiftKey keyboard also
Sent from my SlimICS using xda premium
HypoTurtle said:
Fair point, the last zip I downloaded had a system folder of 130MB thats where I got my sizes from,have had a play with squashfs and have shrunk this down from 130 to 92MB. Will try tomorrow to get a kernel to compile properly and see if squash works here. Haven't tried slim myself, currently running PA and can't see how it can be faster. Have you had any issues when trying to make a call /pressing the call button?
Click to expand...
Click to collapse
If i don't consider common issues which have most of ics hd2, like sometimes funky memory management which on heavy duty can produce little problems, there aren't any un ordinary problem.
Calls working very snappy.
In fact whole rom is fast, responsive, low battery consumption, apps which i tested working correctly even Ted app.
Sent from my SlimICS using xda premium
+ Que PPC said:
Tom who?
Click to expand...
Click to collapse
don't you know Tom the damnautocorrection cat?
Mmhh, not even in the trash sub and the user got deleted as well? Must have been really serious. Would love to know what happened.
Sent from my HTC HD2 using xda app-developers app
Screemi said:
don't you know Tom the damnautocorrection cat?
Mmhh, not even in the trash sub and the user got deleted as well? Must have been really serious. Would love to know what happened.
Sent from my HTC HD2 using xda app-developers app
Click to expand...
Click to collapse
he didnt get deleted http://forum.xda-developers.com/member.php?u=4212197
HypoTurtle said:
Haven't tried slim myself, currently running PA and can't see how it can be faster.
Click to expand...
Click to collapse
I tried both, as well as some other ICS rom and believe me, it's faster than any other 4.0.4 around here. In fact I'm using it as my daily and I find it excellent, such a shame the thread has been deleted.
Hi ppl, sorry for the silence on this. Apparently there was a problem with permissions for Zorua's thread, I asked the moderators advice on the future of my thread, and it was decided to close my thread also. I have no problem with this decision.
Sorry for any inconvenience to anybody caused by this episode.
It is a great shame though, it was a really nice build.