Related
MIUI dont have any armv6 libs so its not possible to port
please close
seems like 9.pngs are not correctly ported
tobbeson said:
hi i got a lot of request in porting MIUI
my first target is the launcher and i have already hit a bump
i used apk manager to first decompile it i then noticed that it wanted to have all imagery in the drawable folder but after that i get several errors that the drawables is missing but they are not
any help on this project is apreciated
Click to expand...
Click to collapse
you just started that is all needed for miui fans[cyanogen mod still i I L U ]
REST OF THE THINGS WILL COME MAN
hi,
according to this thread http://forum.xda-developers.com/showthread.php?t=884161&highlight=miui the guys over at the hero forum have ported all the pngs to mdpi but the problem are the miui devs because they wont release the source code.
xennr3 said:
hi,
according to this thread http://forum.xda-developers.com/showthread.php?t=884161&highlight=miui the guys over at the hero forum have ported all the pngs to mdpi but the problem are the miui devs because they wont release the source code.
Click to expand...
Click to collapse
But Desire have miui ROM where they get source code... ? Can we ask them gently?
Sent from my HTC Legend
janarp said:
But Desire have miui ROM where they get source code... ? Can we ask them gently?
Sent from my HTC Legend
Click to expand...
Click to collapse
well the desire is already hdpi we only actually need source code when porting the imagery
because the 9.png (i think) is created when compiling the apps
Ok. And what is the reason that miui devs wont release source code?
Sent from my HTC Legend
janarp said:
Ok. And what is the reason that miui devs wont release source code?
Sent from my HTC Legend
Click to expand...
Click to collapse
No idea actually seems stupid they could atleast release it or they should do a mdpi version
tobbeson said:
No idea actually seems stupid they could atleast release it or they should do a mdpi version
Click to expand...
Click to collapse
Yes that was I'm thinking too.
Sent from my HTC Legend
janarp said:
Yes that was I'm thinking too.
Sent from my HTC Legend
Click to expand...
Click to collapse
actually it is illegal in most countries not to release source code
android is open sourced in gplv2(i think)
and that states that all modifications to apps and system must be released open source
tobbeson said:
actually it is illegal in most countries not to release source code
android is open sourced in gplv2(i think)
and that states that all modifications to apps and system must be released open source
Click to expand...
Click to collapse
Where we can ask this source code? Maby I try to ask them and let's see what they say to me.
Sent from my HTC Legend
they are from china and this is .... difficult
xennr3 said:
they are from china and this is .... difficult
Click to expand...
Click to collapse
LOL ... good one.
Sent from my HTC Legend
They might speak English?
alexhtclegend said:
They might speak English?
Click to expand...
Click to collapse
Well try to ask them.
Sent from my HTC Legend
checked their whole website no contact what so ever
but if there are someone that wants to port the 9.png files then we maybe could make it work
Is their stuff covered by GPL? Android being open source doesn't mean anything that runs on it has to be as well. HTC doesn't need to open source Sense for example.
Trekvogel said:
Is their stuff covered by GPL? Android being open source doesn't mean anything that runs on it has to be as well. HTC doesn't need to open source Sense for example.
Click to expand...
Click to collapse
well sense is a standalone ui (launcher) like an app
but the actual android code that they edit is released
miui is built from aosp which is covered by GPL so that means that they must release big portions of the source code
The only thing they need to release source code for is the kernel
TheGrammarFreak said:
The only thing they need to release source code for is the kernel
Click to expand...
Click to collapse
And I read somewhere that they released kernel source code.
Sent from my HTC Legend
New thread:
Why did you made a new thread?
mDroidd said:
Hello
first: I want to release this public, but to start I decided to share it with some known guys
I'm into android for a while right now, and tried many things.
A few examples:
theming
build from kitchen
adb
build from source
To do these things, you need to do some steps. If you don't know what they are, or how you should do 'em, then you're in the right place
I teached myself (and my father teached me) some bash scripting.
ATM, I use it for resizing images.
I'll upload a screen tomorrow, together with more detailed specs.
For now, it's an easter egg for you to find out
FEATURES:
DOWNLOAD:
HOWTO:
Remember, many features will come later.
You kids have fun.
Click to expand...
Click to collapse
Wow! That would be cool!! HDPI>MDPI conversion would be very easy!! Thanks!!
Sent from my LG-P500 using XDA App
You're welcome, I had the problem first also
It uses a package called "imagemagick" and a few others, with a nice combination of commands
And don't say thanks only, also thank me
mDroidd said:
You're welcome, I had the problem first also
It uses a package called "imagemagick" and a few others, with a nice combination of commands
And don't say thanks only, also thank me
Click to expand...
Click to collapse
Good work!
Il have to try it asap...!
Updated first post, updated app, updated link.
It's now a direct link, just give it a shot!
And from now on, if people are not grateful (but they don't have to thank me) OR do not give comment on how I could improve it, I will keep this private and for my friends only.
Nice tool!
Will take a look at it and if I have some more ideas to include, I will let you know ; )
Sent from my LG-P500 using XDA App
mDroidd said:
Updated first post, updated app, updated link.
It's now a direct link, just give it a shot!
And from now on, if people are not grateful (but they don't have to thank me) OR do not give comment on how I could improve it, I will keep this private and for my friends only.
Click to expand...
Click to collapse
You might wanna release this in the General Android Development section where more people will be interested, since here there are quite few who are new to developing on android and there are more full-fledged developers who basically dont use such tools... releasing this in the general development section will encourage more newbies who are fairly new to editing apps n stuff or building an environment... this tool is great, but you need to make it public to get the 'actual' response u want...
Anyway, all the best for this tool, sadly now i dont have my pc, jus an old crappy netbook which is jus nuff fo browsing... shall try this in march after my final exams...
RockR172 said:
You might wanna release this in the General Android Development section where more people will be interested, since here there are quite few who are new to developing on android and there are more full-fledged developers who basically dont use such tools... releasing this in the general development section will encourage more newbies who are fairly new to editing apps n stuff or building an environment... this tool is great, but you need to make it public to get the 'actual' response u want...
Anyway, all the best for this tool, sadly now i dont have my pc, jus an old crappy netbook which is jus nuff fo browsing... shall try this in march after my final exams...
Click to expand...
Click to collapse
Thank you also, and you Arjen also.
I will release it there, and also in Android Chef Central. There will more people be intersted, I know.
But for now, I think you people would be nicer to me iwth suggesting idea's, just becuase some of you may know me
Anyways, after someone made a suggestion and I was able to include it and include cpfr, I will release it there
OK, done. included some more things.
I think I will be trying to PORT APK MULTI-TOOL to Linux
Should not be too hard. I'll include it in my script when it's done and submit it to the DEV to publish it.
But I want you to make a request, just to keep myself busy!
Is there ANYTHING that takes you too long, seems too hard for you, or something you want to automate?
If not, I'll continue with building from source.
Please comment within 3 days
mDroidd said:
OK, done. included some more things.
I think I will be trying to PORT APK MULTI-TOOL to Linux
Should not be too hard. I'll include it in my script when it's done and submit it to the DEV to publish it.
But I want you to make a request, just to keep myself busy!
Is there ANYTHING that takes you too long, seems too hard for you, or something you want to automate?
If not, I'll continue with building from source.
Please comment within 3 days
Click to expand...
Click to collapse
Maybe, automate the setting up of build environment for various versions of android...
So it would be like just start ur tool, go into the menu, select the build environment for the version your gonna build and it all does it by itself...
Downloading/installing packages etc..
I havent tested your tool so dunno if u have already included it in your tool...
Also, you might wanna create a directory of different types of custom roms and their github source codes link... like for example, cyanogenmod, omfgb, omgb, oxygen, aokp, codename android and so on...
So i open your tool, select the source i wanna download and it will do it...
Just my 2 cents...
Sent from my LG-P500 using XDA App
RockR172 said:
Maybe, automate the setting up of build environment for various versions of android...
So it would be like just start ur tool, go into the menu, select the build environment for the version your gonna build and it all does it by itself...
Downloading/installing packages etc..
I havent tested your tool so dunno if u have already included it in your tool...
Also, you might wanna create a directory of different types of custom roms and their github source codes link... like for example, cyanogenmod, omfgb, omgb, oxygen, aokp, codename android and so on...
So i open your tool, select the source i wanna download and it will do it...
Just my 2 cents...
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
+1 I think that would be a great addition.
Sent from my LG-P509 using xda premium
Lol, the first thing about installing packages is already included.
I sent you a PM about smthing, pkease watch.
I am busy including the next step: build environment.
Expect it to work within 2 days, if you click the first link it'll be one
Greets!
If you need a Hans with anything let me know
Sent from my PC36100 using Tapatalk
tommytomatoe said:
If you need a Hans with anything let me know
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Sure, I will Thank you.
Btw, tge post is now also at Chef central ;(
Greets!
Updated first post with FEATURES tab
Now everyone who will read this will answer?
mDroidd said:
Updated first post with FEATURES tab
Now everyone who will read this will answer?
Click to expand...
Click to collapse
A small typo??
Should'nt it be 'prepare build FROM source' and not 'form' source??
Leaving it, its come out great... n thx...
Did u add the directory stuff??
Sent from my iPad 3 using XDA App
RockR172 said:
A small typo??
Should'nt it be 'prepare build FROM source' and not 'form' source??
Leaving it, its come out great... n thx...
Did u add the directory stuff??
Sent from my iPad 3 using XDA App
Click to expand...
Click to collapse
Directory stuff: mik: done, oxygen: done, AOSP: done.
But adfad has multiple sources... I am gonna ask him
And yeah, typo, I'll edit right away!
Greets!
mDroidd said:
Directory stuff: mik: done, oxygen: done, AOSP: done.
But adfad has multiple sources... I am gonna ask him
And yeah, typo, I'll edit right away!
Greets!
Click to expand...
Click to collapse
Wait, this tool isnt just for O1...!
Its should me made for every phone out there... so maybe you should add the official sources and not ported sources... cuz if you start including port sources, it will be too much hassle trying to keep the source links updated, sometimes they change, too many ports for every available android device etc...
Also, u will b flooded with requests to add this source, add that source..
Do it like:
CyanogenMod- full official source from CM, github.com/cyanogenmod
Oxygen- full official source by oxygen team, (i dont remember the links)
AOSP
AOKP
CodeNameAndroid
OMGB
OMFGB
Etc etc
Add the official repo's n not ports...
It will help in keeping the sources more update as the official teams work more on their sources than individual porters do on their own sources...
Sent from my iPad 3 using XDA App
RockR172 said:
Wait, this tool isnt just for O1...!
Its should me made for every phone out there... so maybe you should add the official sources and not ported sources... cuz if you start including port sources, it will be too much hassle trying to keep the source links updated, sometimes they change, too many ports for every available android device etc...
Also, u will b flooded with requests to add this source, add that source..
Do it like:
CyanogenMod- full official source from CM, github.com/cyanogenmod
Oxygen- full official source by oxygen team, (i dont remember the links)
AOSP
AOKP
CodeNameAndroid
OMGB
OMFGB
Etc etc
Add the official repo's n not ports...
It will help in keeping the sources more update as the official teams work more on their sources than individual porters do on their own sources...
Sent from my iPad 3 using XDA App
Click to expand...
Click to collapse
I did
I am making funtions like this in bash:
function AOSP
{
repo init -u blablabla
}
and downstairs the script
AOSP
So you can edit it above
I am now making an LG Specific and a stock android one
Updated
Changelog:
Code:
#v1b4:
[^]Added copyright
[^]Updated Animation
[^]Added second section; looks better
[^]OOPS! I added CopieFrom under the option "c" wich is already changelog!
[^]Improved other than home directory - was not working
[^]ICS Blue characters <3
[^]Added BUILD FROM SOURCE option
[^]Custom animation speed :)
[>]To try if this works, please go into terminal and type:
cat --help
if it tells you the manual for "cat", then you are fine.
Option D from the main menu.
Have fun
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.
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