I am trying to edit the build.prop for the NS4G Modem patch for the OG Epic 4g...
I'm trying to make it so that it changes the build number/version automatically for every cm10 nightly build. I'm getting kind of tired of always changing the build.prop to the corresponding nightly build can someone please help... do I need to create another file in the zip for it to update with every build? Please help
treat ur girl like how u treat ur epic
Related
I am currently playing around with customizing my own rom for personal use based of the plain de-odexed rom. I have added various packages like:
Camera mod
oc4 1.2 jac kernal
mobileAP
some custom themes and fonts
swype with voice icon
GPS files from leak
ect
My question is with all the main roms (eugene and Bionix) released there are always references to "Build.prop mods for better data throughput", how can I take JUST THOSE CHANGES and port them into my rom. Is it as simple as using abd pull and push with certain files? Do I need someone to make me a flashable zip package?
Also I noticed eugene in his latest build used a different camera and would love to try that is that just as simple as adb pull and pushing the camera apk?
Any help provided would be truly appreciated I am still kinda a noob.
Also just to be EXTREMELY clear this is only for my personal use and basic knowledge. I wish to take nothing away form the absolutely stellar work these guys do everyday, I simply have some different preferences then the main roms created and would love to learn to take the advantages of each rom and customize them to my own needs.
No one can help me out?
Should I ask in dev section as no one here seems to have any ideas?
I'm in same boat
I am doing the same.i noticed in bionix build.prop the symlinks. I like that.but he also references a "jit" did they port a jit? that would rock
Hi everyone just asking what rom makers do when building a rom?
E.g build bootloader then build kernel etc
Personally, as a beginning Android Cooker, I started by grabbing a ROM from here. Then I changed some things, experimented a bit, and simply change some files in the ZIP updates.
When you're a beginning cooker, I think it's the best to build an AOSP Rom using Cyanogens Wiki. Change some stuff to your liking (make backups...), see what happens, etc.
Thanks I'll have a go at it
Prob best to not experiment with the bootloader till you know what you are doing
Sent from my Droid using Tapatalk
OK, so I took a leap of faith and decided I am going to try and port a stock Sense 3.0 ROM from the Desire HD over to the Thunderbolt.
I have it booted and can naviagte around with out any FCs, but of course as is usually the case on the tbolt I don't have radio/wifi/data.
I also don't have sdcard access, but am reviewing logcats to see if I can fix that.
Did have a camera issue but was able to fix that issue and camera now works fine.
Here is what I have done (basic overview, can go into more detail if anyone is interested in helping to point me in the right direction)
- Created a stock DHD rooted, deodexed rom from the RUU for leak/release 3.06.405.1 (Desire HD RUU)
- Moved usual files over to the DHD rom from stock tbolt rom 2.11.605.5 (lib files, ril files, etc)
- After one hang up on boot and reviewing logcats, I moved over a couple more lib files and was able to get a successful boot
I am sure the issue to fix this will be in framework.jar, but not sure which smali files.
Concerning framework.jar, I already tried to move over the framework.jar from 2.11.605.5, but it hangs up at splash screen.
I also tried to just move over just the thelephony smali folders in framework.jar and recompiling, but it also would hang up during boot.
I guess I need to merge some of the tbolt smali files into the DHD framework.jar, but not sure what and where.
This is a beautiful ROM and outisde of above issues, performs very smooth and I hope to get it completely functional.
I know alot of Sense 3 ROMs out there are Hybrids, and actually have alot of the stock Sense 2.1 base files. But I am trying to port the entire DHD Rom.
If you are up to helping and can give me some good solid direction on this, please PM me or if you want you can post it here, maybe someone can learn something from it.
I appreciate any help anyone can offer.
Also, I have asked a couple of "big" Devs for help on this, but decided to post on here as well as I know these Devs are busy with real life, let alone finding additional time to help on something like this.
i always wanted to make a custom rom with my sing on it but for my personal use only....i manage this with this guide http://forum.xdadevelopers.com/showthread.php?t=1132724
and my rom is working perfectly without bug as i can see until now...but i want to add some custom boot animations or add teawks and some other "hacking" things on my Gnote so i was wondering if some one can show me a guide to do it or tell me...Also i am using the dsixda's Android Kitchen now to see with what method i am doing better work...
I am also new to this but successfully I have created a ROM for SGS II without any kitchen or whatever from Base! My Advice is You first Get a Skeleton Rom and Study Android File Structure(FOLDERS WITHIN ROMS) not FILE SYSTEM(EXT4 etc). I will guide more If you start and finish what I said previously!
Thanks always Appreciated!
ok i have make one rom with skeleton rom and is working perfectly with the cg root kernel and also with abyssnote ...i didnt face any issue so far....
Good! You should now tweak the Framework and make it stable while adding no themes!
Deodexing and CRT off and BatteryMod plus Extended power menu should be in your rom before posting on XDA because all other ppl like these features so much that now it's compulsory in every rom!
That things is what i want on my note from the day i bought it....but i dont know how to add them to my rom (the method to do it)....so far with the guide it was so "easy" (after 20) to learn anything the guide said i have manage to build one deadoxed and zipaling rom tha i am proud of after my hard time with google searching for this staff...But now i am in a dead End.
Taimur Akmal said:
I am also new to this but successfully I have created a ROM for SGS II without any kitchen or whatever from Base! My Advice is You first Get a Skeleton Rom and Study Android File Structure(FOLDERS WITHIN ROMS) not FILE SYSTEM(EXT4 etc). I will guide more If you start and finish what I said previously!
Thanks always Appreciated!
Click to expand...
Click to collapse
Im really noob here.
What is skeleton rom?
Where i can get it?
Thx dude.
Sent from my ZTE BLADE N880 CDMA --using XDA App
Hello here's the thing ...
I got tired of changing between rom so i thought ... gonna make my own ... and so i did ...
I'm no dev ... but imho! It worked out great i picked out a stock DDQ8 and ... i got a solid rom with amazing speed even tough its under locked! and even under locked ... got a benchmark higher than many roms i've tried ... wich had no under lock at all ... !
Now ... there are still some thing's that i need to do ... but as i stated earlier ... i am no dev and i am still leraning
1st - Recently converted system to ext4 (have cf-root b83) and now i wanna install a2sd script ... i know something about that ... but can someone tell me exactly what to do, to get him up and running?
2nd - I wanna deodex my rom ... but im having problems with adb ... i click for it to run and he simple just close's ...
3rd - If i get all of the thing to work as i want ... How can i make this a flashable rom so other may experience it?
Thanks in advance to all of you wich are willing to help
Thing's ive done so far:
Deleted all the junk and i'm still not over with this ...
Modded mms.apk
modded phone.apk
modded gallery3d.apk
flashed cf-root b83
made it possible to read custom boot animation's
made my edit's to build prop
converted it to ext4 file system ...
Change the look's of with the new modded touchwiz from great spacecaker
icons and system ui to look like S2
removed swipe to unlock
added beats audio lib and app
and that's all i can remember right now
All can be done with dsixda's Android Kitchen
Ace-ing all tests.