Related
MoKee Open Source 51.1 (Unofficial)
STATUS: Abandoned.
Features:
Odexed, quicker first boot
March security update
Archived Downloads
Sources
Chance to get a new experience. xD
Very good , exellent rom my friend
Great work! It's very pure like AOSP? Or have themes too?
lohhans said:
Great work! It's very pure like AOSP? Or have themes too?
Click to expand...
Click to collapse
it is a CM-based rom so it has CM themes app.
tank0412 said:
it is a CM-based rom so it has CM themes app.
Click to expand...
Click to collapse
OK, thks, sorry for the ignorance haha...
Another custom rom...great job dev.
Sent from my ASUS_T00F using Tapatalk
For experiment i ported my CM12.1 kernel to this Mookee rom:
https://drive.google.com/file/d/0B-Fin8UxrD6PTjRHbVBDTUY2dWM/view
This kernel was compiled from X Anwar source so it has a ton governors + i/o stuff.
Note: MTP is working.
Maybe it will be needed for someone.
Note2: Kernel from other roms will be incompatible with this Mokee rom without ramdisk bring up for Mokee.
NOTICE
Update your Kernel
The kernel I've released with the first build was a SELinux Enforcing kernel (which I don't give support anymore).
I've forgot to update command-line, sorry.
A new SELinux Permissive kernel has been just released, and the SELinux Enforcing kernel was deleted.
Now, download bootMK-20160324_2-SELinuxPermissive.img and flash it:
Code:
fastboot flash boot bootMK-20160324_2-SELinuxPermissive.img
fastboot erase cache
fastboot reboot
witch wakelocks i need block to get better battery perfomance?
karabeen said:
witch wakelocks i need block to get better battery perfomance?
Click to expand...
Click to collapse
Nothing.
If you disable system wakelocks, device will not turn on due call or something like this. (IMHO)
can you try carbon os
shobint7 said:
can you try carbon os
Click to expand...
Click to collapse
Maybe one day, I just can't maintain many ROM's for Zenfone. I'm sorry
Plus, that soon I'll be moving to Motorola
Very good!
dgadelha said:
Maybe one day, I just can't maintain many ROM's for Zenfone. I'm sorry
Plus, that soon I'll be moving to Motorola
Click to expand...
Click to collapse
Good choice there!
tank0412 said:
For experiment i ported my CM12.1 kernel to this Mookee rom:
https://drive.google.com/file/d/0B-Fin8UxrD6PTjRHbVBDTUY2dWM/view
This kernel was compiled from X Anwar source so it has a ton governors + i/o stuff.
Note: MTP is working.
Maybe it will be needed for someone.
Note2: Kernel from other roms will be incompatible with this Mokee rom without ramdisk bring up for Mokee.
Click to expand...
Click to collapse
Will it work on dgadelha cm 12 too ? Thanks
Sent from my ASUS_T00F using Tapatalk
Ale uto said:
Will it work on dgadelha cm 12 too ? Thanks
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
No.
Ale uto said:
Will it work on dgadelha cm 12 too ? Thanks
Sent from my ASUS_T00F using Tapatalk
Click to expand...
Click to collapse
This kernel version above will work on Mokee only.
But this version below is working on my CM-based roms:
https://drive.google.com/open?id=0B-Fin8UxrD6PZWt6UWIxQmdMT3M
On dgadelhas CM12.1 builds it can boot but it is not guaranted. (It can have troubles with SElinux)
tank0412 said:
This kernel version above will work on Mokee only.
But this version below is working on my CM-based roms:
https://drive.google.com/open?id=0B-Fin8UxrD6PZWt6UWIxQmdMT3M
On dgadelhas CM12.1 builds it can boot but it is not guaranted. (It can have troubles with SElinux)
Click to expand...
Click to collapse
Being Permissive I guess it will work right
how i can flash .img without computer
plz give me instruction
Yeah i know you cant port MIUI but i am asking is it possible to build?
There's some x86 tablets work on MIUI; in theory it's okay. But you need to find sources for x86 and you need to develop it to work on ZF5 afaik.
Technically it is possible, but practically it probably cannot be compiled as easily as you think.
But there's a way to know, try it.
MIUI has a lot of effort from its opensource community.. It should be possible even with x86
Sent from my ASUS_T00F using XDA-Developers mobile app
romngenie said:
Yeah i know you cant port MIUI but i am asking is it possible to build?
Click to expand...
Click to collapse
teoreticaly yes, but only 4.4, so you need 4.4 zenfone device tree,
device tree(have some faults) https://github.com/shakalaca/android_device_asus_a500cg
and you will need miui source code: (maybe this im not sure) https://github.com/MiCode/patchrom_miui/tree/v7-android-4.4.4
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
https://developer.sony.com/develop/open-devices/
Unified 4.4 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues
Hi,
We have updated the project page to reflect the latest progress
http://developer.sonymobile.com/open-devices/
Enjoy
J
jerpelea said:
Hi,
We have updated the project page to reflect the latest progress
http://developer.sonymobile.com/open-devices/
Enjoy
J
Click to expand...
Click to collapse
Is the xa going to be included in the open devices project or excluded due to being a mediatek powered Xperia.
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
Is the xa going to be included in the open devices project or excluded due to being a mediatek powered Xperia.
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
For the moment we don't support MTK
Regards
J
jerpelea said:
Hi,
We have updated the project page to reflect the latest progress
http://developer.sonymobile.com/open-devices/
Enjoy
J
Click to expand...
Click to collapse
Are you going to add X performance / XZ to open device program?
There are no vendor binaries for them on open devices page.
millosr said:
Are you going to add X performance / XZ to open device program?
There are no vendor binaries for them on open devices page.
Click to expand...
Click to collapse
It's a work in progress.
Vendor binaries already released for X Performance on jan 10.
The experimental 7.1 build is working fine (as documented, no front facing camera, fingerprint reader, etc).
It is takes ~5 hours to build on 4 core, 16GB memory vps (Softlayer) and requires lot of disk space (near 106GB repo, source and build output)
Are you going to add the xperia e4 to the open device list?
We have moved to a new address!
https://developer.sony.com/develop/open-devices/
Now you can build the latest Android with the latest 4.4 kernel
Vendor v11 is out
https://developer.sony.com/develop/open-devices/latest-updates
For user security dm-verity and File Based Encryption are enabled by default
Please disable them only if you are developing new features
Regards
J
What is this?
All build guides are updated with the Security updates
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
Here is the list of all known bugs. If you find bugs you can always open a ticket in the bug tracker and we will check it ASAP.
https://github.com/sonyxperiadev/bug_tracker/issues
on disabling dm-verity & FBE
jerpelea said:
For user security dm-verity and File Based Encryption are enabled by default
Please disable them only if you are developing new features
Regards
J
Click to expand...
Click to collapse
Hello, Alin,
thanks for your continuous support,
could you instruct the community on how exactly to disable those 2 functions prior to building an AOSP?
With kind regards,
thank you for your time.
UPD #1: as per https://stackoverflow.com/a/45968174 need to comment out the line (PRODUCT_SYSTEM_VERITY_PARTITION) in ${SOURCE_TREE_ROOT}/device/sony/tone/platform.mk
UPD #2: seems like installing a Magisk module does not change the encryption behaviour Maybe shoud check with TWRP on this.
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Will the lineageOS look same as CM or there will some certain other UI or features? Also there will be Theme engine like CM? And Audio fx?
chetan_1215 said:
Will the lineageOS look same as CM or there will some certain other UI or features? Also there will be Theme engine like CM? And Audio fx?
Click to expand...
Click to collapse
currently, lineage os is cyanogenmod only with a different name. But we don't know what they'll do in the future.
Will we be able to dirty flash the first Lineage OS builds over a current CM build or will it require a wipe?
brb lol said:
Will we be able to dirty flash the first Lineage OS builds over a current CM build or will it require a wipe?
Click to expand...
Click to collapse
you can dirty flash but you'll need to wipe system partition in TWRP (wipe, advance wipe, system and cache) and after you flash the ROM, reflash GAPPS
Will the new Lineage OS builds fix old bugs inherent in the old CM14.1 nightlies? Since the first CM14.1 build for my phone (HTC one m8), fellow Canadian users have reported that turning on location services resulted in bootloops (this did not occur with CM13). The problem was never fully fixed, and it didn't seem like anybody was working on a solution. It would be great if the new Lineage OS builds would have these old issues resolved.
Why is it that noone wants to support a device with an exynos based proccessor, and will it ever happen? For example noone is developing any AOSP roms for the galaxy s6 edge...
What will happen to those devices which didn't had any maintainer in CM? Eg ZUK Z1!
I would like to ask if Lineage OS will be available on the Huawei P8 Lite
DolDrum said:
I would like to ask if Lineage OS will be available on the Huawei P8 Lite
Click to expand...
Click to collapse
Mostly all devices that had support for official CM13 and CM14 will get Lineage OS. MOSTLY!!!! But no worries, newer devices will have official support too. Just we'll have to wait till the official support list comes up!
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Will lineageOS have it on theme engine thank you for your help
Sent from my Nexus 6 using Tapatalk
galaxyman4g said:
Will lineageOS have it on theme engine thank you for your help
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, I think so..... CM Theme Engine is one of the best things CM gave us so, obviously, they're not gonna remove it. If they do, I hope they'll add at least some theme engine or substratum.
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
RandomUsername02 said:
Why is it that noone wants to support a device with an exynos based proccessor, and will it ever happen? For example noone is developing any AOSP roms for the galaxy s6 edge...
Click to expand...
Click to collapse
Samsung makes the Exynos processors and doesn't release the processor source, and it is very difficult to develop on processors when there is no processor sources. Samsung stopped releasing the processor source code after the whole brickbug fiasco.
Additionally, they make it more difficult to develop on Exynos devices by, violating the GPL, (which the kernel is licenced under) by holding back parts of the kernel source code, to where what they provides rarely is enough to create a booting kernel, as is required. This makes it to where we can't really see how they make it work and reverse engineer a working kernel.
Maybe one of the s6 developers will port LineageOS to the S6's.
akc47 said:
Will the new Lineage OS builds fix old bugs inherent in the old CM14.1 nightlies? Since the first CM14.1 build for my phone (HTC one m8), fellow Canadian users have reported that turning on location services resulted in bootloops (this did not occur with CM13). The problem was never fully fixed, and it didn't seem like anybody was working on a solution. It would be great if the new Lineage OS builds would have these old issues resolved.
Click to expand...
Click to collapse
Lineage os = cyanogenMOD yes eventually they will fix it but lineage os is cyanogen so they will have the exactly the same everything except for name. Big and everything will be carried over.
Sent from my htc_m8 using XDA Labs
how can you ask for features to be added in lineageos? will the listen to their users better than cm did?
yakie996 said:
how can you ask for features to be added in lineageos? will the listen to their users better than cm did?
Click to expand...
Click to collapse
OMG how much time do I need to explain this? Lineage=cm every in cm is in lineage. All lineage stuff IS cm. Lineage is just a different name of cm
Sent from my htc_m8 using XDA Labs
justinchao740 said:
OMG how much time do I need to explain this? Lineage=cm every in cm is in lineage. All lineage stuff IS cm. Lineage is just a different name of cm
Sent from my htc_m8 using XDA Labs
Click to expand...
Click to collapse
yeah but other peoples with other ideas/mindset?
yakie996 said:
yeah but other peoples with other ideas/mindset?
Click to expand...
Click to collapse
You can post it on the lineage os main thread and hope it gets read.
Sent from my htc_m8 using XDA Labs
justinchao740 said:
You can post it on the lineage os main thread and hope it gets read.
Sent from my htc_m8 using XDA Labs
Click to expand...
Click to collapse
thats not how it should work, should it? I'll try
Bump
Sent from my Motorola XT1080 using XDA Labs
Hello,
As some people heard, i really try to get Android Wear 2.0 for our beloved SmartWatch 3.
And it's possible, sources, device trees, all exist to build a working own compiled Android Wear 2.0.
So this thread tells about the current process of the port
PROGRESS
Code:
Repo synced
First build finished (not buildable yet due no blobs included
GAPPS Porting in progress
Fixed to 99% the device tree
Updating Blobs to M1D64T in progress
Using own Device tree
SOURCES
Device Tree for tetra:
https://github.com/Sony-SmartWatch-3-OSS/android_device_tree_tetra_eng_prerelease
Device Kernel for tetra (unmodified):
https://android.googlesource.com/kernel/bcm/+/android-wear-6.0.1_r0.99
(we can use MM kernel on Nougat too, maybe some patches needed but that's okay)
Prebuilts/Blobs for tetra:
https://github.com/Sony-SmartWatch-3-OSS/vendor_prebuilts_tetra
For Discussions go to this thread please: https://forum.xda-developers.com/smartwatch-3/general/companion-thread-android-wear-2-0-t3565693
If you want to help me on this project, write to me via telegram: https://t.me/PDesire
I need that so much any ETA ?
By the way keep up the good work !
Nice to see someone is working on this :victory:
Sent from my Sony Xperia Z5 using XDA Labs
Thanks for your job.
Enviado desde mi Redmi Note 3 mediante Tapatalk
great!!! thanks
Dear PDesire,,
My support can be only moral..... :crying:
And I hoping good news soon from you
Thx again for your great hard work :good:
thankx you great hard work and good luck my friend
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Certain components of Android (and therefore Wear) come from third parties and have licenses which require the source code to be made available (e.g. the Linux kernel). The components made available via the AOSP repositories for releases like Wear are, afaik, the components which have that type of license.
Wear is a release which has taken the same path as Honeycomb. I can understand that for open source fans and people looking to tinker with a working system it’s somewhat disappointing to see, but those are the choices Google has made.
Click to expand...
Click to collapse
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
drakonizer said:
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
Click to expand...
Click to collapse
Yeah I've seen these, and already fixed. Patch comes soon.
Things for WLAN and BT for example are on google repo too and if a library or something is missing we can use it from M1D64T
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
Click to expand...
Click to collapse
Lel then I can't understand why the build is working xD at least I am building in time and already 14% finished
I know some libs we have to grab from the Marshmallow FW but that shouldn't be a big deal
At least we also need some things from Preview 2 so we can get our AW 2.0 Preview 2 working
So I try my best to grab much from source and if required also from FW, but all in all its possible for our SmartWatch 3 to get Android Wear 2.0
Your PDesire
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
xpatze85x said:
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
Click to expand...
Click to collapse
Because there aren't any sources of the final version.
@PDesire :
You're the man...keep up a good work ???
Hey @PDesire , any news? I'm sooooo hyped!!!
Thank bro I hope
Thanks for this!
So current status is:
Code:
Repo synced
First Test build stopped to fix things on device tree
Expected in future:
Code:
Blobs dump
Fully fixed Device tree
Creating vendor for tetra
Adding overlays for framework to device tree
Some mix with armv7-a-neon generic
Gapps Dump
Expected in far future:
Code:
Creating an OSS project for tetra (like sonyxperiadev but for tetra)
So guys I will do more tomorrow as I am awake already from Friday 7AM - 3AM Saturday (right now GMT +1) and working on it and I need my sleep xD
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Your PDesire
PDesire said:
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Click to expand...
Click to collapse
And I can confirm my donation is coming when a working build is ready, and I suppose others are coming, isn't it guys? ???
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Neo Cortex said:
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. That'll only work on an official firmware, unfortunately...
Thank you very much, hope you will finish it without problems~!