Related
Hi There we have found complete sources of our phone Micromax A110 MTK 6577
We were hoping if any one Awsum Dev could compile an omni rom for our Beloved Phone here is the link to the sources http://pan.baidu.com/s/1ACPRk#dir/path=%2F8377%E8%BD%AF%E4%BB%B6%E5%8C%85
If u want u can contact our devs u can contact @[email protected] and @khan_frd2002 and also our kernel dev @varun.chitre15
And for compiling there is this guide http://wenku.baidu.com/link?url=GlZC...3XdjfuZXcip5zm
I hope i will receive Positive results and replies
Thnx
Andromodgod:cyclops:
if possible please upload to a better file hosting site. this is so slow it's causing the download to fail
cybojenix said:
if possible please upload to a better file hosting site. this is so slow it's causing the download to fail
Click to expand...
Click to collapse
Thnx for the reply 2 Questions
Are you from the omni team I.E help us in making rom
How long would the compilation take
U can contact all of us we are at http://forum.xda-developers.com/micromax-a110/development
Or Here
http://forum.xda-developers.com/micromax-a110/
Link will be provided as soon as possible :angel:
I'm a contributor there. I'm just curious as to what parts they change. seeing as mtk devices are dirt cheap here, I might consider getting some to work on if their sources aren't desperately bad
edit:
compilation doesn't take long. getting to the stage of getting a working compilation may take a while though
ps can the file labelled "alps patch" be uploaded first please. thanks
Thnx
@cybojenix Thnx for ur interest in our Phone one developer @[email protected] is already working on cm 10.2
And Varun Chitre is also a great dev u can ask anyone and all of them will help u
About the mirror i dont think it is possible cuz most of the people(Dev) Live in india or other places where the Internet connection is slow u can use an extension for firefox i will link it to you https://addons.mozilla.org/en-US/firefox/addon/downthemall/
ANd please try not to post cuz if u see ur post it say """"555 Posts"""" Lucky number
U can PM Me Thnx
I will ask devs to mirror it
yes buddy mirroring is needed....the downloading speed is so less that my downld has failed more than 4 tiimes..
Alps Patch file
Here is the link to patch file @cybojenix http://d-h.st/BAg
Leeching that to take a look.
Since none of us have a 6577 device, someone else will have to do the bringup work, but it would be interesting to see how much commonality there is between 6577 and 6589.
Unfortunately the problem is MTK's sources are a disorganized mess, and in many cases, their HALs are just wrappers around a blob. The source we have for R819 is for 4.2 - while xplodwild got 4.3 partially booting on R819, so far, the display drivers just crash on boot on 4.4.
Entropy512 said:
Leeching that to take a look.
Since none of us have a 6577 device, someone else will have to do the bringup work, but it would be interesting to see how much commonality there is between 6577 and 6589.
Unfortunately the problem is MTK's sources are a disorganized mess, and in many cases, their HALs are just wrappers around a blob. The source we have for R819 is for 4.2 - while xplodwild got 4.3 partially booting on R819, so far, the display drivers just crash on boot on 4.4.
Click to expand...
Click to collapse
From what I've looked at so far in the uploaded patch file, it doesn't seem to be too good. I was expecting to see diff patches.. from what is included in it, it seems to be partial, and out of the camera, there are only headers.
Waiting for the full source to be uploadec
Sent from my Nexus 7 using Tapatalk
cybojenix said:
From what I've looked at so far in the uploaded patch file, it doesn't seem to be too good. I was expecting to see diff patches.. from what is included in it, it seems to be partial, and out of the camera, there are only headers.
Waiting for the full source to be uploadec
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Source are uploaded here you go http://forum.xda-developers.com/showthread.php?p=48303269
Sent from my Nexus 4 using XDA Premium 4 mobile app
[SOURCE]Full MTK6577 AOSP tree + proprietary source: http://forum.xda-developers.com/showthread.php?t=2172440
*edit: These are sources for ICS. Reason: http://forum.xda-developers.com/showpost.php?p=48307124&postcount=134
Progress
Any report on the progress @cybojenix
andromodgod said:
Any report on the progress @cybojenix
Click to expand...
Click to collapse
Sources seem somewhat unhelpful at a first glance, however going deeper into them may reveal key parts that have Been overlooked
Sent from my Nexus 7 using Tapatalk
Any Good News
DO we have any good news from u @cybojenix
We are eagerly waiting for u
andromodgod said:
DO we have any good news from u @cybojenix
We are eagerly waiting for u
Click to expand...
Click to collapse
Please, check this comments:
http://forum.xda-developers.com/showpost.php?p=48628112&postcount=43
http://forum.xda-developers.com/showpost.php?p=48642380&postcount=44
mtk你还是放弃吧，很多都没有开源的，mtk提供整套方案给生产商，连生产商都没有源代码的。
Sent from my One X using xda app-developers app
I thought it is complete
Sent from my Nexus 4 using Tapatalk
Any news?
Related:
MediaTek driver sourcecode (want custom ROMs? read this!): http://forum.xda-developers.com/showthread.php?p=50146816
No complete source, nothing to accomplish.
I have been getting a few PM's for help with upgrading to a 4.4.2 device base. I would like to share what I think is the most efficient way to upgrade to 4.4.2 sources with the least issues. This is the method I use on my Mahdi Rom. I see devs with issues stopping them from going to full 4.4.2 device/kernel/vendor trees and I would like to help get some more roms updated. If most roms follow the same methods we can also have custom kernels again.
4.4 device tree: Heavily modified from our 4.2 CM device tree. I also fixed some RIL issues that would stop the new RIL from working in some roms.
4.4 vendor tree: Completely remade using hammerhead as the base for the best aosp compatibility. Only added necessary blobs to run our hardware. The old vendor tree had way too many added files that didn't need to be used as prebuilts. Added missing files that should be present in kitkat. Sprint camera is currently broken and hopefully a LS980 dev can figure it out (Believe this to be vendor related)
4.4 kernel - clean branch : Only added the commits required for the rom to function normally, specials thanks to rmcc (original author of ril, vibration, bt fixes in my kernel tree) and jackpotclavin for a lot of the original AOSP fixes and many things on the G2 tree. On the 4.4.2 tree I was unable to get call echo fixed and we had other strange audio bugs everywhere due to reliance on the stock rom and taiko file. I decided to replace all the vendor / kernel audio drivers with Nexus 5 wcd9320 drivers and use custom mixers and audio has been working perfectly so far. (All this is already in the links I posted)
Other requirements
This commit must be added to display-caf
Qcom common folder
CM media repo
If anyone needs help with issues updating a rom post here and I will try to help.
Of course, I'm no developer, but I just wanted to say thanks for all your help for the developing community DR87...As an avid ROM flasher, I am very excited at seeing the prospect of more roms being updated to use with 24A
thnx @dr87 from all of G2 community .
hmmmm ...
looks like some goodies are coming for my vs980 buddies
Time to get back to work ....
Hey people don't leave us Sprint G2 users behind.
Looking forward to a unified kernel for G2.
Also if in some way compatibility for jdi and lgd display panels could be found to co-exist in the same kernel it would be much easier for the kernel devs to put out their stuff in fewer kernel variants.
Just a thought.
You're a nice guy @dr87 for sharing to the other Devs.
Sent from my LG-D800 using XDA Premium 4 mobile app
This should be a bigg bigg sticky
Enviado desde mi LG-D802 mediante Tapatalk
Thanks dr87. I've been meaning to hit you up on hangouts, but I've been so busy with work lately. This will definitely help.
Anyone working on this with aospa sources? I am having media issues.
Sent from my LG-D802 using Tapatalk
Thank you so much for posting this, I am one of those PMers who were begging for the mighty wisdom of the doctor. :laugh:
If any of the other devs/maintainers would like a Hangout, I think that might be a great idea, I would be all for joining/creating it.
Reginald476 said:
Thank you so much for posting this, I am one of those PMers who were begging for the mighty wisdom of the doctor. :laugh:
If any of the other devs/maintainers would like a Hangout, I think that might be a great idea, I would be all for joining/creating it.
Click to expand...
Click to collapse
https://plus.google.com/+MarkoMan
Sent from my LG-D802 using Tapatalk
Reginald476 said:
Thank you so much for posting this, I am one of those PMers who were begging for the mighty wisdom of the doctor. :laugh:
If any of the other devs/maintainers would like a Hangout, I think that might be a great idea, I would be all for joining/creating it.
Click to expand...
Click to collapse
I'm getting my g2 today to work on updating Gummy to 4.4.2 sources so if you guys start a hangout, count me in. [email protected]
darkobas said:
https://plus.google.com/+MarkoMan
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
https://plus.google.com/+RussClark shoot me a Hangout and I will add you, please let me know which ROM you work on.
Will be updating Vanir this weekend
Hey doc! What do you know you are on the XDA Portal
http://www.xda-developers.com/android/need-help-updating-your-lg-g2-rom-to-4-4-2-sources/
Congrats you deserve it
arifqur said:
Hey doc! What do you know you are on the XDA Portal
http://www.xda-developers.com/android/need-help-updating-your-lg-g2-rom-to-4-4-2-sources/
Congrats you deserve it
Click to expand...
Click to collapse
Congratulations! Highly deserved! @dr87
arifqur said:
Hey doc! What do you know you are on the XDA Portal
http://www.xda-developers.com/android/need-help-updating-your-lg-g2-rom-to-4-4-2-sources/
Congrats you deserve it
Click to expand...
Click to collapse
Hah nice :good:
Anyone who forked the vendor repo should sync with me again, when I added the rest of the vendor folders I forgot to sort out the device filters which would cause some duplicate errors
hi dr87 this awesome thread is on the PORTAL...
~ups my bad, someone already told you...
thanks for this useful tree you made
I love your mahdi rom :good:
Just wanted to jump in here and say I appreciate all the work you guys are putting in.. I couldn't develop a wet paper bag but if any of you want a tester or somebody to chop it up with I'm your guy hit me up on hangouts [email protected]
Sent from my LG-LS980 using Tapatalk
@dr87, we seem to be having an issue with HD video with the new sources, any thoughts? Also if you want to join our group, there are about 7 of us in there now.
Thanks again for your hard work and huge thanks for sharing. :victory:
I've got slim booting on d800 and everything is working except for a few things I forgot to add overlays for. HD video is working fine on slim.
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimKat, ROM for the Moto E
Contributors
cybojenix
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2014-06-27
Last Updated 2014-06-27
Latest Build
V1.0, SlimKat 4.4.4 Build 6
Mobile data Doesn't work Confirmed
Auto Brightness doesn't work confirmed SlimRoms bug. It's only being polled every 10 seconds.
As far as I know, everything else is fine
I will upload the device folders at a later point closer to when SlimKat goes official for condor.
The kernel is pretty much stock, with minor edits to make camcorder work, and modules load.
Information and Requests
Firstly I'd like to massively apologise for not uploading this till now.
As some of you will already know, I have been somewhat ill due to the amount of work I have been putting in to my projects (no not for moto e).
To make up for this, I am posting a build now as a taster on the aosp qcom sources, rather than the newer caf based qcom sources. It's a daily usable rom, however later builds will have better performance.
I am also releasing a build of cm11 shortly.
XT1022 Is not supported as neither sim will work.
Now for the requests. at some point in the future (a few days, maybe a week), I will need access to the dual sim variant of the Moto E running stock. Ideally I will need access via TeamViewer to a windows or linux based pc with adb already set up, and an unlocked/rooted device that wants cm11.
I repeat.
Dual Sim is coming soon. Please stop asking
Thank you for being patient with me, but it will all soon pay off
from now on, If a question is asked that is answered already in the first page, or the last ten posts, or one that is easy to find with the search bar, please link this post to them.
Yay!! Thanks for your hard work! Will try this tomorrow
Just one question: Dual sim is supported?
Gogeta said:
Yay!! Thanks for your hard work! Will try this tomorrow
Just one question: Dual sim is supported?
Click to expand...
Click to collapse
Please read the third post.
Also SlimRoms does not support dual sim, and has no intention to any time soon.
Thanks for the work
Thanks for the work... can you send me patches for this..
xperiafan13 said:
Thanks for the work... can you send me patches for this..
Click to expand...
Click to collapse
No but I'll say the approach you should take to fix it.
To build, there is an error that shows from qcom/media. To fix that you had to patch a kernel header. Use git to find the commit the definition is made, and that will fix camera.
To fix bt, check the bt loading script in etc. You will notice there are two blobs missing. Running these blobs will show there is another blob missing.
What other bugs do you have?
cybojenix said:
no but i'll say the approach you should take to fix it.
To build, there is an error that shows from qcom/media. To fix that you had to patch a kernel header. Use git to find the commit the definition is made, and that will fix camera.
To fix bt, check the bt loading script in etc. You will notice there are two blobs missing. Running these blobs will show there is another blob missing.
What other bugs do you have?
Click to expand...
Click to collapse
ok thanks... Im check this... Thanks in advance
you rockss!!!
Mobile data
cybojenix said:
Mobile data untested but probably works (can't test as no sim in)
Auto Brightness doesn't work confirmed SlimRoms bug. It's only being polled every 10 seconds.
As far as I know, everything else is fine
I will upload the device folders at a later point closer to when SlimKat goes official for condor.
The kernel is pretty much stock, with minor edits to make camcorder work, and modules load.
Click to expand...
Click to collapse
Mobile data doesn't work, good work on everything else.
Kind Regards.
First of all congrats man
Here are some of the doubts
Since I have a Indian version moto e (dual sim) as per the given information it won't support so my doubt is if I install this ROM will at least one sim work I don't care about other sim and hate dual sim and do I need to replace any files from stock ROM?
Thanks in advance
cybojenix said:
Firstly I'd like to massively apologise for not uploading this till now.
As some of you will already know, I have been somewhat ill due to the amount of work I have been putting in to my projects (no not for moto e).
To make up for this, I am posting a build now as a taster on the aosp qcom sources, rather than the newer caf based qcom sources. It's a daily usable rom, however later builds will have better performance.
I am also releasing a build of cm11 shortly.
Now for the requests. at some point in the future (a few days, maybe a week), I will need access to the dual sim variant of the Moto E running stock. Ideally I will need access via TeamViewer to a windows or linux based pc with adb already set up, and an unlocked/rooted device that wants cm11.
Thank you for being patient with me, but it will all soon pay off
Click to expand...
Click to collapse
I've got the dual sim version.
Also, have team viewer, adb, fast boot, and a rooted stock ROM (not by choice) ready. Let me know when you need access.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
im always ready to help!!
Hetalk said:
I've got the dual sim version.
Also, have team viewer, adb, fast boot, and a rooted stock ROM (not by choice) ready. Let me know when you need access.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
cybojenix said:
Firstly I'd like to massively apologise for not uploading this till now.
As some of you will already know, I have been somewhat ill due to the amount of work I have been putting in to my projects (no not for moto e).
To make up for this, I am posting a build now as a taster on the aosp qcom sources, rather than the newer caf based qcom sources. It's a daily usable rom, however later builds will have better performance.
I am also releasing a build of cm11 shortly.
Now for the requests. at some point in the future (a few days, maybe a week), I will need access to the dual sim variant of the Moto E running stock. Ideally I will need access via TeamViewer to a windows or linux based pc with adb already set up, and an unlocked/rooted device that wants cm11.
Thank you for being patient with me, but it will all soon pay off
Click to expand...
Click to collapse
i do have Teamviewer, Windows 8.1 (ADB), Moto E XT1022 (Stock, Rooted, TWRP)
Hetalk said:
I've got the dual sim version.
Also, have team viewer, adb, fast boot, and a rooted stock ROM (not by choice) ready. Let me know when you need access.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same as above here ^
Contact anyone of us who are online.
not even single sim working in Moto E XT1022
cybojenix said:
Please read the third post.
Also SlimRoms does not support dual sim, and has no intention to any time soon.[/Q]
woah woaaah woaahhh.... its awwwesommmeeee... loved it but sad thing not even single sim working
atleast make single sim to work!!!
anyway awesome work :good::good::good:
Click to expand...
Click to collapse
iblaziner786 said:
cybojenix said:
Please read the third post.
Also SlimRoms does not support dual sim, and has no intention to any time soon.[/Q]
woah woaaah woaahhh.... its awwwesommmeeee... loved it but sad thing not even single sim working
atleast make single sim to work!!!
anyway awesome work :good::good::good:
Click to expand...
Click to collapse
Slim builds are always awesome.
I use them a lot on my gnexus.
Sent from my XT1022 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok thankyou to all the people who replied regarding dual sim. You truly are the best community I've been in so far.
Once I've got cm11 rolling I'll contact one of you to set up a build.
I know the fact that slim doesn't support dual sim is a disappointment, so here's the deal. If I get hold of a dual sim moto e, I will bring support for dual sim devices to Slim (probably unofficially).
cybojenix said:
Ok thankyou to all the people who replied regarding dual sim. You truly are the best community I've been in so far.
Once I've got cm11 rolling I'll contact one of you to set up a build.
I know the fact that slim doesn't support dual sim is a disappointment, so here's the deal. If I get hold of a dual sim moto e, I will bring support for dual sim devices to Slim (probably unofficially).
Click to expand...
Click to collapse
Exactly, you can do a weekly(or bi-weeklies) unofficial builds and post them in the same thread.
That would be awesome.:good:
Ok before any mods start messaging me/closing thread, I forgot to push the patched kernel source last night. I get on a computer in an hour or so. Sorry for the inconvenience.
Does it support dual Sim variant as no ROM support dual sim variant
Sent from my XT1022 using XDA Free mobile app
gtsfreak said:
Does it support dual Sim variant as no ROM support dual sim variant
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Please read first page or at least few previous posts always before posting. It should answer your questions.
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Website:
http://androidarmv6.github.io/
Source code:
https://github.com/androidarmv6
You can watch development as it progresses, or you can sign in and participate here:
http://review.androidarmv6.org/#/q/status:merged
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
sent from my towelrooted LG L34C using daishi4u bumped twrp 2.8.3.0 and bumped key-boot-recovery kernel
...as he looked back on the sleeping giants, exhausted from their long journey, the wizard Androidmeda new that he had taught them all that he could, and they had all that they needed. But he also knew that they would never be able to survive crossing the mountains into the new land. Only their child would be able...
Well I guess this is it my brothers. Seems that all has been tried, and CM-12 will not be released for armv6 devices. But many thanks to our devs for trying. It's been a long run. Amazing, just amazing.
ibub said:
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Source code:
https://github.com/androidarmv6
ROMs:
http://jenkins.androidarmv6.org
sent from my towelrooted LG L34C using tapatalk
Click to expand...
Click to collapse
Congrats! Nice preface wording, bro! :good:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Dovidhalevi said:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Click to expand...
Click to collapse
Thanks, link updated to View/All.
sent from my towelrooted LG L34C using tapatalk
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
D3oDex3D_AyusH said:
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
Click to expand...
Click to collapse
Just to be clear, this is not my work. Androidarmv6 team (mainly androidmeda for p500) compiles these ROMs. Thanks belong to them (him).
sent from my towelrooted LG L34C using tapatalk
Wut? ART isn't compatible with ARMv6, AFAIK.
Casserole said:
Wut? ART isn't compatible with ARMv6, AFAIK.
Click to expand...
Click to collapse
We shall soon see.
sent from my towelrooted LG L34C using tapatalk
CyanogenMod announces official CM12 Nightlies!
http://phandroid.com/2015/01/05/cyanogenmod-cm12-nightlies/
Do not even expect P500 on the list!
EDIT:
CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure
http://blog.gsmarena.com/cyanogenmo...able-31-devices-based-android-5-0-1-lollipop/
While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though! :good:
You can look at development of android_art as it progresses here:
http://review.androidarmv6.org/#/q/status:merged
and here:
http://review.androidarmv6.org/#/c/7676/
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
xu3sno said:
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
Click to expand...
Click to collapse
Trimmed>>Flashed>>Stuck at CM bootlogo
CCXAlex said:
Trimmed>>Flashed>>Stuck at CM bootlogo
Click to expand...
Click to collapse
+1K
GERRIT_CHANGES: 7676 7748 7693 7651 7751 7792
Code:
7676: * runtime : make entrypoints ARM; if the target arch is lower than
armv7, set armv6.
* compiler: add a new define: ARM_MODE_WORKAROUND, enable it if
the target cpu is arm11. Use ARM assembler and replace
Thumb{1-2} opcodes with ARM ones. Update some code to
support new opcodes
NOTE: kArm is not implemented, probably it use to work only in
portable mode.
7748: Compatibility work around for bad graphics driver dependency
7693: legacy OMX: squashed commit for legacy OMX support for LP
7651: Revert "Revert "Turn on BLE, GATT, and SMP of Bluetooth stack""
7751: msm7x27-common: Initial cm-12 bringup
7792: jemalloc: Force gcc for atomic functions
GCC built-in functions provide advanced things like prefetch, expected, synchronization...
Bootloog attached.
It seems bootloop's culprit is regarding with dynamic shared libraries (lib*.so) which must be fixed first.
It does not work on any device arvm6.
Link
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Also, a reminder of some things you shouldn't do (now or ever): don't ask for ETAs, don't spam the dev thread, and don't PM me asking for information that isn't on a public post.
There are many things that need to be fixed for armv6 devices. I've sorted out the major issues specific to Broadcom hardware, but there are more important issues that need solving for ARMv6 devices in general that are being working on by several people (assembly errors, ART compatibility, build system integration, etc.). It's going to take time. Thanks for your understanding.
Click to expand...
Click to collapse
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
xu3sno said:
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
Click to expand...
Click to collapse
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Any PlayStore said:
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Click to expand...
Click to collapse
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Quote:
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Click to expand...
Click to collapse
Yes, yes, we know or should know. But, hey, who does not want to be the first to see this play? The only reason I am staying off is because of the CM tricks with switching system and data partitions meaning recoveries are not compatible.
Anyway, diehards within the CM universe, once in that bootloop if ART had indeed done its thing, check remaining system space and contents of those /system/app/... folders. My (un-) educated guess is that this may become the big problem.
xu3sno said:
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Click to expand...
Click to collapse
I also attempted to install this. Initially my trimming method seems to have broken update binary, so flash failed. Next installed full ROM (/system =189MB) using @HardLight twrp 2.7.0.0 TLS (successfully flashed). Stuck at boot animation. No log (flashing while driving).
sent from my towelrooted LG L34C using tapatalk
Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
Reserved
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.
add me as participant to the repos ^^
https://github.com/OldDroid
OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support
First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying
mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?
Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.