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.
Related
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.
this is beta release. for p900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/RVXpEgc6c4GKo - this is modded recovery. flash via odin
2. https://yadi.sk/d/CHl8wTYYc4GMZ - patched kernel. (patched my 1.3 pro kernel)
https://yadi.sk/d/D2riVhEgc4GPP - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/jc4uxZeCc4GRb - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.
reserved
more reserved
bonuzzz said:
this is beta release. for p900 only.
I'll wrote full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
Click to expand...
Click to collapse
I saw earlier that you had plans for this, but I didn't expect it to happen this quickly.
Anyway, great initiative.
WOW
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
m_carleone82 said:
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
Click to expand...
Click to collapse
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers. I thought about ubuntu, but now I'm not going to have a deal with it. I advice you to look linux deploy
Great job
bonuzzz said:
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers.
Click to expand...
Click to collapse
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
ESmazter said:
Great job
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
Click to expand...
Click to collapse
If you could get it working it would be great.
arcadia2uk said:
If you could get it working it would be great.
Click to expand...
Click to collapse
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
bonuzzz said:
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
Click to expand...
Click to collapse
My appreciation was actually meant for ESmazter saying: I will look into it
oops, i haven't noticed esmazter's phrase
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
bonuzzz said:
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
Click to expand...
Click to collapse
I was still hoping to get the minor issues resolved, notably the issue with Rom's installer are not shown in the installed ROM's section.
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
hhairplane said:
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
Click to expand...
Click to collapse
I dont have any plans to port to other devices. It doesnt fully working and I dont have any progress with it...
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
brock28 said:
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
Click to expand...
Click to collapse
I dont recommend to use this multirom because it has the bug with sharing kernel. So you need to use similar roms as primary and as additional. I dont have an idea how to solve it at this moment.
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
Since this thread is no longer just about me trying to get lollipop running on this phone (I AM still doing that though) I decided to 'rebrand' it as a general development thread for OSA. What's OSA? It stands for Only Some Android...ok so whats that? A team name I came up with to make myself feel more important (btw we're always looking for contributors).
So instead of focusing on just lollipop I will be discussing pretty much anything and everything I am doing in regards to the Desire 510.
Original Post Below:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
OnlySomeDood said:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
Click to expand...
Click to collapse
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
pattyboi:) said:
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
Click to expand...
Click to collapse
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
OnlySomeDood said:
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
Click to expand...
Click to collapse
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
pattyboi:) said:
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
Click to expand...
Click to collapse
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Yeah I have gotten a few of those errors, but not on surfaceflinger, mine are mostly on bionic and libcutils
OnlySomeDood said:
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Click to expand...
Click to collapse
gonna be trying that myself,let me know if you get anywhere
for sure, that's what this thread is for afterall
OnlySomeDood said:
for sure, that's what this thread is for afterall
Click to expand...
Click to collapse
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
dip_spit said:
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
Click to expand...
Click to collapse
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
OnlySomeDood said:
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
Click to expand...
Click to collapse
Gotcha. I didn't even know that was a rule. I was just giving you the heads up lol.
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
OnlySomeDood said:
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
Click to expand...
Click to collapse
whats up with the kernel? im good in that department for the most part,roms are...eh,not my specialty
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
OnlySomeDood said:
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
Click to expand...
Click to collapse
can you post one of the errors when you get a sec?
& none,got so angry at the stupid libqdutils thing i had last night i havent even attempted anything yet,been working on setting zswap/vnswap up so we have some leeway when it comes to ram..you got github at all?
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
OnlySomeDood said:
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
Click to expand...
Click to collapse
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
dip_spit said:
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
Click to expand...
Click to collapse
well sh*t..i think there is a way to disable encryption from the ramdisk..not entirely sure how tho
pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
OnlySomeDood said:
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
Click to expand...
Click to collapse
i dont blame you,makes sense to me
I was thinking: since we have an unlocked bootloader and custom roms, how hard would be to port AOSP Nougat?
There is any tecnical difficulty, like kernel version, that can block us?
Not much, I would imagine.
As far as I can tell, it'd just take a dev that's interested in putting in the effort.
Yes, this counts as my "yes, please" vote for Z00T.
I am votting with yes
I was thinking about do a try and compile it straight away, but i fear i'm not experienced enough to make something bootable
I don't think that the kernel or other thing will block it, but we got a custom ROM so late and I don't think we'll have a CM14 very soon
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Jhyrachy said:
Cm14 should be prettt easy since we have cm 13, the point is that right now is not worth it because it's still in early stage, so a fully fledged cm13 would be more usefull.
AOSP is another talk because it's so barebone
Click to expand...
Click to collapse
Umm, thanks for your thoughts about trying to bring N, it seem you got the answer yourself
from what i look at Z00L/T source, other than some fix and caf one, they could bring N to L/T with some borrowed libs. And looking from our source, I still found some line with L/T on it, so, yes, dev may bring N to this device, just hope that libs going to work with this devices.
But as you said, a fully fledged cm13 would be useful, using RR build for 3 days, and got the problem as they says. Plus, for me, front camera isn't working (called arclib or something, front camera effect when using asus camera, it's working fine with other camera because they didn't load that lib). Constant lag when using GPS other than "gps only" (might RR only problem). etc..
Either way, I hope that you could join the team (or, is he a one man army?) maintaining this device, fixing things come first, upgrade when everything is fine. At least "ok".
I don't know about AOSP, but many say choose CM because of CM broad compatibility layer. If that's true, then AOSP might slightly harder...
or... not really.
Sent from my ASUS_Z00RD using XDA Labs
Interesting, I'm not developer but I think this is possibke, Android 7.0 supports S410, maybe CM14 will better than AOSP.
yeah i still waiting ??
Sent from my ASUS_Z00ED using Tapatalk
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
I, but it will be possible tonight because now i working , phone at home
imjohncarlo9 said:
Who wants to test BeanStalk 6.25 for Z00RD/Z00E?
Click to expand...
Click to collapse
i will try tomorrow ...good for this ??
Sent from my ASUS_Z00ED using Tapatalk
Some news?
waiting :victory:
Waiting for some USEFUL news.
Today I try to compile it, but do not know if I aim, because I'm not a developer and I have no experience, but I try the same, stay connected, sorry for my bad english
I can't download the sources because it me give an errore i can't compile a ROM,sorry
Still waiting for news.
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
kurnalcool said:
I tried to compile it myself, I downloaded all the sources, but since the Z00ED / RD is not officially supported by CyanogenMod, and then the repository and everything else must be manually added, I tried but I get error during compilation. Now we must wait for some developer is able to have time to complete it, because basically if you have created for the Z00L / Z00T do not see why you can not fill because they have the same processor. Sorry for my bad English
Click to expand...
Click to collapse
Hi! Could this help you in some way? I don't know how, but I hope there is something usefull. This is a link to a russian forum where CM13 for ZE500KL was first posted by his original creator. Is in russian but I think you can use google translate to read the forum http://4pda.ru/forum/index.php?showtopic=766921
--FOR MORE INFO AND NEWS ALWAYS CHECK MY LAST REPLY!--
Thanks for understanding!
PROJECT IS ABANDONED.
Regards,
Holy ****, finally. I cant try it out for my self cause i need to leave to malta tomorrow but i can try it later
MIUI Rom, finally!!!!
I hope they fix the bug as soon as possible
Again, the ROM is NOT bootable, I need logcats from you to fix the problem, hopefully.
So don't expect this to boot.
Thanks for understanding!
Try to take a look here Logcats
I hope to have helped
Giuseppe300715 said:
Try to take a look here http://https://forum.xda-developers.com/showthread.php?t=1726238
Click to expand...
Click to collapse
I cannot open the link. It gives me an error.
XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
He meant this link https://forum.xda-developers.com/showthread.php?t=1726238
XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
I just fix the connection
---------- Post added at 09:04 AM ---------- Previous post was at 08:50 AM ----------
[Universal] [Flashable] [Logcat] [Guide] So your test ROM build didn't boot
[UNIVERSAL][LOGCAT]How to get & read a logcat/ Troubleshoot your own issues!
That's all I've found and that can be useful for both this Rom and others that you will develop.
Thank you, but I know how to dump logcats. I asked you if you could provide me some logcats of the rom not booting from your device and send me.
Thank you.
XTutorials said:
The ROM is compiled, but it doesn't boot and me and @AymenDe7 need logcats.
I will provide a download link, but just in google drive so not much downloads will be allowed. Bootable version (if) will be released on androidfilehost.
https://drive.google.com/open?id=0Bx9qplihpe8YVUNZRTNnSFY1bkk
Full no reject source code:
https://github.com/aymende7/XTutorials_Miui8
For now I need logcats from you.
Thanks for understanding!
Click to expand...
Click to collapse
Here's my logcat. http://www117.zippyshare.com/v/WcWK3ksX/file.html
I think there's problem with OpenGL
06-13 10:04:20.297 2468 2468 E libEGL : load_driver(/system/lib64/egl/libGLES_mali.so): dlopen failed: library "/system/lib64/egl/libGLES_mali.so" not found
06-13 10:04:20.297 2468 2468 F libEGL : couldn't find an OpenGL ES implementation
--------- beginning of crash
Click to expand...
Click to collapse
And if you would copy libGLES_mali.so to /system/lib64/egl?
Would it work?
Thank you for your logcats. I will see what I can do.
How does it go with progress?
Should boot if you use custom kernel and copy&replace blobs
I am giving up on trying to fix that error message. I am trying to build AOSP 6 and then try again patchtom, hopefully I won't get that error.
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
haky 86 said:
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
Click to expand...
Click to collapse
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
Yeah. We have like 2 developers(one is a team) On this device. Haky and OpenKirin. And 6 "different" ROMs that all work the same, with the exception off the nougat FOMs, which have even more bugs.
lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
haky 86 said:
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
Click to expand...
Click to collapse
I know man, I wasn't talking about you. I was talking in general. I know you're doing god work, despite I'm not developing anything since a long time I still read forum and follow what's happening.
Like @Vinnipinni said, 2 guys and 6 "different" roms. But all working the same.
Back in times people were more likely waiting for stable CM/AOSP before compiling bunch of other distros. Now it's just mess.
I really wish I could go back to developing for android devices, especially now when I have programming knowledge and experience.