Related
OK so I plan to build us another great ROM for our device but I just need a few things.
1st) Can someone please point me to the device tree and kernel source to build android 5.1, all I could find was a bunch of cm11 stuff.
2nd) I need some developer support. I tried making a ROM before for a Samsung player and I was kinda left to do it alone so I would really appreciate some help.
I will be trying to make Bliss Pop ROM because it is fast, smooth and highly customizable. I'm going to attach a poll and I ask that the L90 users vote on which of the ROMS they want me to port. After this I look forward to making a custom kernal that's completely separated from the ROM and that can just be flashed in recovery.
I would love to make this for the D415, D405,D405N, and the D410. Thanks!
Look at Quarx's github.
GrinningFerret said:
Look at Quarx's github.
Click to expand...
Click to collapse
What kernel do you suggest I use? I want a customizable kernel.
JamesB3 said:
What kernel do you suggest I use? I want a customizable kernel.
Click to expand...
Click to collapse
You can customize every kernel if you have the skills to. Use just the normal kernel on Quarx's github. https://github.com/Quarx2k/android_kernel_lge_msm8226/tree/cm-12.1
@OP
Wrong thread.
You should start with basics...
And learn, search, study by yourself.... You'll achieve nothing by asking for simple solutions...
judas1977 said:
@OP
Wrong thread.
You should start with basics...
And learn, search, study by yourself.... You'll achieve nothing by asking for simple solutions...
Click to expand...
Click to collapse
I know the basics. And all that I am just trying to make a ROM that will work on all variants and will be something the users actually will want to use. I know how to develop a ROM.
Beanstalk! I loved using this back on my old Nexus One, and I forgot all about it until I pulled it out and attempted to resurrect it a couple weeks ago. Unfortunately, that Beanstalk port was way to buggy to use, but I would really love to see it on the L90! I am currently really liking Resurrection Remix, but I wouldn't mind having two equally awesome ROMs to choose from.
I currently have no experience developing Android anything (very minimal experience with programming), but I wouldn't mind learning/helping if someone wants to point me in the right direction and won't laugh at any newbie mistakes. I could also be a tester as long as there isn't much likelihood of bricking the phone (have a d415, by the way).
BellaMay95 said:
Beanstalk! I loved using this back on my old Nexus One, and I forgot all about it until I pulled it out and attempted to resurrect it a couple weeks ago. Unfortunately, that Beanstalk port was way to buggy to use, but I would really love to see it on the L90! I am currently really liking Resurrection Remix, but I wouldn't mind having two equally awesome ROMs to choose from.
I currently have no experience developing Android anything (very minimal experience with programming), but I wouldn't mind learning/helping if someone wants to point me in the right direction and won't laugh at any newbie mistakes. I could also be a tester as long as there isn't much likelihood of bricking the phone (have a d415, by the way).
Click to expand...
Click to collapse
Thanks I'll let you know how you can help. I'll probably begin work on the highest voted on ROM thursday manly because I'm sick right now. I'll be sure to make sure it won't brick your D415 before I ask testers to flash the ROM. Thanks again!
Its official!!!
I'm gonna start building Bliss Pop ROM Tomorrow and my friend is gonna start building Liquid Smooth sometime this week if not in the next 2 days. Both will be Android 5.1. Can't wait to roll out first build of these awesome ROMS!
JamesB3 said:
I'm gonna start building Bliss Pop ROM Tomorrow and my friend is gonna start building Liquid Smooth sometime this week if not in the next 2 days. Both will be Android 5.1. Can't wait to roll out first build of these awesome ROMS!
Click to expand...
Click to collapse
base from cm12 or wether 20vd405n kdz?
judas1977 said:
@OP
Wrong thread.
Click to expand...
Click to collapse
Thread closed. As it appears you have decided what you will do.
JamesB3 said:
I'm gonna start building Bliss Pop ROM Tomorrow and my friend is gonna start building Liquid Smooth sometime this week if not in the next 2 days. Both will be Android 5.1. Can't wait to roll out first build of these awesome ROMS!
Click to expand...
Click to collapse
I am not responsible for you bricking your phone. If you blame me I will laugh at you.
This is one of my first Rom so go easy on me
Download Link - CM 12.1/Android 5.1.1:
Update CM 12..1 05/01 -
LINKS REMOVED BY MOD
Instructions:
Flash ROM(Link above)
BaNkS GAPPS - GAPPS
Donations
Please donate to keep this project alive!! It costs to maintain the hardware, Internet for the frequent updates and various fixes
Change log for 05/01 Build:
Android 5.1.1_r1
Stable Camera
USB OTG Update - This will make OTG super stable - This will be part of next release
Reboot Fix
CM Code Catch-up
Bluetooth updates
Memory optimisation
New CM SMart Dialer
Return of Silent mode
Silent mode toggle
CM File Manager update - I am not sure if anyone uses this
MMS Updates
Time to switch back to nuplayer
Things which are broken:
You tell me
*NewCM team have introduced couple of new apps which are included in this build. Check the build for the surprise
Ignore the title of the download file I have to get that changed
XDA:DevDB Information
Lolli POP, ROM for the T-Mobile Samsung Galaxy S6
Contributors
supy99, matrixzone
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest bootloader
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-05-07
Last Updated 2015-05-07
reserved
also reserved
Your download link seems to be MIA.
First lesson, this should be in original development
Does this have the cyanogenmod kernel or did you build it around the s6 stock kernel?
Sweet. Will try when I get some time.
Omg this is AWESOME. I thought I'd have to wait ages to get CM back in my life lol Supy any bugs or things that do t work we should know about?
Don't get to excited guys....
mikeyinid said:
Don't get to excited guys....
Click to expand...
Click to collapse
Why not?
ethan.r.besbris said:
Why not?
Click to expand...
Click to collapse
Here is all the threads the OP has started. http://forum.xda-developers.com/search.php?searchid=364211818
His github is non-existent. IF he does have a mostly working build of CM, he's using someone elses trees.
mikeyinid said:
Here is all the threads the OP has started. http://forum.xda-developers.com/search.php?searchid=364211818
His github is non-existent. IF he does have a mostly working build of CM, he's using someone elses trees.
Click to expand...
Click to collapse
Well that's f*king depressing... What a turd.
ethan.r.besbris said:
Well that's f*king depressing... What a turd.
Click to expand...
Click to collapse
Naw, it's cool. HERE is something to get excited about ~~~>https://github.com/BMc08GT?tab=repositories
So this is a no-go?
mikeyinid said:
Naw, it's cool. HERE is something to get excited about ~~~>https://github.com/BMc08GT?tab=repositories
Click to expand...
Click to collapse
Kernel source for the Exynos processor?
I thought Samsung kept that hush-hush?
mikeyinid said:
Naw, it's cool. HERE is something to get excited about ~~~>https://github.com/BMc08GT?tab=repositories
Click to expand...
Click to collapse
explain what that means
Sent from my SM-G920T using Tapatalk 2
FroBreadCreamJellyPie said:
Kernel source for the Exynos processor?
I thought Samsung kept that hush-hush?
Click to expand...
Click to collapse
It means BmC is actively working on it. I didn't know he and @eousphoros were working together, but I know if BmC is working on it, we'll have something sooner than later. I noticed slayher is working on it too. Haven't seen him around for a while but he knows his **** too.
dkotoric said:
explain what that means
Sent from my SM-G920T using Tapatalk 2
Click to expand...
Click to collapse
mikeyinid said:
It means BmC is actively working on it. I didn't know he and @eousphoros were working together, but I know if BmC is working on it, we'll have something sooner than later. I noticed slayher is working on it too. Haven't seen him around for a while but he knows his **** too.
Click to expand...
Click to collapse
sweet thanks
Sent from my Galaxy S6
mikeyinid said:
It means BmC is actively working on it. I didn't know he and @eousphoros were working together, but I know if BmC is working on it, we'll have something sooner than later. I noticed slayher is working on it too. Haven't seen him around for a while but he knows his **** too.
Click to expand...
Click to collapse
Slayer, BmC, and myself have been poking at it since launch. Most of our work has been going on thru emails or irc. The next couple weeks should be interesting. Right now we are fighting a framebuffer issue, once we have that resolved things will start moving faster.
eousphoros said:
Slayer, BmC, and myself have been poking at it since launch. Most of our work has been going on thru emails or irc. The next couple weeks should be interesting. Right now we are fighting a framebuffer issue, once we have that resolved things will start moving faster.
Click to expand...
Click to collapse
You're working with pretty good company. Can't wait til you guys break through the framebuffer issue and things get rolling.
mikeyinid said:
You're working with pretty good company. Can't wait til you guys break through the framebuffer issue and things get rolling.
Click to expand...
Click to collapse
More like they are working with good company but yeh. All three of us have solid experience with android and samsung in general. CM will happen eventually. Just keep in mind my original estimate of 9 months till stable release. (8 months left)
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
Here is my build of LineageOS 13.0 for the Galaxy S4 LTE A. It is based on the pure LineageOS code unless indicated otherwise.
* IMPORTANT *
Please note that these builds are based on nothing else than the unchanged official code from LineageOS. So every credit goes to the ones providing the code.
I will not and cannot make any changes to the code. The only thing I can do and will do is build the ROM.
Also, it should be understood that I take no responsibilities whatsoever if anything goes wrong when you install the ROM. Like any custom ROM this is completely at your own risk!
However, you can expect that any ROM I share has been installed on my own GT-I9506 (starting with the latest official Samsung firmware 5.0.1) and runs without obvious issues. Your mileage may vary.
https://www.mediafire.com/?c8q4lqh675hc97b,7dhley6dl6j9dnb
Based on LineageOS official code up to https://review.lineageos.org/154230
Which modem and boot loader can you recommend?
audianer said:
Which modem and boot loader can you recommend?
Click to expand...
Click to collapse
I flashed the latest official Samsung firmware to prepare for LineageOS 13.0
I'm trying to build the latest version, which does build without error, but upon booting gets stuck at starting the apps, i.e. just before showing the lock screen. The latest working build was from January 5th 2017 and I experienced the error first on a build of January 8th 2017. So I suspect the commit in question is one from January 6-8.
Before I'm forced to manually investigate commit-by-commit from the latest working version, does anyone know what has changed that causes this error? I was not able to get any output from adb logcat either, so I have no idea what went wrong... which is rather frustrating.
What device tree and kernel did you use?
DualJoe said:
What device tree and kernel did you use?
Click to expand...
Click to collapse
The same as the working previous build: LineageOS/android_kernel_samsung_ks01lte & LineageOS/android_device_samsung_ks01lte. As far as I can see nothing in the kernel or device tree has changed, thus it must be some incompatibility with the rest of the LineageOS code.
I just tried another build just an hour ago, same result: stuck at the final starting apps (before the vibration). I also tried reverting to a working state of the source (of January 5) by using "repo forall -c 'git checkout `git rev-list --all -n1 --before=", but that one didn't even build.
I would appreciate any help here. It's not like there were some exhaustive documentation about how to build LineageOS. And anyway, apparently building is not the issue here.
If that's still Solk2's stuff it might be very old indeed.
DualJoe said:
If that's still Solk2's stuff it might be very old indeed.
Click to expand...
Click to collapse
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
WeirdSoup said:
No. It seems that @solk2 has started to develop the ks01lte again. See the github commits:
https://github.com/LineageOS/android_kernel_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_kernel_samsung_ks01lte/commits/cm-13.0
https://github.com/LineageOS/android_device_samsung_ks01lte/tree/cm-13.0
https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0
(Note: There is no cm14.1 branch on @solk2's github repo yet.)
Click to expand...
Click to collapse
Uhm... There are cm-14.1 branches too.
zardak said:
Uhm... There are cm-14.1 branches too.
Click to expand...
Click to collapse
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
WeirdSoup said:
I said "@solk2's repo".
And as you can see, there are no additional commits on CM14.1 branch in LOS's ks01lte device repo, compared to cm13.
Click to expand...
Click to collapse
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
Click to expand...
Click to collapse
Oh, I'm sorry. I misstated. I mean, the "device" repo. (https://github.com/solk2/android_device_samsung_ks01lte/commits/cm-13.0)
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
zardak said:
It looks like a waste of time and work, doesn't it? There is no point in having 3 or more different builds with no particular differences. Devs might want to join the official repos instead and make their changes there.
Click to expand...
Click to collapse
You are absolutely right. I dont know, maybe they have reasons not to join the LineageOS team, but when I got my S4 I was rather confused with all this different versions. I mean for many devices you get unofficial builds with extra features/improvements, but for the I9506 its hard to tell the differences. However at the moment I would say the build by gugu0das is the best, but it looks like he is not going to update it anymore. So yes, it would be great to have all those talented developers out there working on the same repos.
PixelChris95 said:
So yes, it would be great to have all those talented developers out there working on the same repos.
Click to expand...
Click to collapse
I believe this is some sick "if you don't figure it out yourself, you're not supposed to know how to do it" attitude of some (most?) developers. Or another symptom of "not invented here" syndrome.
If LineageOS official builds are available I will surely not waste time to build it myself, but in the meantime I would like to be up-to-date. So still, anyone pointing me to information how to do it is very welcome.
zardak said:
Well, solk2 started to push changes on his kernel's repo days ago, even on cm-14.1 branch.
Anyway, I think is just a matter of time. We'll get official builds sooner or later.
I just don't understand why solk2, kyasu, and possibly gugu0das and others don't collaborate all together to only one kernel/device for this phone
Click to expand...
Click to collapse
I think the same of you. It could be better for all of us to make a ROM with the best of their ROMs.
JohnMcClane1htc said:
I think the same of you.
Click to expand...
Click to collapse
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
NeuDLi said:
What do you think? That I do not share what I do? I have provided a ROM for i9506 based on cyanogenmod 11.0 for a long, long time, as well as one for Nexus 7. And I have always made clear from where the sources for those builds came. Perfect transparency, don't you think?
It is because of disrespectful people like you that developers (and people like me, because I am not a developer) stop sharing!
Click to expand...
Click to collapse
If my comment has offended you, I apologize. My comment doesn't want to disparage anyone. And I recognize the effort of the developers because, although I am not, I know how difficult it must be to develop a ROM.
If my comment has offended you, I apologize. I am sorry.
I also create content in Htcmania and always share and show the sources. I only would want to say that sometimes, when finding so many ROMs based on CM, it can be difficult to decide for one or the other, since the changes between them are very subtle.
Regards
Maintaining/creating roms is usually the way people learn Linux, Android, compiling, git and such. That's why there are so many one-man projects. Once they are into it most vanish again/go over to other stuff though. Only few people keep over long time like Temasek. In the end there can't be enough roms. More options are always better than none. As long as people are posting the source code for other people to pick up they do work together already.
Hello everyone, I'm sort of a newbie in ROM building, and decided to compile ParanoidAndroid nougat for hammerhead. I followed the instructions from - https://github.com/AOSPA/manifest
Once I run ./rom-build.sh hammerhead, it runs for about 15 seconds before giving me the error in the screenshot attached.
Any help would be appreciated, thanks!
Wow I just realised those guys are still dead. They release a new version every 2 major Android releases. ? Even amateurs Devs (compared to them) release ROMs far more often. A bunch of ?s.
Sent from my Nexus 5 using Tapatalk
fr3quency said:
Wow I just realised those guys are still dead. They release a new version every 2 major Android releases. Even amateurs Devs (compared to them) release ROMs far more often. A bunch of ?s.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
They're working daily on that. you're free to compile and if you're smart enough you can successfully compile it :silly:
---------- Post added at 02:21 PM ---------- Previous post was at 02:20 PM ----------
DaNightmare said:
Hello everyone, I'm sort of a newbie in ROM building, and decided to compile ParanoidAndroid nougat for hammerhead. I followed the instructions from - https://github.com/AOSPA/manifest
Once I run ./rom-build.sh hammerhead, it runs for about 15 seconds before giving me the error in the screenshot attached.
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
You'll need some knowledge to compile it. You need to import some features from bullhead or angler and adapt it.. It's kinda hard especially if you're starting. I advice you to start building AOSP first and learn from that.
fr3quency said:
Wow I just realised those guys are still dead. They release a new version every 2 major Android releases. Even amateurs Devs (compared to them) release ROMs far more often. A bunch of ?s.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yo you are so ungrateful, show some respect! The only clown is you.
You clearly know nothing about what you are talking about. The Dev's behind AOSPA want to bring a quality ROM, they don't want to rush thing to take a step back in the Custom ROM scene and bring a buggy ROM, so instead they take their time to come up with something nice and good (probably). How fast a Dev can bring up a ROM and update it tells nothing about the quality of the ROM. AOSPA was awesome back in the JellyBean and KitKat days, I'm sure their Dev team is working hard to get back on that level. Instead of whining about them being slow with releasing, you could give them some help or just give it some time and be patience to see with what they are coming up with.
Mr.FREE_Bird said:
Yo you are so ungrateful, show some respect! The only clown is you.
You clearly know nothing about what you are talking about. The Dev's behind AOSPA want to bring a quality ROM, they don't want to rush thing to take a step back in the Custom ROM scene and bring a buggy ROM, so instead they take their time to come up with something nice and good (probably). How fast a Dev can bring up a ROM and update it tells nothing about the quality of the ROM. AOSPA was awesome back in the JellyBean and KitKat days, I'm sure their Dev team is working hard to get back on that level. Instead of whining about them being slow with releasing, you could give them some help or just give it some time and be patience to see with what they are coming up with.
Click to expand...
Click to collapse
It was my primary ROM for YEARS. There are other ROMs that cannot achieve their quality and yet I haven't encountered any bugs at all on those ROMs. How come?
fr3quency said:
It was my primary ROM for YEARS. There are other ROMs that cannot achieve their quality and yet I haven't encountered any bugs at all on those ROMs. How come?
Click to expand...
Click to collapse
Fair question, maybe it's because those ROM's you talk about made a decision between bringing quality or fixing bugs fast. PA probably goes for bringing a quality ROM instead of rushing on things to fix bugs and bring a "half work" ROM. Who knows? I guess we will see eventually
http://jenkins5.legacyserver.in/job/aospa_hammerhead/69/console
marcomarinho said:
http://jenkins5.legacyserver.in/job/aospa_hammerhead/69/console
Click to expand...
Click to collapse
Can you share the build?
theShadow800 said:
Can you share the build?
Click to expand...
Click to collapse
When everything is stable I will release it
marcomarinho said:
When everything is stable I will release it
Click to expand...
Click to collapse
Okay thank you!
I actually had downloaded Paranoid android 7.1.2 from AFH, idk if it was your build @marcomarinho , but it was working flawlessly. It had OMS, but i restored my backup and removed zip file... anyways it was working
aciupapa said:
I actually had downloaded Paranoid android 7.1.2 from AFH, idk if it was your build @marcomarinho , but it was working flawlessly. It had OMS, but i restored my backup and removed zip file... anyways it was working
Click to expand...
Click to collapse
I'm working close with AOSPA team to make it stable. There's much to do.. fix camera, video player, wifi... Only after that I'll release with the permission of paranoid Android team only!!
@marcomarinho how is the work under PA going?
aciupapa said:
@marcomarinho how is the work under PA going?
Click to expand...
Click to collapse
In the final stage almost ?
marcomarinho said:
In the final stage almost ?
Click to expand...
Click to collapse
Great! If you need any testers, logs etc PM me
marcomarinho said:
In the final stage almost ?
Click to expand...
Click to collapse
As @aciupapa said if you need testers or something contact us, really glad to help :good:
My nexus 5 died... 2 day ago motherboard has failed