Related
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
I am browsing through touchpad development forums and trying to decide which ROM to install. It seems some have working camera while others have Bluetooth, does anyone know of a ROM which has both camera and Bluetooth working?
venkythegeek said:
I am browsing through touchpad development forums and trying to decide which ROM to install. It seems some have working camera while others have Bluetooth, does anyone know of a ROM which has both camera and Bluetooth working?
Click to expand...
Click to collapse
Evervolv 4.3.1
8)
and also i believe cm 10.1 does
Problem with KitKat
Hello ,
I have not had success with version 3 kernel . After installation the system is in a loop trying to make the Cyanogenmod boot without success. Appears at a time, Moboot screen and then the screen goes black ( dimly lit ) ... Then the system reboots .
I used Tailor to create the partitions :
USB ( media) : 1.953 MiB
User ( ext3 ) : 1.758 MiB
Android (system ) : 600 MiB
Android ( cache ) : 200 MiB
Android (date ) : 23,148 GiB
Unused Space : None
I created a folder with name cminstall with the following files (all downloaded through the appropriate links) :
cm - 11-20140110 - UNOFFICIAL - tenderloin.zip
GAPPS - kk - 20131208.zip
moboot_038 - tenderloin.zip
recovery - clockwork - 6.0.4.6 - tenderloin.zip
I reseted the WebOS Touchpad through and hit the volume button until the USB connection symbol appeared. Finally , as with all Novacom drivers installed on your computer I entered the following command in the Windows command prompt :
novacom.exe boot mem :/ / < ACMInstaller5M
The system installation appears to be correct , but the system is in boot loop .
Any help is welcome .
Grateful.
CM10 has a working camera, not yet in CM11.
it's not easy to bring the camera to live on 3.x kernels mostly because of qualcomm's proprietary camera stuff. I'm working on this for about month and still have no success.
Did you try to contact qualcomm? What, if they provide you with the information you need??? That would be wonderful.....
ranjib said:
Did you try to contact qualcomm? What, if they provide you with the information you need??? That would be wonderful.....
Click to expand...
Click to collapse
Forget about getting anything from Qualcomm. Tried once and I was redirected to Code Aurora Forum and then at CAF told me that all they have is pushed to git and there's no chance to get any missing headers from them or any information. So every time I need to figure out everything on my own basing on those pieces posted to CAF.
so is cm9 still the only rom with everything working?
anonxlg said:
so is cm9 still the only rom with everything working?
Click to expand...
Click to collapse
No, the CM10.x and CM11 running 2.6.35 kernel has also a working camera. It's not yet working with 3.4 kernel.
I've created a separate thread for camera driver development for 3.x kernel: http://forum.xda-developers.com/showthread.php?t=2611497
_Dorregaray_ said:
Forget about getting anything from Qualcomm. Tried once and I was redirected to Code Aurora Forum and then at CAF told me that all they have is pushed to git and there's no chance to get any missing headers from them or any information. So every time I need to figure out everything on my own basing on those pieces posted to CAF.
Click to expand...
Click to collapse
Thank you for the answer. It sounds like you're quite angry about that.
If I was native English speaker and also a coding freak I would make another try at Qualcomm. Perhaps someone who reads this and knows a little about hardware programming can ask again?
My programming skills stopped with Sinclair ZX81 programming (more or less successful). Z80 machine language called. It's a long time ago. Sorry, I'd love to help in any way....
_Dorregaray_ said:
No, the CM10.x and CM11 running 2.6.35 kernel has also a working camera. It's not yet working with 3.4 kernel.
I've created a separate thread for camera driver development for 3.x kernel: http://forum.xda-developers.com/showthread.php?t=2611497
Click to expand...
Click to collapse
Possible explanation installation
Possible explanation installation driver development for 3.x kernel
Evervolv nondata rom from 10 feb still has a crashing cam too bad, no skype.
Cm11 on hp touchpad success
i finally got cm 11 on my hp touchpad and the camera works but is very narrow. my head looks long. not evervolv. cyanogenmod. i will be posting video's on my channel soon
camera still doesnt work
MrGHLover said:
i finally got cm 11 on my hp touchpad and the camera works but is very narrow. my head looks long. not evervolv. cyanogenmod. i will be posting video's on my channel soon
Click to expand...
Click to collapse
i have tried the latest milaq evervlov and invisilek builds and my camera still doesnt work with default app
Google Camera App and JCS CM11
venkythegeek said:
i have tried the latest milaq evervlov and invisilek builds and my camera still doesnt work with default app
Click to expand...
Click to collapse
Just installed [4.4.2] [CyanogenMod 11 by Jcsullins] [DM] [04/09/14] and then installed the new Google Camera app. HPTP camera works better than it ever has!
My AOKP build has working camera no problem
Sent from my TouchPad using xda app-developers app
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
See device specific install instructions
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device Specifics
Install Instructions:
Unlock your bootloader
Follow these instructions
Credits:
@m11kkaa - for the pointer about kernel dt
@JackpotClavin - for the easier patch for touchscreen
Confirmed to work on XT1021, XT1022, XT1023
Latest Unofficial Download Here
kernel source
Device Tree
Changelog:
TWRP 2.7.2.0 V2.2
bump to V2.7.2.0
built against TWRP internal trees
TWRP 2.7.1.0 V2.1
bump to V2.7.1.0
TWRP 2.7.0.0 V2.0
touch bug fixed
backlight bug fixed
built against the latest caf kk_3.5 rb head (unreleased yet. I'll push it tomorrow hopefully)
TWRP 2.7.0.0 V1.2
Fix external SD mounting (I've only just found my card)
Remove unnecessary partitions from the mounting menu
TWRP 2.7.0.0 V1.1
Add dt kernel, allows for the recovery to boot normally (Thanks @m11kkaa)
Strip out unneeded files, so it will fit in the partition
TWRP 2.7.0.0 V1.0
Initial build
touch doesn't work until screen has turned off then back on
Do not flash! Only boot it
Support:
Live support is available via #MotoE on Freenode with your IRC client, or just click this link.
cybojenix said:
TWRP 2.7.0.0 V1.0
Initial build
touch doesn't work until screen has turned off then back on
Click to expand...
Click to collapse
Yay! We have a custor recovery! Thanks cybojenix, will try and report back ASAP. Now all we need is the kernel source, go Moto!
Yeaah!! Cheers!! Hope all bugs get fixed soon!!
And thanks for device tree too!!
OK guys, you're good for flashing twrp now. find any issues, don't be shy and pop up on here or freenode channel #MotoE
How to unlock bootloader?
Sent from my XT1022 using XDA Free mobile app
Same as other Moto devices
startracker said:
How to unlock bootloader?
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
startracker said:
How to unlock bootloader?
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Evander_F said:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Click to expand...
Click to collapse
Added the link to the main thread. danke for the reminder
New build up, fixes external SDcard
cybojenix said:
Added the link to the main thread. danke for the reminder
Click to expand...
Click to collapse
And Thank you for the recovery ...v.1.1 installed successfully.
cybojenix said:
So here it is, TWRP for the Moto E
Click to expand...
Click to collapse
So it should work once I Suspend the device using power button?
Or do I have to wait till the black screen?
deej_roamer said:
So it should work once I Suspend the device using power button?
Or do I have to wait till the black screen?
Click to expand...
Click to collapse
you need to wait till the black screen, then press the power button
cybojenix said:
Touch won't work until after the device has suspended. I'll patch this once kernel source is up.
Click to expand...
Click to collapse
You might want to ask some of the Moto G developers about how they fixed touch for that device, since I remember a similar issue for quite a while with TWRP on Moto G
jonovw said:
You might want to ask some of the Moto G developers about how they fixed touch for that device, since I remember a similar issue for quite a while with TWRP on Moto G
Click to expand...
Click to collapse
I was planning on just removing the suspend/resume code from the touch driver, which will force it to stay enabled
cybojenix said:
I was planning on just removing the suspend/resume code from the touch driver, which will force it to stay enabled
Click to expand...
Click to collapse
This supports selinux kernal right?
Sent from my XT1022 using XDA Free mobile app
startracker said:
This supports selinux kernal right?
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
yes
I am an idiot. D:
Edit: For those who didn't read OP like I did. Touch doesn't work until the screen times out for now.
cybojenix said:
So here it is, TWRP for the Moto E
Device tree added here
Download Here
Click to expand...
Click to collapse
Hello
Is there any chance you can create a version that would probably work in a non Moto E phone but shares most of the internals (ie MSM8610, Adreno302, etc).?
I've tried to boot it on a MSM8610 non-Moto E phone bit am getting the "Fastboot boot image : dtb not found" error.
kenshinta said:
Hello
Is there any chance you can create a version that would probably work in a non Moto E phone but shares most of the internals (ie MSM8610, Adreno302, etc).?
I've tried to boot it on a MSM8610 non-Moto E phone bit am getting the "Fastboot boot image : dtb not found" error.
Click to expand...
Click to collapse
Which device? There are two ways to do a dtb. Appended, or as a separate image.
You can get the stock dt image using unpackbootimg. If there isn't one there, it's appended to the zImage, in which case just remove the stuff about dt in BoardConfig
Sent from my Nexus 7 using Tapatalk
cybojenix said:
I was planning on just removing the suspend/resume code from the touch driver, which will force it to stay enabled
Click to expand...
Click to collapse
Hi,
I thought that this post might help you - http://forum.xda-developers.com/showpost.php?p=49122115&postcount=129
I'm building TWRP for Xperia T2 Ultra and am experiencing the exactly same touch screen problem. Although enabling the TW_IGNORE_MAJOR_AXIS_0 in the BoardConfig didn't work for me, it might just fix the problem for you I guess
Regards,
abcdjdj
I have an micro usb DVBt dongle which runs fine on my Samsung Note 10.1 2014 Edition but not on my new z3c. I have a rooted stock rom 23.1.A.0.690. Did Sony forget to add the drivers??
Sent from my D5803 using XDA Free mobile app
No other explanation, I guess, besides no drivers. USB-OTG works, tested with keyboard & mouse.
yeah i know host mode is active but android does not know the device...
maybe the kernel modules could be compiled as modules ? loadable with modprobe / insmod? (v4l ,... )
does anyone has a arm crosstoolchain for testing?
Any ideas how to get this working? Got a Tivizen Pico and facing the same problem.
SailfishOS for Xperia XZ
Obviously very beta-quality, but calling, wifi, camera etc. should be working.
Instructions: Please see sx.ix5.org: SailfishOS Installation on Xperia XZ
Don't ask for dualsim or bluetooth or whatever, come help fix it instead.
Everything you need to get up and running for development are the manifests:
manifest
local_manifests
Please do not clutter this thread with your "reviews" or bug reports. We are only interested in genuine development here.
XDA:DevDB Information
SailfishOS for Xperia XZ, ROM for the Sony Xperia XZ
Contributors
local__hero
Source Code: https://github.com/marina-bay
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest .192 stock firmware
Based On: AOSP
Version Information
Status: Beta
Created 2019-03-19
Last Updated 2019-03-19
Reserved
Reserved
Is it possible to update the base to the lastest Sailfish 3.0.2 ?
TalhaGirgen9 said:
Is it possible to update the base to the lastest Sailfish 3.0.2 ?
Click to expand...
Click to collapse
The sources are all there, sadly I have no time rn.
In the spirit of this being a development forum, I'd be glad if someone picked up the work.
I have also collected a lot of info on how sailfish's build system works at sx.ix5.org/foresail, and you can always ask in #sailfishos-porters on IRC - it takes a while to get an answer, but they're nice folks, mostly.
I definitely would love to use sfos as my daily driver
Its a shame that it almost got no interest in here and the lack of android support is the thing thats holding me down.
Since im not into building and stuff (mainly cause of dont have decent hardware&connection combo rn) i cant really help but if you work on sfos anytime soon feel free to let me know.
Innovative gui, especially like these sensible gestures instead of typical navigation bar.
Howto install usualAndroid applications there? Tried to download total commander from direct download link on http://ghisler.com but after downloading apk sailfish says "unknown file type, impossible to open"
pawwaap said:
Innovative gui, especially like these sensible gestures instead of typical navigation bar.
Howto install usualAndroid applications there? Tried to download total commander from direct download link on http://ghisler.com but after downloading apk sailfish says "unknown file type, impossible to open"
Click to expand...
Click to collapse
Unfortunely the android support on sfos is not open source, that means you cant really get it working on community ports afaik.
It's so pitty, this sfos gui is made by an artist! It's so nice and sensible!
Any chance to port it to usual Android e.g. as a installable launcher app?
I'v tried the steps on my xperia xz, but when i reboot the phone stuck on the logo "Sony",
After all i'll retest it again.
I also tried it.
Can confirm it stuck on the sony logo with notification light turns white.
Is there a possibility to install dalvik to run Android Apps? XA2 license will work? Thanks.
Edit: sorry, you can delete this comment.
I don't understand
Can you give me specific instructions for this step?
Then run these commands manually in the device’s recovery, e.g. TWRP:
rm -rf /data/.stowaways/sailfishos/
mkdir -p /data/.stowaways/sailfishos
tar --numeric-owner \
-xvjf /sdcard/sfe-f8331-3.0.1.11-heroic.tar.bz2 \
-C /data/.stowaways/sailfishos
rm /sdcard/sfe-f8331-3.0.1.11-heroic.tar.bz2
@local__hero ,
Hi there,
I am interested in converting my phone to SailFish OS too......
Please see the attached photos on my phone info......
How do i convert to SailFish OS ?
My phone is Singapore variant