Related
To keep them separate from the main thread, post 'em in here
Awesome Rusty, realle needed this thread.. You guys should team up, so it would be clear who is building these kangs. Maybe you could be listed in 1st post, and you could specify the small differences you have. I guess you all put something of your own into the kangs..
Really appreciate your work guys, gives a good hunch about what the future of Android 2.3.4 holds..
ionhide said:
I guess you all put something of your own into the kangs.
Click to expand...
Click to collapse
Not me as it happens
I just build what's been committed, anything from me would be identical to a nightly if the buildbot had run at the time.
I'd suggest to put a sort of scheme in the KANG posts. Something Like
Builder:
Date:
Base nightly:
Last merged commit included:
Cherry picks/custom changes:
So it would look like for example:
Builder: aMpeX
Date: 10/06/2011 11:08 CET
Base nightly: 42
Last merged commit included: Update prebuilt kernel and modules (android_device_lge_p990)
Cherry picks/custom changes: ADW.Launcher: Screen Transitions, Backup Categories
That way, the KANGs would be much more organized and would help to keep the Thread clean.
aMpeX said:
I'd suggest to put a sort of scheme in the KANG posts. Something Like
Builder:
Date:
Base nightly:
Last merged commit included:
Cherry picks/custom changes:
So it would look like for example:
Builder: aMpeX
Date: 10/06/2011 11:08 CET
Base nightly: 42
Last merged commit included: Update prebuilt kernel and modules (android_device_lge_p990)
Cherry picks/custom changes: ADW.Launcher: Screen Transitions, Backup Categories
That way, the KANGs would be much more organized and would help to keep the Thread clean.
Click to expand...
Click to collapse
+1 on this
Most of that is superfluous really.
Builder & date are kinda obvious from the post, and base nightly isn't really relevant when you include the last commit.
All you really need is a link, last commit and an MD5# to keep folks happy. Could always make a uniform template to cover that stuff though
All right, good plan
Builder: destilant
Date: 09/06/2011 - 21:44 CET
Base nightly: #41
Last merged commit included: V8: Stop generating v8.log in build root directory
Cherry picks/custom changes: none
Download
Rusty! said:
Most of that is superfluous really.
Builder & date are kinda obvious from the post, and base nightly isn't really relevant when you include the last commit.
All you really need is a link, last commit and an MD5# to keep folks happy. Could always make a uniform template to cover that stuff though
Click to expand...
Click to collapse
I've seen numerous "what are your cherry picks?" "which commits are included?" "will this print 100$ notes?" questions in the main CM7 Thread so I still think the template is a good idea
Oh yeah it's not a bad idea at all, just thought some tweaking might be in order. Of course you'd mention any cherry-picks, not sure how I forgot that one
Sorry for my noob question and sorry if it's the wrong place to ask: what exactly is a CM7 KANG build?
It's a build of CyanogenMod compiled by users, not the buildbot.
Rusty! said:
It's a build of CyanogenMod compiled by users, not the buildbot.
Click to expand...
Click to collapse
You should put this in the op
Sent from my Optimus 2X using XDA Premium App
New commits posted after #42, anyone up for making updated KANG? :-D
http://cm-nightlies.appspot.com/?device=p990
Sent from my Optimus 2X using XDA App
ionhide said:
New commits posted after #42, anyone up for making updated KANG? :-D
Click to expand...
Click to collapse
+1...
ionhide said:
New commits posted after #42, anyone up for making updated KANG? :-D
http://cm-nightlies.appspot.com/?device=p990
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
I would have done it, but have repo sync problem, due to internet
Fetching projects: 1% (3/259) android.git.kernel.org[0: 2001:6b0:e:4017:1972:112:1::]: errno=No route to host
android.git.kernel.org[0: 2001:500:60:10:1972:112:1::]: errno=No route to host
android.git.kernel.org[0: 2001:6b0:e:4017:1972:112:1::]: errno=No route to host
android.git.kernel.org[0: 2001:500:60:10:1972:112:1::]: errno=No route to host
Click to expand...
Click to collapse
Great that you made a kang thread!
Sent from my Optimus 2X using XDA Premium App
bhanvadia said:
I would have done it, but have repo sync problem, due to internet
Click to expand...
Click to collapse
Yep, getting the same issue here aswell..
Worked all right for me this morning when I updated my CWM thread.
Any of the kangs the notification lights that was shown on youtube?
I tried cherry-picking, but the notification light doesnt seem to be working.
*Update 3/6/12*: I probably should have done this awhile ago, but I just wanted to clarify that this was a one-off release. It will not be updated since Nightlies/Weeklies are up and running again. In fact, they will have everything this ROM has plus more!
In trying to build CM7 (w/ FP) from source, acerbix, crnkoj, and I unwittingly built CM7.2 . You can follow along with our adventures here. We found that using the FP branches of the Atrix-Dev-Team's github repos with the new upstream CyanogenMod changes no longer produced a fully working FP build. After merging and copying the necessary code in frameworks/base from the ADT's repo on top of the newer CM7 stuff, it gave us a working 7.2 build.
I thought others may want to try out an updated CM7. This was my first attempt at compiling from source, so there may be bugs. A few changes I've noticed:
- "Holo" lockscreen
- T9 dialer
- Corrected calendar lockscreen widget
- More detailed battery stats (I think).
There are more if you feel like looking through the CM commits since the last official weekly/nightly release.
I'm not a developer. I will not be offering any kind of support beyond the possible update when worthwhile upstream changes are made. However, feel free to ask and answer questions here. I'm sure the other community members will be willing to help one another out.
Please keep in mind that this is a kang and in no way related to the official CM7 build, so please do not use those threads to post issues if you decide to try this.
Here are all of the sources I used:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android
https://github.com/ghost-og/android_frameworks_base
Here's the download link:
https://rapidshare.com/files/2700446381/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Sorry for using RapidShare. Multiupload was having issues when I tried uploading this there. I'll try to change it later.
*edit* Dropbox mirror. Be gentle:
http://dl.dropbox.com/u/11998742/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Link not working for me mate...
Sent from my MB860 using XDA App
Thanks for this. How recent is this? Does it encompass all of these changes: https://cm-nightlies.appspot.com/?device=olympus
Nice work,ghost_og.
I've used CM7.2 before on my Defy and Milestone 2. Many improvements over previous CM7. I'm waiting for multiupload link. Thanks for your hard work.
guidoido004 said:
Link not working for me mate...
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmm, worked for me. It redirected at first, but then it should give you a 30-sec wait window. Sorry for the crappy hosting.
NguyenHuu said:
Thanks for this. How recent is this? Does it encompass all of these changes: https://cm-nightlies.appspot.com/?device=olympus
Click to expand...
Click to collapse
I built it 1/16/12, so I think the French translations were the last thing I caught. Sorry for the extra work, but checkout the main CM repo and checkout the commit history.
ghost_og said:
Hmm, worked for me. It redirected at first, but then it should give you a 30-sec wait window. Sorry for the crappy hosting.
I built it 1/16/12, so I think the French translations were the last thing I caught. Sorry for the extra work, but checkout the main CM repo and checkout the commit history.
Click to expand...
Click to collapse
Thanks, will test it out, been looking for some updates to CM7.
The only nightly update you doesnt have is the ones specific for atrix....
You also could add tweaks and mods on it ^^
Flashing now, lets see how much good is it. Hehehe
Sent from my MB860 using XDA App
ghost_og said:
In trying to build CM7 (w/ FP) from source, acerbix, crnkoj, and I unwittingly built CM7.2 . You can follow along with our adventures here. We found that using the FP branches of the Atrix-Dev-Team's github repos with the new upstream CyanogenMod changes no longer produced a fully working FP build. After merging and copying the necessary code in frameworks/base from the ADT's repo on top of the newer CM7 stuff, it gave us a working 7.2 build.
I thought others may want to try out an updated CM7. This was my first attempt at compiling from source, so there may be bugs. A few changes I've noticed:
- "Holo" lockscreen
- T9 dialer
- Corrected calendar lockscreen widget
- More detailed battery stats (I think).
There are more if you feel like looking through the CM commits since the last official weekly/nightly release.
I'm not a developer. I will not be offering any kind of support beyond the possible update when worthwhile upstream changes are made. However, feel free to ask and answer questions here. I'm sure the other community members will be willing to help one another out.
Please keep in mind that this is a kang and in no way related to the official CM7 build, so please do not use those threads to post issues if you decide to try this.
Here are all of the sources I used:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android
https://github.com/ghost-og/android_frameworks_base
Here's the download link:
https://rapidshare.com/files/2700446381/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Sorry for using RapidShare. Multiupload was having issues when I tried uploading this there. I'll try to change it later.
Click to expand...
Click to collapse
I think all of the fingerprint changes have been committed today, so you should get them if you pull the source to make your own build. No more splicing files necessary!
EDIT: Oops, I was wrong. Fingerprint branch was updated, but still need to merge those files into the base CM build.
the T9 dialer is great. Looking forward to more updates as more changes are comitted. Good work.
Let me mirror this up for you mate. Give me a while to upload it on my crappy connection.
kennethpenn said:
Let me mirror this up for you mate. Give me a while to upload it on my crappy connection.
Click to expand...
Click to collapse
Thank you! I appreciate it. Hehe, rapidshare...
ghost_og said:
Thank you! I appreciate it. Hehe, rapidshare...
Click to expand...
Click to collapse
http://bandbinnovations.com/xda/update-cm-7.2.0-Olympus-KANG-ghost_og.zip
Have fun!
ghost_og said:
In trying to build CM7 (w/ FP) from source, acerbix, crnkoj, and I unwittingly built CM7.2 . You can follow along with our adventures here. We found that using the FP branches of the Atrix-Dev-Team's github repos with the new upstream CyanogenMod changes no longer produced a fully working FP build. After merging and copying the necessary code in frameworks/base from the ADT's repo on top of the newer CM7 stuff, it gave us a working 7.2 build.
Click to expand...
Click to collapse
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
turl1 said:
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
Click to expand...
Click to collapse
Great news! I was debating whether or not to post this. I didn't want to step on any toes. Thanks for the hard work; I just synced and started a new build.
is it possible to flash this right over neutrino rom or is it best to full wipe?
Sent from my MB860 using XDA App
If coming from a cm7 based rom then just wipe /cache and dalvik. Been working for me switching between different versions.
Sent from my MB860 using XDA App
turl1 said:
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=xHhUmRE2YOo
Can faux kernel be used with this rom?
Nipit said:
Can faux kernel be used with this rom?
Click to expand...
Click to collapse
Yes. The latest open beta runs very well for me.
turl1 said:
Yeah, those two branches were unrebased and unmaintained for quite a bit I have cleaned up the FP code a bit these days and rebased them, so you can now build from them too.
PS: We'll probably release a new weekly soon, with another long term, supported release (ba2tf-style) following after if no obvious regressions appear.
Click to expand...
Click to collapse
Wow great news!! Will the Weekly #5 be based on CM7.2?
Here is my build of lollipop for the T800. it's useable in so far as being able to see what it's like.
It has been posted in here because it is not ready for prime time and I figured others might want to have a look. It has bugs and doesn't fully work so might not be suitable for daily use, but you decide
How to Install
Download zip to phone
Reboot to recovery
Flash CM12 zip
Flash gapps
Reboot
The first reboot may take a while so be patient.
Known Issues
Some slight graphical issues
Camera gives an error after each picture, just reopen to use use again.
Hardware keys aren't disabled if you use on-screen keys (but they are dimmed)
Video/Movies/Youtube won't play
Download Link
lonespeaker version (10th Dec) -- https://mega.co.nz/#!4ckg0BwB!AhpucIfXJ6P-Y1z7mxQgKkWzHVg4dEhkwiVEUvM3gyA
barracuda7 version -- http://forum.xda-developers.com/showpost.php?p=57300243&postcount=22
You can use any gapps but I use these ones -- https://s.basketbuild.com/gapps
Source Code
My CM12 Repo -- https://github.com/lonespeaker?tab=repositories
CyanogenMod -- https://github.com/CyanogenMod
Thanks and Credits
Thanks to @crpalmer (https://github.com/crpalmer) for the picassowifi files without whom this would not be possible.
Thanks to @Barracuda77777 (https://github.com/barracuda7), @eousphoros (https://github.com/eousphoros) for providing help and fixes here and on github.
// end
Changelog
Thanks to @Barracuda77777 - Post #22 contains an alternative version that he is working on.
http://forum.xda-developers.com/showpost.php?p=57300243&postcount=22
10th Dec
Camera is now working! But.... there is an error after you take a picture, so you need to reopen the camera app to take another picture, but at least you can take a picture!
Updated to CM12 sources 10th Dec 15:00 GMT.
7th Dec
Recents button now works. If you enable onscreen buttons, then the hardware buttons still work, albeit with the backlight on them turned off.
The sdcard seems to work, I had to reformat mine to get it recognised.
Wifi is now working thanks to barracuda7
Hoping T700/8.4 is not far behind. Can't test, but great job anyways. [emoji2]
Awesome job buddy!
hhairplane said:
Hoping T700/8.4 is not far behind. Can't test, but great job anyways. [emoji2]
Click to expand...
Click to collapse
T700 got it first check original development. Great work lone speaker on getting lollipop to the t800.
Looking forward to it !!! Great job !
Having more of a nightmare trying to work out how to use git and github to put my changes up there lol
My work is based off @crpalmer excellent work and with some not too big changes but I'd like to fork his work and then push my changes to keep his credits, but I'm having a nightmare
lonespeaker said:
Having more of a nightmare trying to work out how to use git and github to put my changes up there lol
My work is based off @crpalmer excellent work and with some not too big changes but I'd like to fork his work and then push my changes to keep his credits, but I'm having a nightmare
Click to expand...
Click to collapse
I fixed WIFI, Uploading now
Barracuda77777 said:
I fixed WIFI, Uploading now
Click to expand...
Click to collapse
excellent, how did you do it?
This is looking great! Awesome work. I realise its a very early build but hows the speed of it?
lonespeaker said:
excellent, how did you do it?
Click to expand...
Click to collapse
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Barracuda77777 said:
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Click to expand...
Click to collapse
I've been playing with ones from various places and no luck so Im so glad you figured it out. I will fork to my git and then try and work out how to add my own fixes to that fork and maybe be able to contribute this time lol
lonespeaker said:
I've been playing with ones from various places and no luck so Im so glad you figured it out. I will fork to my git and then try and work out how to add my own fixes to that fork and maybe be able to contribute this time lol
Click to expand...
Click to collapse
do you mind if I post my rom in this thread?
Barracuda77777 said:
do you mind if I post my rom in this thread?
Click to expand...
Click to collapse
No not at all, go for it
i
lonespeaker said:
No not at all, go for it
Click to expand...
Click to collapse
thank you
here is the build with WIFI working:
cm-12-20141206-UNOFFICIAL-chagallwifi.zip
here is the link to the vendor files
Also, like lonespeaker, l have borrowed heavily from @crpalmer to get this rom up and going, please thank him and also if you wish to donate to him that would be great, without him there would have been no LP rom yet
Barracuda77777 said:
it was the blobs, I will upload to git soon, I am uploading rom atm, once done, will do that next, so you can fork and fix your build
Click to expand...
Click to collapse
Always the blobs. Some day maybe we will get source for some of this stuff.
Would a build be possible for 805 as well?
Which gapps should I use...can you point me to it? Thanks
naomile said:
Which gapps should I use...can you point me to it? Thanks
Click to expand...
Click to collapse
Im pretty sure you need to use the lollipop gapps since cm12 is lollipop. http://highonandroid.com/android-apps/download-android-5-0-lollipop-gapps/
This is very promising . fun to give it a go. Thankyou for you hard work guys. As said in the OP not ready for daily driver yet. One thing I noticed as I could at the moment its all about smoothing out the bugs. The recents apps button doesn't work. (Although I did select in options to double press home button to bring up recent apps to get around it. On screen buttons disabled
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
Discontinued.
Awaiting for thread deletion.
Thanks...Nice work after your miui 5 ROM
Help please..
Need someone who can risk his device by testing this ROM......
Happy holi.....
Happy holi my friends...
May this holi bring lots of Colors in your life!! and in mine too.
Kunal Gautam said:
Need someone who can risk his device by testing this ROM......
Click to expand...
Click to collapse
I tried to install but it gives error 7 i think update.script should be rechecked.
Deep_dhimaan said:
I tried to install but it gives error 7 i think update.script should be rechecked.
Click to expand...
Click to collapse
Thank you very much, i've understood whats the problem( as a pm by ashkineeeeee).
New update coming soon. Stay tuned.
Hey bros...
so there were some problem with permissions, it seems that it is fixed now..
Flash the ROM and review here....
----------------------edit 1---------------------
dont flash the rom now!!!
Some files are missing in boot.img
how stupid i am!!
------------------------edit 2-----------------------
Flash it now!
Last build not installed,error 7.
mels01 said:
Last build not installed,error 7.
Click to expand...
Click to collapse
Logs,screenshots?
Try installing from internal storage... Or update your recovery to the latest one by android andi...
Thanks!
Hey, I would like to help out, can I have the link to the ROM?
theportal2 said:
Hey, I would like to help out, can I have the link to the ROM?
Click to expand...
Click to collapse
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Links
Kunal Gautam said:
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Have you seen this CM 11? https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cm-11-0-galaxy-tab-2-t3737392
Just made last month by @Deltadroid
Links are removed because *the ROM is not complete yet*.
Thanks, but I need to confirm a few things before I could use a ROM(includes init.d support and a bunch of other things). Also, it is very important that deltadroid provide me permission to use his ROM.
Thank you!
Regards,
KG
-----_edit_--------
I just saw deltadroid's thread, the title clearly says that the ROM is for p3110. I want to make a unified one. I need a ROM made with unified device tree.
If I do port, it will only work on p3110 and maybe on every 7" device. I don't want do this.
Sorry, but yeah thanks!
Just wait till 3 april 2018. Most probably I will upload.
Edit 2
Or I must say it an update. 75 percent of the work is done. Somehow I managed to get a base ROM(only I know how). Only build.prop editing and Updater script editing work left(these are the most difficult BTW).
Update coming soon. Stay tuned.
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Kunal Gautam said:
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Click to expand...
Click to collapse
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
secretwolf98 said:
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
Click to expand...
Click to collapse
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Kunal Gautam said:
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Click to expand...
Click to collapse
FYI, I port ROMs. It was pointers what to fix, if you wanted to get this ROM better, than it is already.
Kunal Gautam said:
(...)
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Android-Andi said:
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Click to expand...
Click to collapse
Thank you. For at least replying. You works will always be appreciated. Now, I am gonna close this thread. Thanks again!