Related
CM 10.1.0 RC2 code base has been released and here it is for your flashing pleasure!
DISCLAIMER:
I am new to android development so more of a builder than a developer at the moment. So please do BACK UP your phone before you get started. If you know how to fix an issue in the ROM then feedback is more than appreciated. Bug reports are welcome, however please understand that I probably won't be able to figure out the solution without help. You can expect that CM code updates will be rolled into this ROM as these come out though.
For those of you looking for Skype audio this ROM does not yet fix it BUT I have tried the tinyalsa_audio stuff from Adam77Root and that does get Skype working just fine, but then it messes up your phone audio to where you don't hear anything or send anything out about 3/4 of the time. So we're getting close but not quite there yet... Oh and bluetooth calling was not fixed when skype worked, so there's something else wrong there...
RC1 was accidentally released with the tinyalsa_audio driver.. So this is RC2 with the "correct" libaudio which means skype is broken but calls work...
Using CWM:
1) BACK UP your current ROM!!!
2) Preform wipe / factory reset
3) Flash the ROM: cm-10.1-RC2-20130530-UNOFFICIAL-i927.zip (MD5 = 2e65e45bdc7539d5260062abdf6cd1cd) Mirror 1
4) Optionally flash GAPPS: gapps-jb-20130427-nonneon-tonyp.zip (MD5 = 13fc57e24ead77ec2613efd643af3800)
Stuff that I've noticed that looks to be fixed / has changed since M3:
- Moved over to KickAss kernel and battery life now totally rocks!
- Picture editing in the gallery is also working fine now.
- HDR photo capture looks to be working just fine also...
- Lock screen lag much less noticeable, but I do sometimes need to press the button twice...
Known issues without workarounds:
- Audio in skype is there but plays back at wrong rate (slower than normal, woman's voice sounds like a man's)
- I was not able to get my two bluetooth headsets working but bluetooth GPS works fine
Known issues with workarounds:
- GPS works great and fast but reports 0-2 satellites only, NMEA data stream seems to be incorrect, so parsing this data may be touchy in some apps
- Pictures taken by camera are shown rotated 90 degrees (then can be manually rotated within the gallery app)
Please don't report any of the above known issues. General CM 10.1 bug tracking thread <- Please check here before posting a bug report!
I'm sure there are others but I've not noticed them yet. I don't use a hands free but I can confirm the bluetooth does work with an external GPS for instance.
Change log:
20130530 - Corrected call audio issue and CM 10.1.0 RC2 code base
20130525 - Moved to KickAss kernel and CM 10.1.0 RC1 code base
20130503 - Fixed gallery pic editing, update OTA image
20130502 - Combined LiteKernel built 20130418, broke the gallery pic editing, added OTA support
20130417 - Combined LiteKernel built 20130414 into the ROM, no need to flash kernel seperately
20130416 - New LiteKernel build by bubor
20130415 - WiFi fix by bubor applied
20130412 - M3 code release, still using LiteKernel from 20130222
20130405 - Rolled back non-monthly code updates to revert this back to the original M2 code release. Corrected build environment to generate proper boot.img, No longer using the one from the LiteKernel which means that the LiteKernelManager is not messing around with settings now.
20130404 - Used the 2013/02/23 branch of the device tree and also re-synced with the CyanogenMod source. SD card mappings now match the CM10.1 later builds so recommend wiping and re-installing fresh for this one,
20130402 - Build LiteKernel into the ROM so no need to flash the kernel separately
Credits:
- KickButtowski for the kick ass KickAss kernel
- tonyp for the non-neon GAPPS package
- bubor: WiFi tether fix and new kernel that fixed data usage, image editing in galley and google now hotword detection as well as new GAPPS
- Adam77Root for the libaudio code that fixed the camera audio in video recordings
- yohan4ws for pointing me towards Adam77Root's libaudio stuff
- gtmaster303: CM 10.1 bug tracking thread maintenance
- The-Covenant team: For the device tree and vendor proprietary files
- dman3285: For the tutorial on building CM10 and CM10.1 from source, and all your work getting this setup
- thegreatergood: For the LiteKernel source and binary
If I've missed anyone apologies in advance and just let me know and credit will be added...
And here is the ling to my device tree should anyone want to follow along. Seperate branch available for the tinyalsa_audio for the more adventurous ones.
Reserved...
sweeeet!
wow, another rom i will try it tomorrow, juts 1 question, if i flash lite kernel the wifi will work? and how about ohter mods or skype?
I am gonna try it tomorrow, thanks thanks
Awesome, thanks!
Can you please list the non working things you have already discovered?
lorddavid said:
wow, another rom i will try it tomorrow, juts 1 question, if i flash lite kernel the wifi will work? and how about ohter mods or skype?
I am gonna try it tomorrow, thanks thanks
Click to expand...
Click to collapse
Correct - If you flash the LiteKernel on top of the ROM then the WiFi will work.
braintweaker said:
Awesome, thanks!
Can you please list the non working things you have already discovered?
Click to expand...
Click to collapse
Done...
This is pretty much just a new build with all the upstream commits, correct?
I suggest everyone review my bug tracker thread before posting bugs, as these builds are one in the same rom...
http://forum.xda-developers.com/showthread.php?p=38339702
gtmaster303 said:
This is pretty much just a new build with all the upstream commits, correct?
I suggest everyone review my bug tracker thread before posting bugs, as these builds are one in the same rom...
Click to expand...
Click to collapse
Agreed.
This build is based on:
- CM 10.1 M2 release code base (released 4 Mar 2013 so the Feb ROMs are based off the M1 release)
- The-Covenant device tree and proprietary files which I assume have not been touched since end of Feb
- thegreatergood's LiteKernel binary which is the same as the other ROMs
So any issues that were related to the kernel or device specific stuff will still be there, but CM based issues may have been resolved. Case in point the audio playback lag is now fixed on my phone.
YMMV of course!
I am doing right now a backup of my current rom. I really want to see if skype and magic jack works now. I will post back in some hours.
Is bluetooth handsfree fixed in this build?
Re: [DEV][ROM][JB 4.2.2][Unofficial] CM10.1-M2 3/31/2013
One question. Do i need to flash the keyboard fix? and the rom is compatiblr with the mod to put external sd as internal? i try to flash but never boot. I will try again in a few moment
Sent from my SGH-I927 using xda app-developers app
jzamoras said:
Is bluetooth handsfree fixed in this build?
Click to expand...
Click to collapse
In my test both headsets connected fine but one gave no sound and the other gave me only static. Not sure if the mic was working on either one. I don't usually use bluetooth so can't say for sure but I think this is still an issue on this build at this time unfortunately.
lorddavid said:
One question. Do i need to flash the keyboard fix? and the rom is compatiblr with the mod to put external sd as internal? i try to flash but never boot. I will try again in a few moment
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
You won't "need" to but the crashing keyboard gets annoying fast. So installation of a keyboard from the play store (I used the hacker's keyboard) is a must to make this usable. now if there is a "fix" available for the stock keyboard on the JB builds then let me know what it is and I'll see about adding it to the ROM by default.
As for the memory cards, the internal is mounted as /mnt/emmc and the external is mounted as /mnt/sdcard. Not sure if that answers your question...
spyke555 said:
In my test both headsets connected fine but one gave no sound and the other gave me only static. Not sure if the mic was working on either one. I don't usually use bluetooth so can't say for sure but I think this is still an issue on this build at this time unfortunately.
Click to expand...
Click to collapse
Is the same I got using AOKP. I guess I'll wait then.
spyke555 said:
You won't "need" to but the crashing keyboard gets annoying fast. So installation of a keyboard from the play store (I used the hacker's keyboard) is a must to make this usable. now if there is a "fix" available for the stock keyboard on the JB builds then let me know what it is and I'll see about adding it to the ROM by default.
As for the memory cards, the internal is mounted as /mnt/emmc and the external is mounted as /mnt/sdcard. Not sure if that answers your question...
Click to expand...
Click to collapse
I was talking about these patches http://forum.xda-developers.com/showthread.php?t=2067954
there is a patch for swap the external sd with the internal, and another for the keys in the keyboard.
Edit: i think that the keyboard patch no needed. But the Patch to swap the the external SD as internal, doesnt work. The rom never boot when i install it.
Another thing, its me, or the wifi is very very slow? i am downloading skype from the market and is taking so much.
Sorry if i wrote something bad :/
Just corrected the link to the LiteKernel, you may want to download this new link and re-apply to make sure you have the latest kernel installed. Trying to get this built into the ROM to avoid any further confusion...
Ok, i will try it again, but the skype/magicjack audio issue still exist
Just posted a new ROM build that now has the LiteKernel-20130222 built in. No need to flash separately. CM code is the same so no change there. If you already downloaded the 20130331 version and installed to 20130222 kernel then no need to re-download.
CM10.1-M3 release should be coming out shortly so do expect another update soon...
spyke555 said:
Just posted a new ROM build that now has the LiteKernel-20130222 built in. No need to flash separately. CM code is the same so no change there. If you already downloaded the 20130331 version and installed to 20130222 kernel then no need to re-download.
CM10.1-M3 release should be coming out shortly so do expect another update soon...
Click to expand...
Click to collapse
I'll jump as soon bluetooth thing is fixed
Hi guys, only few words:
I'm working on a 3.10 kernel just for fun, i dunno if i'm able to make it stable.
If someone want to help any help is appreciated!
it's based on LA.BF.2.1.2_rb1.5 CAF branch
source code is here branch LA.BF.2.1.2_rb1.5 and test_usb
test boot.img is here: http://www58.zippyshare.com/v/eqVBaQhc/file.html
Working list:
- it boots!
- touch screen
- backlight
- sms and call
- audio
- Bluetooth
- NFC
- 3D Graphics
- adb
everything else is not working. use it with a usb cable plugged in or it will not work.
Major issue atm: it doesn't work without usb plugged in.
thanks to @myfluxi for his caf kernel & ROM
thanks to @Sultanxda for some suggestions
That's a good news! Maybe @myfluxi can help?
Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
Very interesting project. I'll keep an eye on this. I'm also available as a tester if you want [emoji5]
Sent from my Nexus 5 using Tapatalk
Interesting.
How did you get past what this guy said?:
Sultanxda said:
Stopped working on it :/ I managed to get modem firmware to load (modem still doesn't work), but 3.10 as a whole has one big problem on the Nexus 5: proprietary TrustZone (TZ) firmware. 3.10 is much, much more reliant on TZ than our 3.4 kernel. 3.10 is so reliant on TZ that the CAF 3.10 branch does not boot with the latest PM (power-management) drivers (I had to use the 3.10 source from the LG G Watch as a base to get this completely booting). There are scm calls to TZ everywhere in 3.10, and in particular all versions of 3.10's PM code are broken to some extreme degree with our ancient firmware (kernel always crashes on CPU idle power collapse). I'm sure it's possible to make everything work with our firmware, but you'd likely need to know things that only Qualcomm engineers know, such as the actual internals of the TZ firmware to see where there are incompatibilities between TZ and the new kernel (TZ firmware source code is confidential/proprietary, so it is not available to the public).
Click to expand...
Click to collapse
nagalun said:
Interesting.
How did you get past what this guy said?:
Click to expand...
Click to collapse
probably because now CAF source has got more patches than 1 year ago! maybe they used patches that already were in lg smartwatch source, who knows... luckily now we have got a booting CAF kernel
Bluetooth seems to work just fine.
3D Graphics work as well.
NFC works too.
(Not sure about hw video decoding & GPS)
Lots of SELinux denials though.
nagalun said:
Bluetooth seems to work just fine.
3D Graphics work as well.
NFC works too.
(Not sure about hw video decoding & GPS)
Lots of SELinux denials though.
Click to expand...
Click to collapse
thanks for the tests, adding to OP
You should REALLY, REALLY get someone involved. This is gold.
Oh and you may find this helping, as we share the same SoC: http://forum.xda-developers.com/son...pment/unified-kernel-msm8974-devices-t2931858
I hope you get the help, collaboration and input you need to succeed!
3.10.x on N5? OMG Yeeees
Thanks for your work, but all my android devices till now had 3.4 kernel, can someone please tell me what are advantages of 3.10 kernel vs. 3.4 on a device like Nexus 5? Thanks.
Creative9170 said:
Thanks for your work, but all my android devices till now had 3.4 kernel, can someone please tell me what are advantages of 3.10 kernel vs. 3.4 on a device like Nexus 5? Thanks.
Click to expand...
Click to collapse
read from here to here, replace the kernel version in the url from 3.4 to 3.10 to get all improvements over the time. yes, backport features from 3.x/4.x to 3.4 will lower the gap between 3.4 and 3.10 but there's a motivation if newer devices use 3.10 instead backport stuff (caf will drop support for 3.4 sooner or later)
blackbird5308 said:
You should REALLY, REALLY get someone involved. This is gold.
Oh and you may find this helping, as we share the same SoC: http://forum.xda-developers.com/son...pment/unified-kernel-msm8974-devices-t2931858
Click to expand...
Click to collapse
i'll take a look
small update:
got adb working (using 3.4 driver), now it's easier to debug for everyone!
http://www58.zippyshare.com/v/eqVBaQhc/file.html
Hi. thx for your project. Maybe n5 users expect your 3.10.x kernel port even they can't write reply.
I test CM13-Caf 20160203.zip nightly with my girlfriend "D821 N5".
1.Rarely can't turn on lockscreen.(but screen was turned on)
-Maybe CM-Nightly's problem but no more happen after once happened.
2.Doesn't work 3g connetion
-I'm not use LTE,only 3g. Can't check LTE is working.
Before flashing kernel, network is working. Now Only work with UMTS. IMEI is fine. Network base is KT in South-Korea.
3.Wifi disconnect
-She don't recognize ip/mac address. Also can't find WIFI (2.4Ghz, 5Ghz)
4.Camera doesn't work.
-She have 3 eyes but only work 1 eye, Front Sensor.
Maybe you already know about it. I just nobody write about this problem in thread so I trying to write that problems.
Your 'Fun' gave us hope which n5 also have 3.10.x kernel. LOL
kwjhgjh said:
Hi. thx for your project. Maybe n5 users expect your 3.10.x kernel port even they can't write reply.
I test CM13-Caf 20160203.zip nightly with my girlfriend "D821 N5".
1.Rarely can't turn on lockscreen.(but screen was turned on)
-Maybe CM-Nightly's problem but no more happen after once happened.
2.Doesn't work 3g connetion
-I'm not use LTE,only 3g. Can't check LTE is working.
Before flashing kernel, network is working. Now Only work with UMTS. IMEI is fine. Network base is KT in South-Korea.
3.Wifi disconnect
-She don't recognize ip/mac address. Also can't find WIFI (2.4Ghz, 5Ghz)
4.Camera doesn't work.
-She have 3 eyes but only work 1 eye, Front Sensor.
Maybe you already know about it. I just nobody write about this problem in thread so I trying to write that problems.
Your 'Fun' gave us hope which n5 also have 3.10.x kernel. LOL
Click to expand...
Click to collapse
Hi!
I already knew that those things are broken, i'm working on it
rmbq said:
Hi!
I already knew that those things are broken, i'm working on it
Click to expand...
Click to collapse
Thx for q~~uick Reply. as i expect, feedback was too late kkk...
Have you ever think about next project which connect with N5 after this project is over?
AS you know, even this project is awesome but unfortunatly it's only work in CAF rom.
So I have curious when this project is over, what will you choose your next activiation.
Get more project like Build AOSP+CAF rom, More fix to work in AOSP, continue fixing this kernel.... or have rest times!
kwjhgjh said:
Thx for q~~uick Reply. as i expect, feedback was too late kkk...
Have you ever think about next project which connect with N5 after this project is over?
AS you know, even this project is awesome but unfortunatly it's only work in CAF rom.
So I have curious when this project is over, what will you choose your next activiation.
Get more project like Build AOSP+CAF rom, More fix to work in AOSP, continue fixing this kernel.... or have rest times!
Click to expand...
Click to collapse
after this project? sounds hilarious! my intention is to maintain CAF CM with 3.10 kernel, if i'll be able to make it stable
rmbq said:
after this project? sounds hilarious! my intention is to maintain CAF CM with 3.10 kernel, if i'll be able to make it stable
Click to expand...
Click to collapse
'hilarious' means...unfamiliar vocabulary to me, but enough to understand your purpose.
I think to consider my main rom as CM-Caf. Good luck to your project!
I'll waiting your work. d=_=b
@rmbq I flashed the Kernel built with your source. It booted fine, but as you mentioned in op, it rebooted the moment I disconnected from USB. Where do we go from here?
rachanta said:
@rmbq I flashed the Kernel built with your source. It booted fine, but as you mentioned in op, it rebooted the moment I disconnected from USB. Where do we go from here?
Click to expand...
Click to collapse
i don't know where is the problem atm, i don't think it's related to USB drivers, sultanxda said it's TZ related... it isn't easy to track, i saved a log with something more than "watchdog bytes". also i don't know if LA.BF.2.1.2 is a good base, some drivers (ex adreno) are older than LA.BF.1.1.3 (our caf 3.4)!! xperiadev are working on LA.BF64.1.2.2 also for msm8974 soc, that branch is very up to date but i can't get it boot on hammerhead, and i don't know if they can get it boot on xperia devices with msm8974 soc...
Hey guys,
I've just managed to make a build of Cyanogenmod with lots of help by a guy called sultanqasim (actually he did most of the work), thanks a lot bro
Probably it's very bugy. Let's call it Pre-Alpha. Anyway, the build is ready and I need guys who'd like to try it out.
I chase GDrive for the first CM build. All Beanstalk builds are uploaded to the official Beanstalk AFH.
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
NFC
Broken:
Audio through built in speakers or headphones
RIL
Camera
Mic
Various other smaller things
Some Sprint users also report that it doesn't work for them. Just try it out if you like. Every tester's report takes the project a bit closer to stable builds.
Download Cyanogenmod (GDrive)
Download Beanstalk (AndroidFilehost)
To flash it:
in TWRP, reformat the userdata partition as unencrypted ext4. Go to Wipe->Advanced Wipe, select data, click on repair or change filesystem, change file system, and choose ext4.
in TWRP, go to Wipe -> Advanced wipe, and erase system, data, dalvik, and cache
flash the file by pushing it to your sdcard or you can use adb sideload. Also you can flash GApps optionally.
reboot into the system
Looking forward to your reviews. Thanks a lot
Good luck to all of you
Remember: I'm not responsible for anything that could happen as a result of following my instructions or anything else.
XDA:DevDB Information
[Testing][ROM] Cyanogenmod 13 - Unofficial, ROM for the HTC 10
Contributors
krassermensch, sultanqasim
Source Code: https://github.com/sultanqasim
ROM OS Version: 6.0.x Marshmallow
Based On: Cyanogenmod
Version Information
Status: Testing
Created 2016-06-10
Last Updated 2016-07-13
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!
Nice!
Moderator Information,
Thread re-opened to allow OP to upload file on XDA host.
Can't wait for CM13 on this phone. I know Squid2 has been a ton of work into this, from what I know, already a solid month behind the scenes.
device boots up? display?
thought this thread was closed till a download link was posted...
i don't seem to find any link or me gone blind lolll
edit:- just read that its opened for uploading the link so it seems upload is in progress
Maybe change the title with correct spelling of " Unofficial "
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
i guess we would need to wait for the upload to be finished to see if its any different or the same as the Op doesn't seem to be much of responding to any comments
@krassermensch - Can you give us a list of what is and isn't working in your experience, at least?
psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
krassermensch said:
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
Click to expand...
Click to collapse
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
psych0r3bel said:
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
Click to expand...
Click to collapse
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
I'm really glad to see this coming along! Keep up the good work. I'm not much of a tester normally but I think Im going to give it a shot later tonight and let you know what issues I can find.
krassermensch said:
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
Click to expand...
Click to collapse
So glad to see the credits given, and insight to what testers will find.
Didn't want to see any drama, I thanks for putting the time in and squid for laying these ground work!
Sent from my HTC 10 using XDA-Developers mobile app
@krassermensch, thanks for your efforts but... If you're going to publish his work, how about updating the OP with his bug list and the title with pre-alpha. Just so users have more information, instead of the vague "it might be buggy". We know its buggy. Specifics about what works and doesn't is what people would like to know.
This still accurate?
squid2 said:
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
Broken:
Audio through built in speakers or headphones
RIL
Fingerprint sensor
Camera
Various other smaller things
Click to expand...
Click to collapse
Moderator Information,
Thread has been moved to general, as the OP is only hosting the work for another user.
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
matteosaeed said:
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
Click to expand...
Click to collapse
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
rav101 said:
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
Click to expand...
Click to collapse
Sweet. I can test more at nights when I am at home. Doing the nanodroid now of this build.
---------- Post added at 09:17 PM ---------- Previous post was at 08:52 PM ----------
question, I am trying to go back but I am getting the failed to mount '/system' (invalid argument), any tips on how to bypass that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click here to get to the new post where we'll keep updating this rom
What it is
It is an LineageOS 14.1 alpha build from official LineageOS sources devices trees and fresh caf 3.4 kernel port. This is not related anymore (2017-03-22) to the Sony Open Device Project (sonyxperiadev). They work on a different way and we are helping each others as often as possible.
This rom is worked to be as stable as possible to be used as a daily driver. There are no changes into LineageOS sources, manifest to build is attached in this post. The idea is to share this built with the community to improve this rom. If it is good enough, maybe, someday, get official again for our D6603. Thanks a lot to @tomascus who made this possible. (his donate link)
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Who can use it
It is only for Z3 and UNLOCKED UPGRADED BOOTLOADERS
How to install
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash this TWRP (version 3.1.x) | If you are a Z3 Dual user, flash zip below before installing Z3 Dual version. / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen
% Wipe system, cache and data
Install rom zip (+ % gapps if you need it)
Reboot
Rolling back to stock
Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
What gapps to flash?
Use f-droid
You can flash any gapps you want, our partition is 2GB and rom is 700MB:
Code:
z3:/ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p23 2.4G 680M 1.7G 28% /system
Just take 'arm' and not 'arm64'
Gapps need to be flashed at first rom flash!
NEW RELEASE
2017-06-13:
Xperia Z3
Download
md5: 2d4ca5f88de0303575f2ab9c249d521f
TWRP 3.1.1 - 2017/06/09
Xperia Z3 Dual
See below
md5: 360fd6f9e0e22eb4ff0de72059c7de24
TWRP 3.1.1 - 2017/06/09 | Mandatory if coming from Z3 builds or new to the rom.
Temporal Z3 Dual rom (fixes SIM problems)
nailyk said:
Many thanks to @xkeita for providing a working rom as soon as the device get delivered.
20170622 / b8a79c826ddf0a786010cc04b3943b2e
twrp / 61e8c27f19c114dc9ac1f33dd4c7fb39
Rom is tagged nailyk because I build it but everything on it is @xkeita work!
Many thanks everybody
Click to expand...
Click to collapse
What's new:
Code:
- Updated Camera profiles
- Reworked Z3 Dual RIL
- Updated Audio HAL flags
- BFQ I/O Scheduler
- Bluetooth aptX support
- Qualcomm Connectivity Engine support
- Imported audio ids from original .291
- ANC Headphones support
- Dual Mic config enabled for voice calls/audio recording
- Ok Google everywhere fixed (untested)
- Tweaked autobrightness (again)
Release notes:
2017-06-09 is just a minor update with some [experimental] tweaks for bt connections and fixed minor issues with z3dual
Older Releases
Based on Kernel 3.4
Some of these can be found here
Release History
Code:
2017-06-09:
- Tweaked a little bluetooth values (untested)
- Fixed Z3 Dual sim problems
- Latest Google source (7.1.2_r17)
- June security updates
- Permission fixes for new PowerHAL
- Z3 and Z3 Dual code cleanup
- Forced camera modes to [email protected], [email protected], [email protected], [email protected]
- Fixed all of the device sensors (they're all online and working properly now)
- Latest LineageOS updates
- Smoother UI rendering with CPU
2017-05-17:
- Tweaked general audio output processing
- Updated vendor audio libraries configs (enables qcom effects)
- Auto brightness/brightness changes
- New thermanager configs based on stock
- Changed deprecated Gello for Jelly
- Some device tree cleanup
- General radio/wifi tcp updates
2017-04-16
- Audio changes,
- NFC fixes,
- Brightness changes,
- Verbosity increased for logs after night reboot + PERISTENT_TRACER
- No more vol- buton at boot time
- A lot more
2017-04-05:
- Enforcing selinux
2017-04-01:
- Audio fixes
- Encryption fix
- A lot more that I can't remember right now
2017-03-22:
- Full rework based on stock 3.4 kernel
Based on Kernel 3.10 by @nailyk
2017-01-23:
Download
md5: 04a3a614d820df78e7a70538df61203d
sha1: 10a3ea95d823a6b87b5f5a8f79896e3dabf7a8b5
Status
Workaround for in-call reboot
Include PR1130 PR1128
2017-01-15:
Download / 2
md5: 8b8898c18d631dc7f9d78a18b1e7500f / b40c7ba870ae579827e1bd7a427afc1f
sha1: 588d2c1e0fd2ef4790706980fc1050a8d793d559 / f28ba7714987a94c5ba43a6ee39fe05f0b5a5fca
Use of the reworked device trees
Include some experimental kernel pull requests
2017-01-01:
Download
md5: 6c5abcbeda01c75344cd4296bb2358d1
sha1: a46ef81e2d26ac9610f16cb90bc13e63d58a2983
Switch to LineageOS
Bluetooth deepsleep fixed
2016-12-02:
Download
md5: 496de65608fd4236f5d451a4179e1ce8
sha1: 74a25eabc0f8ac5be3458bd9d98461f9519c7c73
Bluetooth improvements
P.S.: i'm almost affiliated to LineageOS, just like tomascus who made everything.
Sources
Manifest file.
Everything else is Lineage.
Contribute gerrit.
XDA:DevDB Information
LOS-14.1, ROM for the Sony Xperia Z3
Contributors
nailyk, xkeita
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-06-09
Created 2016-11-27
Last Updated 2017-07-01
Thank you!
Thanks to
@tomascus
@xkeita
@derf elot
@panzerox123
@Robot76
@gr8st
@mcgi5sr2
@rcstar6696
@yecomixer
@TheAvengingTITAN
@@AdrianDC
@@doriandiaconu
@SuperLamic
@DiscMan55
@drakonizer
@aclegg2011
@DevUt
@tomascus
@blackhawk_LA
@erickas
@malacha
@jimRnor
@optimumpro
@steadfasterX
@Myself5
All the members of the ivy team: @Quarx, @Olivier, @cdesai, @Myself5 and the one I miss.
TeamWin
LineageOS
All the dev who made the downstream kernel
All of you for testing rom and supporting me
FAQ
How to post
I want to say thanks --> Thanks you. Gratitude is really important for us. Find some posts from us and hit thanks buttons. It will be most appreciated You can also use @tomascus donate link.
We are here into the dev thread, not user one. For now the rom is under development.
We wont talk here about not related to device problems (where is foo setting, how to flash bar).
Reports will simply be ignored if already answered.
Reports without logs or step to reproduce are useless (read contribute).
Substratum is officially not supported into Lineage.
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to post your unusual and not supported use-cases (like: "I have only ipv6 at home and the RA doesn't work without IPv4")
You are welcome to report any typo, error, etc...
No variant are supported now. Only D6603. You want support for variant? Consider help on porting or a hardware donate.
My device is screwed and I need it for my job interview in 1h --> go to IRC (how to report problem, #3)
I want say how SODP is bad --> Read this and above.
This is not against you but try to keep thread clean as a dev reference. Thanks in advance.
What is not working
BT headset calls --> pending. Detailed post.
OTG --> 2017-04-16
Wifi auto connect (boot/deepsleep),
HW Encryption, --> 2017-04-16
Vibrator level
4k (unfixable without Sony camera app)
120 fps (pending)
Some volume loudness problem --> not reported
Microphone when ok google is installed (do not install gapps will fix! An app which constantly record your microphone is a malware!) -->Pending,
Slow charging,
Phone reboot at 3AM while plugged-in, --> Workaround disable "auto time" into settings.
NFC, --> topic
Wifi access point,
Adaptive brightness not good. --> Fixed by @xkeita
How to report problems
To report problems there are multiples ways, depend on each person. The How to contribute section provide information on the way to do and should be applicable to everyone. The How to get logs section is the final touch on how to report problems.
Thanks wanting reporting, as, for an early development rom, reports are a necessary step to move forward
Some examples:
I cannot record videos with open camera.
Click to expand...
Click to collapse
Is useless on a dev thread and you probably won't get an answer.
Just wanted to report that this ROM doesn't support my 128gb sandisk SD card..and gives a message, unsupported SD card and asks to format.. this is the only bug which prevents me from using this ROM.. however the same card works perfectly fine on all other ROMs like 7.1 CM or AICP ROM and also all lollipop ROMs and stock ROM.
Click to expand...
Click to collapse
Is better as there is explanation, context and cross rom tests. With log this report used to be perfect.
This guide is really detailed and explained everything about bug reports. (deserve all bug-report cases, not specially this thread or xda)
@steadfasterX write a good guide about IRC, here you can get quick support (like when your device is totally broken, etc...)
steadfasterX said:
You talked about using IRC to get support. What is this and how can I use that?
Meaning of IRC => Internet Relay Chat. A very good IRC client is this one here: hexchat <-- download it and read the quick intro to get started: Quick-Start
--> when asked if you want to join a channel type in "#LineageOS" and after connected you will be in.
If you do not want to install anything you can simply use the webchat instead directly over here: Webchat
Howto communicate? IRC means many people talking the same time and there are some goods and bads to know about using IRC.
So please read this mini and very quick overview (especially the good manners there): Good manners in IRC (matches for all OS not for fedora only)
Click to expand...
Click to collapse
How to get logs
Here you have some info about how collecting log. It is always better to include reference to the Installed version.
How to contribute
I have c knowledge:
All the sources to build this rom are public and are provided into the manifest, in the howto build section. It means all the repository are from LineageOS github, except those mentioned into this manifest. Depending on where you find the bug/improvement there is different way to contribute: gerrit, github PR, etc... Contact me to test with you patch as everyone can try and give feedbacks then join IRC to discuss the best way to merge.
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.
Installed version
When reporting problems, specially for work in progress, it is good to provide the build version:
- 'uname -a' will give you the kernel version,
- 'getprop ro.cm.display.version' will give you the rom build version.
What is LineageOS
LineageOS is re-brand of CyanogenMOD. At the end of 2016 some bad things appends. Lineage is the same rom that CyanogenMOD so you can still dirty flash, etc... However as all *cyanogenmod.org services are down, OTA update will not work until you flash lineage one time.
Thanks for posting this rom. Thank you for your awesome developing.
Great work man!!! I hope you will continue you work on CyanogenMod for Xperia Z3!!! Thanks
great work and z3 compact?
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
drakonizer said:
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!
Click to expand...
Click to collapse
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
mcgi5sr2 said:
We are still getting echo on the line and a static in call volume issue on the d5803 with latest sources. rancidfrog has provided logs
https://github.com/sonyxperiadev/device-sony-aries/issues/49#issuecomment-263256754
is the issue isolated to the Aries or do Leo users have this issue as well? Similar question to Honami board devices?
Click to expand...
Click to collapse
Can you report me as I can answer please?
nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
mattia.bf said:
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.
Click to expand...
Click to collapse
Well, thanks then.
Shadow of Destiny said:
Hello, I dont get it, where is the download?
I want it sooo badly, but I am to dumb to find the download
Click to expand...
Click to collapse
Link is not yet added because I'm dealing with weird GPU issues and I'm waiting for a feedback about a fix before adding it. It should be ok in some hours.
drakonizer said:
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.
Click to expand...
Click to collapse
IDK what BBS is but the /sys/kernel/debug/wake_lock table is really instructive. From the early experiments we have two issues: like you ril is one of them, and usb is the second one. If your reboot the device in airplane mode without usb attached wake_locks are a bit better.
Yes building AOSP is a good idea but @accleg2011 never get it working so I really doubt I can. Device was really fine on CAF display, game were really smooth, menu too. With SODP display menu are ok now but game are laggy and I don't know how to check if they are software or accelerated rendered. I tried to mimic hammerhead config.mk (it is the same device than z3 except for camera) but it doesn't provide results. I'm almost sure it is another PEBKAC with a missing flag.
I have a bunch of log to analyse and will post my results a bit later. Thanks for your advice, maybe I simply should buy another ssd.
If you have some time to waste, can you try frozen bubble on your device with SODP display, please? When balls pop, it is the most GPU intensive rendering. Is it laggy for you too? (from what I see ~5FPS)
nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.
We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?
Edit:
Can you report me as I can answer please?
Click to expand...
Click to collapse
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
mcgi5sr2 said:
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees
Click to expand...
Click to collapse
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
nailyk said:
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.
Click to expand...
Click to collapse
Hey no problems, I'm actually battling just to get my latest CM build to install properly
mcgi5sr2 said:
Hey no problems, I'm actually battling just to get my latest CM build to install properly
Click to expand...
Click to collapse
Do you take a look at Myself5 repos ? You can ask him a CarbonRom test but his repo where very helpful for leo. Also, maybe you can reuse mine and we can concentrate our efforts. I try to be as close as possible to SonyCM ones.
I will update the OP with the build instructions when XDA will work.
2016-11-28 release
Rom link added.
I'm currently uploading screenshots.
A bunch of peripherals are broken. Since I test this PR bluetooth is broken.
Hardware accelerated part are missing or broken.
Camera is partially working, switching to video mode crash camera app.
Deep sleep still not working.
Gps seems to be broken too.
Don't forget we are into a dev thread please, so post comments with logs, faulty line or patches. Thanks.
This rom is not intended to be used as a daily driver and is unstable!
cm14.1 wowww :good:
After a total mess-up with bluetooth, a full rebuild make it ~work again (still some crash).
And 3D apps seems to be working too.
Can you confirm/infirm difference please?
An alpha build of Sailfish OS 2.1 for Nexus 10 (manta)
Its in rough shape but we are slowly but surely getting there.
YOU CAN DUEL BOOT WITH ANDROID! - See second post for info
UPDATE July 9th 2018: I am still still working on this. I have some stuff to try, mainly rebuilding the old June 2017 audio jack kernel in both hybris hal and the base rom, meaning, HOORAY - I'll be forced to start building my own android base. in the mean time things are the same in the OP, use the new build if you want the latest release and don't mind a lack of video, use the old one for creepy silent videos. I am counting down for Sailfish OS 3.0 to come out, I already know that its going to break anything I fix. And a big sigh is released.
Credits:
Lineage OS team for the LOS 14.1 Base (seriously, THANKS)
Jolla for that perfect software
followmsi for the fixed kernel sources that don't inherit those dirty lineage audio jack issues.
All the people on the #sailfishos-porters IRC who kept me motivated and full of hope (mal, krnlyng, Mister_Magister, sledges, m4r0v3r, piggz, r0kk3rs, just to name a few)
LOS14.1 Base: https://drive.google.com/file/d/1W3k2PzWKQU_-1qbhho_8MespNzr5zBlD/view?usp=sharing - I didn't make this at all.
Sailfish OS 2.1.3.7 alpha 0.1.2 rootfs: https://drive.google.com/file/d/1QKux9YkUHi7XZtGEJbUh_xYms5-BsLjo/view?usp=sharing - I did for sure make this (well, I ported it, credit to Jolla for sillica and stuff)
Sailfish OS 2.2.0.29 alpha 0.2 rootfs: https://drive.google.com/file/d/1IkWtZxAPGeiSiqCpMcbct-M43QlCsG8m/view?usp=sharing - THIS IS THE SUPER SPOOKY UNSTABLE RELEASE!!! BEWARE!
Adaptations Libhybris page: https://wiki.merproject.org/wiki/Adaptations/libhybris/Manta
My Video Review of alpha 0.1.3: https://www.youtube.com/watch?v=NmEGKZHquhQ
I have a lot to test so Ill populate this list more later but:
What works:
- Rotation
- ALS
- Magnetic Sensor
- Video
- Touch
- Hardware Keys
- Power Management and Sleep
The Checklist of What I Need to Fix
- Audio
- Video (droidmedia is broken in my latest clean build, this does not effect the rom in the OP, I would never update a rom with this many regression bugs)
- USB Charging
- Bluetooth
- GPS
- Haptic Feedback/Vibration
- Camera
CAMERA DOES NOT WORK IN THE BASE ROM SO IT WILL NOT WORK IN SAILFISH OS
Change log:
alpha0 - initial working release
alpha0.1 - added rotation fix, defined MALI_QUIRKS, applied a ton of random patches that did nothing
alpha0.1.1 - fixed taking screen shots, built gst-droid (you can now play mp3s but sound is still broken along with video)
alpha0.1.2 - built SDSVideoFix droid media! we can now play video but there is still ZERO sound at all.
alpha0.1.3 - unreleased, REGRESSION BUG: Video is broken - trying again.
alpha0.2 - Updated image to Sailfish OS 2.2.0.29, droid media still broken. I recommend staying on the old alpha 0.1.2 build.
Our device is the highest resolution device to ever run Sailfish OS (for now). Let's all feel extra special for a bit.
General About
Linux Kernel: 3.4.113
Rom Base: Lineage OS 14.1
Sailfish OS Version: Sailfish OS 2.2.0.29 | 2.1.3.7
Sources:
(This is on the to do list)
Also my Discord ID is dirtymikelikesfeet#9871
Tips and Tricks
Get landscape rotation in ALL apps
Go to warehouse, and install patch manager and autorotate anywhere (or something like that)
Reboot
voila.
Dual Boot Lineage OS 14.1 and Sailfish OS
This is super easy, so basically the Hybris installer doesn't touch /system or /data (at least none of the installed android files) so you can boot between the two rather easily. You will need a Lineage OS 14.1 boot image (Inside the Lineage OS 14.1 zip) and Hybris boot (inside the Sailfish OS zip). When you want to boot between the two, boot into TWRP Recovery, and flash the appropriate boot image. This should make it easier for testers.
Q/A
Does flashing a new Sailfish OS image wipe my android files? - As far as I know? No. But I haven't really tested this. It shouldn't.
"Is this usable as a daily driver?" - No. not right now. Once I fix audio maybe, but as it stands now, unless all you do is read emails, watch silent movies, and play simple games and read books, its pretty garbage. You can browse the web with web cat but it has 1/3 of the screen not used.
"Why did you use the LOS14.1 base you idiot? you realize we will never have working camera now right???" - Lesser of all evils. Once I get a good stable LOS 14.1 based sfos port (working everything), and a list of all my tweaks to fix everything, I will try making an LOS 13 based sfos port. I like camera too, and do occasionally use it on this tablet.
"Does it have android app support?" - No. Maybe one day I will hack alien dalvik onto it and post a concept install for Nexus 10, but no promises.
Looks interesting,I will have to follow your work to see how far this goes. ?
Yes me to. I still have my Nexus 10 but don't use it much because it's horrible for streaming videos, unless I flash gingerbread. Anyway hope you keep at this, thanks for your effort.
Sent from my LG-ls990 using Tapatalk
aheeejd said:
Yes me to. I still have my Nexus 10 but don't use it much because it's horrible for streaming videos, unless I flash gingerbread. Anyway hope you keep at this, thanks for your effort.
Sent from my LG-ls990 using Tapatalk
Click to expand...
Click to collapse
Thanks for the interest, the current thing to do is add minimer to m N10 so I can fix hwcomposer, it is wonked real bad and I think it's why jolla-startupwizard won't work right now.
*bump* because it finally ****ing works (sort of)
sailfish for nexus 10
Galaxyninja66 said:
*bump* because it finally ****ing works (sort of)
Click to expand...
Click to collapse
a better browser please??or a new version??
ted111 said:
a better browser please??or a new version??
Click to expand...
Click to collapse
browser bugs are proving near impossible to solve, and manually rebuilding qtmozembed did nothing. I am going to try and crank out a 2.2 build tonight with the vendor repos included but I doubt much will change. As far as browser, the cut off is a problem with qt that I am still figuring out how to solve.
OKAY! Building new image with mic as I type this. it's at 162/473, hope it doesn't fail but it rarely does at this point. Using followmsi's new 0611 build as a base, and I have thrown in TheMuppets vendor repos for broadcomm and the like, hopefully something cool happens, but I am 99% sure this build will be the same broken build accept based on sailfish OS 2.2. This means no gstreamer, i.e. no videos, no mp3 files, no nothing. Also I doubt Audio will just fix it self either.
Galaxyninja66 said:
*bump* because it finally ****ing works (sort of)
Click to expand...
Click to collapse
tested 2.2.0.29 ,no videos, sound, webpirate browser simple works
ted111 said:
tested 2.2.0.29 ,no videos, sound, webpirate browser simple works
Click to expand...
Click to collapse
Its terrible, I know.
and the audio isses we are no closer to fixing since I have ZERO idea what is causing them, and neither do the people I've worked with. I am reloading the CM11 based port and trying to work out the gralloc issues on it, there are a ton of dependency files missing on that port for hwcomposer, but it should be fixable. everything is fixable.
Galaxyninja66 said:
Its terrible, I know.
and the audio isses we are no closer to fixing since I have ZERO idea what is causing them, and neither do the people I've worked with. I am reloading the CM11 based port and trying to work out the gralloc issues on it, there are a ton of dependency files missing on that port for hwcomposer, but it should be fixable. everything is fixable.
Click to expand...
Click to collapse
any news about it?
123123123123123213 said:
any news about it?
Click to expand...
Click to collapse
I no longer own the device, 10.1 and 11 sources had hwcomposer errors (but working audio afaik). 12-13 sources failed to boot for reasons entirely unknown since the logs looked fine (and no, it wasn't a no UI/display error, I checked and it was in telnet still, again, for seemingly no reason). 14.1 worked like a charm but sadly the audio issues were just a mystery. Rotation was an easy fix and I think at that point GPS had very little mw so it was hit or miss and debugging it was not done often so it was mostly undocumented. Don't know about now.
tl;dr
10.1-11 - broken hwcomposer, wayland is gimped in 2.0 and beyond period, and fbdev wouldn't work either
12-13 - refuses to boot past the telnet stage for unknown reasons
14.1 - audio is broken, using followmsi and the stock lineage sources/matching base images.
I'd love to work on this again actually, but a new N10 would cost me 80 AUD and I'd have to prep a new VM since I wiped all mine switching to macOS.