reported it to be deleted.
wait till tomorrow for my new personal build
Will complete it later on.
Will complete it later on.
wuut?
This is yours CM7 or based on CM7 bieltv?
Alucard1989pl said:
This is yours CM7 or based on CM7 bieltv?
Click to expand...
Click to collapse
Yep my cm7 built from source
The device trees are by biel which I am working on.
downloading .... report in half an hour ...!
EDIT: Sbrick too, trying with hell lock now...
Phone has soft brick by kernel in your cm7 rom . . . system data and cache must be formated to ext4?
Alucard1989pl said:
Phone has soft brick by kernel in your cm7 rom . . . system data and cache must be formated to ext4?
Click to expand...
Click to collapse
use hells fusion from the other thread..
I already use hells fusion kernel but when i installed your cm7 my phone stuck on splash screen and led for 1 sec turn on.
Alucard1989pl said:
I already use hells fusion kernel but when i installed your cm7 my phone stuck on splash screen and led for 1 sec turn on.
Click to expand...
Click to collapse
logcat? its really weird cuz it worked for someone else..
what instructions did u use?
prototype-U said:
use hells fusion from the other thread..
Click to expand...
Click to collapse
Please include your kernel in this thread to make it clearer
You have to use this updater-script for flash cm7. If you don't use this one, the phone will get bricked. http://pastebin.com/htJ8NYTs
For use this updater-script you have to put in the first root of the zip two files: bmlunlock and busybox.
Remember to add the boot.img of hells fusion kernel at second post!
P.S. OP I think that you have to give credits to biel!
Soft Brick. Tried with hell lock flashable zip, softbrick with flashlight with 2 seconds. Now tried with the kernel you provided, stuck on the SGAi bootlogo. Any solution? You said it worked on someone else's device... How did he install? From stock or another rom?
EDIT: Now will try with the updater script you said, @Lopicl.00 . What attachment are you talking about?
mathm2013 said:
Soft Brick. Tried with hell lock flashable zip, softbrick with flashlight with 2 seconds. Now tried with the kernel you provided, stuck on the SGAi bootlogo. Any solution? You said it worked on someone else's device... How did he install? From stock or another rom?
Click to expand...
Click to collapse
Follow my post!
bricked the device while trying to install this rom, i had the kernel from your threat
Angryace said:
bricked the device while trying to install this rom, i had the kernel from your threat
Click to expand...
Click to collapse
Threat is something that puts you in danger
Well, I don't know which is the point of this thread. You are building my sources. You are making my ROM. Why create another thread? You don't have the device, me neither, but I started that project from 0. Why instead of making your CM7 you don't help us? Why don't you make a pull request? Do we need to talk with testers, which are the same for the both of us, to just test the same ROM!? If we want to have something big, we should focus on one CM and not building various CM7. I don't know which is the point of this, and I don't know what were you thinking. In your github there is 0 changes on my device tree. I committed all my changes during the last month and you used my work to build your own, and then it seems that your ROM is better than mine, because I don't release mid-done ROM's. I want to give the best expierence to all the users.
Also, I committed all the changes to help people understand on what I'm working. Many users asked me if I was really working on it, as I did not commit anything to github, but I was. And what happens if I commit? other users use my work to build their ROM's? I think that's not the way to go.
And what about a simple credit to the real author of this ROM? as your signature says: Send me device tree and I'll build the ROM. Why? To be more famous using other people's work? I don't get the point of anything here...
Oh, btw, where are the permissions to do that?
Thanks, Biel.
bieltv.3 said:
Well, I don't know which is the point of this thread. You are building my sources. You are making my ROM. Why create another thread? You don't have the device, me neither, but I started that project from 0. Why instead of making your CM7 you don't help us? Why don't you make a pull request? Do we need to talk with testers, which are the same for the both of us, to just test the same ROM!? If we want to have something big, we should focus on one CM and not building various CM7. I don't know which is the point of this, and I don't know what were you thinking. In your github there is 0 changes on my device tree. I committed all my changes during the last month and you used my work to build your own, and then it seems that your ROM is better than mine, because I don't release mid-done ROM's. I want to give the best expierence to all the users.
Also, I committed all the changes to help people understand on what I'm working. Many users asked me if I was really working on it, as I did not commit anything to github, but I was. And what happens if I commit? other users use my work to build their ROM's? I think that's not the way to go.
And what about a simple credit to the real author of this ROM? as your signature says: Send me device tree and I'll build the ROM. Why? To be more famous using other people's work? I don't get the point of anything here...
Click to expand...
Click to collapse
Ok I am also starting the device tree from scratch. Is that alright?
I will suspend the current build and post a new one tomorrow which will based on my device trees.
About credits? I didnt even complete writing this thread..
About changes thing? I have made changes at my end which are not committed becuz I dont wanna put untested changes on github.
Sorry If I offended someone but I had no real intentions of doing that..
and btw.. I mean somehting else from my sign.. I want to help other device owners to get new roms to their device. Though it contradicts to this build.
Related
Hello everyone,
I am trying to get the camera work on CM9 but it doens't work! so if anyone can help me that would be Great and one last question can we use the camera drivers from the official TAB 7.7 ICS firmware?
using also this: http://forum.xda-developers.com/showthread.php?t=1651530
EDIT:
First fix doesn't work
EDIT:
Trying to do the kernel work now!
EDIT:
There is no boot.img file in the official samsung rom! (4.0.4)
Decompile the 7.7 kernel, find the driver for the camera, pull that section of code, recompile the cm9 kernel with the new driver.
FlanFlinger said:
Decompile the 7.7 kernel, find the driver for the camera, pull that section of code, recompile the cm9 kernel with the new driver.
Click to expand...
Click to collapse
Downloading 7.7 Firmware now after that i will decompile kernel and find the driver for the camera i will pull that to the cm9 kernel and recompile it wish me luck! PS Where to find the kernel in the Boot.img Or am i wrong?
You've got the source code for ICS on the 7.7 ?
FlanFlinger said:
You've got the source code for ICS on the 7.7 ?
Click to expand...
Click to collapse
No can you give me?
Yeah sure, here you go
FlanFlinger said:
Yeah sure, here you go
Click to expand...
Click to collapse
You don't know what you are saying man! im just trying something and you do this
I will never come back on this thread again (Galaxy Tab 8.9)
You guys are just Crazy To say im having ADHD you don't know what that means i think so im the calmest person here now
No need for that language
But lets just clear a few things up shall we......
You are going to reverse engineer (as you have no source code) about 6mb of data from the 7.7 kernel, find all the relevant parts that drive the camera and then use that to recompile the CM9 kernel to get the camera working.....
This is you whose only dev experience is taking a few apps out of a stock rom, repacking it, releasing it WITH NO CHANGELOG and then shortly after deleting the contents of your release post.
FlanFlinger said:
No need for that language
But lets just clear a few things up shall we......
You are going to reverse engineer (as you have no source code) about 6mb of data from the 7.7 kernel, find all the relevant parts that drive the camera and then use that to recompile the CM9 kernel to get the camera working.....
This is you whose only dev experience is taking a few apps out of a stock rom, repacking it, releasing it WITH NO CHANGELOG and then shortly after deleting the contents of your release post.
Click to expand...
Click to collapse
Im now busy with Porting Bindroid rom from galaxy tab 10.1 section i have permission from him is that also not good or can i do that?
safariking said:
Im now busy with Porting Bindroid rom from galaxy tab 10.1 section i have permission from him is that also not good or can i do that?
Click to expand...
Click to collapse
What I've just put in bold is what's really important. Sure, as long as you're willing to fix bugs the community reports because ports usually contain bugs since they are mostly not using native code.
nirogu325 said:
What I've just put in bold is what's really important. Sure, as long as you're willing to fix bugs the community reports because ports usually contain bugs since they are mostly not using native code.
Click to expand...
Click to collapse
Off coarse i will do that
I just wanna save you the trouble since it's not doable, especially not by you. Stop trying and wait for an official 8.9 ICS, only then we would be able to get the camera working.
Don't use this rom due to random bootloop .
Hi all here the latest aokp milestone rc2 based on the latest unoficial cm9 rom BY Erwin.P
It's aokp milestone 6. version 4.0.4
Enjoy the aokp rom
The defauct lanchet is nova i think is the fastest but you can always use apex lancher or other ics one.
Detail:
Ics interface.Cm9 theme chooser, aokp setting and more will come.
What need to be fix :
Aokp stock live wallaper .But it's all and all cm9 bug.
Download:
https://docs.google.com/open?id=0B-5I_FmNMNolX0JpdEVFX2NIZG8
WARNING:
Before to install you have to delete 77tweaks in System/etc /init d
Credit:
Erwin.p
Aokp developer for wildfire.
Cyanogenmod team
can't download
Hello Pator57,
First I want to express my intentions with this post: I'm VERY glad that you have started to work on these ROM ports, and I'm only willing to help ya so that you can contribute more and more for the wildfire.
For me, a ROM presenting shouldn't be done in this way. First , lets start with the thread name-you should specify what actually is in this thread, is it a port/mod/build-from-source/etc, not only 'aokp update' for example, you should specify a date/version of the specific ROM , so that the users can keep an eye on the ROM since its almost certain that it will have some bugs , that should be fixed in new versions.
Later, in the thread its good not only to explain how and what you did it, but to put screen-shots/videos. To give details about the features,the ROM base and from where did you ported it, about the performance and some glitches. Plus that don't forget to include some disclaimer, so that you are not taking any responsibility for bricked phones, earthquakes or anything else. There can always be someone to point at you and claim that you bricked his precious phone. Detailed credits are also good to write, but you have made it so its OK.
Moreover,the actual zip of the ROM. Its not cool to name it 'aokp.zip' or 'miuiv4.zip'. I again think that including date/version is good, because when you make 3-4 different zips with bug fixes for example, personally i love to store more than a one version of the ROM I use and with these names it wouldn't be practical.
Of course one can rename it himself , or try the ROM to find out whats in,but(I think) these small suggestion would make you look more professional and reliable, just the way a developer/porter should look. This will give me personally convince in you, and that the things you do wont harm my phone. I hope noone will feel offended in any way. My intention as I said is only to help you, so that we can have one more ROM "producer" here. All what I wrote are personal views on how the things are done around here, its your choice whether to follow them!
Vency77 said:
Hello Pator57,
First I want to express my intentions with this post: I'm VERY glad that you have started to work on these ROM ports, and I'm only willing to help ya so that you can contribute more and more for the wildfire.
For me, a ROM presenting shouldn't be done in this way. First , lets start with the thread name-you should specify what actually is in this thread, is it a port/mod/build-from-source/etc, not only 'aokp update' for example, you should specify a date/version of the specific ROM , so that the users can keep an eye on the ROM since its almost certain that it will have some bugs , that should be fixed in new versions.
Later, in the thread its good not only to explain how and what you did it, but to put screen-shots/videos. To give details about the features,the ROM base and from where did you ported it, about the performance and some glitches. Plus that don't forget to include some disclaimer, so that you are not taking any responsibility for bricked phones, earthquakes or anything else. There can always be someone to point at you and claim that you bricked his precious phone. Detailed credits are also good to write, but you have made it so its OK.
Moreover,the actual zip of the ROM. Its not cool to name it 'aokp.zip' or 'miuiv4.zip'. I again think that including date/version is good, because when you make 3-4 different zips with bug fixes for example, personally i love to store more than a one version of the ROM I use and with these names it wouldn't be practical.
Of course one can rename it himself , or try the ROM to find out whats in,but(I think) these small suggestion would make you look more professional and reliable, just the way a developer/porter should look. This will give me personally convince in you, and that the things you do wont harm my phone. I hope noone will feel offended in any way. My intention as I said is only to help you, so that we can have one more ROM "producer" here. All what I wrote are personal views on how the things are done around here, its your choice whether to follow them!
Click to expand...
Click to collapse
It's the same port as tamahal port but based on the latest cm9 09/20 rom.But exept that and some tweaks it's exactly the same rom.
Sent from my HTC Wildfire using xda premium
ROM dont work, enter pin code and always boot screen
Fulfen said:
ROM dont work, enter pin code and always boot screen
Click to expand...
Click to collapse
Ho too bad.Flash this fix and it should work now.
OT: dafuq, what is this updater-script for a simple build.prop replace
Vency77 said:
OT: dafuq, what is this updater-script for a simple build.prop replace
Click to expand...
Click to collapse
Yea i change it but before i have testing the rom without the build prop change and all was working well.So come back to the stock build prop of cm9.IF it still doesn't work i will try again a new port this week end
now just htc logo... so still fail
Strange it was working well for me..But do you make an factory reset, wipe data, wipe dalvik cache,wipe cache partition before flashing ?
Ok but if the rom still doesn't work i will deleted the thread.
Sent from my HTC Wildfire using xda premium
I'm going to backup my current CM9 setup and try this out? What device did you port from?
Sent from my Wildfire using Tapatalk 2
It's not an port it's an uptate of the other aokp rom by thathanmal66.
Sent from my HTC Wildfire using xda premium
im biting my tongue here lol
R.V.3 (MokeeOs)
Pator57 said:
Strange it was working well for me..But do you make an factory reset, wipe data, wipe dalvik cache,wipe cache partition before flashing ?
Ok but if the rom still doesn't work i will deleted the thread.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
yes i have wildfire for 2 years i know how to flash rom, i did all those things.
Looks like i am having some great fun here
Sent from Hell!!
Pator57 said:
It's not an port it's an uptate of the other aokp rom by thathanmal66.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
I'm sure it shouldn't be called like this,because its a whole-ROM zip , and you tell that we should wipe everything when installing it,but whatever.Since its an 'update' of tathanhlam66's ROM , why do you make a whole new thread and not just continue what tathanhlam66 started ?
EDIT: Plus that , you have not edited both threads as I suggested you, which is making them BOTH look just funny. If you are not serious , and constantly state 'This is an update...blqblq', they will continue to look funny and futile!
and i hope you got permission to post and uptate his work?
R.V.3 (MokeeOs)
slymobi said:
and i hope you got permission to post and uptate his work?
R.V.3 (MokeeOs)
Click to expand...
Click to collapse
...and to play scrabble with his name
As on the MIUI thread, is it possible to provide some more details on that? Screenshots, bug list?
It's quite tricky to flash a ROM without knowing the results..
There are no bug but if im wrong tell me like my miui port.But it report to doesn't boot so i will try to make it boot next weekend.And i don't need to ask permision aokp it's like miui it's an open software and no need screenshoot the rom it's an ics rom but only with some aokp option tweaks
Sent from my HTC Wildfire using xda premium
I heard that cm10.1's 07/07 kernel has no whitescreens. I am using a newer version of cm10.1 . Can I flash 07/07 kernel on its own via CWM? If yes, how can I make it flashable? Thanks in advance.
G i said:
I heard that cm10.1's 07/07 kernel has no whitescreens. I am using a newer version of cm10.1 . Can I flash 07/07 kernel on its own via CWM? If yes, how can I make it flashable? Thanks in advance.
Click to expand...
Click to collapse
here is the flashable kernel
ahmedadd said:
here is the flashable kernel
Click to expand...
Click to collapse
Dayyyum. That was fast. Thank you so much buddy. Any idea why Wifi isn't working?
EDIT: I turned off Wifi optomization, but still I can't enable wifi. Can you tell me the process to flash the kernel over my ROM? Maybe i did something wrong.
G i said:
Dayyyum. That was fast. Thank you so much buddy. Any idea why Wifi isn't working?
EDIT: I turned off Wifi optomization, but still I can't enable wifi. Can you tell me the process to flash the kernel over my ROM? Maybe i did something wrong.
Click to expand...
Click to collapse
no you did not make any wrongs to use 7-7 kernel the wi-fi wont work at all.
ahmedadd said:
no you did not make any wrongs to use 7-7 kernel the wi-fi wont work at all.
Click to expand...
Click to collapse
ffs this phone. everytime something's broken. at first the whitescreens, then the sdcard mount problem, now wifi is disabled...god pls!
you flash an old kernel/ramdisk and wonder why Wi-Fi isn't working... it's just...
TheWhisp said:
you flash an old kernel/ramdisk and wonder why Wi-Fi isn't working... it's just...
Click to expand...
Click to collapse
I mean, there should be a stable ROM with everything working. Maybe not the latest release but it would be stable. I know all ROMs are stable for your phone since you don't have WS or mount problem, but there's no rom for my phone that won't malfunction.
I am not your employee if you haven't noticed yet.
TheWhisp said:
I am not your employee if you haven't noticed yet.
Click to expand...
Click to collapse
Holy **** dude, your attitude. Everybody in this forum loves you cuz you're the only developer this ****ty phone has but you keep acting like a douche, throwing a tandrum to whoever dares to mention WS or sd card mount problem or even something that has been stated before. We are noobs, we're trying to learn, this place's like a school to us. XDA ain't your own business, we're members of XDA as well. Did I even ask you to do something for me? Did I even post to your github or anything like this? No, cuz I know that douchebags like you better leave 'em alone.
but there's no rom for my phone that won't malfunction.
Click to expand...
Click to collapse
Sorry, but you have clearly misunderstood the whole point of XDA. Most of the developers here (including me) do this as a hobby. I make this ROM for myself and then I share with anyone else. I am not going to do something, in this case fix bugs I have never experienced nor can reproduce, just because something is not working on your device. Douches are people who constantly spam and whine about things. Use GB and be happy.
TheWhisp said:
Sorry, but you have clearly misunderstood the whole point of XDA. Most of the developers here (including me) do this as a hobby. I make this ROM for myself and then I share with anyone else. I am not going to do something, in this case fix bugs I have never experienced nor can reproduce, just because something is not working on your device. Douches are people who constantly spam and whine about things. Use GB and be happy.
Click to expand...
Click to collapse
Ok kiddo
You know, you should really take a chill pill....TheWisp is trying to do something for free here..i don't think you really understand the "free" part...myself, i couldn't spare the time to learn to develop for Android, much less fix bugs and try to create a stable rom without up-to-date blobs ( which by the way is really harder than simply porting cm to a certain device which already has jb or a variation of it)...if you really want something 100% stable go for stock (tough good luck with random crashes)..if you want something 97% stable go for cm10 or cm10.1 (i find 30/06/2013 cm10.1 to be one of the smoothest and stable of all the cm10.1 builds), and if you want something 95% stable go for cm11(the one i have right now)...you should really stop complaining, and instead of being part of the problem, start learning to develop and be a part of the solution (if developing is for you). Peace!
Welcome to the official thread for the Lollipop roms for our Optimus 2x
As to start, this thread is exclusively for the developers who are interessted/working on on the Lollipop ports for our Optimus 2x
We had alredy some build like the OmniRom , CM12 and even ParanoidAndroid.
This thread is exclusively for discussions for the developers and for the testers to test the new made roms so I will update the links as the roms get made. So I am only posting here the links of the latest version, to get the versions from the past you wil need to browse throught this thread
Update 05/6/2016
Gucky did it again! New build for CyanogenMod 12.1 is up, and now with fixed camera! When I get the full list of working features and bugs, I will upload it here. Thank you Gucky for your massive help and contribution to this community. This device is very old after all, and you still find the time to tinker on it. No words really. Respect!
CM12.1 : https://sourceforge.net/projects/lg...cm-12.1-20160531-UNOFFICIAL-p990.zip/download
WARNING the Rom is still not stable, but we are close!
ParanoidAndroid: https://s.basketbuild.com/devs/Puri/p990/AOSPA(lollipop)
Take in mind that all these roms are unstable besides the CM12 rom,but it still has some major bugs which we as a group will fix.
As in all of this, stay tuned for updates
Good job my friend
Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!
um
gucky01 said:
Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!
Click to expand...
Click to collapse
um.......*noob mode activated.....BOOP * what you mean with manifest? lol
Could you please share your sources.
TheMysteryouse said:
Hello everyone.As you might know me from some threads where i comment some stuff.Anyways, since Lollipop was announced i was obssesed with it and my wish was that i would be the first one to make the version availble for our device.
Well i kinda did it....KINDA of course but we need some help if we wanna make it work.I call ALL of the developers for our device to work together to make it work.We are so close to get it fully booting.I made it boot to the animation and now where the help comes in use.We need some developers who can enable ADB on our device in the bootanimation.TO be honest i dont really know anything about sources and that stuff but i know some things.With the help of @tonyp and @timduru which I am the most thankfull of that gave me hope to make this.So here we go!
WARNING!!!
ONLY FOR DEVELOPERS
No one should download and flash this rom because you will get stuck in the bootanimation and will need to install previouse rom again and install everything over...blah blah blah.
Also the link to the rom is here ----> https://www.dropbox.com/s/fwhg08ux7qhtgsh/5.0 test.zip?dl=0
So if someone gets it working, please pm me in the progress. Cheers
Click to expand...
Click to collapse
TheMysteryouse said:
um.......*noob mode activated.....BOOP * what you mean with manifest? lol
Click to expand...
Click to collapse
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Oh
Hugo-PT said:
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Click to expand...
Click to collapse
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol
TheMysteryouse said:
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol
Click to expand...
Click to collapse
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
nope
gucky01 said:
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
Click to expand...
Click to collapse
nope, didn't touch anything other than the updater script i think and the build prop because i wanted fully stock experience
I can be your tester my phone got a battery problem so im having fun with flashing roms
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Well, it might be that he used KatKiss from timduru for the TF101 which has a Tegra 2, but still our phone uses the Tegra 2 AP20H, while the TF101 uses Tegra 2 T20. Small difference in the chipset, but still a difference. Easiest would be to port from the Galaxy R or Captivate Glide, but they too struggle with Lollipop over in their forum. Anyway, TheMysteryouse used timduru's AOSP rom, so maybe it would be easier building the whole thing from the demo CM12 sources available.
nonono
DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Nope, this rom has NOTHING to do with the tegra 3 rom.I used the rom for TF101 tablet which is tegra 2 but had a cmall chipset difference.So yeah I am still trying to do some things like searching the framework sources from tony to see if he has a code in the build.prop which directly enables ADB from the boot, but cant really find it.Anyways try your best and so the others.Cheers
Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!
Any video or screenshot? xD
Sorry for nob request, but working well or not, its great to our comunity
p.s. if need tester in future, you, TheMysteryouse or DJNoXD.
Im ready for
...WoW!...That´s Good News...Thank You for All of You, Guy´s...
gucky01 said:
Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!
Click to expand...
Click to collapse
Awesome news buddy! Lollipop on first power dual core android device! Switch to 1+ One as a primary phone for some reason but I will continue to follow and supporto you!
That is great!!! ))))))))
Ok. I have to go one step back. The rom is not ready for the testers and I'm too tired to test more. For those, who want to repeat my steps or want to finish...
I replaced the files in Mystery's rom with my own Kitkat ones. The first half, than the second. Now I could get it to finish the booting process. This steps I went on and on. So I could reduce the problem to the framework-files in "system". If you replace all of them, it boots up with some error messages.
I think we have to reduce the 40 files inside more and more to find the reason for the bootloop.
All the best to you,my friends!
Damm this is great a device from 2010 receives android L. 4years later. If I can borrow the old optimus 2x from my father then I could also look into the problems if it's not booting yet then. Till then continue your work.
I recently decided to do some personal builds of CM for the OnePlus 3. I have seen that the other threads are not updating their builds since they are the ones working on them. I am simply sharing the current builds from the CyanongenMod Repos. I did not do any of the development work and I will kill this thread the moment we get official nightly builds. I am not responsible for anything that may happen and I do not care what does and does not work. You are deciding to flash this ROM. Bugs can be reported to the CM devs but include a logcat or GTFO.
Link to build folder - https://www.androidfilehost.com/?w=files&flid=74080
Instructions:
1. Unlock Bootloader
2. Flash TWRP
3. Fastboot format userdata
4. Boot into TWRP
5. Flash ROM
6. Flash GAPPS
7. Reboot
Thanks for making another ROM for our OP 3
papi92 said:
I recently decided to do some personal builds of CM for the OnePlus 3. I have seen that the other threads are not updating their builds since they are the ones working on them. I am simply sharing the current builds from the CyanongenMod Repos. I did not do any of the development work and I will kill this thread the moment we get official nightly builds. I am not responsible for anything that may happen and I do not care what does and does not work. You are deciding to flash this ROM. Bugs can be reported to the CM devs but include a logcat or GTFO.
Link to build folder - coming soon (waiting on AFH approval)
Instructions:
1. Unlock Bootloader
2. Flash TWRP
3. Fastboot format userdata
4. Boot into TWRP
5. Flash ROM
6. Flash GAPPS
7. Reboot
Click to expand...
Click to collapse
Hehe thanks for this Started building them as well but don't really know how, so made a little guide for others like me Feel free to share your knowledge if you want
build is up
papi92 said:
build is up
Click to expand...
Click to collapse
Downloading...
_MartyMan_ said:
Downloading...
Click to expand...
Click to collapse
Thanks
Thanks for doing this dude. Going to download now. Can finally ditch OOS.
Sent from my ONEPLUS A3000 using Tapatalk
Wooohoo! Everything is working Good job!
_MartyMan_ said:
Wooohoo! Everything is working Good job!
Click to expand...
Click to collapse
Does VoLTE work? I haven't stuck in my T-Mobile SIM lol and i didn't do anything so no thanks to me. It's all @Grarak and @Romanbb
Not trolling but we dont need several twrp, cm, resurrection and so on rom threads here. I believe the mods starting closing these. Not discouraging you from building but several threads just confuse people.
Nah mods don't close it, maybe move it.
It's a nightly build from cm13, did u see a nightly build around? Nope.
Good work, fastest cm13 build around, good to have some nightlys around. Thanks
fix-this! said:
Not trolling but we dont need several twrp, cm, resurrection and so on rom threads here. I believe the mods starting closing these. Not discouraging you from building but several threads just confuse people.
Click to expand...
Click to collapse
These are nightlies. I'm more than happy to close once CM sends the OnePlus into Jenkins.
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
nadejo said:
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
Click to expand...
Click to collapse
Yeah not my work at all. Nor would I pretend it is. Way over my head
So anyone confirm VoLTE is working? I want to switch to T-Mobile once it does.
nadejo said:
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
Click to expand...
Click to collapse
Tbh i dont think alot of devs even have the device in hand yet. thats why im running stock rooted. no offense to the op, wasnt my intention. just been seeing alot of the same threads pop up and its confusing and uneeded. im sure these nightlies are appreciated.
Put up a second build. I saw some commits to snap and wanted to share.
Possible to link the source?
Not that I know where it is, but I'm to lazy to search all the time.
Only thing I noticed is the battery drain compared to stock, not a big one, maybe it need to settle a little.
1 hour SOT 21% on cm
1 hour SOT 14-16% on stock.
Lets see how it settle.
Edit:
Compared to others Roms who looks like they are on a older source, it's running like it should, compared to stock min. the same smoothness, maybe even better.
And I can't test lte because I only have a h+
secXces_debaki said:
Possible to link the source?
Not that I know where it is, but I'm to lazy to search all the time.
Only thing I noticed is the battery drain compared to stock, not a big one, maybe it need to settle a little.
1 hour SOT 21% on cm
1 hour SOT 14-16% on stock.
Lets see how it settle.
Edit:
Compared to others Roms who looks like they are on a older source, it's running like it should, compared to stock min. the same smoothness, maybe even better.
And I can't test lte because I only have a h+
Click to expand...
Click to collapse
The source is just github.com/cyanogenmod
papi92 said:
Does VoLTE work? I haven't stuck in my T-Mobile SIM lol and i didn't do anything so no thanks to me. It's all @Grarak and @Romanbb
Click to expand...
Click to collapse
Sorry I can' test that