Related
New ROMs out every day, you gotta love the "original" ones, that come usually besides the only useful rooting with A2SD+ (buggy), deodexed (space wasting) and "bash".
So, why the heck does anyone need bash? The normal user definitely does not. The advanced user (read, the one that can use adb) may occasionally feel lazy to type a command twice and uses command completion/repetition. But hey, don't we already have ash in busybox? What the heck do we need bash for? It eats some 2 MB of precious memory, without adding any real value?!
So please educate me, why does anyone adds bash into their ROMs (besides the other crap)?
Custom scripts may rely on features that bash offers that the default shell doesn't. That makes it vital for those. And Linux memory handling isn't as simple as adding up executable sizes.
teppic74 said:
Custom scripts may rely on features that bash offers that the default shell doesn't. That makes it vital for those. And Linux memory handling isn't as simple as adding up executable sizes.
Click to expand...
Click to collapse
I have yet to see a script that would rely upon bash and not running with a standard sh. And if so, someone should fix the script. So no, that's not an acceptable explanation .
I don't want to go into a holy war here, it just looks pretty silly to me that everybody who manages to start a kitchen has to press every button that is there. Without understanding what it does.
My point is, if you want to make an in any way called "official" ROM, I could go with rooting and perhaps busybox, but that's it. Anything else is unnecessary garbage. And too many cooks spoil he broth as we see here, once again.
When I wrote my downgrade tool I had to use bash explicitly to get it to work transparently on a Mac, since the default shell (sh) on OS X behaves differently. To say there's never a problem with compatibility between shells is untrue.
teppic74 said:
When I wrote my downgrade tool I had to use bash explicitly to get it to work transparently on a Mac, since the default shell (sh) on OS X behaves differently. To say there's never a problem with compatibility between shells is untrue.
Click to expand...
Click to collapse
AFAIK sh is Unix standard since the 70's or so . Same as vi.
mmaacc said:
It eats some 2 MB of precious memory
Click to expand...
Click to collapse
where did this number come from?
mmaacc said:
AFAIK sh is Unix standard since the 70's or so . Same as vi.
Click to expand...
Click to collapse
/bin/sh is not the original shell on any system, nor is vi. /bin/sh on one machine may behave differently on another. It may behave the same as bash, or it may not.
snq- said:
where did this number come from?
Click to expand...
Click to collapse
Filesize of bash
teppic74 said:
/bin/sh is not the original shell on any system, nor is vi. /bin/sh on one machine may behave differently on another. It may behave the same as bash, or it may not.
Click to expand...
Click to collapse
The reason is sh != sh. Which may be bash or zsh or csh. Depending on the OS. Still the original sh should be there if needed by a script. Again, same as vi != vim . We all understand that.
The reason for my posting was that I get really annoyed from the "original" ROMs that are already compromised by lots of "press button" kitchen changes. It just causes a lot of additional and unnecessary work to reverse such changes if you want to use a particular new version, that someone puts out as "original" messed up version as it happened a number of times recently.
mmaacc said:
Filesize of bash
Click to expand...
Click to collapse
oh please
speaking of file sizes though, linking bash against bionic is A Good Idea (tm):
Code:
$ stat -c %s `which bash`
397620
snq- said:
oh please
speaking of file sizes though, linking bash against bionic is A Good Idea (tm):
Code:
$ stat -c %s `which bash`
397620
Click to expand...
Click to collapse
Perhaps that is a dynamically linked version. If you look at the random cooked ROMs bash comes with 2.5MB+ of size (as in dsixda kitchen). And I consider this waste of precious resources.
Without trying to sound too harsh.. choose a different Rom or cook your own.
Each cook personalises there Rom to their needs although I kinda see where your coming from its unfair to criticise the very people who spend their own time customising time for our consumption.
Sent from my HTC Desire using XDA App
rosebud said:
Without trying to sound too harsh.. choose a different Rom or cook your own.
Each cook personalises there Rom to their needs although I kinda see where your coming from its unfair to criticise the very people who spend their own time customising time for our consumption.
Click to expand...
Click to collapse
You need to read the posting again. I'm not talking about people making customized ROMs. I'm just getting sick of all the wannabie "official" ones who don't know what buttons they press. And yes, I made my own .
i see your point, and i agree with you, but 2mb is next to nothing, i don't see what the big deal is.
why's your issue with bash? why not hate all the people who add wireless tethering or vpn support just because you don't use it.
cgrec92 said:
i see your point, and i agree with you, but 2mb is next to nothing, i don't see what the big deal is.
why's your issue with bash? why not hate all the people who add wireless tethering or vpn support just because you don't use it.
Click to expand...
Click to collapse
I do
Blabla...thing is, post an official ROM, keep it official. I can and do accept rooting, and busybox, for a so called "official" ROM, everything else, down the drain.
even rooting a rom or installing busybox makes it NOT official.
adding an APK or updating an existing APK makes it NOT official.
i dont know why you have such a big mouth and YOU are *defending* official ROMs throughout XDA, now you must be VERY bored to have started all this but seriously go find something constructive to do.
Why don't you just make an anti-social networking rant and start a thread protesting the file size of Facebook.apk
cgrec92 said:
even rooting a rom or installing busybox makes it NOT official.
adding an APK or updating an existing APK makes it NOT official.
i dont know why you have such a big mouth and YOU are *defending* official ROMs throughout XDA, now you must be VERY bored to have started all this but seriously go find something constructive to do.
Click to expand...
Click to collapse
I don't know what your problem is, I stated mine clearly.
Rooting a ROM is necessary to flash it and get it working properly. Busybox adds necessary features. That is as far as I could go under the tag "official" and to keep that ROM usable as a basis for other devs.
I can not accept other "press button but don't know what this is" kitchen stuff that most recent so called "official" ROMs had. Like bash or A2SD+.
And if you did not get the message by now, I made MacLite which is one of the most efficient ROMs available.
Thanks for your interest
mmaacc said:
I don't know what your problem is, I stated mine clearly.
Rooting a ROM is necessary to flash it and get it working properly. Busybox adds necessary features. That is as far as I could go under the tag "official" and to keep that ROM usable as a basis for other devs.
I can not accept other "press button but don't know what this is" kitchen stuff that most recent so called "official" ROMs had. Like bash or A2SD+.
And if you did not get the message by now, I made MacLite which is one of the most efficient ROMs available.
Thanks for your interest
Click to expand...
Click to collapse
Ooh well i'm sure everyone here is sorry they can't match up to your 'OFFICIAL ROM' standards...
Busybox is as far as you'll go..... wow..
So the message was that you made MacLite? not about Bash but you just wanted to tell the world you made a ROM, and by made you copied an 'OFFICIAL ROM', removed a few things and posted it as your own? Thank you for MAKING a great ROM!
Thread moved to Q&A.
cgrec92 said:
So the message was that you made MacLite?
Click to expand...
Click to collapse
Read the posting again. Timewaster.
Just curious since CM has this function... Being a new Amon-Ra user this seems like something that would make the users life much easier. I previously has all my custom things in a folder on my sd called EvoDev and roms in one folder, zip mods in another, etc.... I now must leave all my stuff on root of sd or move back and forth with a file manager if I want to do anything.
I'm not mad or anything, just curious as to why Amon-Ra doesn't have this ability. Anyone know?
P.S. - Sorry if this is wrong section but I didn't view it as a general Q&A... It was more specific to a function of a program that is used daily in development so I thought this would be the appropriate place to ask.
leenypost said:
Just curious since CM has this function... Being a new Amon-Ra user this seems like something that would make the users life much easier. I previously has all my custom things in a folder on my sd called EvoDev and roms in one folder, zip mods in another, etc.... I now must leave all my stuff on root of sd or move back and forth with a file manager if I want to do anything.
I'm not mad or anything, just curious as to why Amon-Ra doesn't have this ability. Anyone know?
Click to expand...
Click to collapse
i wish it had this funcion. this is the only reason why i do not use it.
because he hasn't implemented, 2.0 is on the horizon, there is potential its going to be implemented, however something so simple can easliy be worked around
2.0 can but amon-ra hasn't ported it over to the evo yet.
Sent from my PC36100 using XDA App
xlGmanlx said:
however something so simple can easliy be worked around
Click to expand...
Click to collapse
Are you saying there is a way to make it see past the root? I can't figure it out. Please elaborate..
If you are just saying it is easy to work around as in it is easy to just move my files to root of sd.... Well sure, it isn't hard to do..... but it does take more time.... And say you are doing something complicated requiring flashing a few things one after the other... Well... That becomes a bit of a PITA if you ask me... Especially after using CM for so long....
I like Amon-Ra better actually... Aside from the lack of seeing past root of SD...
As I said, I'm not mad, just wanted to know if maybe a change was in the works or if anyone knew a way to force seeing further.
no way around it, but if you are by a computer, enabling USB mode allows you to mount the SD card and manage it while in recovery.
leenypost said:
Are you saying there is a way to make it see past the root? I can't figure it out. Please elaborate..
If you are just saying it is easy to work around as in it is easy to just move my files to root of sd.... Well sure, it isn't hard to do..... but it does take more time.... And say you are doing something complicated requiring flashing a few things one after the other... Well... That becomes a bit of a PITA if you ask me... Especially after using CM for so long....
I like Amon-Ra better actually... Aside from the lack of seeing past root of SD...
As I said, I'm not mad, just wanted to know if maybe a change was in the works or if anyone knew a way to force seeing further.
Click to expand...
Click to collapse
david279 said:
2.0 can but amon-ra hasn't ported it over to the evo yet.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thank you. Do you know if he has stated that he plans to port it over at some point?
xlGmanlx said:
no way around it, but if you are by a computer, enabling USB mode allows you to mount the SD card and manage it while in recovery.
Click to expand...
Click to collapse
Ahhh, see I didn't know that since I just started using. Is that what that first option line is for? I think it has 2 letters then a dash and two more letters?
Thanks for the info.
yup, whatever says usb, you hit it, connect up your phone and its just like hard drive mode when your phone is on, life saver especially if you jack up something or wipe everything but forgot to move a ROM to the root of your HD
leenypost said:
Ahhh, see I didn't know that since I just started using. Is that what that first option line is for? I think it has 2 letters then a dash and two more letters?
Thanks for the info.
Click to expand...
Click to collapse
xlGmanlx said:
yup, whatever says usb, you hit it, connect up your phone and its just like hard drive mode when your phone is on, life saver especially if you jack up something or wipe everything but forgot to move a ROM to the root of your HD
Click to expand...
Click to collapse
Cool, thank you. That's a really great feature to have!!
your welcome, glad i could help you learn something about AMON
leenypost said:
Cool, thank you. That's a really great feature to have!!
Click to expand...
Click to collapse
Yep, I always use usb-ms mode when I do some flashes/updates since it's quick and easy. The file explorer would be a bonus, but amon ra is great the way it is. As long as I have my nandroid backup includes my 4G RSA keys then that's all that matters.
mizzos4 said:
Yep, I always use usb-ms mode when I do some flashes/updates since it's quick and easy. The file explorer would be a bonus, but amon ra is great the way it is. As long as I have my nandroid backup includes my 4G RSA keys then that's all that matters.
Click to expand...
Click to collapse
Does it back upo 4G-RSA keys automatically or do I have to do a separate backup for that?
i'm sure it will be implemented in the evo build soon. just be patient.
not to sound anal but unless it involves added 400 extra lines of code why not ad this basic feature from the get go?
I mean my sd was nicegly organized, now i have all they files jammed into the root of my sc card. Making trying to find one to flash out of gillions very hard
To port over the iPhone emoji? its getting a little lame not to have a universal emoji.. but surely if Handcent can do it the system should be able to..
Found THIS
Download, unzip, replace /system/fonts file of same name, reboot. It only covers about 70ish% of emoji. Better than 0%.
Nandroid Backup before flashing... you've been warned.
So it zips it into correct spot or do I have to by hand?
Mahlhavoc said:
So it zips it into correct spot or do I have to by hand?
Click to expand...
Click to collapse
Unzip and physically put the file in the directory listed but nandroid first.
roger.. doing now. Thanks man.
Ok, hate to be an idiot here, but I was taught the only dumb question is one un-asked.. Astro will not move the files or replace.. seems maybe the system is using the font? If I can do this in recovery then I am unsure of how.. little help on the moving of said file and replacing?
Sorry man.. maybe I am missing something?
blakeboys said:
Found THIS
Download, unzip, replace /system/fonts file of same name, reboot. It only covers about 70ish% of emoji. Better than 0%.
Nandroid Backup before flashing... you've been warned.
Click to expand...
Click to collapse
Mahlhavoc said:
Ok, hate to be an idiot here, but I was taught the only dumb question is one un-asked.. Astro will not move the files or replace.. seems maybe the system is using the font? If I can do this in recovery then I am unsure of how.. little help on the moving of said file and replacing?
Sorry man.. maybe I am missing something?
Click to expand...
Click to collapse
That is the system folder [internal memory] and astro can't access it, well write to it; you'd have to use root explorer to paste it there.
yup.. dumb moment.. gonna use all my thanks up in a simple fonts q and a...
teh roxxorz said:
That is the system folder [internal memory] and astro can't access it, well write to it; you'd have to use root explorer to paste it there.
Click to expand...
Click to collapse
This. You must be rooted to have superuser permissions (access to write to the /system partition).
Use Root Explorer like roxxors said, give it SU permissions, navigate to your system/app folder, mount R/W at the top right (read/write) and then you can long press on items to delete or modify the apps and permissions.
Remember you have to mount R/W before you can edit, paste, move things into, or otherwise modify what's in /system
Its ok as long as you get it figured out.
Mahlhavoc said:
yup.. dumb moment.. gonna use all my thanks up in a simple fonts q and a...
Click to expand...
Click to collapse
Well we all have slow moments, and it was an honest question, and you'll get 5 more thanks for tomorrow.
At least you didn't get your evo stolen before calculus III, like I did today.
teh roxxorz said:
At least you didn't get your evo stolen before calculus III, like I did today.
Click to expand...
Click to collapse
Dude, that sucks man. I saw your post about it earlier and how someone said "Did you have a phone locator app?"
I've used locating apps in the past, but being a performance freak I try to keep my phone pretty barebones. Hearing your tale of sadness makes me wonder about reinstalling it.
Wouldn't do much use if the person who took it knows the first thing about Android. Not that I ever would but if I stole an EVO first thing I would do is turn of GPS and do Airplane Mode and either uninstall locating apps or do a factory reset.
But maybe someone found it on accident and it will be at the lost and found tomorrow?
Or maybe this is God's way of telling you to switch to the EVO 3D when it comes out!
mexlos said:
Dude, that sucks man. I saw your post about it earlier and how someone said "Did you have a phone locator app?"
I've used locating apps in the past, but being a performance freak I try to keep my phone pretty barebones. Hearing your tale of sadness makes me wonder about reinstalling it.
Wouldn't do much use if the person who took it knows the first thing about Android. Not that I ever would but if I stole an EVO first thing I would do is turn of GPS and do Airplane Mode and either uninstall locating apps or do a factory reset.
But maybe someone found it on accident and it will be at the lost and found tomorrow?
Or maybe this is God's way of telling you to switch to the EVO 3D when it comes out!
Click to expand...
Click to collapse
Well me being the mini guru I am, keep my gps off when not in use, and had no locator apps, and called my mom to call sprint and deactivate it and but a bad esn on it [which they did]. Its rooted, with all the bells and whistles, so I don't expect to get it back, and like I said, its been deactivated...and have to use a "shudders" blackberry for like 10 days, til i get the replacement. And it may be...
well works mostly.. still a few I still cant see, but it seems to be working! Thanks guys.
EEEP bad deal on Phone man.. crappy deal
Mahlhavoc said:
well works mostly.. still a few I still cant see, but it seems to be working! Thanks guys.
Click to expand...
Click to collapse
Glad that you got it working man.
I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.
I'll direct to you the Q&A forum.
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?
ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App
Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.
Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk
Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App
Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?
So I took the CM9 rom, deleted a few things, changed a few things, messed around changes A LOT of things actually...
But I did this all on Windows believe it or not, so without further explanation this rom needs somebody elses work on it to make it flashable.
I did this for my Epic 4G, and the results were amazing, especially battery life.
This rom; once it works, should free up a tleast 5-10 or maybe more ram. And you should be getting an 1-5 hours more battery life.
So here is the rom that needs work.
Please do not flame me for this, I know I did not make this rom from scratch, all I did was make a few changes for it to be better.
***For the devs who want to work on it: The problems I am concerned about is that I changed the build.prop and the update-script so you will have to double check to make sure that it is ok.***
Notes: I did change one minor(its actually major) thing that might effect everything, I do NOT have an Epic Touch yet so I do not know if it is laggy or not. I am trying to buy one currently.
I did this for my Epic's rom a while ago, so I had the option of 2 things to do to that certain thing, one option is laggy but gives more ram, the other option is smooth as a mofo but a lot less ram. Don't ask what it is, I won't say, I'm sure somebody will figure it out and tell everybody.
This rom needs to be fixed in order to be flashed, thank you.
If I posted it in the wrong section move it or remove it. I posted it here because I didn't CREATE the rom, and I didn't want any trouble.
I took cold medicine that helps me sleep so I am very drowsy now, this whole thread might not make sense, but I wanted to put it up before I went to bed so when I wake up it'll have posts.
wow....so does the text auto fit in browser works?..is video fixed?...wow....lots of things need lots of help...
asteetva said:
wow....so does the text auto fit in browser works?..is video fixed?...wow....lots of things need lots of help...
Click to expand...
Click to collapse
No, I just made what already worked better, I do not have a lot of time on my hands but I am working on those things don't worry friend
Did u use winrar? If so thats ur problem. U should use 7zip amd pastebin the updater script if u can
Sent from my SPH-D710 using xda premium
T.C.P said:
Did u use winrar? If so thats ur problem. U should use 7zip amd pastebin the updater script if u can
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I should be sleeping but I am up waiting for replies lol. Yea I used winrar, I will do that first thing when I wake up.
prochargedls2 said:
I should be sleeping but I am up waiting for replies lol. Yea I used winrar, I will do that first thing when I wake up.
Click to expand...
Click to collapse
ok thats one of ur problems, also u said u edit build prop and updater script, did u use notepad +? anything else always errors out, that can be another problem..
T.C.P said:
ok thats one of ur problems, also u said u edit build prop and updater script, did u use notepad +? anything else always errors out, that can be another problem..
Click to expand...
Click to collapse
Yes I did, I don't know of many tools for this lol.