Related
We have 2 phones with have same chipset and kernel 3.0.x
http://www.gsmarena.com/huawei_u8860_honor-4197.php
Huawei u8860
Chipset Qualcomm MSM8255T Snapdragon
CPU 1.4 GHz Scorpion
GPU Adreno 205
http://www.gsmarena.com/htc_one_v-4575.php
Chipset Qualcomm MSM8255 Snapdragon
CPU 1 GHz
GPU Adreno 205
link for one v sources(3.0.16)
houwei u8860(3.0.8)
:highfive:
Or eaven porting form CAF (3.0.23)
CAF kernel link
Guys ho porting from CAF are using RAY, MINI , LWW , NEO , so no dev form here was join that project
That all from me
[/B]
This howto is working only with 2.6.32.X kernel, when this project will be finished will add HOWTO for 3.0.8
You need linux machine, i don't know it is possible on Windows and if so i don't help you with that!!!
1. Download toolchain.
Download toolchain and extract it to /opt/ directory.
Should looks like:
Code:
/opt/arm-eabi-4.4.3/
2. Set up evn.
Edit your:
Code:
~/.bashrc
file and add at the end of file this two rows:
3. Download kernel - 2.6.32.9.
You can download kernel sources from J repo Doomlord or other repo, and extract to ~/kernel/, this kernels has already needed drivers etc.
4. Compile kernel:
When i'm compiling kernel i'm doing it in this way:
5. Output files.
6. Create boot.img
- Swap kernel and modules and then:
- Creat boot.img
Extract files here /usr/local/bin and set permissions to 755.
are u trying the impossible? lol.. if this is possible it should have happened before during the x10 days. you're just wasting your time bro.
dyepnoodle said:
are u trying the impossible? lol.. if this is possible it should have happened before during the x10 days. you're just wasting your time bro.
Click to expand...
Click to collapse
NO , im now learning C and C++ code
Look here a lot of people think Galaxy S plus will not get 3.0 , same you think for xperia 2011 phone , but look here its link for galaxy s plus 3.0.43kernel. Evertying is posibole only need siklz
It is possible.
3 devs are working on it
they got help from a Sony dev.
They know how to get it booting
1 dev is rewriting the clock for 2011 devices and an other the last board fixes and then it will boot
nickholtus said:
It is possible.
3 devs are working on it
they got help from a Sony dev.
They know how to get it booting
1 dev is rewriting the clock for 2011 devices and an other the last board fixes and then it will boot
Click to expand...
Click to collapse
can you give me link .
ps: how much mony your freind zack have?(for repair phone)
did you fix ril?(for sense 4.0A)
Hi, look at github.com/kamarush
3.0 kernel isn't updated in a few days, but they are still working on it
He has (not 100% sure) $12.00
Ril is still not working, waiting for help from htc devs
I dno why but the thread for donations is gone, without letting me know
Sent from my Xperia P using xda app-developers app
any update on this?
sjondenon said:
any update on this?
Click to expand...
Click to collapse
Here is backport of 3.0.8 form xperia s
https://github.com/tkymgr/KTG_test
Thats all,but we now have nAa on our side...i hope he will done it in future
here is naa sources LINK
N1kolaa, im available for testing/compiling anything, i cant code C, C++, i only know Java, can you set up an IRC channel so we can meet ?
For C let me know if you need help with it. I may not be of great help but can to some extent
Is there a cifs.ko module for Xperia Z?
I'd like to use CifsManager to mount some shares.
I have a rooted XZ, with locked bootloader.
Edit: I read that the modules needed are: cifs.ko, md4.ko, nls_utf8.ko?
Bump.
I have a rasther large music collection on my NAS. It would be nice to access it directly as a mounted share.
So, for the last few days, I look xda forum looking for how to get my XZ to work with cifs module in KitKat. Your best bet would be to build it yourself. So I need a linux machine, the kernel sources, sdk, some knowledge in unix, and patience. With each of the above I have some problems especially with access to the pc (my 3 year old daughter watching Winnie the Pooh and Mickey Mouse on YouTube
But suppose I have needed kernel modules (cifs.ko, md4.ko etc.) and in addition they need custom or stock kernel will work with them?
Of course, the drawback of kernel modules built is that it almost certainly will not work after the upgrade. This begs me to another idea. Porting a function of the newer models xperia you got above Z1- Remote Shares. http: //forum.xda-developers.com/showthread.php?t=2753926 No native support for Samba in the Z / ZL is very sad. Maybe to one of the prominent developer/porters would be able to get it working.
Wysłane z mojego C6603 przy użyciu Tapatalka
Hi all, if your goal is simply to play music and video from your NAS to your android device, you can use Kodi (xbmc) that can access cifs path directly!
Unofficial CyanogenMod 10.1
Rom: Unofficial CyanogenMod 10.1
Android version: 4.2.2
Status: Alpha (means not ready as beta or even stable release!)
What doesn't work:
Sound partially, only calls not working right
Wifi
GPS
Bluetooth
Brightness control
Airplane mode
Camera, did work though in earlier version
Disclaimer
I am not responsible for bricked devices, broken hearts, thermonuclear war or you getting fired because the alarm app failed. It's up to you, not to me.
Click to expand...
Click to collapse
Downloads:
Google Drive CM10.1
Mirror, hosted by Burn02
The version differences:
Code:
24/2/14
[LIST]
[*] Using new audio hall
[*] Microphone works now, call still doesn't
10/2/14
[LIST]
[*] Initial audio support
[*] Fixed Wifi symlink for MAC-adres
[*] ICS_AUDIO_BLOB disabled
[/LIST]
01/12/13
[LIST]
[*] ICS_AUDIO_BLOB enabled
[*] Using original audio blobs
[/LIST]
14/11/13
[LIST]
[*] Both Internal storage and external storage working
[*] Build modified init from source
[*] Dalvik with x86 houdini support
[*] More modules build from source
[/LIST]
6/11/13
[LIST]
[*] Only internal storage working
[*] Libc with x86 wrappers support
[*] Pixelflinger/charger with x86 encoder support
[*] Ramdisk changes
[*] Android Build fixes for x86
[*] Add intel specific codes
[/LIST]
Workarounds:
The Rom can bootloop when installed in TWRP. If so use CWM instead for a while till TWRP is working correctly.
Want to help?
This Rom is made by many people that contribute to it, if it is in code, new information or just bug logs. Everybody can help. Make a 'Logcat' about the problems u encounter and post them here. Give a brief explanation of what u did and wanted to archive (we will try our best to get them sorted, eventually) or contribute with code into my github at the moment.
Click to expand...
Click to collapse
Source:
https://www.github.com/HazouPH
About the sound:
When using the rom zip with ICS_BLOBS_ENABLED and adding the right files:
etc/parameter-framework/*
etc/sound.conf
etc/audio_effects.conf
etc/media_codecs.xml
etc/phonecall_es305b_*
lib/hw/alsa.smi.so
lib/hw/audio.primary.smi.so
lib/hw/audio_policy.smi.so
lib/parameter-framework-plugins/*
lib/libasound.so
usr/lib/alsa-lib/*
usr/share/alsa/*
The rom will bootloop and the mediaserver will crash with a log file. See attachment. If u have any idea on how to solve it, i would happily like to know.
Hazou said:
About the sound:
When using the rom zip with ICS_BLOBS_ENABLED and adding the right files:
etc/parameter-framework/*
etc/sound.conf
etc/audio_effects.conf
etc/media_codecs.xml
etc/phonecall_es305b_*
lib/hw/alsa.smi.so
lib/hw/audio.primary.smi.so
lib/hw/audio_policy.smi.so
lib/parameter-framework-plugins/*
lib/libasound.so
usr/lib/alsa-lib/*
usr/share/alsa/*
The rom will bootloop and the mediaserver will crash with a log file. See attachment. If u have any idea on how to solve it, i would happily like to know.
Click to expand...
Click to collapse
Good work Hazou !
I will give you some idea. And why don't you use JB libs ?
1. Replace mediaserver by ICS one
2. Replace /system/lib/hw/audio.primary.smi.so by CyanogenMod file
3. There is a problem with libc.so, so just try to replace this lib with ICS one....
4. Replace /system/lib/libat-manager.so (if exist) by CM one
Do these steps one by one and logcat for each step.
GalaxyUser
GalaxyUser said:
Good work Hazou !
I will give you some idea. And why don't you use JB libs ?
1. Replace mediaserver by ICS one
2. Replace /system/lib/hw/audio.primary.smi.so by CyanogenMod file
3. There is a problem with libc.so, so just try to replace this lib with ICS one....
4. Replace /system/lib/libat-manager.so (if exist) by CM one
Do these steps one by one and logcat for each step.
GalaxyUser
Click to expand...
Click to collapse
Ty, for the suggestions. Some i can already answer
1. We could try this, but then also the libaudioflinger needs replacing. And maybe another file.
2. Can try it, but most likely doesn't work. The stock cyanogenmod one doesn't have the right code the execute our soundcard. I found out that the audio_policy.smi.so is the stock one with just small modifications.
3. Libc can't be switched. To many things depend on libc. And besides that, the code in libc were it goes wrong is the same one as my modified jb libc
4. libat-manager is a specific module for our device. we don't have the right sources to build it. But i can maybe replace it with the one from the 4.2.2 drop of the chineze version. But then it has some restrictions because off the chinese firewall.
Keep up the ideas. Maybe we get there someday
Hazou
Hazou said:
Ty, for the suggestions. Some i can already answer
1. We could try this, but then also the libaudioflinger needs replacing. And maybe another file.
2. Can try it, but most likely doesn't work. The stock cyanogenmod one doesn't have the right code the execute our soundcard. I found out that the audio_policy.smi.so is the stock one with just small modifications.
3. Libc can't be switched. To many things depend on libc. And besides that, the code in libc were it goes wrong is the same one as my modified jb libc
4. libat-manager is a specific module for our device. we don't have the right sources to build it. But i can maybe replace it with the one from the 4.2.2 drop of the chineze version. But then it has some restrictions because off the chinese firewall.
Keep up the ideas. Maybe we get there someday
Hazou
Click to expand...
Click to collapse
Thanks for answer.
1. Try to replace libaudioflinger.so, then provide a logcat please. It may need hex edit (and I can do it).
4. Yes try it because sound need this lib.
I think first answer is the best... If the rom allow logcat access after replacement.
Edit 1: my Razr I is broken but I would like to help
Edit 2: Sound is very hard to works on porting rom (even if it's not the same thing with CM), so perhaps it needs some others files to change
Edit 3: Try to replace these libs too, with the chineze version:
/system/lib/libamc.so
/system/lib/libevent-listener.so
And you need to add FM's lib because ICS libaudioflinger.so needs these files:
Code:
12-05 16:14:35.939 527 527 E AudioHardwareALSA: Cannot load FM HW Module
http://xt890.blogspot.com.ar/2013/12/101-rom-cyanogenmod-build-3-para.html the site over there claims that the wifi is working..can you have a look?
EDIT: the rom download link is your google drive
Hazou said:
Unofficial CyanogenMod 10.1
Click to expand...
Click to collapse
Thanks!.. is a great news...
antkalaitzakis96 said:
http://xt890.blogspot.com.ar/2013/12/101-rom-cyanogenmod-build-3-para.html the site over there claims that the wifi is working..can you have a look?
EDIT: the rom download link is your google drive
Click to expand...
Click to collapse
Y' i know. He asked permission tot post it
Wifi working isn't a very big problem. I want to first hopefully fix the sound, or hope that some ideas might help.
Sent from my GT-P5110 using XDA Premium HD app
Hey can somebody post some screenshots ??
I don't think it's the right thread to post screenshot. This thread is for helping to develop and make all features work.
great .. thanks @Hazou
Enviado desde mi Moto usando Tapatalk
ICuaI said:
I don't think it's the right thread to post screenshot. This thread is for helping to develop and make all features work.
Click to expand...
Click to collapse
What would be the thread to post in, other than the one who actually presents the rom we are taking screenshots of?
hotpokets said:
What would be the thread to post in, other than the one who actually presents the rom we are taking screenshots of?
Click to expand...
Click to collapse
You don't need a screenshot, if this doesn't work yet. This is a thread to make the rom functional. Then it can be released to the regular users like us, who just want to use it regardless of the making process
You can go in every CM10.1-thread in this forum. I am sure that you will find enough screenshots of CM10.1. The rom for our xt890 doesn't have another look.
Or try this alpha-build on your own phone
And now for me I'll stop being of topic
Sorry for that to all the devs
GalaxyUser said:
Thanks for answer.
1. Try to replace libaudioflinger.so, then provide a logcat please. It may need hex edit (and I can do it).
4. Yes try it because sound need this lib.
I think first answer is the best... If the rom allow logcat access after replacement.
Edit 1: my Razr I is broken but I would like to help
Edit 2: Sound is very hard to works on porting rom (even if it's not the same thing with CM), so perhaps it needs some others files to change
Edit 3: Try to replace these libs too, with the chineze version:
/system/lib/libamc.so
/system/lib/libevent-listener.so
And you need to add FM's lib because ICS libaudioflinger.so needs these files:
Code:
12-05 16:14:35.939 527 527 E AudioHardwareALSA: Cannot load FM HW Module
Click to expand...
Click to collapse
So, i tested the methods u supposed.
first off, the roms doesn't need the fm module to work It's like the usb and hdmi audio modules that are expanding the audio functions, but aren't necessary for booting.
Than the rest, i found out that all the libamc, libevent*, libat-* etc. the files were we don't have the source from are the same as the stock jelly ones. So no need to change those. Like the other libs, mediaserver is the same as the one i compiled compared to the chinese 4.2.2 one.
For the libaudioflinger part, if i switch them, they won't boot up there service anymore. Why i doný know, but i have the feeling that the libaudioflinger won't solve the mystery.
Another thing i read from the logcat is that it crashes right at the moment the sound-card (medfieldaudio) aka 0x00000002 is called, after it is set that it can be used. So it seems to me that the alsa lib can't read the device properly. Somewhere allong the line a thing can't reach it or is giving the wrong data. But what....
The next thing i gonna try is making my own alsa module with tinyalsa implementation. To get only the sound working. FM and the audience driver won't work then. Great chance that it won't work, but you gotta try
Hazou said:
So, i tested the methods u supposed.
first off, the roms doesn't need the fm module to work It's like the usb and hdmi audio modules that are expanding the audio functions, but aren't necessary for booting.
Than the rest, i found out that all the libamc, libevent*, libat-* etc. the files were we don't have the source from are the same as the stock jelly ones. So no need to change those. Like the other libs, mediaserver is the same as the one i compiled compared to the chinese 4.2.2 one.
For the libaudioflinger part, if i switch them, they won't boot up there service anymore. Why i doný know, but i have the feeling that the libaudioflinger won't solve the mystery.
Another thing i read from the logcat is that it crashes right at the moment the sound-card (medfieldaudio) aka 0x00000002 is called, after it is set that it can be used. So it seems to me that the alsa lib can't read the device properly. Somewhere allong the line a thing can't reach it or is giving the wrong data. But what....
The next thing i gonna try is making my own alsa module with tinyalsa implementation. To get only the sound working. FM and the audience driver won't work then. Great chance that it won't work, but you gotta try
Click to expand...
Click to collapse
Will this ROM work on Lenovo K900?
charming.arpit said:
Will this ROM work on Lenovo K900?
Click to expand...
Click to collapse
Not out of the box, no.
Sent from my GT-P5110 using XDA Premium HD app
intel released source code for android 4.4
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
if its helpful
Did you guys saw this?
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
drunk_ryder24 said:
http://software.intel.com/en-us/articles/android-4-4-kitkat-x86-emulator-system-image
if its helpful
Click to expand...
Click to collapse
hey this is just
Android* 4.4 (KitKat) x86 Emulator System Image
this is for developers who running a pc (x86) and want to emulate the newest android.
this has nothing to do with our fone.
i think the problem is, this image dont got the drivers for our device.or any drivers expect for emulation.. dont know but thanks for the info that intel is developin
regard
Hi everyone !
I've seen on the forums for the GS2 that there has been a port for this device, so I think we could also port that on our phone. I've also seen that another thread has already been created, but it hasn't been updated since a while.
I already started working on multi window a few weeks ago, by trying to apply the tutorial I found about modifying android.policy.jar and SecSettings.apk (and some more files) and it didn't work well, because of a simple reason : in pur framework, there are not all of the files we need to port multi window. I request your help to try to find out what files / components we should modify. I think some parts of android.policy.jar are missing (in comparison to the S2 one) but I haven't had enough time to investigate
Perhaps we should also look at the first JB builds for S Advance : they could contain the framework properties we are looking after
I'm already waiting at your feedbacks about my idea(s), and will try to reply to you as soon as possible (I'm not doing development during the next two weeks, and I'm not sure I'll have some internet
Good luck if you have the courage to begin this hard work. I'll do my best to support you and to port it on my site !!!
Edit : if you are interested, I will try to attach my first .zip update (it doesn't work but it shows the files we must modify or add)
Have a look... And dude imo this thread should be in Q&A
Current progress of this project -> http://forum.xda-developers.com/showthread.php?p=43252806
Sent from my GT-P3100 using Tapatalk
Well it seems like this thread is a little bit abandoned... There also hasn't been lots of progress (IMO). And I would like to make this project a community project, where everyone can help
Sent from my GT-I9070 using xda app-developers app
I respect your decision to make a multi window working mod for our device. But since we have just a 4 inch screen it wouldn't be helpful. We already have multi window OmniRom working but I never used that feature at all. Just my 2 cents.
Sent from my GT-I9070 using Tapatalk
Hey guys I have got some great news for Xperia E1 and E1 dual users. There is going to be a CyanogenMod 11 Port for these two devices. I have been working on this port and 50% of it is done.
Once I have a stable version I will post the link for the ROM and might start porting CM12 for Xperia E1/E1 Dual.
but i need help from some people. Right now the xperia e1 is stuck at the cm11 boot logo.
It would be grateful if some could assist/help me so I can port the rom quickly.
I'll keep you guys updated.
We discontinued for a reason.
Any Custom rom for E1 Will not be possible. EVER.
It has been repeated enough times already.
If you didn't notice, you could have first tried the "basic" porting
Such as searching another MSM8210 phone with a CM port and try copying Xperia E1's system files into the port ROM
The reason it will not work is because the lib files does not communicate with other Android ROMs other than Sony's stock ROM
Either hack the libs, search for similar "drivers", or wait for Sony to release AOSP support for this device (which I assume they will never give support for this phone...)
Sadly we can't do anything about it, we tried everything. The only way to boot into CM on E1 is trying the above I typed.
Regardless of this, I will help you out. Just mentioned this to let you know
I can help you with logcat logs If needed, and trying out test builds
I don't know what's wrong with some people. There are ports for other xperia devices but not for xperia e1. Rather than saying it's impossible you should help each other. Just because you can't do it doesn't mean they it's impossible.
Sent from my D2005 using XDA Free mobile app
jalp_14 said:
I don't know what's wrong with some people. There are ports for other xperia devices but not for xperia e1. Rather than saying it's impossible you should help each other. Just because you can't do it doesn't mean they it's impossible.
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
You say it like we never tried it before. Saatvik, who's good at porting stuff apparently failed porting both CM11 and 12 for E1
Not because he does not have the knowledge to do it, it's the phone itself that is holding him back.
A guy who works at Sony said this that we should not bother with E1 as it's system files (Sony vendor) will never communicate with Cyanogenmod at all, no matter how we struggle to make it work. (This includes AOSP as this phone does not have AOSP support)
OK now I understand what you are saying.
Sent from my D2005 using XDA Free mobile app
Xperia E1
Xperia e1 should have AOSP suppourt.
There is a article from tomshardware that says all the 2014 xperia devices with qualcomm chip is getting AOSP support from Sony.
Xperia E1 was released in 2014 and has a Qualcomm chip so it should hae AOSP suppourt.
jalp_14 said:
Xperia e1 should have AOSP suppourt.
There is a article from tomshardware that says all the 2014 xperia devices with qualcomm chip is getting AOSP support from Sony.
Xperia E1 was released in 2014 and has a Qualcomm chip so it should hae AOSP suppourt.
Click to expand...
Click to collapse
"Xperia E1 can not be added to our AOSP project because there is no support for msm8210 (Snapdragon 200) in AOSP and our goal is to build a clean AOSP without patches
Google AOSP code https://android.googlesource.com/ can be a good place to check which devices can be added to AOSP"
I hope this will open your eyes.
---------- Post added at 04:50 PM ---------- Previous post was at 04:32 PM ----------
However I still does not understand why Sony vendor (msm8210) does not work with Cyanogenmod, they said It will not communicate because It has no AOSP support, and Cyanogenmod is a heavily edited AOSP rom
From what I've been experienced in the last 6 months, It is simply Sony that does not care about E1. Low budget phone, weak components, etc. You know the rest
We could hack msm8226 libs to work with msm8210, but when It is finally finished, everyone else will have a better phone than E1
This doesn't make any sense
Other phones with snapdragon 200 like Moto E and ZTE Open C has cynogenmod why????
Sent from my D2005 using XDA Free mobile app
jalp_14 said:
This doesn't make any sense
Other phones with snapdragon 200 like Moto E and ZTE Open C has cynogenmod why????
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
E1 is Europe exclusive == It is not available in the USA
I've seen petitions regarding CM port for E1 (and AOSP), it is useless, nobody will do it.
Can we do something like you said hack the lib files
Sent from my D2005 using XDA Free mobile app
jalp_14 said:
Can we do something like you said hack the lib files
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not an Android expert, nor good at Hex editing
If you could find someone who could do it, then there's a small chance that we can get Cyanogenmod
I found out that Xperia E1 has AOSP suppourt. Look at the screenshot attached https:
Kizoky said:
If you didn't notice, you could have first tried the "basic" porting
Such as searching another MSM8210 phone with a CM port and try copying Xperia E1's system files into the port ROM
The reason it will not work is because the lib files does not communicate with other Android ROMs other than Sony's stock ROM
Either hack the libs, search for similar "drivers", or wait for Sony to release AOSP support for this device (which I assume they will never give support for this phone...)
Sadly we can't do anything about it, we tried everything. The only way to boot into CM on E1 is trying the above I typed.
Regardless of this, I will help you out. Just mentioned this to let you know
I can help you with logcat logs If needed, and trying out test builds
Click to expand...
Click to collapse
Also I downloaded the AOSP build for Xperia E1 and it has the Kernel and the lib file
jalp_14 said:
Click to expand...
Click to collapse
https://www.dropbox.com/sh/fldeqf2kglrlwh2/AAB5zVOOrsG74ST8EaMna1oMa?dl=0
jalp_14 said:
https://www.dropbox.com/sh/fldeqf2kglrlwh2/AAB5zVOOrsG74ST8EaMna1oMa?dl=0
Click to expand...
Click to collapse
No, It has NO AOSP Support
While the kernel (MSM8210) is not owned by Sony, they are forced to release every kernel files (source files) If asked
That is only the kernel, nothing more (Which is useless)
And how about LG L70? It uses MSM8210, and have a working CM 11 port.
Zsenyka said:
And how about LG L70? It uses MSM8210, and have a working CM 11 port.
Click to expand...
Click to collapse
We can try it. But I don't think Wi-Fi and Bluetooth will work though
Here's the CM 11: androidforums.com/threads/unofficial-cyanogenmod-11-for-lg-l70-d320-d320n-d325.890205/
And it has CM 12 too: androidforums.com/threads/unofficial-cyanogenmod-12-for-lg-l70-d320-d320n-d325.893621/
(I can't post outside links yet :/)
CM11
Found another phone with MSM8610, it also has CM 11: modaco.com/forums/topic/373214-devrom88-cyanogenmod-11-android-444-for-zte-open-c-kis-3/