i recently installed the wonderful Gummy 4.4 kit kat rom. however an app i want to use, references the build.prop for compatibility. and is now not compatible. im assuming my build.prop has been changed at some point, some how. how to i restore the build.prop to stock?
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
I've read through tons of threads trying to figure this out.
I'm running rooted OTA 2.2 (froyo) since 4/21/11 and am very happy with the performance so I'm trying not to mess with roms/kernal upgrades.
Is it possible to change my boot animation and sound without replaceing the stock kernal. (if not what kernal should I use?) I've read and read about trying to change or edit the .qmg file but no luck so far.
Also, what should I use or do to hide/remove all the bloat on my applications menu?? If I change my kernal to OTB would I notice any performance diferance from stock 2.2 froyo and would that help my situation?f
Thank you in advance for any insight on this.
You have to have a kernel that supports custom boot animations, and the stock one does not. Adrynalyne has some that work very well, and they can be found in the ROM/Kernel sticky in the developer forum. Most custom kernels will say if they support this feature.
As far as removing bloatware, both uninstaller pro and titanium backup have the ability to remove bloatware that verizon shoveled on us.
Problem:I need a default Build.Prop from anybody on the .208 ICS Leak, because wifi is not working, and the only difference between the other people on this leak and me: I restored an older Build.Prop from Gummy 1.2.3 and I remember wifi working at startup. So it must be the Build.Prop
Solution: I need a backup of the the default Build.Prop for this build.
TL;DR I need a backup of Build.Prop from the .208 leak.
Thank You
Greetings,
I was trying to create custom roms for the Galaxy Y pro (B5510) but I am having problems deodexing the latest stock ROM lately. I tried all tools which deodexes a ROM but I have no luck with any of them, as if there is something wrong during the actual deodexing process.
As you can see, there is no working custom ROM for the Galaxy Y pro lately. If someone can make things work (just let it deodex the stock ROM) then I might as well donate for your efforts
landono5 said:
Greetings,
I was trying to create custom roms for the Galaxy Y pro (B5510) but I am having problems deodexing the latest stock ROM lately. I tried all tools which deodexes a ROM but I have no luck with any of them, as if there is something wrong during the actual deodexing process.
As you can see, there is no working custom ROM for the Galaxy Y pro lately. If someone can make things work (just let it deodex the stock ROM) then I might as well donate for your efforts
Click to expand...
Click to collapse
Never mind,
Already figured it out, the easiest way to deodex the rom was using Virtuous Ten Studio... The Auto Deodex feature worked for the stock 2.3.6 Gingerbread ROM by setting the API Level to 10. Just a reference for those who will encounter similar problems. I tried other tools but it returns an error when deodex is initiated. I guess I have to donate to myslef then
Simple question... anyone have problems compiling with tw 4.3? System ui ends in fc. Phonesec.apk ends in loss of baseband ect ect. Apks of play store have no problems so I'm thinking it's to do with it being 4.3 as 4.1.2 works very well. Am I missing something. Many thanks.
Edit: apktool not fully compatible with tw 4.3 yet. Bk on 4.1.2 and error logs now showing and were its failing. Were as 4.3 would build apk and not show its failed. Any one has info on this pls post. :thumbup: