Database Users

Help Build ROM!!

So during the time was ban on XDA for flaming Noob. I have had the time to take a rom of my liking and personalize it to what I believe to be the perfect rom, well for me at least. Now that have everything all together I want to share my creation with the world and Good people here on XDA. But I have no idea how to make everything in to a DOT .zip file. I need help and I was wondering if anyone would care to help me.
What will be included in the rom:
GB launcher2
Galaxy tab TWlauncher clone
OC 1.2ghz Kernel w/ universal lagfixes
Gingerbread style theme w/ a little color
GPS fix
swype
Gb keyboard w/ working vibration and sound
boot-animation.zip
Avatar Movie app
Sims3 app and sims3.apk
Rom manager
Xda app
Root explorer
Superuser
New market app
Android 2.2.1
and more.....
This rom will be a mix of Eugene and masters roms so all thank goes to them and a couple other people on the forum.
Thank You

sader2202 said:
So during the time was ban on XDA for flaming Noob. I have had the time to take a rom of my liking and personalize it to what I believe to be the perfect rom, well for me at least. Now that have everything all together I want to share my creation with the world and Good people here on XDA. But I have no idea how to make everything in to a DOT .zip file. I need help and I was wondering if anyone would care to help me.
Click to expand...
Click to collapse
Hi. I think you'll find a lot of support on XDA for building your own ROM and/or for theming. You've covered a lot of different areas in terms of what you want to do. I have a few recommendations.
1. Do a quick search, either here or in Google, on how to build Android ROMs. There's a lot of good information out there and some of it might resonate with you in terms of how they explain things. That said, if all you're doing is changing a few files around; files you already have, then you would simply add them to, or replace the existing ones from a ROM you like. Just be sure to connect with the developers of that ROM so you can give credit where credit is due. Or, you could start with the Stock ROM and do it that way. But, in either case, you would be essentially using WinZip or some similar app to build the .zip file as you'd like to see it.
2. Consider hooking up with one of the existing developers and start making contributions to their work. That would give you a chance to work with some of the best people who are already doing what you want to do. I think in that case, it wouldn't take too long for you to come up to speed on who they've approached things. Also, this helps you from making some novice mistakes that I'm sure they've made along the way.
Lastly, consider the "value add" of your ROM over those that are already available. If you build something and no one has heard of you and then they don't see your ROM as having anything better or different to offer, then people might not want to use it. For example, Team Whiskey has Obsidian. Then they released Onyx. However, Onyx was materially different than Obsidian in that they removed a lot of the TouchWiz based theming and T-Mobile applications. So, a lot of people saw value in that.
Anyway, good luck. I'm sure you'll have a lot of fun!

This thing sounds quite nice! Would you be interested in posting the 2.2.1 build you got your hands on and the GB KB with Vibration? I haven't seen either of those elsewhere.

vinnydakid said:
This thing sounds quite nice! Would you be interested in posting the 2.2.1 build you got your hands on and the GB KB with Vibration? I haven't seen either of those elsewhere.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=845162
updated version has vibration
accidently hit thanks

sader2202 said:
So during the time was ban on XDA for flaming Noob. I have had the time to take a rom of my liking and personalize it to what I believe to be the perfect rom, well for me at least. Now that have everything all together I want to share my creation with the world and Good people here on XDA. But I have no idea how to make everything in to a DOT .zip file. I need help and I was wondering if anyone would care to help me.
What will be included in the rom:
GB launcher2
Galaxy tab TWlauncher clone
OC 1.2ghz Kernel w/ universal lagfixes
Gingerbread style theme w/ a little color
GPS fix
swype
Gb keyboard w/ working vibration and sound
boot-animation.zip
Avatar Movie app
Sims3 app and sims3.apk
Rom manager
Xda app
Root explorer
Superuser
New market app
Android 2.2.1
and more.....
Thank You
Click to expand...
Click to collapse
First, google WINRAR and download it.
Then select all your files, right click and click ARCHIVE and then choose location, name, and wait until its done, and it'll be in a .zip.

Root Explorer is not a free app, so you may want to reconsider adding that as part of your ROM.

wannagofast said:
Root Explorer is not a free app, so you may want to reconsider adding that as part of your ROM.
Click to expand...
Click to collapse
Oops thanks for the heads up. I've been using it so much that i forgot that i brought it.

xriderx66 said:
First, google WINRAR and download it.
Then select all your files, right click and click ARCHIVE and then choose location, name, and wait until its done, and it'll be in a .zip.
Click to expand...
Click to collapse
Thanks i had that install in my pc. thanks again.

xriderx66 said:
First, google WINRAR and download it.
Then select all your files, right click and click ARCHIVE and then choose location, name, and wait until its done, and it'll be in a .zip.
Click to expand...
Click to collapse
wannagofast said:
Root Explorer is not a free app, so you may want to reconsider adding that as part of your ROM.
Click to expand...
Click to collapse
Following the steps above, able to get him to do his ROM.
So this thread is no longer necessary!
Thanks for the help and feedback of all!
Closed Thread!

[INFO] Note to all ROM makers

There seems to be issues with baksmali/smali v1.2.6 when deodexing latest samsung roms (2.3.4 maybe also some 2.3.3!).
If you baksmali framework.odex and smali it back to a dex file (without changing anything) your ROM will become laggy!
Some people say its the hardware acceleration that no longer works.
The web browser becomes unusable. There have been reports that video player and camera also seems laggy.
My suggestion is NOT to deodex framework.odex! I'm sorry to say this...
I know this means no custom deodexed roms! But I do believe you will run into more problems we don't know about yet!
But you can still do mods!
Just not deodexed framework mods. You can deodex apk files in the app folder. You can also try and deodex files in the framework folder as long and you dont deodex the framework.odex file! But here you have to convert them back to odex files!
As proof I have made this mod for stock XXKG1. I have the odexed the files back to odex using the dexopt-wrapper tool.

It is not just 1.2.6, I have built from the latest source and still has problems.

I disagree 100% fwiw with OP
I have no speed issues beyond that stupid browser, and that looks just like a baksmali bug. I don't do the "quit" attitude - I will fix it...
But anyway, there is no lag or anything here, even on 2.3.4 deodexed and underclocked.
So while there may be a browser issue, I would not suggest to people not to deodex. I can provide thousands of posts of people happy with a properly Deodexed and optimised ROM...

do we know why this happens? Is there an logic explanation

stian230 said:
do we know why this happens? Is there an logic explanation
Click to expand...
Click to collapse
Most likely minor baksmali bug

designgears said:
It is not just 1.2.6, I have built from the latest source and still has problems.
Click to expand...
Click to collapse
Maybe if we can debug using source we can figure out what goes wrong!

pulser_g2 said:
I disagree 100% fwiw with OP
I have no speed issues beyond that stupid browser, and that looks just like a baksmali bug. I don't do the "quit" attitude - I will fix it...
But anyway, there is no lag or anything here, even on 2.3.4 deodexed and underclocked.
So while there may be a browser issue, I would not suggest to people not to deodex. I can provide thousands of posts of people happy with a properly Deodexed and optimised ROM...
Click to expand...
Click to collapse
I hope you are right... But alot people also complains about all sorts of problems with the custom roms... and we dont really know if its related to this or not...

I spent all yesterday thinking about that...
The odex file is only valid when used with the exact BOOTCLASSPATH files. dalvik enforces this by storing a checksum of each file that the odex file is dependent on, and ensuring that the checksum for each file matches when the odex file is loaded.
When you are deodexing an apk, even if you don't need to set BOOTCLASSPATH for it (because you don't get any error msg while baksmali), by default these 5 jar are already included in the classpath: core.jar, ext.jar, framework.jar, android.policy.jar and services.jar. This means that an odex file has dependencies on every "BOOTCLASSPATH" file that is loaded when it is generated.
So i was thinking about to deodexing every apk in /system/app a part Browser.apk (i.e leaving Browser.odex) and try to figure out which jar file inside /system/framework has to remain odexed.
Maybe we can still have overscroll glow mod, renounce to have the extended power menu in order to get an HW accellerated Browser!
I don't know if it make sense for you as my english need to be improved

_JKay_ said:
I hope you are right... But alot people also complains about all sorts of problems with the custom roms... and we dont really know if its related to this or not...
Click to expand...
Click to collapse
You got any examples to hand?
The common issues I see are
- failing to read my install instructions
- trying to come from some other ROM without following the instructions
- trying to restore titanium backups entirely, depositing apps that are codes like half-polished turds in the phone
- pushing incorrect files into rom without knowing what they are doing
- stupid setcpu config
Am interested to see if you have found other issues, as camera and video player are confirmed by a fair number to be fine...
I swapped my phone with one running stock, and I had to tell my friend what I had done, as he was sure it was his oh, and I was underclocked to 800 max too at the time

pulser_g2 said:
You got any examples to hand?
The common issues I see are
- failing to read my install instructions
- trying to come from some other ROM without following the instructions
- trying to restore titanium backups entirely, depositing apps that are codes like half-polished turds in the phone
- pushing incorrect files into rom without knowing what they are doing
- stupid setcpu config
Am interested to see if you have found other issues, as camera and video player are confirmed by a fair number to be fine...
I swapped my phone with one running stock, and I had to tell my friend what I had done, as he was sure it was his oh, and I was underclocked to 800 max too at the time
Click to expand...
Click to collapse
The frameword.odex is not compiled correctly!! That's a fact!! The laggy browser proofs it. Framework.odex the largest most important file in the android framework!! And that does not concern you? Is that not a bit naive?

_JKay_ said:
The frameword.odex is not compiled correctly!! That's a fact!! The laggy browser proofs it. Framework.odex the largest most important file in the android framework!! And that does not concern you? Is that not a bit naive?
Click to expand...
Click to collapse
I believe what I see. I have asked HomerSp if he can take a look at it, when he can, as he knows a lot about the deodexing process.
But at the end of the day, while there is clearly something not working in baksmali or smali, this seems a good opportunity to fix it and pass on the fix to JF
I know what is in framework.jar, and that it covers most things...
I do genuinely have interest in seeing the issues you raised, as perhaps there is disparity between methods of deodexing??? I am interested to see if I can reproduce any here too, as that would highlight a wider issue.

pulser_g2 said:
I believe what I see. I have asked HomerSp if he can take a look at it, when he can, as he knows a lot about the deodexing process.
But at the end of the day, while there is clearly something not working in baksmali or smali, this seems a good opportunity to fix it and pass on the fix to JF
I know what is in framework.jar, and that it covers most things...
I do genuinely have interest in seeing the issues you raised, as perhaps there is disparity between methods of deodexing??? I am interested to see if I can reproduce any here too, as that would highlight a wider issue.
Click to expand...
Click to collapse
Well.... I will not use deodexed custom roms so I won't find any issues!!! But some people probably will or already has...
I'd rather spend my time on fixing this and create odexed mods until its fixed!
As soon as I see that the framework.odex can be compiled without breaking the browser... I might try some custom roms again..

That's weird. I'm using Lite'ning 1,5 ROM (which is deodexed) since i bought this phone and everything runs very smooth (including browser, video playback, gaming, launcher and so on). Before i had HTC Desire Z with CM7 on it and it was freezing slow if compared to my current setup. It's just flying.

AllWin said:
That's weird. I'm using Lite'ning 1,5 ROM (which is deodexed) since i bought this phone and everything runs very smooth (including browser, video playback, gaming, launcher and so on). Before i had HTC Desire Z with CM7 on it and it was freezing slow if compared to my current setup. It's just flying.
Click to expand...
Click to collapse
I know that version (2.2) does not include the original stock browser but a patched version.
Sent from my GT-I9100 using XDA Premium App

_JKay_ said:
I know that version (2.2) does not include the original stock browser but a patched version.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
You're basing all your points on 1 main problem, the browser.
That's hardly the way to go. Rather, they will work to solving the problem regarding the browser, then we can continue to have proper custom roms. Besides, KG1 is a leaked rom. Deodexing didn't affect KF2, it might not cause problems for later leaked or "official" roms.
Rather than directing others to your odexed mods, the way for things to move on is to see the problem being fixed. There's a reason why custom roms are almost always deodexed. Don't rock the boat if you don't like the status quo.

kenkiller said:
You're basing all your points on 1 main problem, the browser.
That's hardly the way to go. Rather, they will work to solving the problem regarding the browser, then we can continue to have proper custom roms. Besides, KG1 is a leaked rom. Deodexing didn't affect KF2, it might not cause problems for later leaked or "official" roms.
Rather than directing others to your odexed mods, the way for things to move on is to see the problem being fixed. There's a reason why custom roms are almost always deodexed. Don't rock the boat if you don't like the status quo.
Click to expand...
Click to collapse
That's actually exactly what I am saying!! Don't spend time on fixing the browser! Spend time on fixing the baksmali/smali tools!!
But until that's fixed I believe you can't really rely on the deodexed roms because framework.odex does not compile correctly!!
Some people said that you can't do mods that are odexed!! Thats the reason for the example! You actually don't need to deodex the framework!! But I admit.. it's easier not to odex files...

BTW guys, following the OP IDEA i got my own custom rom working with the odexed stock Browser (i.e. HW accellerated).
Basically all the apps have been deodexed apart Browser, and i left the framework jar files odexed!
Basically i got the same features/mod as before, the only think i have to renounce is the overscroll glow effect (i don't like it at all, i prefer the stock Samsung bounce effect) and the extended power menu (we can easily replace it by using quickboot).
That's it
thanks _JKay_ for the IDEA!

But I do think the problems wont fix itself in the future. The SGS facing the same problems with XXJVQ!!

LeoMar75 said:
BTW guys, following the OP IDEA i got my own custom rom working with the odexed stock Browser (i.e. HW accellerated).
Basically all the apps have been deodexed apart Browser, and i left the framework jar files odexed!
Basically i got the same features/mod as before, the only think i have to renounce is the overscroll glow effect (i don't like it at all, i prefer the stock Samsung bounce effect) and the extended power menu (we can easily replace it by using quickboot).
That's it
thanks _JKay_ for the IDEA!
Click to expand...
Click to collapse
No problem! Actually my mod gives you the extended power menu

_JKay_ said:
But I do think the problems wont fix itself in the future. The SGS facing the same problems with XXJVQ!!
Click to expand...
Click to collapse
I agree with you, but at least, since a lot of people complain about the stock browser, we can stay happy with it!
I reckon we need new tool for deodexing, smali backsmali are dated now...

[REQ] 2WCR port or patch guide for AOSP-MIUI

Hi, I don't know the proper way of doing this but I do humble request to someone with spare time to make a PATCH or post some guide for patching at least the default MIUI kernel to have proper 2WCR on it.
I don't live in the US so 2WCR laws don't restrict me from recording my own calls.
Thank you in advance.

Is there a problem with the built-in method of 2wcr? I've never tried it, but it should work fine out of the box.
MIUzI weighs a ton.

EndlessDissent said:
Is there a problem with the built-in method of 2wcr? I've never tried it, but it should work fine out of the box.
MIUzI weighs a ton.
Click to expand...
Click to collapse
Built-in method from the EVO4G is only good if you make calls using the loudspeaker because it records from the MIC.

Wrong section my friend.

Sorry, I really didn't knew where to make the request, but I really hope someone has the spare time to make or help me accomplish this. If any moderator read this please be kind enough to move this thread to the appropriate section, and sorry for any inconvenience.

To Add it into the Kernel is pretty easy. Just replace 6 files in the source code of your Kernel with the ones from my www.github.com\detcup4evr
Sorry I haven't had a chance to look at ASOP kernel much, but code looks pretty similar.
Add these files
arch/arm/mach-msm/qdsp6/amrnb_in.c
arch/arm/mach-msm/qdsp6/vocpcm.c
Edit these or just replace
arch/arm/mach-msm/include/mach/msm_qdsp6_audio.h
arch/arm/mach-msm/qdsp6/Makefile
arch/arm/mach-msm/qdsp6/pcm_in.c
arch/arm/mach-msm/qdsp6/q6audio.c

Thank you very much for your response, I know it looks simple to do but for me those tips you gave me are like rocket science,I don't have the sightless idea on how to accomplish it but I will try to make some time to read and learn how to compile that, between work and my 2 kids I don't have too much spare time hehe, but I appreciate your kindness.

detcup4evr said:
Just replace 6 files in the source code of your Kernel
Click to expand...
Click to collapse
whether it is suitable for all devices, or for HTC only? e.g. will it work for LG O1, CM miks ROM?
thanks very much

detcup4evr said:
To Add it into the Kernel is pretty easy. Just replace 6 files in the source code of your Kernel with the ones from my www.github.com\detcup4evr
Sorry I haven't had a chance to look at ASOP kernel much, but code looks pretty similar.
Add these files
arch/arm/mach-msm/qdsp6/amrnb_in.c
arch/arm/mach-msm/qdsp6/vocpcm.c
Edit these or just replace
arch/arm/mach-msm/include/mach/msm_qdsp6_audio.h
arch/arm/mach-msm/qdsp6/Makefile
arch/arm/mach-msm/qdsp6/pcm_in.c
arch/arm/mach-msm/qdsp6/q6audio.c
Click to expand...
Click to collapse
Sadly it's not a cut and paste in the case of AOSP. I am having to rewrite of amrnb_in.c in order to evern suggest getting it to compile. I strongly discurage anyone from copy and pasting those files over as the have dependencys on things that come with sense that are simply not in AOSP.

vocpcm and qdsp6
atyoung said:
Sadly it's not a cut and paste in the case of AOSP. I am having to rewrite of amrnb_in.c in order to evern suggest getting it to compile. I strongly discurage anyone from copy and pasting those files over as the have dependencys on things that come with sense that are simply not in AOSP.
Click to expand...
Click to collapse
Hi, did anyone get this working ok ? I just tried the suggestion above but it seems like I am missing a bunch of dal headers etc.
Is it just working on specific Qulacomm DSPs in HTC devices ? I have for example a qdsp6v2_1x directory in my HTC sources for HTC Sensation
Anyone tried to build this on kernel 3.x ?
cheers
Mark

[GUIDE] How to port sense to non-HTC devices.

How to port Sense.
Source: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/164989-guide-how-i-port.html (second post)
This is NOT my guide, just posting it here!
This is a very difficult process that I hope you'll understand.
First step is to find a device that is preferably VERY similar to your device, in this instance I guess we would use the htc thunderbolt, which I've been told multiple times that it is used for the MT.
You're going to want to use CM7 for parts. Simple enough.
I will be referring the Sense ROM to SENSE and CM7 as BASE to simple things up. So remember that.
When I say replace, I would recommend deleting from one and adding it with the other
Open up Sense and Base in different windows.
Put in the boot.img from Base into Sense (make sure you put the original boot.img in some other place that you'll remember)
go into /system/usr on both
replace keylayouts and keychars from Base into Sense (this is just your keys)
download dsixda's kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
Get the ROM you have so far set up in it and what not (I'm a little fuzzy at this part)
Once you get done with that, run the menu in terminal and navigate your way to decompile the boot.img (action key- "a") and then run the same thing except run the action key "w" to decompile the original boot.img. So the key here is to decompile both boot.img's.
Go into the ramdisk on both and go into init.rc
THE MOST IMPORTANT PART IN THIS (THE MATTER OF BOOT AND BOOTLOOP) IS THE LINE
"export BOOTCLASSPATH" near the top. It will have a bunch of lines after it. Now in the Base's boot.img, delete this whole line. Replace it with the lines from Sense's boot.img.
Now you can add anything else you want that looks like it belongs (preferably anything sense related)
Don't recompile the boot.img yet.
Now we add a2sd. To do this, just follow this guide (https://www.facebook.com/note.php?note_id=158823170833688)
The only thing you do in there is the edits to the init.rc, don't listen to the decompiling/recompiling mentions. Now you can go back into the menu for the kitchen and recompile the boot.img (action key - "b"). Now don't compile the WHOLE ROM, just take the new boot.img in working_** and put it into the Sense zip.
Now you're going to want to download my ROM (sorry, just don't feel like uploading each individual file) http://gannon5197.blogspot.nl/2012/03/got-sense-booted.html
And go into the /system/bin on both
these are the files you're going to need: a2sd, bash, apps2sd.hlp, busybox.a2sd, chka2sd, jita2sd, launcha2sd, starta2sd, and maybe possibly sh (try once without it)
And you're going to want to set permissions for each one of these in the updater-script (look at mine for references)
Now also look at my zip and you'll see move_cache_sd. Put that in yours and set permissions for it in updater-script (use mine for references)
After that, the other stuff is mainly just getting rid of all the bloatware, (look in /system/app and /system/media) I wouldn't delete any libs as of right now. If you try to flash it and it reboots recovery then it is too big.
If it is too big, you're probably going to want to move a lot of the apps to data. To do this, just make a file called data/app/put_your_apps_here on the root of the zip. You're going to have to set permissions for it in the updater-script, but use the test.zip I sent you in the original.
This will most likely get you booted. Nothing will likely work. Which is expected. If you have any problems, just use logcat. It will be your bestfriend. Have fun porting
Click to expand...
Click to collapse

reserved

Thanks for reopening it bro...
Sent from my LG-P500 using Tapatalk 2

No problem :thumbup:

Don't know how this above awesome thread is so blank
Have u tested if this way works
Sent from my LG-P500 using Tapatalk 2

great guide, gonna try out soon

hmm this one's new for me. saved
should come in handy sometimes

someone has to do this for the Galaxy S2.
Will it also work for ICS ROMs?

I must do this. Anybody know where I can get the firmware for the One S?

Can i use a Gingerbread ROM as a base instead of cm7?

Hello for lg p500 there is 2 sense rom but data and mic not working in both rom can you help to solving that problems????btw great tutorial.

in fact sensse porting is differnet from the tutorial showed it is a little bit more difficult and there are some libs needed that there is only for the devices you are porting to. so a general tread will not really work

QuBe2 said:
in fact sensse porting is differnet from the tutorial showed it is a little bit more difficult and there are some libs needed that there is only for the devices you are porting to. so a general tread will not really work
Click to expand...
Click to collapse
Well this is not my tutorial just found it on the internet so I don't know if it works

Lord Inglip said:
Well this is not my tutorial just found it on the internet so I don't know if it works
Click to expand...
Click to collapse
why sharing things on the internet

QuBe2 said:
why sharing things on the internet
Click to expand...
Click to collapse
Because it's the internet. This guide was the only thing I could find.
Well you ported a htc sense One x rom to the Nexus S, so can you show us how you did it?

Lord Inglip said:
How to port Sense.
Source: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/164989-guide-how-i-port.html (second post)
This is NOT my guide, just posting it here!
Click to expand...
Click to collapse
Similar phone means the same chipset,processor and gpu??

a2441918 said:
Similar phone means the same chipset,processor and gpu??
Click to expand...
Click to collapse
Yes it's better if the phones have the same hardware

Lord Inglip said:
Yes it's better if the phones have the same hardware
Click to expand...
Click to collapse
I have an xperia x10.. will the nexus one and HTC desire be suitable??

My cm7 rom which i downloaded doesn't have a boot.img file.. So how to get it?? Is it the system.img got from a nandroid backup?? and the sense rom which the post refers to is the stock sense rom of the phone in a zip format or a modded one??

Not working..stuck at boot logo

[MOD][MIUI4] Volume+ Mod for MIUI4 v2.7.20 (Hold volume to skip tracks)

The prebuilt android.policy.jar ZIP attached is only for MIUI v2.7.20 for the Arc S (and unofficial ports based on that build, as long as the porter didn't already mess with that jar file). If you want it for other devices, get the 'Source Info' file and port it yourself.
You all know it. Roots in Cyanogenmod, ported to MIUI Gingerbread and many other ROM's over time... but new MIUI4 ROM's have missed out for too long. So here it is. Hold Volume-Up to skip forward a track, Down for back. Only works while music is playing and while screen is off and locked. Apparently it will also change FM channel if playing Radio, don't know and don't care.
It is based on MIUI UK's MIUI v2.7.20 for the Arc S, with the source info it should be easy to port to any other device. Might work on older/newer versions of MIUI too, don't know. This took me half an hour to do, it wouldn't have been possible without 7OH's original mod for Xperia's on Stock ICS. I just ported it to MIUI.
This is not a flashable ZIP, sort it out yourself. Extract, push android.policy.jar to /system/framework/ (overwrite old one) and optionally chmod it to 644.
Integrate it in your ROM if you wish, credit would be appreciated. Don't be an ass and claim it as your own. Just say "Volume+ Mod by CosmicDan and 7OH" in the credits.
Also attached is some info on the smali changes (a unified diff and two new files).
Bye!

i tried this on my galaxy siii but i just get bootloops

daniel9522 said:
i tried this on my galaxy siii but i just get bootloops
Click to expand...
Click to collapse
Galaxy S III is an unofficial MIUI device, contact your ROM developer to make the changes or try a different port. Also tell us which MIUI version it is and where you downloaded it from so others know. Thank you.

daniel9522 said:
i tried this on my galaxy siii but i just get bootloops
Click to expand...
Click to collapse
Just fyi, now that miui is based on stock firmwares, this will only work on devices it comes from (I.e the arc s). Miui gb was compiled from source, which is why stuff like this worked on all roms. Now they just patch some miui stuff into the original jar file, so the chances of a one-jar-fits-all are non-existant. The same patch will work, just that it needs to be done specifically for each rom. Too many framework changes between e.g. sense, touchwiz, Xperia etc.

lenny_kano said:
Just fyi, now that miui is based on stock firmwares, this will only work on devices it comes from (I.e the arc s). Miui gb was compiled from source, which is why stuff like this worked on all roms. Now they just patch some miui stuff into the original jar file, so the chances of a one-jar-fits-all are non-existant. The same patch will work, just that it needs to be done specifically for each rom. Too many framework changes between e.g. sense, touchwiz, Xperia etc.
Click to expand...
Click to collapse
Ahhhh OK fair enough, thanks for the info! I guess I will post in the Arc S section then. I will leave this here though because the other ZIP has a diff of the smali changes. and the MIUI port maintainers can take care of it. Still relevant for this section, also this is a first (at time of writing, no other site/ROM has it in MIUIv4 except for mine).
First post updated.

and this probably works for Neo V also thanks I try that later

Dan can you please provide me any information about how to use the diff file?

_polimorph_ said:
Dan can you please provide me any information about how to use the diff file?
Click to expand...
Click to collapse
Pretty sure you can't. It's for devs and users who want to integrate this feature into other roms. (Unless diff is associated with miui or somthing else then ignore me)

_polimorph_ said:
Dan can you please provide me any information about how to use the diff file?
Click to expand...
Click to collapse
With a program like WinMerge or patch binary compiled for win32. But you will need to edit variables, labels and line numbers where necessary. If you don't know how, don't bother. Basically if it's v0 on mine it might be v1 on yours, you can compare similar code around my changes to get an idea of what it should be.