Related
So i just did a system dump of the Huawei P1 and i think the radio Might work i got all the Libs frameworks now need to modd it for CM10 + ICS
FM Radio
In ICS check the kernel Dir for Radio0
on Huawei its at dev/radio0
On Cm10 sys/class/video4linux/radio
must add android/hardware/fmradio to framework to jar to test
UsbHost
I think i saw in arcee commits its enabled in the kernel so i will attempt to use the libs from p1 + framework tweak to add android/hardware/usb
I also got the Camera App Which Imo is better than Stock CM10 Camera + ArcCamera it has panaroma + HDR it can adjust sharpness saturation exposure(not Lg's "Brightness" which they call exposure) and brightness + Contrast Red Eye Reduction Plus i think it uses custom Flash Pattern For camera the Issue with it is something is causing it fill the buffer and the app freezes when using Features that require the Huawei camera Library framework
Edit: No go radio Broadcom Chip Same as Prada.
Camera P1 Only Panorama HDR is implimented in CameraHal.
OTG Need OTG Cable to test.
defcomg said:
So i just did a system dump of the Huawei P1 and i think the radio Might work i got all the Libs frameworks now need to modd it for CM10 + ICS
FM Radio
In ICS check the kernel Dir for Radio0
on Huawei its at dev/radio0
On Cm10 sys/class/video4linux/radio
must add android/hardware/fmradio to framework to jar to test
UsbHost
I think i saw in arcee commits its enabled in the kernel so i will attempt to use the libs from p1 + framework tweak to add android/hardware/usb
I also got the Camera App Which Imo is better than Stock CM10 Camera + ArcCamera it has panaroma + HDR it can adjust sharpness saturation exposure(not Lg's "Brightness" which they call exposure) and brightness + Contrast Red Eye Reduction Plus i think it uses custom Flash Pattern For camera the Issue with it is something is causing it fill the buffer and the app freezes when using Features that require the Huawei camera Library framework
Click to expand...
Click to collapse
Hi defcomg,
Any progress on the USB host? I desperately hope that you can make USB OTG work on O3D!!!
schubeir
Please link me to the camera u speak of. I live HDR photography lol
Sent from my LG-P920 using xda app-developers app
---------- Post added at 05:59 PM ---------- Previous post was at 05:58 PM ----------
Well... when you got it kinda working lol
Sent from my LG-P920 using xda app-developers app
MIUI V4
Im trynna Patch Stock ICS so far so good Will Need Testers if it Builds can't test oN CM10 and I are to Lazy to flash ics and then back again:good:.
If It works i will try Patch CM10 Next
H8 my internet damn 99% Upload and then fail trying again
I Give up for now it's still failing
defcomg said:
I Give up for now it's still failing
Click to expand...
Click to collapse
Good luck uploading, is this a test for otg?
Sent from my LG-SU760 using xda app-developers app
defcomg said:
I Give up for now it's still failing
Click to expand...
Click to collapse
hahha -160kbs , how does that even make sense lol, hope you havent given up totally, i could try the patch rom if you want , im back on ported ics
defcomg said:
Im trynna Patch Stock ICS so far so good Will Need Testers if it Builds can't test oN CM10 and I are to Lazy to flash ics and then back again:good:.
If It works i will try Patch CM10 Next
Click to expand...
Click to collapse
Are you talking about miui patchrom?
Sent from my LG-P920 using xda app-developers app
rezzsha said:
hahha -160kbs , how does that even make sense lol, hope you havent given up totally, i could try the patch rom if you want , im back on ported ics
Click to expand...
Click to collapse
yeah it always shows incorrect upload speed only have 512kbps upload internet is crap in my country they expensive as **** lol I will try again if that fails I will just do the github thing and upload the patchrom I used the lu6200 as template
berni987654321 said:
Are you talking about miui patchrom?
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
I have already patched it that's the ROM for testing
Only error I had was compiling settings apk had to manually patch it and that was it
Sent from my LG-P920 using xda app-developers app
***********************************************************************************
wARNING THIS IS A TEST ROM MIGHT BOOT LOOP I DUNNO TEST AWAY BASED ON ICS
**************************************************************************************
MIUIV4-ICS.zip - 251.02 MB
i'll try it out soon
edit: doesnt go pass the lg Logo
rezzsha said:
i'll try it out soon
edit: doesnt go pass the lg Logo
Click to expand...
Click to collapse
i think its the updater script
Code:
set_perm(0, 0, 06755, "/system/xbin/invoke-as");
it should at the least bootloop it patched the framework files without issue the only apps i patched was Gallery and ArcCamera
okay i should edit my reply to ,it gets stuck on the lg logo, restarts after a bit , then goes into recovery
If you need a tester I'm running ICS and ready to brick my phone :good: .
I had some free time so I synced cm10.1 source and started compiling it. Already fixed some compiling errors but got into trouble with the LGInfineon.java will post details later
Sent from my LG-P920 using xda app-developers app
posted last lines on pastebin hope somebody has an idea
hey defcomg , so i tried the mui port you posted above ,and added the line to the updater-script and had samnos j/h kernel , and instead of rebooting i get stuck on the "secure booting unsuccessfull" black screen, ive already flashed the signed u-boot but still nothing. Anyone else tried it ??
berni987654321 said:
posted last lines on pastebin hope somebody has an idea
Click to expand...
Click to collapse
Only saw this now According to the 2X Forum you need to move that file the issue i think it's refrencing files that do not exist in that dir
device/lge/p920/ril/telephony/java/com/android/internal/telephony/
to
frameworks/opt/telephony/src/java/com/android/internal/telephony/
Click to expand...
Click to collapse
Code:
$ mv ~/cm10.1/device/lge/p920/ril/telephony/java/com/android/internal/telephony/LGEInfineon.java ~/cm10.1/frameworks/opt/telephony/src/java/com/android/internal/telephony/LGEInfineon.java
rezzsha said:
hey defcomg , so i tried the mui port you posted above ,and added the line to the updater-script and had samnos j/h kernel , and instead of rebooting i get stuck on the "secure booting unsuccessfull" black screen, ive already flashed the signed u-boot but still nothing. Anyone else tried it ??
Click to expand...
Click to collapse
Then Secure boot needs to be turned off in Ramdisk does it logcat? on that screen
ok I just copyd it to that folder and cept the old one in the p920 directory
will try it later
About the kernel:
This is an almost "stock" kernel for Android 4.2.2 and Sense 5.
Since we don't have any kernel source, i ported One XL 4.2.2 kernel to One S.
I tested it with MaximusHD and everything is working like stock orignal closed-source kernel, so this is a base for future custom kernels
Source:
https://github.com/anoane/ville-4.2.2-sense5-evitaul_porting
Donation:
http://forum.xda-developers.com/donatetome.php?u=2351000
Help me to buy an original HTC MHL Cable and an original HTC One X+ 2100mha battery, i'll try to add full battery support for One S and video-out at [email protected], i read somewhere that FullHD support is crappy
Changelog and dowload:
v0.2: first public version:
http://www.4shared.com/zip/prUybCsg/fabane_ville_13_09_13.html
v0.3: updated all ville-board-* files, fixed usb detection, usb charge and adb are working now
http://www.4shared.com/zip/eHUJyZe8/fabane_ville_13_09_13_v03.html
v0.6: wifi fixed using cyanogenmod/zarboz prima_wlan (compiled from source, now on a new branch)
http://www.4shared.com/zip/y1rp6zNK/fabane_ville_17_09_13_v06.html
v1.0: wifi fixed using flar2 patch (using stock prima_wlan from MaximusHD)
http://www.4shared.com/zip/1brHpu0i/fabane_ville_04_10_13_v10.html
v1.1: fixed incoming call quality issue
http://www.4shared.com/zip/NUW_ieLg/fabane_ville_14_10_13_v11.html
https://mega.co.nz/#!oVdSyJaY!LCxmKX3e6_UOYCIPUgHqJkHcM8pagVvgZTbb6nv8vrc
Did signal break in the process? Or was it already not working?
When I booted it it had no signal, so I guess it's not your fault
usaff22 said:
Did signal break in the process? Or was it already not working?
When I booted it it had no signal, so I guess it's not your fault
Click to expand...
Click to collapse
i'll try to check dmesg and logcat with some app, since usb/adb it's not working
but i have very little spare time now, so i posted my work until now, so someone can continue it
Oh yes, finally!
Great job here..
So you used stock sense 4+ kernel, and patched it with Evita kernel update?
Sent from my One S using Tapatalk 2
Thanks a lot Guy !!!
I'm very happy to see that! :good::good::good:
yes + some ville-board-* files (following evita-board changes) to compile it without errors
Wow ! That's good news
Envoyé depuis mon HTC One S avec Tapatalk 4
Does this mean htc 4.2.2 is not far away? And we will have sense 5 with it? Or it's just experimenting?
Thank you! If you need a tester I'm here for you..
Sent from my HTC One S using xda app-developers app
Good job, cant wait to use Sense 5 + 4.2.2 on my HoS!
good news, usb is detected now, battery charge and adb are working now, so i can get logcat and dmesg and fix problems easily
i think i finished to update board-ville-* files
i'll update git source and post a v0.3 test kernel soon
pirlano said:
good news, usb is detected now, battery charge and adb are working now, so i can get logcat and dmesg and fix problems easily
i think i finished to update board-ville-* files
i'll update git source and post a v0.3 test kernel soon
Click to expand...
Click to collapse
Any idea about the current buglist?
Sent from my One S using Tapatalk 2
RockR172 said:
Any idea about the current buglist?
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
i think we need a ported 4.2.2 rom to check them...
dmesg is pretty good
logcat show errors and crash, maybe rom related, maybe not
pirlano said:
i think we need a ported 4.2.2 rom to check them...
dmesg is pretty good
logcat show errors and crash, maybe rom related, maybe not
Click to expand...
Click to collapse
If you have been following the zenROM thread, me and usaff22 were trying to do the same, but the kernel never booted past the boot animation(technically it did, but nvm) and so we put it on hold until we had a booting kernel..
Now I don't have much time, since I got exams.. So maybe @usaff22 could help in the port of 4.2.2 based Sense..
Sent from my One S using Tapatalk 2
RockR172 said:
If you have been following the zenROM thread, me and usaff22 were trying to do the same, but the kernel never booted past the boot animation(technically it did, but nvm) and so we put it on hold until we had a booting kernel..
Now I don't have much time, since I got exams.. So maybe @usaff22 could help in the port of 4.2.2 based Sense..
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
me too, ****ing exams
btw, cannot use rom because of this error (phone is unusable), error is repeated thousand times:
Code:
E/AndroidRuntime(21591): FATAL EXCEPTION: main
E/AndroidRuntime(21591): java.lang.ExceptionInInitializerError
E/AndroidRuntime(21591): at com.android.providers.telephony.MmsSmsDatabaseHelper.<init>(MmsSmsDatabaseHelper.java:1063)
E/AndroidRuntime(21591): at com.android.providers.telephony.MmsSmsDatabaseHelper.getInstance(MmsSmsDatabaseHelper.java:1072)
E/AndroidRuntime(21591): at com.android.providers.telephony.SearchdbProvider.onCreate(SearchdbProvider.java:93)
E/AndroidRuntime(21591): at android.content.ContentProvider.attachInfo(ContentProvider.java:1085)
E/AndroidRuntime(21591): at android.app.ActivityThread.installProvider(ActivityThread.java:5516)
E/AndroidRuntime(21591): at android.app.ActivityThread.installContentProviders(ActivityThread.java:5097)
E/AndroidRuntime(21591): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5034)
E/AndroidRuntime(21591): at android.app.ActivityThread.access$1300(ActivityThread.java:162)
E/AndroidRuntime(21591): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1432)
E/AndroidRuntime(21591): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(21591): at android.os.Looper.loop(Looper.java:158)
E/AndroidRuntime(21591): at android.app.ActivityThread.main(ActivityThread.java:5751)
E/AndroidRuntime(21591): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(21591): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(21591): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1083)
E/AndroidRuntime(21591): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:850)
E/AndroidRuntime(21591): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(21591): Caused by: java.lang.NoClassDefFoundError: android.provider.Telephony$MmsSms
E/AndroidRuntime(21591): at com.android.providers.telephony.util.DatabaseMonitor.<clinit>(DatabaseMonitor.java:22)
E/AndroidRuntime(21591): ... 17 more
I/ActivityManager( 792): Start proc com.android.nfc for restart com.android.nfc: pid=21603 uid=1027 gids={41027, 3002, 3001, 1015, 1028}
W/ActivityManager( 792): Process com.android.phone has crashed too many times: killing!
I/ActivityManager( 792): Recipient 21591
I/ActivityManager( 792): Process com.android.phone (pid 21591) has died.
I/ActivityManager( 792): Start proc com.android.phone for restart com.android.phone: pid=21616 uid=1001 gids={41001, 3002, 3001, 3003, 5012, 1026, 5006, 5011, 1028}
D/PhoneStatusBar( 1253): updateIcon slot=nfc index=13 viewIndex=0 old=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=false num=0 ) icon=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=true num=0 ) compareIcon= name=bottom_divider_glow vis=false >> true
D/PhoneStatusBar( 1253): updateIcon slot=nfc index=13 viewIndex=0 old=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=true num=0 ) icon=StatusBarIcon(pkg=com.android.nfcuser=0 id=0x7f020005 level=0 visible=false num=0 ) compareIcon= name=bottom_divider_glow vis=true >> false
basically com.android.phone problem and nfc (we don't have nfc)
maybe @usaff22 already know the problem...how i can fix network signal and remove nfc stuff?
btw v0.3 uploaded on second post
EDIT: commit done
EDIT2: maybe i found the most important problem: sd cards (internal partition of course) seems not mounted, it will not save picture (camera and camcorder should be working): "Unable to save file to storage card due to insufficient file permissions", and i think it's a kernel problem, since i have the same behaviour with Sense 4+ too
I will post logcat and dmesg and try to fix sdcard mount
did you do anything to rom? like any kind of porting?
pirlano said:
EDIT2: maybe i found the most important problem: sd cards (internal partition of course) seems not mounted, it will not save picture (camera and camcorder should be working): "Unable to save file to storage card due to insufficient file permissions", and i think it's a kernel problem, since i have the same behaviour with Sense 4+ too
I will post logcat and dmesg and try to fix sdcard mount
Click to expand...
Click to collapse
The mount error might be from the Rom
I'm going to try with the kernel and stock 4.2.2 to see if I can help in any way nice work
Sent from my HTC VLE_U using Tapatalk 2
Flashalot said:
The mount error might be from the Rom
I'm going to try with the kernel and stock 4.2.2 to see if I can help in any way nice work
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
you left out a bunch of the fuse_sdcard stuff and other things fuse uses
but we dont need to emulate SDcard like other devices do since we have partiiton
rc420head said:
did you do anything to rom? like any kind of porting?
Click to expand...
Click to collapse
no, zero, untouched :silly:
Flashalot said:
The mount error might be from the Rom
I'm going to try with the kernel and stock 4.2.2 to see if I can help in any way nice work
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
i checked with adb and sdcard is mounted correctly, so maybe it's rom related
FOR EVERYONE:
The ROM IS NOT BOOTING YET. This thread is for DEVELOPERS ONLY, if you can't help me, don't post here,
and NO, I WON'T GIVE UP UNTIL WE HAVE A WORKING MIUI ROM.
Status: STUCK ON BOOTANIMATION
You can find more info on MIUI ROM right here: http://en.miui.com/
Changelog:
20140726: Ported from LG / Google Nexus 4
Based on MK4.44 20140726 nightly
20140705 #2: Based on latest 20140705 nightly
20140705: MIUI Patch ROM
20140704 #2: Base updated to "cm-11-20140704-NIGHLTY-falcon"
20140704: Some kernel changes
20140703: First build
Downloads:
20140726: http://www.androidfilehost.com/?fid=23578570567718880
20140705 #2: http://www.androidfilehost.com/?fid=23501681358557999
20140705: http://www.androidfilehost.com/?fid=23501681358557706
20140704 #2: https://www.dropbox.com/s/ws8ioh1kwdelhw6/miui_falcon_4.6.27_20140704_2.zip
20140704: https://www.dropbox.com/s/7blu7jpcvfp7xw1/miui_falcon_4.6.27_20140704.zip
20140703: https://www.dropbox.com/s/vql0c0yp50v4i9p/miui_falcon_4.6.27_20140703.zip
Working:
-
Not working:
-
Instructions:
1. Update recovery
2. Wipe Data / Factory Reset (Format /system if you want)
3. Install the ROM
4. Install GApps
5. Reboot
ROM Review (thanks to TechJunkieReviews):
Credits:
Google / AOSP
@kromuch
dhacker29
Cyanogenmod
MIUI (Xiaomi)
If you help me, your name will be here!
Did you build this, or did you just copy and paste files into a working rom? It'll be hard for a dev to help you if it wasn't built. (to my knowledge at least)
YoshiShaPow said:
Did you build this, or did you just copy and paste files into a working rom? It'll be hard for a dev to help you if it wasn't built. (to my knowledge at least)
Click to expand...
Click to collapse
Yes he ported according to me taking cm as base
And @K3VYNC did u port the kernel?
cant help unless the OP states what steps he / she has taken. we will know what files are missing and what framework needs modification
I working in the port of this from Patch_rom source .----. If any can help send me PM [DEV only and who have knowledge about this.]
EDIT:
did you make changes in bootclaspath in the ramdisk? because you need add directives of MIUI in the ramdisk
Cheers.
TeamMex said:
did you make changes in bootclaspath in the ramdisk? because you need add directives of MIUI in the ramdisk
Click to expand...
Click to collapse
Here is my kernel with shelld in ramdisk, recently I've ported MIUI to Moto G, but it had many software bugs, so, I deleted ROM and now have only ported kernel.
Flash this manually, it's not a flashable ZIP.
Pff we need work a lot xD
Code:
E/qdhwcomposer( 240): hwc_set_primary: display commit fail for 0 dpy!
E/qdhwcomposer( 240): configure: No pipes available to configure fb for dpy 0
E/qdhwcomposer( 240): hwc_sync: ioctl MSMFB_BUFFER_SYNC failed, err=Function not implemented
E/qdhwcomposer( 240): hwc_sync: acq_fen_fd_cnt=1 flags=16 fd=16 dpy=0 numHwLayers=2
E/qdoverlay( 240): Failed to call ioctl MSMFB_DISPLAY_COMMIT err=Function not implemented
E/qdoverlay( 240): static bool overlay::eek:verlay::displayCommit(const int&, const overlay::utils::Dim&): commit failed
E/qdhwcomposer( 240): hwc_set_primary: display commit fail for 0 dpy!
E/qdhwcomposer( 240): configure: No pipes available to configure fb for dpy 0
E/qdhwcomposer( 240): hwc_sync: ioctl MSMFB_BUFFER_SYNC failed, err=Function not implemented
E/qdhwcomposer( 240): hwc_sync: acq_fen_fd_cnt=1 flags=16 fd=16 dpy=0 numHwLayers=2
E/qdoverlay( 240): Failed to call ioctl MSMFB_DISPLAY_COMMIT err=Function not implemented
E/qdoverlay( 240): static bool overlay::eek:verlay::displayCommit(const int&,
TeamMex said:
Pff we need work a lot xD
Click to expand...
Click to collapse
@K3VYNC how you make mistakes? My port was successful with one try! However, some sensors and phone app did not work, but the phone worked. @K3VYNC, from which device you ported it?
im waiting for this YOHOO !! MIUI in MOTO G
i hope this will be avaialble on xt1033 variant
kromuch said:
@K3VYNC how you make mistakes? My port was successful with one try! However, some sensors and phone app did not work, but the phone worked. @K3VYNC, from which device you ported it?
Click to expand...
Click to collapse
Your port was from what device ?
it's more EASY make it from source
kromuch said:
@K3VYNC how you make mistakes? My port was successful with one try! However, some sensors and phone app did not work, but the phone worked. @K3VYNC, from which device you ported it?
Click to expand...
Click to collapse
instead of bashing, why dont you post your build or help the guy porting it?
TeamMex said:
Your port was from what device ?
it's more EASY make it from source
Click to expand...
Click to collapse
From the official Nexus 5 (adding to the OP)
Sent from my Moto G using XDA Free mobile app
K3VYNC said:
From the official Nexus 5 (adding to the OP)
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
maybe is better to port it from xiaomi mi2 due to the screen resolution
http://en.miui.com/download-2.html
kromuch said:
Here is my kernel with shelld in ramdisk, recently I've ported MIUI to Moto G, but it had many software bugs, so, I deleted ROM and now have only ported kernel.
Flash this manually, it's not a flashable ZIP.
Click to expand...
Click to collapse
I've added to the ROM
Sent from my Moto G using XDA Free mobile app
TeamMex said:
Your port was from what device ?
Click to expand...
Click to collapse
From Nexus 5 too.
K3VYNC said:
I've added to the ROM, I'm uploading later today
Click to expand...
Click to collapse
Does ROM boot now?
Important! Forgot to say that this kernel is from GPE ROM, so you must flash GPE before flashing MIUI, because Motorola ROM and GPE ROM use different file systems. If anyone give me last Moto-stock kernel (from backup or by another way), I'll add required files to it too. But for Moto-stock kernel must be Moto-stock based port, the same for GPE kernel.
kromuch said:
Yes, from Nexus 5 too.
Does ROM boot now?
Important! Forgot to say that this kernel is from GPE ROM, so you must flash GPE before flashing MIUI, because Motorola ROM and GPE ROM use different file systems.
Click to expand...
Click to collapse
Okay, thanks bro (added to the OP) and no, I couldn't test it.
And yes, I can send you the stock kernel
Sent from my Moto G using XDA Free mobile app
K3VYNC said:
Okay, thanks bro (added to the OP) and no, I couldn't test it, but it's uploading (almost DONE), can you test it?
And yes, I can send you the stock kernel
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
will download it and report...
Edit: download gets canceled at end moment.
The latest build gets an error 509
antarix said:
will download it and report...
Edit: download gets canceled at end moment.
The latest build gets an error 509
Click to expand...
Click to collapse
Try the latest one, tell me if something is changed.
Now I have dev acess to AndroidFileHost! :victory:
Sent from my Moto G using XDA Free mobile app
Cooooll, i watiiiing
Hello Everyone,
First of all, I don't want to earn credits to making this guide on how to install CM 11 on Xperia E3 (d2203) I'm just translating the tutorial made by #moiremoi
Warning: This modification of your phone state will remove the warranty. Moiremoi, FXPTeam, xda developpers staff or even myself will decline any responsability on possibles issues you could get by using this ROM, flashing or any method used from this tutorial.
REVIEW:
This ROM is an unofficial CM11 ROM created from the FXP Team. It is stable and final (this mean that there would not be any update anymore)
Its is 4.4.4 based
SCREENSHOTS:
HOW TO INSTALL:
Requirements:
Sony Xperia E3 d2203 (i don't tested other versions so idk if it works or not)
Unlocked bootloader
CWM or Teamwin Recovery
Rooted android 4.4.4 firmware 18.5.C.0.19
Better do a recovery of your phone state before doing any modification
Things to download:
CM 11 ROM : http://uploaded.net/f/zx9n6h/
GAPPS : https://www.androidfilehost.com/?fid=95916177934553399 (please take these for CM11 or Android 4.4.4)
Updater-Script: http://www.mediafire.com/file/400vsdcaasc9619/updater-script (modified "Updater-script" to avoid ''Leo'' error)
How to do:
- First of all, open the CM11 archive without unzipin it and navigate to "META-INF/com/google/android" and replace the existing "updater-script" file to the one required (link to download required file just over there)
- Copy and paste the CM11 + gapps zip to your SD card (just place it to sd, do not make it in any folder to retrieve it faster)
- Turn you phone on (or reboot it) and press many times the Vol + and Vol - at the booting sony screen to go on recovery mode
- Navigate into the menu and choose Wipe cache/data (if you forget to do a wipe, you just can forget to install the ROM)
- Then;
install zip from sdcard >> choose zip from sdcard >> (select ROM .zip) >> Yes
install zip from sdcard >> choose zip from sdcard >> (select GAPPS .zip ) >> Yes
Now, you just have to wait untill finish and choose reboot now
BUGLIST:
No NFC
Not really listed as bug but I find the audio power a bit lowered compared to Stock
Time of the phone battery charge (from 0 to 100%) a bit longer (it can depend on which usb you use too, maybe not a bug)
Camera, audio and every other sony related things are 100% WORKING
I will not help you if you occurs any type of errors, I installed this ROM and its working, If you don't know how to... just go ahead
Thanks and credits to:
FXP team for the ROM
Moiremoi for the modified updater script which is making the rom working and tutorial (on another website)
Myself for testing, editing and for screenshots.
(If I forgot someone please tell it to me through MP)
Have fun and enjoy your new CM11 ROM !
Regards,
Exerath
Well, this changes many...
So the error was only in updater-script?? How? I see you added these lines, but they shouldn't take any effect.
Code:
getprop("ro.product.device") == "leo" ||
getprop("ro.build.product") == "leo" ||
In build.prop on D2203, there isn't ANY ro.product.device value
When there is a bad value, updater-script stops installing, but when there isn't any value, it fallsback (assumes a virtual value) to leo, am I right?
Why the hell is just our device so different , we don't even have last_kmsg where it is supposed to be
Vynikal said:
Well, this changes many...
So the error was only in updater-script?? How? I see you added these lines, but they shouldn't take any effect.
Code:
getprop("ro.product.device") == "leo" ||
getprop("ro.build.product") == "leo" ||
In build.prop on D2203, there isn't ANY ro.product.device value
When there is a bad value, updater-script stops installing, but when there isn't any value, it fallsback (assumes a virtual value) to leo, am I right?
Why the hell is just our device so different , we don't even have last_kmsg where it is supposed to be
Click to expand...
Click to collapse
Can i do this process for d2212 xperia e3 model
jayesp0411 said:
Can i do this process for d2212 xperia e3 model
Click to expand...
Click to collapse
porting in progress.
no network.
D2212
---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------
Vynikal said:
Well, this changes many...
So the error was only in updater-script?? How? I see you added these lines, but they shouldn't take any effect.
Code:
getprop("ro.product.device") == "leo" ||
getprop("ro.build.product") == "leo" ||
In build.prop on D2203, there isn't ANY ro.product.device value
When there is a bad value, updater-script stops installing, but when there isn't any value, it fallsback (assumes a virtual value) to leo, am I right?
Why the hell is just our device so different , we don't even have last_kmsg where it is supposed to be
Click to expand...
Click to collapse
i downloaded cm11 from fxp and flashed it without editing updater-script it failed than i wipe data and cache then flashed it worked.
i was using my own latest cwm with fixed resolution.
(i have tested it with ported kernel)
device is leo bug was because old cwm was made for leo new fixed resolution is for flamingo.
so no bug,s
vinay said:
porting in progress.
no network.
D2212
---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------
i downloaded cm11 from fxp and flashed it without editing updater-script it failed than i wipe data and cache then flashed it worked.
i was using my own latest cwm with fixed resolution.
(i have tested it with ported kernel)
device is leo bug was because old cwm was made for leo new fixed resolution is for flamingo.
so no bug,s
Click to expand...
Click to collapse
I seen that you did a lot of great work for the E3, now I am just curious to know if you (or someone else reading this) can make the volume of CM11 a bit louder (aka stronger)
I reflashed stock 4.4.2 with Viper4Android on my E3 and the sound is drastically higher as with CM11+Viper4Android (On 4.4.4 xLoud is missing too, idk why, I tought it were a stock official firmware ??)
I checked every setting about sound but I don't see any error, could it be the sony XLoud thing (absent on CM11) which could make this issue with lower powered sound?
Searching on Google to ''install or flash xLoud" but no hope atm, I found nothing working (a lot of error flashing .zip but none working) :/
This is known on almost all devices. The volume is always lower on AOSP ROMs than on stock. Xloud isn't easy to add, only very good themers are able to include it. You have to understand Xloud is proprietary and not open-sourced.
Trust me, it was truly a shock, when I heard silent speakers of my old LWW with CM just installed
Vynikal said:
This is known on almost all devices. The volume is always lower on AOSP ROMs than on stock. Xloud isn't easy to add, only very good themers are able to include it. You have to understand Xloud is proprietary and not open-sourced.
Trust me, it was truly a shock, when I heard silent speakers of my old LWW with CM just installed
Click to expand...
Click to collapse
Volume was higher with cm 10 on my xperia J as on Stock, on AOSP we have the possibility to disable audio security imposed from governments, on stock not, that's why I asked
Thanks Exerath for thé translation !
you guy,s are lucky.
i am thinking why did i bought this dual variiant even if rom get ported to non lte dual sim still gona need porting for second sim support.
never gonna buy non lte or dual sim again.
even tho there is no lte in my area.
all i get is no baseband.
vinay said:
you guy,s are lucky.
i am thinking why did i bought this dual variiant even if rom get ported to non lte dual sim still gona need porting for second sim support.
never gonna buy non lte or dual sim again.
even tho there is no lte in my area.
all i get is no baseband.
Click to expand...
Click to collapse
Why not release it for d2202? Network might work for us
Finally updated to 4.4.4 xD
hell_lock said:
Why not release it for d2202? Network might work for us
Finally updated to 4.4.4 xD
Click to expand...
Click to collapse
Well uday tested it.
No network on d2202 even. I will upload it in free time.
problem is with ril.
(and before flashing cm11 if your wifi is off then it won't turn on. That's what i found. And i gave up. i can't fix ril tried replacing libril.so, refrences_ril.so and one more lib i forgot name. And tried thousands of combination of stock and cm11)
(i am not experienced in porting uploading kernel soon on this thread.)
Sent from my D2212 using XDA Free mobile app
D2202,d2212 support.
Port moved here => http://forum.xda-developers.com/xperia-e3/general/d2203-testers-cm11-t3179189
vinay said:
@Exerath can you give a link to this post on OP so other,s can find it easily.
STEPS
* DOWNLOAD boot.zip attached below.
* flash cm11 then flash this boot.img inside boot.zip.
it will work on d2202 and d2212
BUG,s
NO RIL NO BASRBAND (mean no network)
who is gonna fix bug,s => probably not me.
warning make sure your wifi is on before flashing cm11 or you can,t turn on after flashing cm11.
Click to expand...
Click to collapse
I will but not today, it is late and Im freaking ko
btw: If we flash your kernel, install hudge game and go back to normal, it would be working ? or not ?
Exerath said:
I will but not today, it is late and Im freaking ko
btw: If we flash your kernel, install hudge game and go back to normal, it would be working ? or not ?
Click to expand...
Click to collapse
Nope this is a just port kernel for d2202 and d2212.
Sent from my D2212 using XDA Free mobile app
Can i flash this on d2212 if yes what are the bugs????
Plz provide direct download link
Sent from my Moto G 2014 using XDA Premium 4 mobile app
amritmalviya said:
Can i flash this on d2212 if yes what are the bugs????
Plz provide direct download link
Sent from my Moto G 2014 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
just see two posts up thare is written everything.
Exerath said:
I will but not today, it is late and Im freaking ko
btw: If we flash your kernel, install hudge game and go back to normal, it would be working ? or not ?
Click to expand...
Click to collapse
no ril working then what is use of flashing cm11
Sent from my Moto G 2014 using XDA Premium 4 mobile app
amritmalviya said:
no ril working then what is use of flashing cm11
Sent from my Moto G 2014 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ril problem is just in d2212 and d2202 so other,s are enjoying it with ril.
back button and menu not work, how to solve?
entony80 said:
back button and menu not work, how to solve?
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------
easy solution.
use a hammer to press back button with full force.
-------------------------------------------------------------------------------------------
hard solution
try re flashing whole rom and wipe data/cache
--------------------------------------------------------------------------------------------
Hi，anyguys can help me ? I'm in trouble with multi ROM. I use sultan's CM13 as the primary ROM and I installed another ROM as the second ROM today . But I just can't choose to boot into the second one because it boots into the CM13 each time straightly. And by the way,I've changed the filesystem of data partition to f2fs,so does this matters? Could anyone tell me how to deal with this? I'll be appreciated ! (^_^)v
Sent from my A0001 using Tapatalk
Walter yzw said:
Hi，anyguys can help me ? I'm in trouble with multi ROM. I use sultan's CM13 as the primary ROM and I installed another ROM as the second ROM today . But I just can't choose to boot into the second one because it boots into the CM13 each time straightly. And by the way,I've changed the filesystem of data partition to f2fs,so does this matters? Could anyone tell me how to deal with this? I'll be appreciated ! (^_^)v
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Try to see in the multirom options list in the recovery or there are mentioned 2 roms, if so try to see if the timeout time is set to 1 sec or so and set it to 5 sec
wulsic said:
Try to see in the multirom options list in the recovery or there are mentioned 2 roms, if so try to see if the timeout time is set to 1 sec or so and set it to 5 sec
Click to expand...
Click to collapse
The timeout time is 5 seconds ,and there's only the second ROM in the multi ROM selection in recovery.
Sent from my A0001 using Tapatalk
Walter yzw said:
The timeout time is 5 seconds ,and there's only the second ROM in the multi ROM selection in recovery.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Is the multirome trampoline properly installed? try to patch the kernel else again/ install multirom trampoline:good: guess that's the issue