Hi.
Atm i am developing a bit, but i try to find the best kitchen for the SGS2. I mean programs to edit APKs, deodex, sign, align etc...
I am using "dsixda's kitchen" atm, working good, but there are some problems.
When deodexing the newest ICS (4.0.3 LPB) samsung keyboard gets force closes after flashing. Also WIFI isnt connecting.
Moreover i am flashing CF-Root, but e.g. Titanium backup isnt working.
Maybe its because of this kitchen, i dont really know... so there is the question to you: what do you use to deodex etc or what do you know? i used something from "sicopat" in the past, but i think thats only for gingerbread.
Thank you for answering,
greetz, Cloud2F
Cloud2F said:
Hi.
Atm i am developing a bit, but i try to find the best kitchen for the SGS2. I mean programs to edit APKs, deodex, sign, align etc...
I am using "dsixda's kitchen" atm, working good, but there are some problems.
When deodexing the newest ICS (4.0.3 LPB) samsung keyboard gets force closes after flashing. Also WIFI isnt connecting.
Moreover i am flashing CF-Root, but e.g. Titanium backup isnt working.
Maybe its because of this kitchen, i dont really know... so there is the question to you: what do you use to deodex etc or what do you know? i used something from "sicopat" in the past, but i think thats only for gingerbread.
Thank you for answering,
greetz, Cloud2F
Click to expand...
Click to collapse
The keyboard ICS issue was fixed a month ago in the kitchen.
dsixda said:
The keyboard ICS issue was fixed a month ago in the kitchen.
Click to expand...
Click to collapse
so you mean i am using an old version of your kitchen? thx for the answer
// i am using 0.188, so its the newest version... trying all different types of rom now, zipaligned, nonzipapligned, newer kernel etc....
Related
mySlide-1.0.2
YOU PROBABLY DON'T WANT THIS...DON'T WASTE YOUR TIME!!!!!
This is just what I want, not necessarily what you want http://www.mediafire.com/?tstgikwhfezj6ph
This Rom will mostly be unsupported and unmaintained.
Flash at your OWN RISK.
What it is:
Stock slide rom.
added busybox
added netcat (busybox nc isn't good enough for me)
added bash
added htop
removed link toolbox->df (prefer the one in busybox)
removed link toolbox->rm (prefer the one in busybox)
changed the default animated boot ADVERTISEMENT and jingle
pngcrushed and zipaligned apks (with the execption of one) to save some space
Kangs:
what isn't.
maybe a few more little changes I forgot.
changes:
from 1.0.0 to 1.0.1:
added a2sd (from eugene373's smr5r1. breaks boot animation)
added default themes back.
from 1.0.1 to 1.0.2
added e2fsck
mySlide-1.0.0-signed
mySlide-1.0.1-signed
mySlide-1.0.2-signed
Themes in this are broken (1.0.0 only). If you want the default themes back then flash this...
themes-signed.zip
hey dumfuq glad to see you over on the slide section now. can we expect some overclocked kernals from you like on the g1?
jriv said:
hey dumfuq glad to see you over on the slide section now. can we expect some overclocked kernals from you like on the g1?
Click to expand...
Click to collapse
I sure hope so, but only time will tell.
That would be sick wonder how high this processer can go?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Is the IM app erased in this and the tmobile app pack? i hate those apps
Nevermind i used ur rom and erased the files and signed it again. Thanks for the rom
dumfuq said:
YOU PROBABLY DON'T WANT THIS...DON'T WASTE YOUR TIME!!!!!
Click to expand...
Click to collapse
Not sure why you say that (in those words), but this does look decent!
Also, noob question, but are the stock ROMs (apps included) not zipaligned by default?
Yup they were already zipaligned. At least the ones I just checked
Honesty I didn't even look first. The crush actually takes off about 10Mb though.
yo dumfuq quick question... what exactly is required in editing a kernel to allow for overclocking and undervolting?
kingofyo1 said:
yo dumfuq quick question... what exactly is required in editing a kernel to allow for overclocking and undervolting?
Click to expand...
Click to collapse
Not exactly sure if this is what your asking but basically...
You need the kernel source code to edit (the legend kernel source has the espresso board files),
A handy dandy text editor (like vim),
a cross-compiler (There is one under prebuilt/linux-x86/toolchain in an AOSP or cyanogenmod build environment),
and a linux environment (cygwin might work not really sure).
1. download source
2. unpack source
3. edit source
4. set environmental variables
4. compile source
5. make a boot.img or an update.zip
Obviously that's incredibly simplified, but hopefully you get the idea.
Ok quick question to the maker of this rom... How can i add the themes back to this rom? I want to put the themes back but i dont kno which folder to put them in. Also which folder is where i can change the boot animation you have installed to stock? Thanks
this actually seems like exactly what i want. My only question is does it support a2sd. if so.. i have a new rom
btate0121 said:
this actually seems like exactly what i want. My only question is does it support a2sd. if so.. i have a new rom
Click to expand...
Click to collapse
good question. a2sd is a plus
you don't put them in anywhere. you can download and install them. there's a thread already with a small pack of themes to download and install. You install like any other APK. Search this forum section for them.
NiN39Z said:
Ok quick question to the maker of this rom... How can i add the themes back to this rom? I want to put the themes back but i dont kno which folder to put them in. Also which folder is where i can change the boot animation you have installed to stock? Thanks
Click to expand...
Click to collapse
The PNG crush killed the stock themes. If you want them back you can either boot to recovery and push the original ones to /system/app/ or just flash this...themes-signed.zip. That is just an update.zip that will copy the original themes back to your phone.
btate0121 said:
this actually seems like exactly what i want. My only question is does it support a2sd. if so.. i have a new rom
Click to expand...
Click to collapse
Nope, no a2sd.
any plans to add a2sd? I mean seriously... this would be PERFECT for my needs if it only had a2sd. I'm happy with a stock rom... i just want a2sd.
btate0121 said:
any plans to add a2sd? I mean seriously... this would be PERFECT for my needs if it only had a2sd. I'm happy with a stock rom... i just want a2sd.
Click to expand...
Click to collapse
Nope. Currently I don't use a2sd, or this rom really. I made this just for an optimized stock rom to bounce back to when needed. Currently I'm running a customized version of eugene's cm6 as my daily driver.
in your experience.. how hard would it be for a novice to add a2dp to this? I did a quick google and found about 3 good pages of data.. but it seems pretty complicated (packing and repacking boot.img looks to be pretty intense on a windows machine without any experience from what i can tell). Do you think i should attempt this? LOL.
dumfuq said:
Nope. Currently I don't use a2sd, or this rom really. I made this just for an optimized stock rom to bounce back to when needed. Currently I'm running a customized version of eugene's cm6 as my daily driver.
Click to expand...
Click to collapse
what is the difference between your customized version and the regular?
btate0121 said:
in your experience.. how hard would it be for a novice to add a2dp to this? I did a quick google and found about 3 good pages of data.. but it seems pretty complicated (packing and repacking boot.img looks to be pretty intense on a windows machine without any experience from what i can tell). Do you think i should attempt this? LOL.
Click to expand...
Click to collapse
what were the links they seem like the ones i have been looking for lol! i can already unpack and repack a boot.img im just looking for the steps i need to add to get aps2sd to work! i had a link explaining it but i cant find it anymore or google it!
well kitchen is for x10mini but x10mini is similar to x10 mini pro and x8 so it sould work... right?
thank you in advance...
http://forum.xda-developers.com/showthread.php?t=897662
Do you tried it? I would like to try it too, because i want to use app2sd, but the links are down. May you can upload the files a second time, please?
well
uploading last build.. dropbox says 4 min
Im thinking about this. With the standard method for rooting 2.1 this have to have sucess. Have this 'kitchen' a build in function for omit to build a system.sin?
oh right...
in my first post is link to my kitchen...
and in my signature is my rom...
testers are needed for kitchen,,,
but i fyou have balls you can test kitchen too ... lol..
I've used HTC kitchen and it work3d fine atleast for me
Oupps!! I changed the links... Sry, i will try your kitchen..
So... Has the bootloader cracked?
I think the rom kitchen works only in this case.
yes it works with image of SIN files
thanks on trying...
but i ment "testers needed for building x8 rom with this kitchen"...
so that i can see if it works.. on x8
Limit8 said:
Im thinking about this. With the standard method for rooting 2.1 this have to have sucess. Have this 'kitchen' a build in function for omit to build a system.sin?
Click to expand...
Click to collapse
Thats a very good point. I think the main issue will be the differences in hardware. Things like screen resolution and the camera. Chances are we would still be stuck with 2.1 but maybe we can make custom roms. If this is the case then all we need to do is crack the bootloader and start porting 2.2. If my experience with WM roms is anything to go by they'll be a group of phone specific files and the rest can be changed to match the build.
Hi, got a little question..
just want to know if you can use standard apps from 2.2.1 (like camera, and messages)
to include then in 2.1 rom?
like take the libcameraservice.so etc. and the apk from /system/app and replace them with
the ones from a 2.2.1 ROM
could it work?
thx
Not sure it will.. Often the camera is annoying at this point.. Why don't just flash a 2.2-rom? Then you will be able to use more of the "new" android functions as the push-messages/chrome-to-phone things?
mljjlm said:
Not sure it will.. Often the camera is annoying at this point.. Why don't just flash a 2.2-rom? Then you will be able to use more of the "new" android functions as the push-messages/chrome-to-phone things?
Click to expand...
Click to collapse
yeah i'm using 2.3 atm, but i want to obtain some knowledge about the system and try some things on an older ROM before messing with newer stuff noticed the camera being hard, don't even know if they'll fix it
Heya,
I have been trying to get pdroid running on Indie's Omega rom (http://forum.xda-developers.com/showthread.php?t=1663656), but as yet have been unable to. Currently using Omega v11 but have been trying since v9.
The latest method I have been trying is by using the Auto-Patcher by mateorod and pastime (http://forum.xda-developers.com/showthread.php?t=1719408). Every different type I have tried comes back with 'error: failed framework.patch'.
So, the main question is, has anyone gotten Pdroid running on Omega rom or a stock S3 deodexed, rooted, rom and if so what patcher/script etc did you use?
Uptil now I have been using LBE but from everything I have read I would be remiss not to use pdroid instead.
I know I could switch to Aokp, CM etc, however I really like Omega rom and would prefer sticking to it if I can.
As this is my first post I hope it is in the right place, if this is not the case I apologise and please feel free to delete or move it as is fitting.
Thankyou in advance!
EDIT: Really? No one has tried putting pdroid on an omega/sammy rom?? Or am I missing something (ie a better alternative, it's not possible, etc)
Iormangund said:
Heya,
I have been trying to get pdroid running on Indie's Omega rom (http://forum.xda-developers.com/showthread.php?t=1663656), but as yet have been unable to. Currently using Omega v11 but have been trying since v9.
The latest method I have been trying is by using the Auto-Patcher by mateorod and pastime (http://forum.xda-developers.com/showthread.php?t=1719408). Every different type I have tried comes back with 'error: failed framework.patch'.
So, the main question is, has anyone gotten Pdroid running on Omega rom or a stock S3 deodexed, rooted, rom and if so what patcher/script etc did you use?
Uptil now I have been using LBE but from everything I have read I would be remiss not to use pdroid instead.
I know I could switch to Aokp, CM etc, however I really like Omega rom and would prefer sticking to it if I can.
As this is my first post I hope it is in the right place, if this is not the case I apologise and please feel free to delete or move it as is fitting.
Thankyou in advance!
EDIT: Really? No one has tried putting pdroid on an omega/sammy rom?? Or am I missing something (ie a better alternative, it's not possible, etc)
Click to expand...
Click to collapse
Hmmm, PDroid hasn't been updated for a while and it was having problems with the latest ROMs in my old (faithful) Galaxy Mini, so maybe when a Universal Patcher comes out as promised by the developer we may be lucky. That is probably my most missed app. BTW, there were other patchers that are meant to continue on pdroid's so I guess you can try them, I haven't myself because I know very little about developing or creating ROMs, etc. I'm barely able to flash after reading the instructions about 32 times.
Unfortunately from what i understood that great tool of autopatchrr is working only on cms aosp and aokp.
We have to hope period owner will throw out a specific version of it for ics jb ...
Thought this thread got buried without a reply. New version of the autopatcher is out, is looking closer to working on non aosp/aokp roms. (if not already?)
The alternative I have been using is LBE security, not the market one as that isn't JB supported.
The english translation of the latest versions are here: http://forum.xda-developers.com/showthread.php?t=1422479
Still buggy but overall works well.
LBE is a security problem
Iormangund said:
Thought this thread got buried without a reply. New version of the autopatcher is out, is looking closer to working on non aosp/aokp roms. (if not already?)
The alternative I have been using is LBE security, not the market one as that isn't JB supported.
The english translation of the latest versions are here: http://forum.xda-developers.com/showthread.php?t=1422479
Still buggy but overall works well.
Click to expand...
Click to collapse
LBE is a closed source product. Devs are not responding. The app has complete root access.
=> BIG Security ISSUE
If you really go for security I would use this. Just answer for yourself:
Do you trust the manufacturer of LBE in a way that you open the complete phone for any access for them just to stop a couple of applications accessing your contacts? (just as an example ...)
Finally Noxious Ninja was able to run PDroid on Galaxy S3 with Stock ROM and TouchWiz!
But it's for the Verizon Version.
I hope with this the biggest obstacle is overcome. Maybe here is somebody able to make it analog for the International Version (I9300) and Omega Rom?
MysteryIII said:
Finally Noxious Ninja was able to run PDroid on Galaxy S3 with Stock ROM and TouchWiz!
But it's for the Verizon Version.
I hope with this the biggest obstacle is overcome. Maybe here is somebody able to make it analog for the International Version (I9300) and Omega Rom?
Click to expand...
Click to collapse
Awesome news, nicely spotted. Hopefully it wouldn't take too much to do it for the international. If I knew enough I would give it a go myself.
Been a long time coming.
Ninja didnt share the most important thing. How he managed to run the patcher on that ROM.
Maybe it would be already possible to create the patch.., we need to know how he achieve this. I was already writing in there
Inviato dal mio GT-I9300 con Tapatalk 2
any news ? :/
Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.