OK now i test the s2 version 
If don't work...i test the galaxy s version,because the screen size is 4",the motorola defy 3,7"
If don't work...i test the galaxy s version,because the screen size is 4",the motorola defy 3,7"
Last edited:
Surprised? I've been telling you guys that for the last couple days! That's why I'm anxiously awaiting brajesh to share what he had to do to get his JB build to work...OK now i test the s2 version
If don't work...i test the galaxy s version,because the screen size is 4",the motorola defy 3,7"
Isma1306 said:I manage to get the port from the S2 PA to the 12 quarx rom, but i have some issues (wifi VERY unstable, GPS doesnt work) but still dont have any FC. .....
Check this thread and see the release date of 1.98Another thing that's interesting is that he says to test S2 PA 1.98, but the latest I could find was 1.97![]()
a noob question : what are AOSP & AOKP ROMS..?Check this thread and see the release date of 1.98![]()
AOSP - Android Open Source Projecta noob question : what are AOSP & AOKP ROMS..?
how are they different from other normal roms, like quarx & eppy ones .. ?
thanks
Sent from my MB525 using XDA
Thats why i made this tool. You can port yourself!please make the Rom PARANOIDANDROID JB for defy&defy+
I will check your tool this sunday again and will see what's causing the ROM to get in bootloop. I've been porting from s2 and got success in all the version from 1.96 to 1.99JB doesnt work well. Try with ICS
Sent from my MB526 using xda app-developers app
No, If you make that kind of a tool then people will appreciate you.Are there provisions in the tool to make the necessary xml changes in the framework and recompile? Without those, you may get a rom to boot, but much of the hardware will be useless (like sdcard, wifi, backlighting, etc).
lol I'm sure! Aren't most of the changes (at least hardware wise) isolated to arrays.xml and generally consistent for a specific device?No, If you make that kind of a tool then people will appreciate you.