Hy all
I've tried to port a rom for my defy ^_^ and I'm blocking in the bootanimation of the rom. I would like do a logcat, however, adb says "waiting device"
Have you got an idea ? few advices ?
Thanks in advance.
kyle77680 said:
Hy all
I've tried to port a rom for my defy ^_^ and I'm blocking in the bootanimation of the rom. I would like do a logcat, however, adb says "waiting device"
Have you got an idea ? few advices ?
Thanks in advance.
Click to expand...
Click to collapse
Ok....so what are you porting from?
What are you porting? You may need to add to prop to persist adb not sure of the exact syntax but check to see in other roms...
Let me know
Thanks
I'm trying to port the last release of miui from galaxy s to defy.
Unfortunately, I go to bootanimation of ROM miui without logcat And in the build.prop : ADB is enabled with parameter 1.
Thanks
Ok.....
What are the resolutions for each?
Also what is your porting method.
Are the versions of android the same? Did you do smali mods which are most definitely needed
my defy has a resolution 480x854 pixels (WQVGA) and the galaxy s ....
For the method, I keep the last build from my cm10's defy and I replace some files like frameworks and apps ... so I keep the build.prop and updater script... But it is the good way ?
Hum... Finally.... our cm10 is based on 4.1.2 while the miui I'm trying to port is based on 4.2 So there is a problem ! Maybe downgrade to the last version of miui on 4.1.2 like our cm10?
And I don't have done smali mods .... but I'm searching on it
I can help u most likely with the port.....u need smali for miui...definitely and no miui is 4.2 its 4.1.2.
Pm me and i can show you how to do it all
change the default.prop in your boot image to the following
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
This should get adb working, If for some reason it doesn't you can explicitly start the adbd service in the init.rc file, just after the exports in the "on init" section normally does the trick
Code:
start adbd
Good luck!
Thanks trevd I will try later
And an other question.... It's possible to emulate my device to be sure that Rom boots ?
kyle77680 said:
Thanks trevd I will try later
And an other question.... It's possible to emulate my device to be sure that Rom boots ?
Click to expand...
Click to collapse
Not really, well not that I know of and besides you won't really need to once you've got adb going. ...
Thanks.
So can we, with adb, modify Rom from the PC without reboot our phone or always flash rom ?
Related
These roms are flashable with xRecovery 0.1 (backup restore)
update 1
slightly updated AOSP rom to try :
AOSP 2.1 v.0.1
update 2
firmware load fixed, vibrate fixed, some other small fixes.
AOSP 2.1 v.0.2
Todo:
Voicecalls (GSM/3G)
Location services
Google checkin provider
Camera
reserved.............
only if we could mount sdcard and start adb logcat we could investigate further..
It was nice to roam around in 2.2
If we want to create working rom we should know which files from the original ROM are the drivers so we can take them and try to put them in the custom rom.Otherwise froyo will not be able to interact with our specific hardware.
you can ask some one more experians in custom roms so he could recognise the drivers
even if he don't have x8
remember: just ask for help , dont be rude and ask for custom rom
sorry for my bad english and for my interrubed
i am building a working one please wait. i have discovered the drivers and etc.
When it will be ready for test?
trapacska said:
i am building a working one please wait. i have discovered the drivers and etc.
Click to expand...
Click to collapse
nice info... i will waiting
hugerth said:
When it will be ready for test?
Click to expand...
Click to collapse
i started, i trying, i will share it as soon as i can! i would not like to share sh*t, because the working rom is better than a wrong one.
It's just about changing drivers? I would be too easy I think...
hugerth said:
It's just about changing drivers? I would be too easy I think...
Click to expand...
Click to collapse
no, there is some conf file and etc what i have to change.
trapacska said:
no, there is some conf file and etc what i have to change.
Click to expand...
Click to collapse
Share your finds..
One error which i am constantly getting is concerning gralloc any idea whats it about?
trapacska said:
i started, i trying, i will share it as soon as i can! i would not like to share sh*t, because the working rom is better than a wrong one.
Click to expand...
Click to collapse
I want to try this as soon as possible it will be great to have froyo run on my X8.
Thank you for your effort.
And Happy New Year !
trapacska said:
i started, i trying, i will share it as soon as i can! i would not like to share sh*t, because the working rom is better than a wrong one.
Click to expand...
Click to collapse
Best of Luck mate....
any progress? any good news for 2.2 froyo for our x8s??
any updates about the custom 2.2 froyo rom ?
now a little bit work, but just some minutes, and it says system is not responding and restart, but not full restart, just it get to the boot animation and then start.
the first step: i have to make it work, patches and drivers the second step. i tryed much thing to get working it, and i am sure i am not as far as i was.
I really hope that you will get this running because as it seams this will be the only way to get Froyo or Gingerbread on our X8.
Hope you will make this works. And if I can help with something let me know.
Hope this helps zdzihu released sources for his x10 froyo rom
Zdzihu x10 froyo source
trapacska said:
now a little bit work, but just some minutes, and it says system is not responding and restart, but not full restart, just it get to the boot animation and then start.
the first step: i have to make it work, patches and drivers the second step. i tryed much thing to get working it, and i am sure i am not as far as i was.
Click to expand...
Click to collapse
Maybe it's power managment, display, or some other driver problem? Or kernel?
Hi there,
As I am developing my first apps for Android, I've run into an issue that bothers me. When trying to logcat (via terminal or Eclipse), this is the output I get:
Unable to open log device '/dev/log/main': No such file or directory
Click to expand...
Click to collapse
I've googled, but found solution only for Huawei devices (getting into service menu and activating logging) but it doesn't work with my P500. Everything (deploying , debugging) works just fine. BTW I am using NightlyFourE V4.1 ROM (that's Cyanogenmod 2.3.7) and linux workstation. Any help appreciated!
Sent from my LG-P500 using Tapatalk
Look for a tweak the same as that on the /system/etc/init.d folder
rm -r dev/log/main
or something similar to that and delete it..
Sent from my LG-P500 using Tapatalk
Coffei said:
Hi there,
As I am developing my first apps for Android, I've run into an issue that bothers me. When trying to logcat (via terminal or Eclipse), this is the output I get:
I've googled, but found solution only for Huawei devices (getting into service menu and activating logging) but it doesn't work with my P500. Everything (deploying , debugging) works just fine. BTW I am using NightlyFourE V4.1 ROM (that's Cyanogenmod 2.3.7) and linux workstation. Any help appreciated!
Click to expand...
Click to collapse
next you should use stock roms for testing and developing applications not modded ones
dnle71 said:
Look for a tweak the same as that on the /system/etc/init.d folder
rm -r dev/log/main
or something similar to that and delete it..
Click to expand...
Click to collapse
Thanks a bunch man! Worked like a charm..
trettet said:
next you should use stock roms for testing and developing applications not modded ones
Click to expand...
Click to collapse
I guess I should, but as long as it's my daily-driver I think I will prefer custom ROMs (i'm definitely not full-time developer, just a fan)..
Yes, we just got our own forums and YES it seems a bit pointless to be offering this up right away.
However, I've been reading up on ROM kitchens, etc, and I am *very* eager and excited to start playing with the newest ICS build for the Mediapad.
If anyone starts working on any CWM-9 based ROM, I would more than gladly be an active tester. My tablet currently acts as a daily Pandora-listening device, so I am more than willing to test nightly/bi-nightly/4x per day builds, whatever you request.
My tablet is at your command. Heck, if you need to remote into my PC to access the tablet, I can set up a dedicated computer connected to the Springboard, just for you.
Otherwise, I am also very much willing to temporarily donate/lend my device to a credible dev who would like to work on this.
great idea to start a thread like this..
i'm also willing to do alpha/beta testing of some new custom ROMs for our lovely MediaPad
Adreno 2xx drivers for ICS now available!!!
https://developer.qualcomm.com/deve...phics-optimization-adreno/tools-and-resources
zombolo said:
Adreno 2xx drivers for ICS now available!!!
https://developer.qualcomm.com/deve...phics-optimization-adreno/tools-and-resources
Click to expand...
Click to collapse
I have installed them on my huawei phone,-not noticed much difference.
patch
manual install
maybe try it on the pad? remember to edit build prop and set composition type to gpu.
mangoman said:
I have installed them on my huawei phone,-not noticed much difference.
patch
manual install
maybe try it on the pad? remember to edit build prop and set composition type to gpu.
Click to expand...
Click to collapse
Wouldn't the ICS build we're running already have this driver?
I'm working on a CM9 port now but it'll be my first ROM ever so it's slow going haha. It will happen though.
i think they're already on the MediaPad, but we can try this...
anybody can post a short list of steps, how to install it on the MediaPad?
or is it just as simple as extracting the zip to /system folder and modifying the build.prop?
i've checked the files on mediapad already:
- /system/etc/firmware -> has the "leia" and "yamato" files, but doesn't have the "a255" and "a300" files...
- /system/lib -> this folder doesn't exist at all
hiko36 said:
I'm working on a CM9 port now but it'll be my first ROM ever so it's slow going haha. It will happen though.
Click to expand...
Click to collapse
that's excellent news hiko36
let us know if you need testing, or anything we can provide you with, to help you on this journey
Klacik said:
i think they're already on the MediaPad, but we can try this...
anybody can post a short list of steps, how to install it on the MediaPad?
or is it just as simple as extracting the zip to /system folder and modifying the build.prop?
i've checked the files on mediapad already:
- /system/etc/firmware -> has the "leia" and "yamato" files, but doesn't have the "a255" and "a300" files...
- /system/lib -> this folder doesn't exist at all
that's excellent news hiko36
let us know if you need testing, or anything we can provide you with, to help you on this journey
Click to expand...
Click to collapse
Yes, they are already there and they are more performance oriented than the genaral drivers (NenaMark2: 33.2 fps for the general driver vs. 37.9 for the one already there). Tried it by adb pushing the new driver files to the mediapad.
€: /system/lib did not exist on your device? What firmware do you use?
mblaster said:
Yes, they are already there and they are more performance oriented than the genaral drivers (NenaMark2: 33.2 fps for the general driver vs. 37.9 for the one already there). Tried it by adb pushing the new driver files to the mediapad.
€: /system/lib did not exist on your device? What firmware do you use?
Click to expand...
Click to collapse
thanks for the information.. i'm not going to try it then
i'm using the ics b010, but the /system/lib exists.. i must've been blind or something.. maybe i've looked ih /system/etc... sorry, my bad
Hey guys,
Do you believe it would be possible to get Team Win Recovery Project on our devices? Because it looks much better than clockworkmod and it has so great functions! But I don't know much about this recovery; if this is only for nexus devices or Samsung or whatever, I just wanted to ask
It looks like they took the AOSP recovery and built it on top, but do you think it would be possible on xperias?
Sent from my Nexus 7 running Android 4.2.1
Okay it looks like we could give it a try and compile it, so would anybody be interested?
Who wants to know what TWRP is could look here!
There is a working recovery for the Xperia S, so maybe we could get one, too? Any developer who would be interested in that?
mihahn said:
Hey guys,
Do you believe it would be possible to get Team Win Recovery Project on our devices? Because it looks much better than clockworkmod and it has so great functions! But I don't know much about this recovery; if this is only for nexus devices or Samsung or whatever, I just wanted to ask
It looks like they took the AOSP recovery and built it on top, but do you think it would be possible on xperias?
Sent from my Nexus 7 running Android 4.2.1
Click to expand...
Click to collapse
I am pretty sure it can be done, because I am pretty sure there is support for mdpi screens (320x480). Thomas1991_12 compiled it for the Ray and I know that it wasn't easy and that ChampionSwimmer helped him out with the dual ramdisk kernel. The instructions from dees_troy are pretty easy to follow but of course it didn't work right out of the box but Thomas1991_12 might be able to help you out. Here is the final product thread: http://forum.xda-developers.com/showthread.php?t=2046977 and here is the dev thread: http://forum.xda-developers.com/showthread.php?t=1948097. It is also working on the X8 at least for ics.
TWRP is really nice. It has some added features which are nice but it is also a lot faster than CWM, at least on my device.
justmpm said:
I am pretty sure it can be done, because I am pretty sure there is support for mdpi screens (320x480). Thomas1991_12 compiled it for the Ray and I know that it wasn't easy and that ChampionSwimmer helped him out with the dual ramdisk kernel. The instructions from dees_troy are pretty easy to follow but of course it didn't work right out of the box but Thomas1991_12 might be able to help you out. Here is the final product thread: http://forum.xda-developers.com/showthread.php?t=2046977 and here is the dev thread: http://forum.xda-developers.com/showthread.php?t=1948097. It is also working on the X8 at least for ics.
TWRP is really nice. It has some added features which are nice but it is also a lot faster than CWM, at least on my device.
Click to expand...
Click to collapse
I would like to see this done, too, but I'm no developer at all, never did anything regarding kernels. I could try to get the recovery image, but I wouldn't know what to do after that. And if there are many errors I couldn't go on, so maybe a "real" dev could do it
Do you think we could even try to do this with cm10.1 cyanogenmod sources or better sync to cm9?
Edit syncing my repos to cm9, let's see how it works!
Okay I'm trying it on cm9, what to do with this error? I thought there was something to delete but not sure
Code:
make: *** Keine Regel vorhanden, um das Target »bootable/recovery/res/images/icon_firmware_error.png«,
benötigt von »out/target/product/mango/root/res/images/icon_firmware_error.png«, zu erstellen. Schluss.
Can you help me?
EDIT: Got it by deleting the whole #PRODUCT_COPY_FILES like explained here, but after flashing with
Code:
fastboot flash boot recovery.img
I get the FreeXperia logo and a black screen. What to do now?
mihahn said:
Okay I'm trying it on cm9, what to do with this error? I thought there was something to delete but not sure
Code:
make: *** Keine Regel vorhanden, um das Target »bootable/recovery/res/images/icon_firmware_error.png«,
benötigt von »out/target/product/mango/root/res/images/icon_firmware_error.png«, zu erstellen. Schluss.
Can you help me?
EDIT: Got it by deleting the whole #PRODUCT_COPY_FILES like explained here, but after flashing with
Code:
fastboot flash boot recovery.img
I get the FreeXperia logo and a black screen. What to do now?
Click to expand...
Click to collapse
obviously, debug. as its been said by justmpm it wont just work out of the box just like that. u probably need to to ask Thomas1991_12 what he changed in the source to get it working for ray. since all xperia 2011 gen share similar hardware, ray config should work for other 2011 phone too with minimal changes.
an0nym0us_ said:
obviously, debug. as its been said by justmpm it wont just work out of the box just like that. u probably need to to ask Thomas1991_12 what he changed in the source to get it working for ray. since all xperia 2011 gen share similar hardware, ray config should work for other 2011 phone too with minimal changes.
Click to expand...
Click to collapse
I wrote him a PM, hope he could help me :good:
Can't thank you for now because the 8 thx limit
mihahn said:
I wrote him a PM, hope he could help me :good:
Can't thank you for now because the 8 thx limit
Click to expand...
Click to collapse
I think Thomas1992_12 might be taking a holiday, as he isn't replying to questions in his kernel threads.
I never tried to compile with cm9 but with cm10 the black screen is where I got stuck. Thomas1992_12 was able to get past this point and if I remember correctly, the problem is with init.rc. If you check the ray dev thread, he has a solution for getting past it. After you fix this, you will
probably face the "ghost touches" on the screen and then you will have to figure out how to boot into recovery. Again, Thomas and/or ChampionSwimmer will probably be able to give you the fixes. But don't give up....you are really close!\
justmpm said:
I think Thomas1992_12 might be taking a holiday, as he isn't replying to questions in his kernel threads.
I never tried to compile with cm9 but with cm10 the black screen is where I got stuck. Thomas1992_12 was able to get past this point and if I remember correctly, the problem is with init.rc. If you check the ray dev thread, he has a solution for getting past it. After you fix this, you will
probably face the "ghost touches" on the screen and then you will have to figure out how to boot into recovery. Again, Thomas and/or ChampionSwimmer will probably be able to give you the fixes. But don't give up....you are really close!\
Click to expand...
Click to collapse
Thanks, I really want this project to be done!
First I downloaded the TWRP bootable/recovery sources as a zip, but the zip was named ..-jb-..zip so now after some research I'm trying it with ...-master-...zip and I hope I will get past this black screen. The init.rc is the one from TWRP, because I replaced the whole bootable/recovery folder with the files/folders from the master zip...
I think I will ask championswimmer, but I guess he is very busy, because he's such a great dev! :good:
GUYS I GOT IT! WORKING!!! TOUCH IS WORKING VERY WELL!!!
BUT!
I just flashed the cm9 FXP kernel and after that I flashed the recovery image. I plugged off and powered on and it's booting straight into TeamWinRecovery 2.2.2.1, hope somebody could help me to get booting in system.
Time is wrong, but touch is working guys
Will upload it for testing purpose if you want :good:
Working:
Touch
File Manager
Settings
Terminal Command
Onscreen Keyboard
Flashing Files
Wiping Cache/Dalvik Cache
Backup
Locking Phone in Recovery
Need to test:
Mount usb (not working in linux, will test with windows tomorrow)
Restore
Changing time zone
Not working:
Booting into system
Click to expand...
Click to collapse
mihahn said:
GUYS I GOT IT! WORKING!!! TOUCH IS WORKING VERY WELL!!!
BUT!
I just flashed the cm9 FXP kernel and after that I flashed the recovery image. I plugged off and powered on and it's booting straight into TeamWinRecovery 2.2.2.1, hope somebody could help me to get booting in system.
Time is wrong, but touch is working guys
Will upload it for testing purpose if you want :good:
Click to expand...
Click to collapse
You the man!!! You the man!!!
ChampionSwimmer has the fix for getting it to boot correctly. The one set up on the ray has dual recovery: hit the power key and you go into twrp, hit vol dwn and you get cwm.
Keep up mihahn, I want TWR so bad, that I can't sleep
Come on mihahn! You can do it!
Sent from Hubble Telescope
Okay guys I will upload it for testing and wait until Championswimmer can help me :good:
Okay guys go here if you want to see the progress or try it yourself
Hallo, this is unoficialll MIUI V5 for Xperia Go based on STOCK JB rom!
First thing that I must to say is "disclaimer":
Everything that is not originally maded by Sony is custom thing, so everything from here is modified Sony files and these files is "custom files"! So before you go to play with these modified files keep in mind that everything from here is custom thing and you installing these things on your own risk! I no want and I will not be responsible if something go wrong, if you lost your private data, if your device can not boot ...etc...etc, you doing everything on your own risk!!! If you no want to risk than skip this thread!!!
Rom is complete but not for daily use! All patches is welcome!
git:
https://github.com/munjeni/miui_v5_lotus
[QUOTE [...] ]have some popup messages with error to phone apk[/QUOTE]
:good:
First impressing after looking through rom-folders is framework-res is "mighty fat". Its nearly double-sized than stock ones.
I have no time to check framework-res because I need to fix smali bugs which prevent first "stable" screen. If some one want to contribute and fix remaining bugs, here is temp folder -> http://munjeni.homeunix.com/temp after initial patchings so we need to look into reject folder and fix remaining smalis to get rom working! If some one patched (and tested) something please attach it here (only working things!) !
My git is here -> https://github.com/munjeni/miui_v5_lotus
Because Micode have no mdpi apks I used them from MIUI V5_MINI PRO_3.4.19
Good news for you, got it!
How to:
remove Phone.apk from /system/app (phone can not boot using this apk! Only a way by now is removing them. Framework smalis need patchings to get this apk and mobile networks working!)
remove Provision.apk from /system/app (Whats use of this apk???)
remove SEMCSetupWizard.apk from /system/app (phone can not boot using this apk)
replace android.policy.jar using file from attachment
Install these modified zip and you are done :good:
You can start reporting everything about this rom! Rom need a lot of work and I have no free time by now to work in them, hope some one use them and patch all remaining bugs! This rom you can use as a base! Hope Sola, P and U guys use this rom and finish them! Rom is 80% finished, 20% is bugs! Enjoy!!!
munjeni said:
Good news for you, got it!
How to:
remove Phone.apk from /system/app (phone can not boot using this apk! Only a way by now is removing them. Framework smalis need patchings to get this apk and mobile networks working!)
remove Provision.apk from /system/app (Whats use of this apk???)
remove SEMCSetupWizard.apk from /system/app (phone can not boot using this apk)
replace android.policy.jar using file from attachment
Install these modified zip and you are done :good:
You can start reporting everything about this rom! Rom need a lot of work and I have no free time by now to work in them, hope some one use them and patch all remaining bugs! This rom you can use as a base! Hope Sola, P and U guys use this rom and finish them! Rom is 80% finished, 20% is bugs! Enjoy!!!
Click to expand...
Click to collapse
Ok :good:
I got this rom compiled, signed, installed without errors, but get BL after Kernel. So, i will try your hints. Maybe it need to fix also some things in build.prop.
akkufix said:
Ok :good:
I got this rom compiled, signed, installed without errors, but get BL after Kernel. So, i will try your hints. Maybe it need to fix also some things in build.prop.
Click to expand...
Click to collapse
No need to edit build.prop its edited by default by micode, only you need to use 2 libs from stock rom (libhwui.so and libjni_latime.so) and one binary (installd) and add them to your rom zip, allso you can use all frameworks from current rom and add to your rom zip, allso you need to add shelld service to ramdisk, and allso you need to remove some apk from your zip (see previous post) and you will get rom working!
Make sure compile hdpi apks instead of xhdpi (you need to find where is xhdpi definition and change them to hdpi)... !
Edit:
Forgot to let you know something. You need:
adb shell chmod 06755 /system/xbin/*
adb shell chmod 755 /system/bin/*
...because some files have no right permission!
munjeni said:
No need to edit build.prop its edited by default by micode, only you need to use 2 libs from stock rom (libhwui.so and libjni_latime.so) and one binary (installd) and add them to your rom zip, allso you can use all frameworks from current rom and add to your rom zip, allso you need to add shelld service to ramdisk, and allso you need to remove some apk from your zip (see previous post) and you will get rom working!
Make sure compile hdpi apks instead of xhdpi (you need to find where is xhdpi definition and change them to hdpi)... !
Edit:
Forgot to let you know something. You need:
adb shell chmod 06755 /system/xbin/*
adb shell chmod 755 /system/bin/*
...because some files have no right permission!
Click to expand...
Click to collapse
Sure, i already put "local-density := HDPI" in makefile
Permissions... i didn't look after the in xbin - /bin is set.
Good news for P guys Got booted for Xperia P
Working: Launcher, Statusbar, Toggles and also task manager!
not working: anything else (even file explorer won't open and get reboot on lock! but will try to fix )
EDIT:
got working other Mi programs by replacing android.policy.jar (so it's a smali bug) but modems are not working and settings is a bit miss sized
will try to fix these :good:
hope we can get a fully working MIUI V5 :fingers-crossed:
Well, since you have working build you can start patching frameworks. You no need to use patchrom anymore, just simple using apktool you can patch a rest of smalis trought "reject" folder / reading logcat...
sijav said:
Good news for P guys Got booted for Xperia P
Click to expand...
Click to collapse
great news! good job!
why don't u share ur work with dron_GTR or dimon2242 from the xperia p dev section? they worked on MIUI before and can maybe help patching
go for some teamwork and we have MIUI v5 up and running in no time
teamwork is the best work
thanks munjeni! thanks devs!
tapatalked!
stothegee said:
great news! good job!
why don't u share ur work with dron_GTR or dimon from the xperia p dev section? they worked on MIUI before and can maybe help patching
go for some teamwork and we have MIUI v5 up and running in no time
teamwork is the best work
thanks munjeni! thanks devs!
tapatalked!
Click to expand...
Click to collapse
I recently buy Xperia P didn't know these guys but thnx and will share with them
Indexed
Added to Index :highfive: keep up the great work!
hey Munenji..
I love miuiv5 .. but i can't download this torrent.. and can you tell that when will you fix its bugs and make it ready for daily use .
Maybe never, maybe soon, I don't know! Now I am very satisfied with stock rom + ex.se and simple thinking stock rom is better that MIUI, so no need by now to waste time in making bug clean MIUI v5 Hope some one use them and finish them?!
well, all the good stuff from miui are in the ex.se so..
And for those who want the "iphonish" look, just ad the miui launcher found at playstore
I just love MIUI music Player, sad that is not ported to another rom
Sent from my Xperia Go using xda app-developers app
@munjeni - Have you tried building the ROM on top of the latest firmware available? Maybe the changes needed with it are less troublesome.
Fortun said:
@munjeni - Have you tried building the ROM on top of the latest firmware available? Maybe the changes needed with it are less troublesome.
Click to expand...
Click to collapse
Porting MIUI will ever be difficult for our phones, because we haven't "standart hardware", like ST-E U8500 chip, mali gpu and some other things. So, whatever rom we would like to port needs to get the drivers for that. It would be quiet easier, if we have a Qualcomm chip and an Andreno gpu.
akkufix said:
Porting MIUI will ever be difficult for our phones, because we haven't "standart hardware", like ST-E U8500 chip, mali gpu and some other things. So, whatever rom we would like to port needs to get the drivers for that. It would be quiet easier, if we have a Qualcomm chip and an Andreno gpu.
Click to expand...
Click to collapse
true, but MIUI sure is worth it
wouldn't it be easier to wait for a stable cm10 and use that to port from another cm10 based rom?
Sent from my LT22i using Tapatalk 4 Beta