Related
First of all, I know that this might not be the right forum for this, but since this id is new I am not allow to post the thread on the development forum. Now that I got that out of the way. I think a lot of you would really enjoy this video =)
We have started an effort to port HTC View to AOKP ICS. It's far from fully working. But we hope to get some of the basic functionality working in the coming weeks before we release the rom. So stay tuned!
Video 1
http://youtu.be/mW8qLrse4pc
Video 2
http://www.youtube.com/watch?v=bA9IllruYZA
List of things that are working so far.
WiFi, touch screen, captivity buttons(no back light), GPS, sound, HW accelaration? (not sure, as we don't know how to test it), internal sd card
List of things that we're working on before a rom release.
1. On screen button has weird look on some apps, it shrinks to a very small icons.
2. HD movies don't play, Omx codec issue?
3. Touch screen seems to be un-responsive in some game apps.
4. BT doesn't work at all (not as important)
5. Pen doesn't work at all (not as important)
If you have any ideas on how to fix these issues or provide some ideas what could be the cause of the issue (for example, you encounter the issue in other devices and know where to look for the issue) Please let us know by posting on the thread or PM us so we could speed up the release.
This thread is now close and has been moved to development forum as there is a pre-alpha rom for download.
http://forum.xda-developers.com/showthread.php?t=1673430
That looks great, i dont have an evo view, but a flyer bu i see that you have been able to avoid the graphic seizure we have on the flyer roms, i think maybe you and drew garen could colaborate some of your work, but idk, im not a dev or anything, but looks great
Drew Garen ROM
Same here hope you can collaborate with drew to get the graphical seizure issue worked ot between the two of you - I'll post this in Drew Garen's Dev thread.
We're open to share our experiences, if someone post specific questions regards to a specific problem like graphical seizure issue mhkabir98 mentioned. We could provide some ideas. But keep in mind that we're still talking about 2 different devices so there might be areas where they will differ.
Can you elaborate or maybe post a short video of what you mean by graphical seizure?
if i get the time i will eventually take some pics and tape it so you can see it
Wow, looks great so far. Hope to see WiFi, Bluetooth, and GPS working soon.
I'm willing to test if you need it. I don't really use my View for anything important right now.
awesome man! pumped!
looking good! thanks for sharing the progress. sounds very promising. as a view user, the idea of getting ics before the flyer makes me grin.
schadenfroh said:
looking good! thanks for sharing the progress. sounds very promising. as a view user, the idea of getting ics before the flyer makes me grin.
Click to expand...
Click to collapse
your name fit's very good to your comment xD
freak4dell said:
Wow, looks great so far. Hope to see WiFi, Bluetooth, and GPS working soon.
I'm willing to test if you need it. I don't really use my View for anything important right now.
Click to expand...
Click to collapse
Got sound to work. Graphic is much better now, there are no red boarders anymore. Wifi is so close to working.... thanks for the offer, will probably need help when we test app compatibility.
yncconsulting said:
Got sound to work. Graphic is much better now, there are no red boarders anymore. Wifi is so close to working.... thanks for the offer, will probably need help when we test app compatibility.
Click to expand...
Click to collapse
funny,
i think the Flyer is at the same stage too
you're in a competition and reached the same breakthrough around the same time, cool!
you should work with Garen on the wifi solution, there are always room for programmers to fix things.
This is awesome!!! I had kind if given up.
Sent from my Galaxy Nexus using xda premium
wow i might have to dust off my view now lol
wifi works now. will post a video later with the latest
I will happily donate for this, thanks for your hard work!
oldpueblo said:
I will happily donate for this, thanks for your hard work!
Click to expand...
Click to collapse
thanks. that's encouraging
Update video.
http://www.youtube.com/watch?v=bA9IllruYZA
That's looking great -- awesome work!
Got a newbie question. Since we're building this rom from HTC HC kernel source + AOKP source tree. Does this consider porting or building a rom? What is the difference?
yncconsulting said:
Got a newbie question. Since we're building this rom from HTC HC kernel source + AOKP source tree. Does this consider porting or building a rom? What is the difference?
Click to expand...
Click to collapse
my personal opinion which is: porting if you have no compatible drivers available or framework already working on the platform.
- If HTC did not develop any drivers and framework for ICS and for our view/flyer, it becomes a port.
- If you use drivers from another device because HTC did build it, its a port.
- If you take panel device kernel driver and adapt it to this device, its a port. but changes are development.
porting is using existing source or drivers and make it work on another device.
kernel is an exception since all of it is opensource and everything build a custom kernel.
framework in aokp builds are modified aosp sources, where most is compiled from source with changes to source (which becomes a port, like you see old games ported to new devices)
but those i made, are nearly 100% ports, i did smali changes, a few library hardcoding changes into binary files, and only a few kernel changes.
i would call my changes 100% porting.
even if i ported a camera driver from desire hd, which again is not build from scratch.
a rom build is very common as i see it, when guys combine files after their choice and changes some graphics + apk's changes. that is a definate rom build. if you got not development c/java/smali involved) it cannot be a port or a developer rom, its a rom mod(ified) of an original with changes.
its not easy to define "build" .
a modified rom build, or compiled build from source.
not a direction on the term, but just my opinion on this.
(previously already mentioned that ports never are any good, and ICS builds from source are better.)
some people porting are better than others.
I'm confused - what are the differences/advantages/disadvantages/progress/status of the two options of CM9 ROMs?
MunJeni
WinSuk
"official" CM9 (which I haven't really seen yet)
Maybe I'm the only one confused, but these two ROM developers seem to be working both together and separately.
Don't get me wrong - I'm thrilled that multiple people are working on an ICS ROM for the Aria. I just want to know what the differences are.
Thanks,
Dan
They use different kernels. as far as I know thats pretty much it. I'm running munjini's currently and it works great for the most part
80+% of munjeni's ROM came from mine, if that helps. Yet everyone is exploding over it
I think that the projects should be merged with the best parts in each one. You both do great work and it should be best for the community to combine efforts and avoid confusion and supporting two projects.
CaptainMaki said:
I think that the projects should be merged with the best parts in each one. You both do great work and it should be best for the community to combine efforts and avoid confusion and supporting two projects.
Click to expand...
Click to collapse
Already tried that.
CaptainMaki said:
I think that the projects should be merged with the best parts in each one. You both do great work and it should be best for the community to combine efforts and avoid confusion and supporting two projects.
Click to expand...
Click to collapse
I tried but all my commit pushed to WinSuk github was reverted so I opened separated git using initial repo from WinSuk and started working separated... but builds between WinSuk and me is not drastically diferent, thing about 2 roms is good thing becouse we have 2 diferent tests and we are at finish abble to merge good things between 2 roms!
if you both be able to work together in the end that would be awesome and the best for the community.
Again, thanks for both of you on all the hard work you put into this.
Big thanks to you both. I have been running the Munjeni May 10 build for just a few days now but it is working great. I love how fast the GPS gets a lock (easily 20x faster than CM7.2).
what navigation software are you using. cause I'm still have trouble with getting a fast lock on some of them.
CaptainMaki said:
what navigation software are you using. cause I'm still have trouble with getting a fast lock on some of them.
Click to expand...
Click to collapse
Stock Android Maps and Navigation. However, the first time it did say I was a full 2 states away. Letting it settle for a day seemed to do the trick.
Hey guys, hoping anyone who finds this project interesting reads this.
I'm currently working on a tw kernel for the i9505, and have been doing some major backporting feature-wise to our device, including power management (autosuspend, faux's powersuspend, state notifier, all working!), cpu/scheduling infrastructure, all the fun little tweaks, etc.
I'm wondering if anyone wants to work on it with me? Making kernels is fun, but I'd love to have fellow geeks to discuss/work on stuff with.
Eventually I'd like to look into reasonably building an upstreamed kernel with full device tree support, (min 3.10) as mainline is finally adding 8064/8960 dtb support. Only issues there is that support for the board skipped kernel versions 3.4-4.1, so some 3.1x hacking would come into play, as well as the unique qualities of jfltexx's board that are samsung specific (again more hacking). Still, it's more of a head start than it would be from scratch. Also we'd have to use of_compat given that little kernel bootloader building is (probably) out of the question for this device.
Anyway, anyone who is interested feel free to get a hold of me, and check out https://github.com/robcore/machinex
Cheers
Rob
i do
i although i am working on CM roms
optimized cm13.0 is mine
optimzied cm14.0 too
now releasing optimized cm14.1
if u care to come with me,tell me
side said:
i do
i although i am working on CM roms
optimized cm13.0 is mine
optimzied cm14.0 too
now releasing optimized cm14.1
if u care to come with me,tell me
Click to expand...
Click to collapse
Hehe I was just chatting with someone today regarding how I'd be more than happy to work on a CM kernel, but have no bloody clue regarding the specific needs I'd have to consider for cm. I'm more than happy to work with you though, so long as you are able to point me in the right direction sometimes and are willing to be patient with my *limited* git skills (I've had a couple blokes help me with cherry-picking instead of manual patching, but haven't attempted yet because last time I broke my repo :silly: ). I'm more than happy to "branch" out, pun intended. Do you have telegram? I'm @robcore
robcore said:
Hehe I was just chatting with someone today regarding how I'd be more than happy to work on a CM kernel, but have no bloody clue regarding the specific needs I'd have to consider for cm. I'm more than happy to work with you though, so long as you are able to point me in the right direction sometimes and are willing to be patient with my *limited* git skills (I've had a couple blokes help me with cherry-picking instead of manual patching, but haven't attempted yet because last time I broke my repo :silly: ). I'm more than happy to "branch" out, pun intended. Do you have telegram? I'm @robcore
Click to expand...
Click to collapse
i just saw that reply.i dont know how i lost it. u better send me a pm
Any word out for Cyanogenmod for Moto Z?
TWRP Team has showed amazing support already building recovery for it
The Hardware is awesome, would be cool if CM 13 or 14 comes to this phone
I hope but I don't think so.
CM does have very few SD810/20 devices. We have to hope for an unofficial port.
I hope so too, the phone is still new to the market, lets wait until developers get their hands on it
The problem with Z phones is the mods and how easy/hard it will be to support mods in other than stock based mods. But I sure hope that simple mods like the battery mod will work eventually. All depends on the additional needed software. Are the "Moto stuff" downloadable and useable on other roms than stock? Or do other roms need to build the very own support all from scratch?
İ finally built working cm14.1
But so many things are not working
Like
Wifi
Brightness
Simcards
Camera
Mods(are you kidding me!)
And also drains battery so flawlessly
But other things working like:
Bluetooth
Fingerprint
Touch
...
I'm working on it until someone upload official stock firmware 7.1 but this device need more developer and I'm alone on this project
If someone can help me contact me to build more stuffs together
just registered to say i've got most things working (ish) here:
the github url slash motoz-2016/android_device_motorola_griffin (not going to spam a bunch of posts just to submit a link, derp)
only things broken in 14.1 are:
- weird battery life issues (it lasts quite a while, but sometimes certain tasks seem to drain it way down)
- radio doesn't recover if it loses signal (curse you elevators)
- no mods support
- camera (this was working in 14.0 and died when i moved to 14.1)
- generally odd little things.
I havn't had much time recently to work on it (hope to change that soon) but it's been a daily driver of mine for a few weeks.
on the mods side of things, all the kernel support for them is already released on moto's github. it's just a matter of us actually using it (my kernel actually builds the kernel modules but that's not quite enough)
if any devs want to help contribute feel free to contact. (sent you a PM @erfanoabdi)
erfanoabdi said:
İ finally built working cm14.1
But so many things are not working
Like
Wifi
Brightness
Simcards
Camera
Mods(are you kidding me!)
And also drains battery so flawlessly
But other things working like:
Bluetooth
Fingerprint
Touch
...
I'm working on it until someone upload official stock firmware 7.1 but this device need more developer and I'm alone on this project
If someone can help me contact me to build more stuffs together
Click to expand...
Click to collapse
can't wait to see that out
sebirdman said:
just registered to say i've got most things working (ish) here:
the github url slash motoz-2016/android_device_motorola_griffin (not going to spam a bunch of posts just to submit a link, derp)
only things broken in 14.1 are:
- weird battery life issues (it lasts quite a while, but sometimes certain tasks seem to drain it way down)
- radio doesn't recover if it loses signal (curse you elevators)
- no mods support
- camera (this was working in 14.0 and died when i moved to 14.1)
- generally odd little things.
I havn't had much time recently to work on it (hope to change that soon) but it's been a daily driver of mine for a few weeks.
on the mods side of things, all the kernel support for them is already released on moto's github. it's just a matter of us actually using it (my kernel actually builds the kernel modules but that's not quite enough)
if any devs want to help contribute feel free to contact. (sent you a PM @erfanoabdi)
Click to expand...
Click to collapse
Just to simplify things: https://github.com/motoz-2016/android_device_motorola_griffin
Not much of a developper, however I can host files and probably set up an automated build on some servers.
sebirdman said:
just registered to say i've got most things working (ish) here:
the github url slash motoz-2016/android_device_motorola_griffin (not going to spam a bunch of posts just to submit a link, derp)
only things broken in 14.1 are:
- weird battery life issues (it lasts quite a while, but sometimes certain tasks seem to drain it way down)
- radio doesn't recover if it loses signal (curse you elevators)
- no mods support
- camera (this was working in 14.0 and died when i moved to 14.1)
- generally odd little things.
I havn't had much time recently to work on it (hope to change that soon) but it's been a daily driver of mine for a few weeks.
on the mods side of things, all the kernel support for them is already released on moto's github. it's just a matter of us actually using it (my kernel actually builds the kernel modules but that's not quite enough)
if any devs want to help contribute feel free to contact. (sent you a PM @erfanoabdi)
Click to expand...
Click to collapse
oh thanks for your post, i'm ready, let's do it together
thanks again for your device tree :fingers-crossed:
Soon.
Sent from my XT1650 using Tapatalk
Any update guys..
Manish54 said:
Any update guys..
Click to expand...
Click to collapse
i was working on naught droid OTA porting. but no success
so came back to CM project
as @sebirdman shared his device tree that was big step on project now i made todo list on google docs : https://docs.google.com/document/d/14-SJ6NVgDSHSiGkqpWVkXCc6N79BydhMnnYJaA-Htqo
if i make it little more useful i'll share flashable zip in this forum :fingers-crossed:
erfanoabdi said:
i was working on naught droid OTA porting. but no success
so came back to CM project
as @sebirdman shared his device tree that was big step on project now i made todo list on google docs : https://docs.google.com/document/d/14-SJ6NVgDSHSiGkqpWVkXCc6N79BydhMnnYJaA-Htqo
if i make it little more useful i'll share flashable zip in this forum :fingers-crossed:
Click to expand...
Click to collapse
CM sounds a lot better than the OTA :laugh:
Many many thanks sirs!!!
CM 14.1 please!!
CM is on the way
(uploading rom to mega ...)
check this out :
sadly I have the droid version I can't use this I wish sunshine team would work on the moto z but they said they are not Is there any bugs on the cm14.1?
Can't wait to try it
erfanoabdi said:
CM is on the way
(uploading rom to mega ...)
check this out :
Click to expand...
Click to collapse
I thought CM would never come to this phone.... :crying:
hassanman1997 said:
Can't wait to try it
Click to expand...
Click to collapse
now you can try it :
http://forum.xda-developers.com/moto-z/development/rom-cyanogenmod14-1-moto-z-t3514432
Once galactic stryder started to collected crowd funding to buy a new le max 2 and then also ordered it and then it now arrived because of some issues. Anybody can tell me what happened to the money of yours you donated? And why he is not developing? Just curious to know that!
Heyyo, he posted a while back that he has had stuff going on in life so it was delayed a few months for software development.
Tbh even once he starts it could be a few months before he has a properly working x2 build as he uses his own kernels with some stuff based on Darkobas (Oreo) and I haven't seen anything happening there either... So really who knows when we shall see some AOSPA x2 stuff.
Such is the way with crowdfunding anyways. We funded a device for him and it will take time for things to get done. I know I donated a bunch too but hey I am barely making progress on Oreo but I try with my limited software development skills and time.
He wrote to me that let max 2 "will be supported on our AOSPA 8 from April"
Let's wait for the guy solve his issues. Nobody forced us to donate. I am sure that he didn't run away with the LeMax2 :laugh: Any user should understand that developers are also people with jobs, family, etc. Heck, even to reply to xda Q&A takes time (thanks @ThE_MarD), so it's often to see that there's no answer from the dev to "why torch is not working" question or stuff like that.
Honestly speaking, even without him, the development of X2 is at a very good level by my standards.
I think we should also donate to infrag and all the others who worked really hard to fix the builds for this device.
Thanks to all for info
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
nope that's not correct bro recently he updated his profile and added le max2 and I can see some commits done in his lambda kernel so everyone cheers and hope for good
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
Forgive me, but it's a sad statement.
Actually, a passionate and skilled guy who did a good job with a very similar phone, offered to work on improving support for this device. I can't event think he needed another underpriced (because of lack of official support from manufacturer, bankrupt) smartphone
giaur said:
Let me undersrand it correctly. You bought new phone for some guy in hope he will develop rom, but no news from him, he ran away with new phone. Well there's a sucker born every minute.
Click to expand...
Click to collapse
He is very active kernel dev for Le pro 3, so it wasnt like, hey lets give new phone to random guy.
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
GalaticStryder said:
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
Click to expand...
Click to collapse
Thanks for clearing situation
Nice to see you after long break, hope you like yours new device
GalaticStryder said:
Hi, sorry for the delay, the phone has reached my door only yesterday, 5 months waiting - or even more - it's good that I have time now to develop and the phone, I just didn't get to XDA those last months so I get the hesitation of all the users when I was off and without the phone; time's passed and as you can see on my Github we have started moving again, wrote all my Kernel script to support the new device on both versions - one Kernel fits all, right? (my LG G2 users should remember that one) - as I'm planning to support stock M versions and the upcoming, if ever coming, N versions of EUI.
The stock Kernel code is a mess just like the one from Pro3 - what did I expect? - so I may time until Saturday to get the vanilla CAF one up and running stable. After that I'll set up my Ryzen machine with another distro, probably BBQ, to compile a more recent version of N or O.
I have just updated to the latest Chinese ROM (X821) to compare the Kernel messages and take some information to merge with my previous work, I'll open a DEVB thread as soon as I get something stable running for EUI users.
Hope that clears out any misunderstandings...
Click to expand...
Click to collapse
Thank you galactic stryder!
https://forum.xda-developers.com/showpost.php?p=75925873&postcount=318