Related
i read something in the net while i was surfing yesterday, you can look here: http://www.androidcentral.com/motorola-atrix-hd-gets-official-cyanogenmod-support
and then reading these lines made me surprised(maybe getting official cyanogenmod support for ancora is impossible after this moment but who kowns?)
If an Android device has enough of a following, and there are developer(s) willing to commit (no pun intended) to maintaining the device in the official CyanogenMod source tree, this device becomes officially supported -- and receives official builds of the CyanogenMod ROM.
if someone be maintainer for our device can we get official support from CyanogenMod?
is this really possible?
ı mean our device source code are available in github(kernel source device source and vendor files)
maybe forking our device source into CyanogenMod source tree can make this possible or am ı wrong??
maybe this is a bulsh*it after this moment but just wondering
for example galaxy s is getting official support from Cyanogenmod still if im not mistaken mr. pawit is their maintainer and developer
ım waiting your answers brothers what do you think about that? @arco68 @arsradu @LeroViten @honeyx and all ancora devs
with my best regards :good:
The SGW was for more than 3 years without official CM support and we didn´t miss anything, so I don´t think this is that much important for the rest of it´s counted days.
honeyx said:
The SGW was for more than 3 years without official CM support and we didn´t miss anything, so I don´t think this is that much important for the rest of it´s counted days.
Click to expand...
Click to collapse
ı understood bro but is there any hope for galaxy w? return of ancora :good: and also ı understood that from your comment : technically this is possible,galaxy w can get official support from CM Team but this is unnecessary for this dead device isnt it?
I simply don´t think this will happen because you have to look from their point of view.
1. this device is a low activity device in Amercian terms. 2. So never was that popular to get their attention. 3. is already old and not up to date. 4. It´s hype time is almost over and many earlier SGW users are going to replace it. 5. CM is going a different route now and will be focusing on their "device" they are going to launch soon. And finally 6. Why should they change this now after already 3 years?
So if I were CM I would look for the future not looking back to the past with it´s outdated devices and not even waste a single tought about devices like the SGW.
Is this bad for the SGW owners? As long we are having Devs like Radu who are porting the latest ROMs to this device it really doesn´t matter CM is supporting it officially or not supporting it.
So what do you expect from being supported by CM? You only would be able to install the latest nightlys launched by the CM team with all the bugs in the CM code included and maybe some day fixed. A Dev who is porting their CM sources of course has to fight with these bugs too, but also cares to fix the most important ones.
I asked arco68 a while ago, and he said it's because of legacy camera drivers that we are unsupported.
Sent from my Nexus 5 using Tapatalk
SGWUser said:
I asked arco68 a while ago, and he said it's because of legacy camera drivers that we are unsupported.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
auhh thats true sir arne is right as always anyway thanx man for informing us
regards :good:
I don't think so...anyway, we already have the stable n smooth ROM so far. Without Officail, it's does not matter at all.
Hello sir @arco68
First of all huge thanx for your great work on our Wonders
And secondly i wonder something
We are using s5k4ecgx sensor for back camera
And if we add the following patches and if we use v4l2 for camera driver, Can we use CAF based qcom cameraHAL?
-http://www.spinics.net/lists/linux-media/msg50380.html
And probably if we use new qcom cameraHAL, then we wont need legacy stuff the CM doesnt like(MemoryHeapBase,Overlay)
Then maybe we can get cm nightlies
Maybe porting new camera Hal to our phone can be hard but we must not give up. We are so close to official CM after ION i think. We can do it and we can success :good:
Thanx
Regards
hack4er said:
Hello sir @arco68
First of all huge thanx for your great work on our Wonders
And secondly i wonder something
We are using s5k4ecgx sensor for back camera
And if we add the following patches and if we use v4l2 for camera driver, Can we use CAF based qcom cameraHAL?
-http://www.spinics.net/lists/linux-media/msg50380.html
And probably if we use new qcom cameraHAL, then we wont need legacy stuff the CM doesnt like(MemoryHeapBase,Overlay)
Then maybe we can get cm nightlies
Maybe porting new camera Hal to our phone can be hard but we must not give up. We are so close to official CM after ION i think. We can do it and we can success :good:
Thanx
Regards
Click to expand...
Click to collapse
That would be so f... Awesome *-*
Please we need someone who knows how to do this
Hallo i watch all this roms... They are all 4.2.2. In the sort time adroid L its out... And i have the big question when we have one real update ??? I have this phone 9 months until now i live in eu
gkm8123 said:
Hallo i watch all this roms... They are all 4.2.2. In the sort time adroid L its out... And i have the big question when we have one real update ??? I have this phone 9 months until now i live in eu
Click to expand...
Click to collapse
100% agree but unfortunately duo to mate 2 is out they have no plan to update mate1 to 4.3 or 4.4:crying:
i really think ham is good phablet and deserve better support from manufacturer.
mazi_v said:
100% agree but unfortunately duo to mate 2 is out they have no plan to update mate1 to 4.3 or 4.4:crying:
i really think ham is good phablet and deserve better support from manufacturer.
Click to expand...
Click to collapse
This kind of support let me turn away from Huawei. A pitty. But i want decent support. A phone schould get 2 year regular updates. Thats wat a customer deserves
Well you'll have to dive deeply into it to do the job of building a custom Android ROM. I just downloaded the kernel sources from the official JB (4.1) release, but I'm not sure how far I can get with that. Some experienced devs here posted that they would need Huawei's sources for KitKat to build a KitKat ROM, but I also have an Ascend P1 and I'm running a custom KitKat CyanogenMod build from the forums here although Huawei only released ICS (4.0) Kernel sources. I will have a try with a custom cross compiling toolchain of mine that I use for my Radxa Rock, but it's quite generic. I'll let you know how far I could get if at all.
Cheers!
The kernel build was successful, but I've simply used Google's latest toolchain (arm-linux-androideabi-4.6-android-4.4.4_r1). I'm now syncing the most recent Android repo, that will take some time. I will try to set everything up to start compiling tomorrow morning or something...
Just in case you want to build the kernel yourself as well: There is an indentation issue in one of Huawei's Makefiles for the touchscreen, you'll see an error message about it if you run the first make according to the README_kernel.txt. You can just add tabs and your file should look like this:
[drivers/huawei/device/touchscreen_Mate/Makefile]
Code:
[COLOR="DarkOrange"]#
# Makefile for the touchscreen drivers.
#
# Each configuration option enables a list of files.
obj-y += synaptics_i2c_rmi.o
obj-y += rmi_dev_6.o
obj-y += rmi_f54_6.o
obj-y += rmi_fw_update_6.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean[/COLOR]
CyReVolt said:
The kernel build was successful, but I've simply used Google's latest toolchain (arm-linux-androideabi-4.6-android-4.4.4_r1). I'm now syncing the most recent Android repo, that will take some time. I will try to set everything up to start compiling tomorrow morning or something...
Just in case you want to build the kernel yourself as well: There is an indentation issue in one of Huawei's Makefiles for the touchscreen, you'll see an error message about it if you run the first make according to the README_kernel.txt. You can just add tabs and your file should look like this:
[drivers/huawei/device/touchscreen_Mate/Makefile]
Code:
[COLOR="DarkOrange"]#
# Makefile for the touchscreen drivers.
#
# Each configuration option enables a list of files.
obj-y += synaptics_i2c_rmi.o
obj-y += rmi_dev_6.o
obj-y += rmi_f54_6.o
obj-y += rmi_fw_update_6.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean[/COLOR]
Click to expand...
Click to collapse
A kitkat kernel that would make you in my opinion almost immortal for Mate users
henk_j said:
A kitkat kernel that would make you in my opinion almost immortal for Mate users
Click to expand...
Click to collapse
We'll see, I'm still learning about the stuff, but the chances look quite fair. I've set up the rest of the environment and the build is running now. But I guess it will take some more hours. I usually need about 3.5 hours to build chrome, firefox or libreoffice. AOSP should be similar. I'll see how far it got today evening/night. But for now it looks good, I'm running with -j4 as recommended. ^^
CyReVolt said:
We'll see, I'm still learning about the stuff, but the chances look quite fair. I've set up the rest of the environment and the build is running now. But I guess it will take some more hours. I usually need about 3.5 hours to build chrome, firefox or libreoffice. AOSP should be similar. I'll see how far it got today evening/night. But for now it looks good, I'm running with -j4 as recommended. ^^
Click to expand...
Click to collapse
if you have more cores processor why dont increase the thread value so that build process will complete more quickly
svvv said:
if you have more cores processor why dont increase the thread value so that build process will complete more quickly
Click to expand...
Click to collapse
I have 2 cores, so 4 is quite fine. The next option would have been 16.
Take your time! we need more developers
Any news ?
Really appreciate the works here.
so many had forgotten Mate 1 and P6 since 2 & 7 came out...
For me the first editions are always the best although the the 2nd might have little differences or improvements (but always have flaws or bugs more than the 1st editions)..
so very much grateful and thanks for devs that spent their time looking at mate 1 and p6...
Will donate if theres any need for it..count on me for that..
[email protected]
gkm8123 said:
Any news ?
Click to expand...
Click to collapse
Come on, I'm writing every couple of hours...
Well, the news is: v8 failed in some point. I've just resynced the AOSP repo to start over. ^^ I'll let you know how it went today evening. I also have a job, you know.
CyReVolt said:
Come on, I'm writing every couple of hours...
Well, the news is: v8 failed in some point. I've just resynced the AOSP repo to start over. ^^ I'll let you know how it went today evening. I also have a job, you know.
Click to expand...
Click to collapse
Ok no problem, thank so much for your help
Well, the newer patches didn't resolve the issue so I decided to try the normal user build (I tried a full debug build first). For now it looks very promising. I'm not sure if I can figure out how to to fix the issue I had, so if this one fails at the same point (although as far as I understood it was one of the debug parts so it shouldn't), it might get a little harder. We'll see ^^
thank you mate.. i mean CyReVolt.
i hope ur doing ok with ur job also,, and really hope u give us a good news..
cumanisengdoang said:
thank you mate.. i mean CyReVolt.
i hope ur doing ok with ur job also,, and really hope u give us a good news..
Click to expand...
Click to collapse
Sure, np... actually, it failed again due to the same problem, and I quickly figured out the cause (I already had suspected that): I'm on a strongly hardened Linux system, and the
Code:
mksnapshot
tool was killed due to NX protection (see http://wiki.gentoo.org/wiki/Hardened/PaX_Quickstart#Understanding_PaX). So if you're running a PaX protected kernel or similar you might run into the same issue. Duh... -.-
It's up and running again, so let's wait for a result!
While waiting you can try the Android kernel I have attached. Don't ask me how to do that. I have no clue. This is just for fun. And for you!
Considering work: It was actually quite funny today because I had to work on a Mac and OSX feels just horrible to me. My boss asked me to take a glance at Xcode and especially the new beta and Swift. I'm so glad to be back at my Linux machine now.
CyReVolt said:
Well you'll have to dive deeply into it to do the job of building a custom Android ROM. I just downloaded the kernel sources from the official JB (4.1) release, but I'm not sure how far I can get with that. Some experienced devs here posted that they would need Huawei's sources for KitKat to build a KitKat ROM, but I also have an Ascend P1 and I'm running a custom KitKat CyanogenMod build from the forums here although Huawei only released ICS (4.0) Kernel sources. I will have a try with a custom cross compiling toolchain of mine that I use for my Radxa Rock, but it's quite generic. I'll let you know how far I could get if at all.
Cheers!
Click to expand...
Click to collapse
The main problem is not the kernel. We can build a kitkat rom with the 3.0.8 kernel , but we have no source for display part , audio part. We have to use the prebuilt hwcomposer , grallloc etc. . These prebuilt libs are compatible only with the android version of the stock rom they are coming from and with the kernel they are patched for.
With sources of display driver we can patch the kernel and the driver to work on KK . Like I did JB on ZTE V11,V71,V55 tablet with 2.6.35 kernel , but that device was QC based device with available display driver sources. (http://forum.xda-developers.com/showthread.php?t=1629630)
I have compiled a 4.3 rom for mate , but I am stuck at display. There are changed routines in framework which are not working with 4.2's display drivers . One solution can be to get these sources , or to change the framework to work with the 4.2' display driver.
The Mate is my first non QC chipset based device , but also the last too. This is my fourth device from Huawei and until now I was satisfied , they simply do not care Mate customers. The release of the KK for Mate is just a few hours job , but they wont do it.
joe.stone said:
The main problem is not the kernel. We can build a kitkat rom with the 3.0.8 kernel , but we have no source for display part , audio part. We have to use the prebuilt hwcomposer , grallloc etc. . These prebuilt libs are compatible only with the android version of the stock rom they are coming from and with the kernel they are patched for.
With sources of display driver we can patch the kernel and the driver to work on KK . Like I did JB on ZTE V11,V71,V55 tablet with 2.6.35 kernel , but that device was QC based device with available display driver sources. (http://forum.xda-developers.com/showthread.php?t=1629630)
I have compiled a 4.3 rom for mate , but I am stuck at display. There are changed routines in framework which are not working with 4.2's display drivers . One solution can be to get these sources , or to change the framework to work with the 4.2' display driver.
The Mate is my first non QC chipset based device , but also the last too. This is my fourth device from Huawei and until now I was satisfied , they simply do not care Mate customers. The release of the KK for Mate is just a few hours job , but they wont do it.
Click to expand...
Click to collapse
Thats why we have to get some sense into their heads thats trough they're Wallet. The only way tot make them do this strangely by hurting them where it counts.
Alright, I'm getting the point now... so I did some research.
The GPU is a Vivante GC4000, so might this help https://github.com/laanwj/etna_viv ?
I wouldn't mind the sound at first. I would love to work on this somehow.
Can you point out which files I should look at? I know a bit about the ARM/Thumb ISA, so I'd try to reverse engineer a little to either adjust the pre-built drivers or the framework using them. =) I don't give up very quickly, you know! Finally, I'd just contact Huawei and talk straight to them. Thanks in advance for all your efforts.
Cheers
CyReVolt
Hi everyone
Well, I'm trying to build my first rom today, and after a lot of tutorial, still something I don't understand.
So, I want to start with the last AOSPA and for now, I don't really know how to put in the local_manifest file. I have found some Github with android_device_samsung_klte source (I guess ?), but I see a lot of local_manifest (for aospa) with vendor = pa_klte. Someone can explain me that ? x)
Other question, what's the command "brunch" is ? Seems to be used to build, but my Linux didn't recognize it...
So, to sum up, I looking for someone who had already build an AOSPA Rom, in order to help me to build the klte build !
I would like to see a version of Paranoid Android for the Galaxy S5 as well. I own the Verizon Developer Edition of the phone and am willing to test out Paranoid Android builds for it.
We will never officially support the s5
#stayparanoid
No problem about the "officialy supported".
Anyone to help me ?
After some tests... Same error...
Why will you never officially support the s5?
I have been practicing c,c++,java,php,html since 5 years now i am making android apps its been 5 months doing that.I also have been rooting android devices and flashing custom roms since 2 years now I want to get my hands into porting Custom Roms for various devices. Since I dont know anything so I just want to know about how can I do this. Well making a complete rom will be not possible way to learn completely at once this is what I think. But now I am having two custom roms Cyanogenmod11 and Cyanogenmod12 for a low end device named Samsung galaxy fame gt-s6812 somebody has ported these roms for this device.Now, cm11 is working really very fine but cm12 having lot of bugs : 1.Microphone not working 2.Speaker not working 3.Unkown Baseband and IMEI number etc. I just thought that by just replacing some of the things like folders or files from cm11 to cm12 will work for this. Because many people are porting roms by just copying folders from one into another.
If this can be happened then which folders will get me rid of these bugs. Please help me out Links , explanations, videos anything which can give knowledge about all these stuffs. Thank you
Try to send @wulsic or @corsicanu a message, those two are main developers for out Galaxy Fame section.
dushyant30suthar said:
I have been practicing c,c++,java,php,html since 5 years now i am making android apps its been 5 months doing that.I also have been rooting android devices and flashing custom roms since 2 years now I want to get my hands into porting Custom Roms for various devices.
Click to expand...
Click to collapse
Well, its not as easy as copy and pasting because in the cm12.1 repository there are made some changes which removes compatibility with jellybean 4.1 based binaries so we are using patches to add back that compatibility and also for telephony etc. So we are on the way to get a good working cm12.1 the build with which I am busy with should work much better as the cm12 alpha0.1 as the dpi,sound,performance,security,telephony, microphone, video playback should be fixed. The only problem I still have to find out is why the rom is stuck at starting apps. If you want you can help to get it fully working as I dont own the device and the fame from corsicanu is still broken I believe. If you want to start compiling cm12.1 for the fame then you can look in the general section there is a compiling tutorial but beware I must edit it/ make a new one for cm12.1 so if you want more help or info just contact me. I am not a pro with all these things but I can give you the basics :good:
Sent from my LG-D802 using Tapatalk
@dushyant30suthar
appreciate u want to help
u can follow instruction to download cm12.1 from guide made by wulsic
change repo init to. ... https://github.com/cyanogenmod/android (at that link u can find the guide to download the source code)
u also can check the device tree https://github.com/wulsic/android_device_samsung_nevisp
https://github.com/wulsic/android_vendor_samsung_nevisp
kernel : https://github.com/wulsic/Hyper_CM11
and the patches from pawitp who working cm11-12.1 for broadcom chipset (grand duos) : https://gist.github.com/pawitp/88a1d4514a0734c866c7 ( try to change some line to work with our hardware phone)
good luck :*
*i am stuck at building the rom with external hdd,it will change all the file (git status modfied)
I hope that the developers could fix a lot of bugs in cm12.1, faizauthar12 and wulsic are doing a great job!
There's already a good-working ROM out (at least for S6810):
http://forum.xda-developers.com/showthread.php?p=63426739
faizauthar12 said:
@dushyant30suthar
appreciate u want to help
u can follow instruction to download cm12.1 from guide made by wulsic
change repo init to. ... https://github.com/cyanogenmod/android (at that link u can find the guide to download the source code)
u also can check the device tree https://github.com/wulsic/android_device_samsung_nevisp
https://github.com/wulsic/android_vendor_samsung_nevisp
kernel : https://github.com/wulsic/Hyper_CM11
and the patches from pawitp who working cm11-12.1 for broadcom chipset (grand duos) : https://gist.github.com/pawitp/88a1d4514a0734c866c7 ( try to change some line to work with our hardware phone)
good luck :*
*i am stuck at building the rom with external hdd,it will change all the file (git status modfied)
Click to expand...
Click to collapse
Do anyone have cm12.1, Cm13 cm14 for Samsung Galaxy fame Gt-s 6812 please give me a link :good:
Abu Swalih 1 said:
Do anyone have cm12.1, Cm13 cm14 for Samsung Galaxy fame Gt-s 6812 please give me a link :good:
Click to expand...
Click to collapse
Did you check the link for CM12.1 in the post above yours?
:confused
BenjyTec said:
Did you check the link for CM12.1 in the post above yours?
Click to expand...
Click to collapse
Nop but I don't see name Samsung Galaxy fame Gt-s 6812 show me link please
I'm using cyanogenmod 12.1 on my samsung galaxy fame everything working only SIM card no when I was instaling that say SIM card no detected bat I have it inserted so I don't know what do?
In recent months, I was disappointed that Huawei has not updated P6 to Lollipop.It states that currently use this smartphone with the PAC ROM and in the past I used the CM11 with the compiler ART, as well as various official rom some of which could support ART. I did so much research, and I came across the bitter truth that the cousin of our P6 the Huawei Ascend D1 had received a port functioning of CM12.1 and other rom-based lollipop. I sincerely in modding are not very practical and something I'm trying to learn it but I would like to make some considerations.
The hardware of 'U9500 or Ascend D1 is very similar to that of P6, especially as regards the processor that is the K3V2. Also I am doing some research I found the source of those Roma who were made to the U9500 user XDA ShevT.
Here the link to the thread on XDA : http://forum.xda-developers.com/android/development/u9500-rom-s-utilities-huawei-ascend-d1-t3137928
and here link to ShevT github : https://github.com/shevt
Now assuming that the ROM is required to compile a working kernel and pretty stable I thought you could use the AK-Angel Kernel v9.
http://forum.xda-developers.com/asc...nel-ak-angel-kernel-huawei-ascend-p6-t2982661
You think it is feasible such a thing?
I speak in particular to the general Surdu_petru that usually did the port on our device.
Sorry for my english.
Almost got my hopes up, but D1 U9500 runs a different chipset, so nope
Chipset TI OMAP 4460
CPU Dual-core 1.5 GHz
GPU PowerVR SGX540
And if that's not enough, look at his github tree for .mk files
Code:
# /vendor/lib/egl
PRODUCT_COPY_FILES += \
$(VENDOR_DIR)/vendor/lib/egl/libEGL_POWERVR_SGX540_120.so:system/vendor/lib/egl/libEGL_POWERVR_SGX540_120.so \
$(VENDOR_DIR)/vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so:system/vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so \
$(VENDOR_DIR)/vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so:system/vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
You can clearly see that the egl blobs are for PowerVR SGX540
Sorry i'm confused with Ascend D1 quad XL
https://kernel.googlesource.com/pub...mu/updates/drivers/clk/hisilicon/clk-hi3620.c
We might be able to build a lolipop rom, we "just" have to build a lolipop compatible graphics library from sources.
there are some sources around with the graphics sources included.
As far as I know this is one of them: https://github.com/locusf/cm11-p6
If anyone wants to build a rom it wont be easy to do and lots of time is a must.
(I'm not the author of this repository)
gs-crash-24-7 said:
We might be able to build a lolipop rom, we "just" have to build a lolipop compatible graphics library from sources.
there are some sources around with the graphics sources included.
As far as I know this is one of them: https://github.com/locusf/cm11-p6
If anyone wants to build a rom it wont be easy to do and lots of time is a must.
(I'm not the author of this repository)
Click to expand...
Click to collapse
I would really appreciate this, if somebody would try to compile this for us...
Sent from my HUAWEI P6-U06 using XDA Free mobile app
pepo.k said:
I would really appreciate this, if somebody would try to compile this for us...
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
I will try to compile a kernel but no prommises, i have to do school stuff to. There will be lots of reading and programming involved just to get the phone booting with the new kernel
gs-crash-24-7 said:
I will try to compile a kernel but no prommises, i have to do school stuff to. There will be lots of reading and programming involved just to get the phone booting with the new kernel
Click to expand...
Click to collapse
Hoorai,
Possibly I could test for you
Sent from my HUAWEI P6-U06 using XDA Free mobile app
So... any news?
No unfortunately not I killed my phone in the process of building graphics drivers