Develop Bugs

[ROM]{Project Restarted} CyanogenMod 6 Compiled From Sources For LG Optimus ME P350

Guys Today I Brought To You New And Unique For LG Optimus ME P350 "Cyanogenmod 6" Yes ! It is Compiled From The Sources and It is Very fast Rom ! But still it is bit buggy but bugs will be fixed soon !
FEATURES :
BOOTED
TOUCH SCREEN
HW ACCELARATION
AUDIO
BLUETOOTH
WIFI (SHOWS NETWORK BUT UNABLE TO CONNECT)
SENSORS
BUGS :
RIL (STUFFS RELATED TO BASEBAND NO CALLS NO NETWORK NOTHING)
GPU (2D - 3D)
VIDEO Decoding ( NO AUDIO )
WIFI
CAMERA
All Things Which Are Not Listed Here !
DON'T WORRY GUYS THIS ALL ARE THE EASY BUGS WILL BE FIXED SURELY GUYS BUT GUYS ANYWAYS WE GOT IT BOOTED THAT'S AN GREAT THING IF ANYBODY WANT TO TASTE IT A BIT CHECK IT OUT DEVS I NEED UR HELP PLZ HELP
LINK For Build 1 : http://www.mediafire.com/?ea8quma377uhzd2
Source Code : http://github.com/PecanCM/
PROJECT RESTARTED​

thanks friend, waiting...

Devs Need Ur HElp
Devs plz help me in fixing Baseband Im unable to fix it if anybody can fix plz help

BB waiting...
thanks

gpu fixed ( mean i found how to fix) i will recompile this rom again when i will back in india but about baseband it's too hard

Bro Can U try with Froyo Stable SOurce As I dont have stable sources so not compiled Best Luck For compilation Let's see we can fix bb

kdmaru said:
Bro Can U try with Froyo Stable SOurce As I dont have stable sources so not compiled Best Luck For compilation Let's see we can fix bb
Click to expand...
Click to collapse
yes i will try on froyo stable in 1st may now just hope we get and good thing is build bot is back from 1st may with new server so you know

it is stop?

usevelez said:
it is stop?
Click to expand...
Click to collapse
true

Guys Finally Here is Good News CM6 Project Restarted next Build and Updates Coming Soon ! Stay Tuned !

rom2maru said:
Guys Finally Here is Good News CM6 Project Restarted next Build and Updates Coming Soon ! Stay Tuned !
Click to expand...
Click to collapse
good news , best luck :good:

That's good news buddy! I love Android FroYo but I can't stay using the stock ROM because it is too slow as compared what it could be, I'm looking forward your next releases!
Good luck!
Skyheiser​

Yeah I too Dont Like AOSP but Im sure you gonna love cm6 due to it's performance , ram management and much more !

First Intial Device Folder Pushed Have A View : https://github.com/PecanCM/android_pecan_cm6_device

Hey!
Just passing by, hum.. how is the development going? Any release date yet?
To be honest, I'm very anxious to get my hands on this rom.
Skyheiser​

FInally Builded CM6 Build #2 Now Going to test it Gonna release Build 2 in two days

rom2maru said:
Guys Finally Here is Good News CM6 Project Restarted next Build and Updates Coming Soon ! Stay Tuned !
Click to expand...
Click to collapse
bro when ur next build is coming.........?
eagerly waiting for the CM6

Sorry Bro But I Got my Source Deleted As Formatted Everything Now Having Fresh ubuntu So will Download ICS and Cm6 Both Sources.... Builds coming soon !

When?

in near time.
Sent from my LG-P350 using xda app-developers app

Official support from CyanogenMod Team for Galaxy W

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

We need one real update...

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

Device tree, Kernel source, Vendor blobs

Heya, I just got my hands on a J200H, and I get to keep it for a while.
As I was using it, I thought if there is any lineageos for it, and there is not.
Now it would be great if you guys point me where I can find Device tree, Kernel source, Vendor blobs for this device, so that I could start working on this device and add the repo to official lineageos server for build ( provided all things goes smoothly nearly one month is enough )
Also I saw some varients of this device, it would be great if you could add device models (the codes- like J200H) and their source codes too, I could try merging them into a universal source code and patch as universal makes less problem.
Thanks In advance! And any update will be posted here.

I doubt if the things mentioned are available.
But if the are really willing to do this than this can be useful .
Have a look a this
https://web.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
and this
https://forum.xda-developers.com/an...ow-to-create-device-tree-android-rom-t3498355

ad. said:
I doubt if the things mentioned are available.
But if the are really willing to do this than this can be useful .
Have a look a this
https://web.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
and this
https://forum.xda-developers.com/an...ow-to-create-device-tree-android-rom-t3498355
Click to expand...
Click to collapse
got em on samsungs website, but holy ****e their bandwidth....they are killing me.....
Just look at these download speed.... god no...
https://ibb.co/gnDQLQ

uts58 said:
got em on samsungs website
Click to expand...
Click to collapse
I don't know but I guess they are just kernel source .
Once downloaded you can know what is that actually.

@uts58 Are you still working on it????

General Finally! RM8P kernel code source is already released

(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Edit :
It's already released.
Now I hope the developers start creating fantastic roms for this beast phone

salahomer said:
(Dear Valued RedMagic Customer,
Thank you for your patience,
Please check the source code at https://github.com/ztemt. If you cannot access the connection, please refresh the interface and try again the next day. Thank you for your understanding.)
Click to expand...
Click to collapse
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Edit: Cool! It's finally released!

JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Very soon, not now...so let us wait a few more days or weeks

JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
I see there are 7S and 6S kernels, but I don't see any custom ROMs for them, so idk if we will see any for this phone too.

The repo is now available, however, it's empty by the time of me posting this now. It took them two weeks just to create the repo, that's insane. Well, at least it finally happened. Waiting for sources to be uploaded, they probably have to use slow vpn or something to do that, so it might take quite a bit of time.

What can we do with the kernel source?

So it is here.

JWnSC said:
Isn't our device NX729J? I don't see kernel source released for this... Sounds like they giving you the run around. They would sell a lot more phones if they did release. I almost didn't buy one due to this.. Hopefully they will release it soon.
Click to expand...
Click to collapse
Edit :
It's already released, check again.
Now I hope the developers start creating a new fantastic roms for this beast phone

Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.

aaa.bbb111222 said:
Well, apparently we'll have to write drivers for our device:
Code:
# nubia driver
drivers/nubia
arch/arm64/configs/vendor/nubia
arch/arm64/configs/vendor/NX729J_diff.config
arch/arm64/configs/vendor/NX729J-perf_diff.config
arch/arm64/configs/vendor/NX729J_driveronly.config
This is from .gitignore, so we can't build this kernel and run it i.e. on stock rom.
Click to expand...
Click to collapse
So... What does that mean for new custom roms

gwenmillett said:
So... What does that mean for new custom roms
Click to expand...
Click to collapse
We're not gonna see them until someone writes these drivers or zte publishes them. Both are very unlikely, so...

Seems like they uploaded it again, on zips. I checked and it seems to contain several things inside the /drivers/nubia folder so we probably have now a full workable kernel source