Related
Can anyone tell me what is a nightly build? Ive read over at the Development forum in the Cyonegen thread. there are mentions of a nightly build ROM. What is this?
Thanks in advance
If my definition if correct, it's one that is still being worked on. Not like a regular one with a few bugs. This is like a build before they would announce it a beta/rc.
Kinda like an underground build for only the advanced
Yes. Its the 'current build'. Another way to look at it - better two beta builds.
my understanding of nightly builds are that those builds are not supported in any way, they are experimental. flashing them on our phones=120% our responsibility even if it crashes. u find links at some places but i guess theres a reason for it to not be out in the open.
Nightly build = An automatic build from a codebase.
Simple as that. Implies it's untested, and yes, could eat babies as the other replies imply.
In software development, a neutral build is a build that reflects the current state of the source code checked into the source code version control system by the developers, but without any developer-specific changes.
A nightly build is a neutral build that takes place automatically. These typically take place when no one is likely to be working in the office so that there are no changes to the source code during the build. The results of the build are inspected by the arriving programmers, who generally place a priority on ensuring the recent changes to the source code have not broken the build process or functionality of the software.
When someone says a developer "broke the build", they are effectively saying that a developer checked in code which might very well have compiled (and hopefully also run properly) in their account, but does not compile (and therefore, cannot be run) in anyone else's account. This is typically due to additional developer-specific changes that were either not checked in, or (in the case of environment variables, etc.) were modifications to systems not under revision control. One of the most common cases is remembering to check in all modified files, but forgetting to add newly created files to the repository. If the other developers check out the new code without being aware of the problem, their work may grind to a halt while they wait for the problem to be fixed (or try to fix it themselves, which can be even more problematic, if multiple developers attempt to fix the issue at the same time). This naturally can result in a significant loss of productivity.
Neutral builds are important for software development processes running at high loads with short schedules; not having them means that any build that needs to be created for the Software Quality Assurance department has to be created using code which may be in the middle of major modifications, and which would best be left out of a build for testing (particularly a build being evaluated for possible release).
Neutral builds can be done on a machine which is also used for active development if enough caution is taken, but it is safer to dedicate a machine to that purpose because an issue in the build process could cause the machine to become unstable.
http://en.wikipedia.org/wiki/Nightly_build
Thank you everyone!!
Not sure if this is where to ask.....…but if you load the latest nightly tenderloin build for my touchpad, do you need any of the previous builds I still have not loaded
?????
sonnyford said:
Not sure if this is where to ask.....…but if you load the latest nightly tenderloin build for my touchpad, do you need any of the previous builds I still have not loaded
?????
Click to expand...
Click to collapse
No.
Sent from my HTC Desire using xda app-developers app
Chromium said:
No.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply. Where can I ask if I can unload the old web is I still have in my touchpad that is now shared with the android system you guys helped me install? Thanks again for all the help
sonnyford said:
Thanks for the reply. Where can I ask if I can unload the old web is I still have in my touchpad that is now shared with the android system you guys helped me install? Thanks again for all the help
Click to expand...
Click to collapse
Sorry, Im not sure what youre asking. Could you please clarify.
Chromium said:
Sorry, Im not sure what youre asking. Could you please clarify.
Click to expand...
Click to collapse
I have a HP touch pad that I was able to load android on with the help of all the xda information. My 1st question is, i have both the android and the original web os still installed. How can I wipe out the web os?
2nd I was finally able to load one of the last nightlys and I am having some issues. i see there are 2 releases and I have downloaded 1 but I have not been able to loade It
sonnyford said:
I have a HP touch pad that I was able to load android on with the help of all the xda information. My 1st question is, i have both the android and the original web os still installed. How can I wipe out the web os?
2nd I was finally able to load one of the last nightlys and I am having some issues. i see there are 2 releases and I have downloaded 1 but I have not been able to loade It
Click to expand...
Click to collapse
Ah ok. This is the nexus one section, so I'll suggest that you post your questions here instead which is the q&a section meant specifically for your device. You will get better info there, rather than here.
Just wanted to let you guys no that you can now go into the downloads section of ROM manager and you'll see the Sonofskywalker3 section. Blackhole is not quite ready for release yet, so you won't see it there, but I have put up a large collection of live wallpapers, multitouch keyboards from camelot, boot/shutdown animations, and launchers that you can now flash easily straight from your phone. I haven't been able to test these since i don't have a vibrant, so i'm relying on you guys. Please post any problems you have wiht anything in ROM manager to the official error reporting thread at www.androiddoes.net/sonofskywalker3 or right here in this thread and i'll try to keep on top of it. thanks for all your support guys.
Awesome! Checking it out now.
Sent from my SGH-T959 using XDA App
Dude, can you please send me instructions on how to get this added to rom manager.... I have tried koush with no luck.
Awesome you were able to!
Will this need a ROM Manager update, or is it all ready to go? (I'd look myself, but I'm flashing back from CM at the moment..)
Edit: Oh wow, is this nice. s15274n- It's under the download rom section. I know it mentions something about the premium version, click that.
to answer both questions at once: www.github.com hosts all koush's code for rom manager manifests. If you open an issue there with the code you want added one of his team will add it. once it's added you show up in rom manager instantly, no upgrade needed, because when you click donload rom in any version of rom manager it parses the code at github.com in manifests.js and looks for any vibrant = true tags, and if it finds it, it displays the info. I personally forked the manifest, edited it, and used a pull request to get it committed to the main manifest. if you want help getting yourself in rom manager, look for me in #sonofskywalker3 on irc tomorrow evening and i'll be glad to chat with you and walk you through it.
I love you...whomever the fark you are!
(Awaiting the final...mac fag sadly).
/final being tested....I hate ODIN
//no access other than work
///slashies
If it's that easy, why aren't the ROMS in there? That would save so much time and heartache.
None of the live wallpapers work for me...Axuras 2.1
Patience.....fauk, someone is going the proper route and you want to rush them.
CMR flashing FTW!
None of the live wallpapers work for me...Axuras 2.1
Give it time...an updatable rom via CWM is awesome yet time consuming....waiting patiently
Using a chihuahua to post up in this B
Hey lightninbug, do the wallpapers just not work? Did you flash them thru clockwork? Im at work and I dont want to do anything to soft brick my phone.
So you actually flash a wallpaper?? Sounds strange.... lol
yeah they dont soft brick.....just fc upon trying to open them.....yes flashed thru clockwork n rom manager...they installed to system/app..dont work tho
Thanks lightnin. I'm having trouble finding this stuff tho. My download section says it only has extras and free stuff. Not sure where to find these goodies at.
Sent from my SGH-T959 using XDA App
I'm seeing everything in the download rom section. But im on ji6 and most of the items are for 2.2 . Do i need to be running a 2.2 build fot this to work right?
Sent from my vibrant
Op 1 week ago you posted a galaxy tab Rom that bricked phones. Soon after you just recently asked devs how to make a Rom. Now your going to post a Rom. No thanks noob that's one black hole I won't be goin down.
Jerzeeloon said:
Op 1 week ago you posted a galaxy tab Rom that bricked phones. Soon after you just recently asked devs how to make a Rom. Now your going to post a Rom. No thanks noob that's one black hole I won't be goin down.
Click to expand...
Click to collapse
I'm afraid you have me confused with someone else. I have never released a ROM for galaxy tab, only one before this was the version for fascinate, and it's working great on my own phone as well as many others. Also I have never posted here asking how to make a ROM. I got started by reading tutorials online, getting help from other devs in IRC, and a lot of trial and error with my own phone before I ever released my first ROM. I don't mind criticizm, and welcome error reports, both are ways to improve the final product. However they are only helpful if they are true. If you can link me to the posts where I supposedly did these things I may better understand what you're talking about.
As far as the live wallpapers they are from the fascinate, I was hoping they would be installable without modification. Is anyone else having this issue with other roms? could you please get me a logcat during an fc so i can see what it's doing? also please try the digital rain wallpaper, it's from the market so we can use it as a kind of control group. thanks.
Sonofskywalker,
you will have to excuse the comments and tone of some in here. Recently this section has many unacceptable outbursts. I agree, issues must be raised in a constructive manner, rather than just being rude.
thanks for your work and I'll take a look.
blackerwater said:
I'm seeing everything in the download rom section. But im on ji6 and most of the items are for 2.2 . Do i need to be running a 2.2 build fot this to work right?
Sent from my vibrant
Click to expand...
Click to collapse
Actually, the bootanimations are firmware independent, so they'll work fine, the keyboards have been tested on 2.1 on the fascinate and they worked, so give them a try, and the livewallpapers came from 2.1 on the fascinate, and don't work on at least 1 2.2 rom, so if you can try them out that'd be great. and all these updates do is add an apk file to your system partition, so there's no worry of bricking as long as you have a nandroid backup.
that being said, I need a few people to test the final alpha build before i release it as a public beta, just got it uploaded this morning. Please email me at [email protected] if you're interested, and i'll be glad to send you a link. please note you'll need to have a jk6 modem and kernel installed, but i'll be glad to send you links for those too.
Has anybody taken a look at the new official JB release that popped up at http://sbf.droid-developers.org/cdma_maserati/list.php ? (Although, I can't access it currently)
It's been mentioned on another thread (http://forum.xda-developers.com/showthread.php?t=2277830 ) regarding the ability to root, but it doesn't look like it's been looked at in any depth whether it includes any fixes, etc. The build date has changed to the 5th April, and the version is 9.8.20-72_VZW-18-2.
Cheers,
Steve.
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
alex94kumar said:
This should probably be in q&a section... but yeah I wonder what is in it too... either way, I'm pretty happy sitting on eclipse 1.0.6 right now
Xoom'd using the XDA-Developers Android app
Click to expand...
Click to collapse
You could be right regarding the location, apologies if people object - I just thought the ROM guys would probably be the ones most likely to be all over it.
File Mirror
FWIW - I found that droid-developers.org seemed a little hit and miss, so I've set up a private file mirror for this new release. If somebody wants access to it, then just PM me. I'm trying to sort out a public mirror too, and will update this post when/if I get that sorted out.
Cheers,
Steve,
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
sd_shadow said:
I am uploading cdma_maserati/cdma_maserati_9.8.2O-72_VZW-18-2_1ff.xml.zip
to my http://d-h.st/users/sd_shadow/?fld_id=12041#files
via remote url upload, usually doesn't take very long, quite a bit faster than uploading from my pc
Click to expand...
Click to collapse
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
cellzealot said:
This same version upgrade for XT926 HD appeared and was said to be a bugfix for the 4.1.2 OTA and that another more significant update would appear shortly for all devices but still remain 4.1.2 and would include Isis.
So we should expect to see a couple of OTAs pushed out on accelerated schedule that will match this XML file and the subsequent update.
Click to expand...
Click to collapse
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
It's safe for now...
StevePritchard said:
Nice one - I'm currently 66% of the way through uploading to FileDropper (which I've never used before, but it was free, and didn't require sign up).
So is the "more significant update" meant to be coming after this April 5th release?
Cheers,
Steve.
Click to expand...
Click to collapse
Yes, and I just flashed the boot, system and radio images from the MR2 XML and then rerooted using razr_blade.
So, we are safe to use this file to upgrade the firmware without any loss of root or any other issues.
The secure version did not increment so it is also possible to revert to the prior -18 release without risk of soft bricking.
This follows the pattern of the update for the HD and will likely be the same for the other devices that just recieved 4.1.2 in this cycle.
The next update is the one the will include ISIS and may also have security enhancements that will need to be carefully scrutinized.
That is conjecture on my part, at this stage, we don't know.
It would be nice to know what changes the release addresses. My hope is that it sorts out the hardware keyboard problem of unsticky shift keys in some applications.
Cheers,
Steve
I have decided to rework the thread to ovoid any confusion as the intent of posting this thread was to ask questions about compiling custom Roms from AOSP source that someone like myself who gained their development experience on other devices that building from pure AOSP code was not an option and are not as familiar working with AOSP. In the past my own experience comes from using and modifying for example the Cyanogenmod source so after attempting to now base my Rom on AOSP this time around with Lollipop have run into a few unfamiliar differences. As each question or topic is addressed I will update the Op. The hope is not only will I find solutions or answers to my own questions but that others in the same position will also be able to find use of the discussions posted in this thread.
Compiling the AOSP source into a format that can be safely flashed using a custom recovery. This was a 3 part question the first was just simply how to compile AOSP in a format other then .img files that can be flashed using a custom recovery without the need of flashing through fastboot or needing to use the adb sideload option.
1, Compiling AOSP into the for of an update.zip.
This was answered in short by know.patience by suggesting to use the “make otapackage” command in place of "make" to start the build. Was also made aware that a few modifications would need to be made to avoid producing an update package that does not use the new block format but instead the old style zips we are most used to seeing.
2, Now can create an update.zip using the “make otapackage” command ran into an issue that by flashing the update.zip produced would in the process replace the custom recovery used to flash with the Nexus Stock recovery. This was answered by Lethargy who suggested and provided a Link for the following commit.
For getting rid of the AOSP recovery:
https://github.com/Lethargy/android_build/commit/48521e167c642db76c9d4f52b1c63f9abc7f707f
https://github.com/Lethargy/android_build/commit/1d9224bd45ef2b4f5601a157de2bfe3bb1c95558
3, Now can create an update.zip using the “make otapackage” and after applying the above commit are now able to flash the update.zip without replacing the recovery Lethargy also provided links for the following commits.
To get rid of the block-based zip format:
https://github.com/Lethargy/android_build/commit/4d458300d935a3a9d893a590286cb578dcf54db2
You'll also want to make sure you have this commit so it doesn't flash awfully slow in recovery (8~ minutes, but only around 1-2 minutes with this commit):
https://github.com/Lethargy/android_system_extras/commit/52f8d5fc3edfacd112827d0a41516c1dc5f4a468
This one isn't required but you may as well:
https://github.com/Lethargy/android_build/commit/242be9ae4f05e3cb1d39d635cac7147ff904700c
Compiling using the AOSP Master branch vs release branches. In following the directions provided on the Google development site are given the command for downloading the source code using the Master branch. Using the Master branch as apposed to a release branch such as android-5.0.2_r1 or lower have found that the source compiles just fine but have run into one issue and just a general question that a little explanation would be helpful for general understanding of the AOSP Master branch.
The issue is that after flashing a Rom compiled using the Master branch everything in the Rom works as expected other than the radio. I have so far using the same exact vendor blobs as compiling a release branch have not had a signal and baseband version is listed under about phone as unknown.
The general question is that the android version listed compiling a Rom using the Master branch is version 5.0.50.50.50.50. In general I have yet to understand what this version number represents and very little to no information available via the Google Box.
Between the both I now wounder if the Master branch is intended for actual use or if so what changes are required so the baseband version is recognized and radio / Ril will work?
Quick Answer:
Google first commits new code into master and then is later tagged with an update for realease so in generall many things can be broken and the master branch is and not intended to be stable so if building from master expect that things will be broke or buggy.
Compiling Rom and Kernel together. For those of us again used to compiling using say the CM code are now used to compiling the Kernel along with the rest of the code. I know it is easy to just compile the Kernel and include in the device tree but for those of us who would still like the Kernel compiles with the rest of the code there is no information available on the Google Developers site for doing so and there seems to be a few differences as have tried just using the lines used in the CM Hammerhead device repository. I have come across these commits from Cl3Kener that should help. Hate posting other developers code but is on Github so is there for the public at large. So far have only tested as is so will update if finding not all changes are necessary or can be modified.
Inline Kernel Building
https://github.com/OptiPop/device_lge_hammerhead/commit/7de8fd95b6df16cb6311161d5048874d69cf1cb1
https://github.com/OptiPop/device_lge_hammerhead/commit/87768896f4eb8fcd989ce3b8492ca65305513851
https://github.com/OptiPop/device_lge_hammerhead/commit/5460eb3aa76ea5d813f64a3b3bab6ace1be6de68
Adding Pre-Built APK's
Seems Sprint users need a few apk's for updating prl and what not that are included into the Stock release but are not part of the AOSP code. For some reason through vendor or even device have tried adding these apk's into the build. First try I created a sprint vendor section and received a few errors untill learning would need to add sprint into a vendor white list found in build. Will post link to file later. After found the extra "Services.jar" I found in the stock image not found in the aosp compiled Rom did copy into the build but the apk's had not. Looking in the other vendor blobs noticed lge adds "qcrilmsgtunnel.apk" so followed the example and even tried just adding the other spk's into lge expanding the list used for adding in "qcrilmsgtunnel.apk" but still no luck. Also have tried adding through the device files for Hammerhead just to get them into the Rom for testing and still no luck. If this was CM or any other Rom not using pure aosp this would have been a 5 minut project so need to do some aditional homework.
Again think this thread could be a good resource for developers who are new to building their Roms around AOSP so wanted to include everything I run into during the process of moving away from using a heavily modified CM based code as the base of my Rom to using AOSP in its place so developers who are or in the same process or for those in the future can use as a resource to quickly adjusting. I have been building CM based Roms like Starship for years and after hours of working on other aspects to suddenly be stumped by these small differences between platforms can be very frustrating.
to the OP:
answer to your first question comes in two parts.
a) use 'make -j# otapackage' will generate a zip that is flashable in custom recovery.
b) if you plan on adding other files after the zip is made, you will need this info here:
https://github.com/android/platform_build/commit/26e6619c37e294fe2ee63aaa759e0ac861775ce8
There are some modifications needed to generate the OG zip files instead of the new "block" format.
Google hasn't released the 5.0.1 image for the N5 but that doesn't mean you can't build it and install it yourself. I'm running it and it seems okay to me so far although I'm hardly an expert.
simms22 said:
op.. this section is only for developers, to get work done. if you have questions, they belong in the q&a section. you arent new, you should know this. again, this section is only for developers, mot for the normal xda folk to post questions. you have a q&a section just for asking questions. please, ask a mod to move your thread there.
Click to expand...
Click to collapse
I am building a customized AOSP Rom I am interested in sharing so was looking for help or direction in creating an update zip that can be flashed in a custom recovery like TWRP. I am not used to compiling AOSP and with the help of know.patience in the first reply am now able to compile an update.zip I can flash in TWRP but in doing so it also replaces TWRP with the Stock recovery. I have still been using the .img files to flash personally but am still trying to figure out how to solve the recovery replacement issue. I still have other features I am adding and testing before I would like to post my work but before I get to that point I still need to figure out my recovery replacement issue. Maybe using the words personal use may have been confusing but at the moment until ready I have only been using my work personally but would like to at some point post and share. I also have work that is not AOSP based I am sharing in the Android Development section but I have been building CM and other source based Roms and sharing for years. This is the first device I have been able to build AOSP and still have a few things to figure out before sharing any of my AOSP based work. I am otherwise not sure why you think these are questions for general Q&A.
I started this thread in Android Development as there was only about 4 posts in this section and I see many AOSP based Roms in Android Development who's developers obviously know the answers to my questions so tried to get away posting there in hope one of these developers could help or like in the first response point me in the direction of a commit before the thread was moved by a mod into this section. Do you think someone in the general Q&A section is better equipped to help answer questions about compiling an AOSP based Rom in the form of an update.zip that can be flashed in TWRP without also replacing TWRP with the Stock recovery?? Would also be nice knowing what changes in the code need to be made in compiling an old style update.zip that does not use the new block format. This would be a bonus but overall not %100 needed as instead of moving files around after the code has been compiled have added init.d support and first have all the files I want moved into a staging directory and then form an init,d bash script to move the files during first boot and remove those that are not needed like this example I used in my CM based version of the Rom I am trying to update for AOSP for 5.0.
https://github.com/Starship-Android/android_device_starship-common/blob/cm-11.0/app-update
https://github.com/Starship-Android/android_device_starship-common/blob/cm-11.0/cleanup
I must seriously be underestimating the knowledge and in general the types of questions being asked and answered in the general Q&A section.
Honestly if not for the amount of times thanked I would think this comment was not so much about helping or community but more about someone trying to puff themselves up by trying to appear important by making decisions about what questions are worthy of being asked but judging by the number of times they have been helpful I am thinking its either a case of not reading or understanding the question being asked or my own inability to express my questions in the proper manor. Either way its definitely not about taking up resources in a section with less than 10 total posts. The frustrating part as a community as I like to believe we are all in is that why I worked on other parts in updating my Rom had expected that at least more than one developer out of all the AOSP based Roms posted in the development section would have helped me with this one part. Its not like I am asking how to be a developer just a resource to help with two simple things I am sure I could have figured out and will most likely still figure out without any help. Overall my thoughts behind posting this question was that why I am working to figure out something a bit more time consuming at least more than one person would be helpful enough to copy and past a commit.
XDA is weird in that with other devices all the developers would join a team and start a shared group of repository’s for one another to use in trying to make the best possible experience and options for everyone. For example in the op I posted an example of hours of work I did showing what libraries are needed by one another just so others could use it also in trying to port as much as possible for in that case the Galaxy Mini. Then with other devices like seems to be the case with the N5 its all about competition and what I am starting to call the smartest person in the room syndrome. Its just a shame there are only 5 maybe 6 threads posted in this section and I think that says allot about the community in general. So many good things could come about if we just tried to be helpful and pull as much knowledge together as we could. Anyhow think its time for ending this rant.
chairshot215 said:
compiling an AOSP based Rom in the form of an update.zip that can be flashed in TWRP without also replacing TWRP with the Stock recovery?? Would also be nice knowing what changes in the code need to be made in compiling an old style update.zip that does not use the new block format.
Click to expand...
Click to collapse
To get rid of the block-based zip format: https://github.com/Lethargy/android_build/commit/4d458300d935a3a9d893a590286cb578dcf54db2
You'll also want to make sure you have this commit so it doesn't flash awfully slow in recovery (8~ minutes, but only around 1-2 minutes with this commit): https://github.com/Lethargy/android_system_extras/commit/52f8d5fc3edfacd112827d0a41516c1dc5f4a468
This one isn't required but you may as well: https://github.com/Lethargy/android_build/commit/242be9ae4f05e3cb1d39d635cac7147ff904700c
For getting rid of the AOSP recovery: https://github.com/Lethargy/android_build/commit/48521e167c642db76c9d4f52b1c63f9abc7f707f then https://github.com/Lethargy/android_build/commit/1d9224bd45ef2b4f5601a157de2bfe3bb1c95558
Lethargy said:
To get rid of the block-based zip format: https://github.com/Lethargy/android_build/commit/4d458300d935a3a9d893a590286cb578dcf54db2
You'll also want to make sure you have this commit so it doesn't flash awfully slow in recovery (8~ minutes, but only around 1-2 minutes with this commit): https://github.com/Lethargy/android_system_extras/commit/52f8d5fc3edfacd112827d0a41516c1dc5f4a468
This one isn't required but you may as well: https://github.com/Lethargy/android_build/commit/242be9ae4f05e3cb1d39d635cac7147ff904700c
For getting rid of the AOSP recovery: https://github.com/Lethargy/android_build/commit/48521e167c642db76c9d4f52b1c63f9abc7f707f then https://github.com/Lethargy/android_build/commit/1d9224bd45ef2b4f5601a157de2bfe3bb1c95558
Click to expand...
Click to collapse
Thank you this is well beyond what I was looking for and don’t worry I make it a point not to send out PM's with questions that can be helpful for others as well. Otherwise would have blown up the AOSP Rom posters in development but thanks for the information.
chairshot215 said:
.. and don’t worry I make it a point not to send out PM's with questions that can be helpful for others as well..
Click to expand...
Click to collapse
If you mean "I'll probably ignore you if you try asking for support over PM.", that's part of my forum signature.
If you need anything else feel free to @mention me in a thread, though.
I reworked the Op to avoid confusion as Mods have been moving the thread around into different sections. I personalty believe these questions are more geared towered development than general Q&A but at least at the moment I appear to be wrong about that. Never know though as in the past one day one of the mods may decide to move the thread back into its intended location but until then I guess these topics will be of better use to general users than developers.
chairshot215 said:
I reworked the Op to avoid confusion as Mods have been moving the thread around into different sections. I personalty believe these questions are more geared towered development than general Q&A but at least at the moment I appear to be wrong about that. Never know though as in the past one day one of the mods may decide to move the thread back into its intended location but until then I guess these topics will be of better use to general users than developers.
Click to expand...
Click to collapse
You should include the other commit (https://github.com/Lethargy/android_build/commit/1d9224bd45ef2b4f5601a157de2bfe3bb1c95558) which fixes building since the first one results in "IndentationError: unexpected indent".
Lethargy said:
You should include the other commit (https://github.com/Lethargy/android_build/commit/1d9224bd45ef2b4f5601a157de2bfe3bb1c95558) which fixes building since the first one results in "IndentationError: unexpected indent".
Click to expand...
Click to collapse
Thanks for the heads up, when testing these I also cherry picked a few other things that looked related. Have to double check but may have forked the repository’s from you so would receive credit if anyone decided to look over my repository’s. Well overall my personal Github has been pretty bare as in the past most work was done on more obscure Virgin Mobile devices with only a few developers so we would pretty much create an organization for all the developers to use.
https://github.com/MTDEV-CM7
https://github.com/MTDEV-CM10
https://github.com/vmobi-triumph
https://github.com/MTDEV-KERNEL
https://github.com/MTDEV-MIUIv4
https://github.com/MTCM9
https://github.com/MTCM10
https://github.com/HTCCM9
https://github.com/HTCCM10
https://github.com/HTCStarShip
https://github.com/HTCUbuntu
https://github.com/vmobi-shooter
https://github.com/vmobi-gogh
These days have been keeping everything under Starship-Android.
https://github.com/Starship-Android
Have 2 other members listed who I had worked with in the past but has otherwise been a solo organization with one of the other members who decided on going with the Moto X and Verizon over the N5 and showed little interest in his 2012 version of the N7 as it was intended for being a Nexus only device line up and the second being my Kernel Guru from a few devices back who mainly joined to help me out with a few things but ultimately what I am getting around to is this is the first time working %100 solo. Have to say without having anyone to bounce off ideas and share findings with things definitely move much slower and take a bit of getting used to. Is also the reason for starting threads like this. Most of this stuff looking in the developer section appeared to be pretty common knowledge but having never worked from pure AOSP before was slowing down other development for about a week just to figure out what seemed like half the community had already known and with what probably took at the most 5 or 10 minutes of copying and pasting commits probably saved me a weekend of sifting through github and testing. I hope by creating a thread like this will be able to do the same for others.
Hi guys,
Anyone manage to fix RIL problems with master branch?
I also build AOSP roms so for sure i will hangout here
Sent from my AOSP on HammerHead using XDA Free mobile app
malcho said:
Hi guys,
Anyone manage to fix RIL problems with master branch?
I also build AOSP roms so for sure i will hangout here
Sent from my AOSP on HammerHead using XDA Free mobile app
Click to expand...
Click to collapse
Never tried.
ODEXED
i am successfully build cm12 with fully odexed. now i like to odex some prebuilt apk also but LOCAL_DEX_PREOPT=true not odexing prebuilt apk. can somebody help me? already DEX_PREOPT=true working fine.
soorajj said:
i am successfully build cm12 with fully odexed. now i like to odex some prebuilt apk also but LOCAL_DEX_PREOPT=true not odexing prebuilt apk. can somebody help me? already DEX_PREOPT=true working fine.
Click to expand...
Click to collapse
Why do you need to odex a prebuilt apk?
Not sure if what you want is even possible.
But if odexing your prebuilt apk is necessary then why not odex it then include the .odex with the prebuilt?
Lethargy said:
Why do you need to odex a prebuilt apk?
Not sure if what you want is even possible.
But if odexing your prebuilt apk is necessary then why not odex it then include the .odex with the prebuilt?
Click to expand...
Click to collapse
suppose i want to odex gapps. how to?
malcho said:
Hi guys,
Anyone manage to fix RIL problems with master branch?
I also build AOSP roms so for sure i will hangout here
Sent from my AOSP on HammerHead using XDA Free mobile app
Click to expand...
Click to collapse
Nothing so far, I downloaded the master and 5.0.2_r1 branches and have loaded both in meld for looking over differences but have not yet identified from the dif between the 2 branches that is responsible for ril working in release branch but not master. Still have allot to look over though still. Still have not found a decent explanation of the master branch to know if its recommended to build from but still just for Knowledge sake am interested in knowing. At first thought maybe apn's but not so sure with baseband also listed as unknown from my Master branch builds.
chairshot215 said:
Nothing so far, I downloaded the master and 5.0.2_r1 branches and have loaded both in meld for looking over differences but have not yet identified from the dif between the 2 branches that is responsible for ril working in release branch but not master. Still have allot to look over though still. Still have not found a decent explanation of the master branch to know if its recommended to build from but still just for Knowledge sake am interested in knowing. At first thought maybe apn's but not so sure with baseband also listed as unknown from my Master branch builds.
Click to expand...
Click to collapse
As far as i know all the patches goes to master branch then from this branch ,if they are ok,is distributed to lower branches.I also didn't find info why is named as 5.0.50.50.I will try to investigate this ril problem
malcho said:
As far as i know all the patches goes to master branch then from this branch ,if they are ok,is distributed to lower branches.I also didn't find info why is named as 5.0.50.50.I will try to investigate this ril problem
Click to expand...
Click to collapse
Thanks will definitely update the Op with any findings. Was very surprised to find the thread again as it has now been moved 4 times by 4 different Mods, some bounce it to general Q&A and then is bounced back here by another. I understand its not comprised of the most advanced development topics but with that said is still way more advanced than the topics being discussed by general users over in the general Q&A section. I had just thought it would be a nice one stop place for learning the basics of AOSP development. With the constant moving and scolding messages being received one would think the threads very existence is up there with crossing the streams and threatens the existence of Android development.
@chairshot215 Thank you for starting this thread. Thank you @Lethargy for all of your insight. I like to do my own perosnal builds every once in a while for my nexus devices. What I have observed over the years is that the Master Branch will sometimes have funky version numbers like you have described. One thing to consider is what @malcho mentioned. If all commits indeed go there first before the respective branches(although this may not entirely be the case), then it is likely that some things may be broken in the master branch from time to time, hence the ril problem. I think with the galaxy nexus I ended up running into issues from time to time with the master branch, and from there learned to build for specific branches/tags. For instance, there are times when items within a specific branch will be ahead of master in some areas and behind it in others, as in this link to platform_build for lollipop release https://github.com/android/platform_build/tree/lollipop-release. So with that, it is probably in our best interests to just use specific branches.
Milly7 said:
@chairshot215 Thank you for starting this thread. Thank you @Lethargy for all of your insight. I like to do my own perosnal builds every once in a while for my nexus devices. What I have observed over the years is that the Master Branch will sometimes have funky version numbers like you have described. One thing to consider is what @malcho mentioned. If all commits indeed go there first before the respective branches(although this may not entirely be the case), then it is likely that some things may be broken in the master branch from time to time, hence the ril problem. I think with the galaxy nexus I ended up running into issues from time to time with the master branch, and from there learned to build for specific branches/tags. For instance, there are times when items within a specific branch will be ahead of master in some areas and behind it in others, as in this link to platform_build for lollipop release https://github.com/android/platform_build/tree/lollipop-release. So with that, it is probably in our best interests to just use specific branches.
Click to expand...
Click to collapse
Thanks for the response and have definitely learned its better building from branches with a release tag. Still very curious why and how the branches are structured so thanks for the explanations.
Way totally off topic for the thread but landed a brand new SSD and decided to install everything fresh. After everything was set back up and wanted to start building I ran my usual,
-j'grep 'processor' /proc/cpuinfo | wc -l'
a very old habit before fully understanding what number to use after -j so used grep to figure it out based on Googles recommendation. The command did not work so removed the grep and just made it -j4 but also with 0 success. At first just figued I missed somthing setting everything back up and "make" is just not working but wrong again as running "make" command without -j of any number works just fine.
Also tried this with CM12 as I am doing 2 versions of my Starship Rom. One from AOSP and one using CM. Figured AOSP would be special for Nexus users why also having a version for CM I can make most changes by adding a Starship Device Tree could easily port the Rom to any device running CM supported or not.
https://github.com/Starship-Android/android_device_starship-common/tree/cm-12.0
Also found why compiling CM that -j also results in an error
Invalid lunch combo: cm_hammerhead--j4
No such item in brunch menu. Try 'breakfast'
So far have not found anything using the Google Box so figured may as well ask. If have not figured out by now I have no shame in asking questions. Oddly enough that is for things that are probably relatively simple. Took a better part of a week figuring out how to start CM using the Now Launcher and setting up init.d bash scripts for moving around and replacing libs after learning the Gapps package includes libs that will not work so the solution needed to be that the CM Gapps package libs needed to be replaced with either stock or libs pulled after installing the Now Launcher from the Play Store after flashing Gapps and the Rom staring. Also then what if user updates and wipes the system partition after the new and updated llibs have been moved into place. Anyhow point of story is things like this I will just figure out without bothering anyone but for the cant believe I need to stop what I am working on to figure out something most likely very simple and can be answered with very little time spent I have no shame in just asking. Not that someone else’s time is less important but like I have mentioned before is frustrating just after spending hours or days figuring out something asked in dozens of threads is just frustrating getting caught up or loosing momentum and thought processes over something so simple there are little resources available. Also I assume most devs have the same experience when you have an idea or thought behind resolving an issue that once you stop and change direction it just sometimes never comes back and that short time you had I guess can be called an epiphany is gone once going back. Otherwise thats how I justify asking dumb ars questions.
Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?