[ROM] CyanogenMod 9 / August 18 / Stable!?! - Asus Eee Pad Transformer Prime

August 16
Quick note on the OP
My apologies for neglecting the original post for nearly a month! I'm a kindergarten teacher, and I've been super busy preparing for the approaching school year.
I think the OP is mostly just a tool for newcomers (especially now that support for the 201 kinda slowed down - I'm sure most of you don't need a guide to flash your daily dose of CM, and don't need an OP!).
That said, I still think it's an important tool, because there are always newcomers. The OP could just get erased entirely and this thread/the discussion would survive, but I don't think newcomers would be as likely to start using CM without a handy OP. Whether or not that matters is up to you. Personally, I like seeing CyanogenMod grow (that's what she said?), and I think a larger install base = a better CM (that's what she said?), but to each their own.
For the nxet few months, I will try to keep up with the updates, but my guess is that I'll update about twice a month. That leaves a few options: 1) just let the OP updates be infrequent, 2) start a new thread, or 3) hand over the reigns to someone else.
option 1: Not my favorite. Like I said, I think a somewhat up-to-date OP is a good thing.
option 2: Not my favorite, UNLESS a mod can merge the new thread with the old thread. Many questions and answers are in these pages, and it's nice to search within a single thread and not the entire board
option 3: My favorite! If someone else wants to take over, it's cool with me. You can even have all of the "thanks," which some people care about so deeply. I only ask that you keep it classy - like CyanogenMod - and flash the updates yourself before posting.
I know from asking the mods before that people can't "share" OPs, I know from experience that nobody wants to do a google docs OP (*sniff*), but maybe someone can take over full ownership? if not, then I push for option two, but I'd like to see this old thread live on! Yes, it's an unofficial thread, but some of the devs have posted here, and I even got dalingrin's blessing in a PM, which is enough in itself to make this thread special!
So if you want to be the OP, just ask me, and we'll ask a mod to do some voodoo. failing that, maybe I could just give you my account...? But I'm not a huge fan of that idea, because I'm still going to use XDA.
Why does this thread exist?
​TL;DR answer:
It exists so that the thread title will say something like "[ROM] CyanogenMod 9 / Updated April 3," the OP will have relevant information, and people will have a place to discuss CM9 on XDA.
It does NOT exist because I want thanks (I do not) or because I want to scam people for donations (I have no donation link).
Long answer:
Right before the CyanogenMod team began posting nightlies for the TF201, theeggman posted his own build. In his thread, he stated: "Once official nightly builds are downloadable and confirmed useable, I will no longer regularly update this build." True to his word, his build (and the OP) is no longer updated. Despite the fact that the [KANG] label does not apply to the official nightlies, and the OP is not up to date, CM 9 users like myself are still posting on that thread.
There are two small problems with using that thread: 1) CM 9 users need to check CyanogenMod to see if new builds are available, because the thread title is never updated 2) The OP does not reflect the current offerings from CyanogenMod; unless you read the thread, you wouldn't even know that nightlies exist. I posted my concerns about this yesterday, and asked if anyone would object to a new thread devoted to the official CM nightlies (and stable builds, when/if they become available). Almost 24 hours have passed, and nobody has posted any objections, so I went ahead and created this thread.
Update:
I hoped that this could become a collaborative OP, but I asked Mr. Clown, and he said that it is not possible to share editing rights for posts. However, I really think it could be helpful to collaborate on things that change frequently, especially when considering the fact that we all use our tablet differently. With this in mind, I suggested a Google docs collaboration that could get periodically copied and pasted into the OP. If you're a regular CM user interested in helping, send me your gmail and I'll add you to the doc's list of editors.
Moving on!​
CyanogenMod 9 for the TF201!​I am not affiliated with CyanogenMod in any way, shape, or form. Please direct your thanks and donations to the CyanogenMod team, or consider donating to some of the other fine TF201 ROM developers on XDA.
Alert! CyanogenMod 9 may irreversibly break your TF201. Also, you need to unlock your bootloader to install CM 9, which completely voids your TF201's warranty. You assume ALL responsibility for any damage. Use CyanogenMod at your own risk. If you are not willing to accept these risks, then do not proceed.
Features: There are dozens of websites - including the official CyanogenMod website, found below - that describe the features of CyanogenMod, so describing them here would be superfluous. If a new feature premieres on a build for the TF201, it will be noted on the build list. In a nutshell, it has a very stock AOSP/vanilla/Nexus feel, but with performance tweaks and added tools/abilities.
Screens can be found here and changelog can be found here. (thanks paddycr)​​
Some fun news about CyanogenMod 9 (and ten!)
CM10 (running Jelly Bean!) will probably come our way!
Interesting presentation by CyanogenMod founder, neat stuff, not overtly technical. Check it out for some opinions, history, knowledge of how CyanogenMod works as an organization.
Latest Nightly
Released August 16
Size: 132.79 MB
MD5: cc1621b630e54a32cea024ef8fce5444
Latest Release Candidate (RC)
Released July 19
Size: 132.49 MB
MD5: 484e9cb7318e484c84a1434921cb6de7
Latest Stable build
Released August 10
Size: 132.79 MB
MD5: 62bebfdf39cfa91a93676e363b6442c6
Known Issues​
Remember, this thread is not maintained by a CyanogenMod developer, so these issues are not necessarily going to be addressed; this is just information for people considering using this ROM.
Toggling WiFi on/off can, in certain situations, freeze and reboot the tablet (WiFi issues seem to be completely fixed!)
Screen wakes upon closing tablet dock
External SD does not support NTFS
Battery Stats usage not available (only bar graph, no apps)
CyanogenMod custom setting to skip to next/previous track using volume keys when screen is off works poorly; one track can be skipped, but the volume keys turn the screen on, reverting the volume keys to their volume behaviors. Device is NOT set to wake with volume keys.
These issues are (hopefully) compiled collaboratively by other forum members on a Google doc. If you use CyanogenMod on your Prime, your help with the list would be very appreciated!
Installation instructions​
Prior to installation, please make sure you have read and understand the red "Alert!" above.
So your tablet is unlocked has root access? Time to install a custom recovery. When your tablet has root access (helpful) and is unlocked (mandatory), installing a custom recovery is easy, thanks to some amazing apps that are freely available on the android market. If this is your first time flashing a ROM, there are a few different ways to proceed, but I would suggest downloading either "ROM Manager" or "GooManager" from the Play market: they are probably the easiest ways to install a custom recovery. Both are very user-friendly. ROM Manager will help you set up ClockWork Mod (CWM, not to be confused with CM), GooManager will help you set up TWRP.
I get a lot of questions about this, so put another way: The free apps ROM Manager and GooManager can help you install custom recovery ClockWork Mod or TWRP, respectively. You need a custom recovery to install CyanogenMod. Although incredibly helpful, you do not need need ROM Manager or GooManager, but they can help you install a custom recovery. If you're not sure which one to use, just read their threads and see what appeals to you. I'm inclined to suggest ROM Manager / CWM because they have been around for a super long time and it's included with CyanogenMod, but I have used CWM and TWRP with CM9 and they both work great.
If using CWM: You MUST use Clockwork recovery 5.8.2.0 or higher. If you have an older version of clockwork installed, you will run into problems. If you made a nandroid with an older version, make a new nandroid. I think the easiest way to update is to use the ROM Manager app, available on the market.
Update: In fact, use 5.8.2.0 specifically, which can be found in ROM Manager under the heading "all CWM recoveries" (or something) near the bottom of the list. ROM Manager may make you install the latest version of CWM before allowing you to install the alternate versions, but don't let that scare you; just flash the latest, and then flash 5.8.2.0. Apparently the latest CWM update brought some problems for the TF201? someone correct me if I'm wrong.
Have you been using Root Keeper? Great app, but it doesn't play nice with the alternate recoveries (and now that you have an unlocked bootloader, you don't need it anymore anyway - CM9 is already rooted, turn it on/off in the settings). Delete the root backup, uninstall the app, and delete any backups (like TiBu backups) you have made of Root Keeper, as well as any nandroids that include Root Keeper.
The following instructions assume that your bootloader is unlocked and you installed a custom recovery like CWM or TWRP:
1) Download CyanogenMod 9 (below) Be sure to make note of the MD5 checksum. After the download finishes, make sure the MD5 on the download page matches the MD5 on your downloaded file (there are many apps that calculate MD5 freely available on the market). Your ROM file will probably be in your downloads folder.
2) Turn off your prime
3) If docked, remove your prime from the dock
4) Holding the volume down button, turn your prime back on. When you see the white text appear in the top left, press volume up.
5) Make a nandroid backup
6) New to CyanogenMod? Wipe data/factory reset, wipe cache, and wipe dalvik cache. If you're updating from an older nightly, that step is probably not necessary.
7) Install .zip from SD card, and chose the file you downloaded earlier
8) (optional) Install .zip from SD card, and chose the gApps
9) Reboot!
ALSO: Thanks to disturb3d1, you can watch his how-to-install-CM video here. Unlock, root, custom recovery install, and all sorts of other how-to videos are also available.
Download CM 9
As this ROM is build from stock CM sources the GPL parts can be found in the official CM repo (thanks Diamondback)
Download gApps
The gApps link is for April 29, 2012.
http://www.cyanogenmod.com/​

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

No need for disclaimer. Warranty is voided once you unlock your bootloader.

Thanks jdeoxys
Itaintrite said:
No need for disclaimer. Warranty is voided once you unlock your bootloader.
Click to expand...
Click to collapse
It seems like other ROMs that need bootloader unlocked to install still have some kind of warning. I'll take it off if you're sure, though.

Thanks for the thread. I don't think I will flash CM9 again until some more features are added, but its great to keep tabs on.
Transformer Prime/Galaxy Nexus CDMA

It's not the ROM that voids warranty but unlocking the bootloader.
As long as you can restore your device at initial factory state your warranty is preserved. For example on my phone I just have to use nvflash to restore a full stock ROM and to have a brand new factory device.. because on LG phones bootloader is open.
So you can remove those warnings, and people know what cyanogen is, even if I'm surprised by the proportion of total Android noobs here (seems like the prime is the first Android device of many here).

Itaintrite said:
No need for disclaimer. Warranty is voided once you unlock your bootloader.
Click to expand...
Click to collapse
Brave man to do that. I would expect that a noob could make a reasonable case for arguing that he assumed you'd thoroughly tested the rom before posting links to it.....
Remember also, users from different jurisdictions read these forums. Having a general disclaimer is unlikely to be a bad idea.
IMHO.
Sent from my Transformer Prime TF201 using xda premium

tangiers said:
Brave man to do that. I would expect that a noob could make a reasonable case for arguing that he assumed you'd thoroughly tested the rom before posting links to it.....
Remember also, users from different jurisdictions read these forums. Having a general disclaimer is unlikely to be a bad idea.
IMHO.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
+1
Sent from my Transformer Prime TF201 using xda premium

although file size seems 119.30mb, the download file size is 59.3mb
can you check please?

ayk33 said:
although file size seems 119.30mb, the download file size is 59.3mb
can you check please?
Click to expand...
Click to collapse
There is nothing to check, he doesn't maintain the server, which is cyanogen one.
And he mentioned in OP that there is an issue with latest nightly download.
Try to report directly to Cyanogen or wait for a new build.

I thought the same thing when i was downloading the file i did it twice but didnt make no sence from 59mb and then sometimes a 79mb n looking at the right 119mb no wonder i was updating it on my table n said it was a bad file SMH LOL
Sent from my Transformer Prime CM9 using XDA Premium App

tangiers said:
Brave man to do that. I would expect that a noob could make a reasonable case for arguing that he assumed you'd thoroughly tested the rom before posting links to it.....
Remember also, users from different jurisdictions read these forums. Having a general disclaimer is unlikely to be a bad idea.
IMHO.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
+1 10 char

OP
Thanks for the thread . If someone doesn't like it, then just don't read it.
if you want to add this link, it's the changelog for the prime that includes what has been added to the nightly and what's in the works for the next one.
http://cm-nightlies.appspot.com/?device=tf201
So far what I can see there are the general Cyanogenmod changes, nothing specific for our Prime.

apascual89 said:
OP
Thanks for the thread . If someone doesn't like it, then just don't read it.
if you want to add this link, it's the changelog for the prime that includes what has been added to the nightly and what's in the works for the next one.
http://cm-nightlies.appspot.com/?device=tf201
So far what I can see there are the general Cyanogenmod changes, nothing specific for our Prime.
Click to expand...
Click to collapse
Wow, nice! That's awesome, I never saw that before. Adding now!

The direct DL for the nightly is bad for some reason, but the BT link works just fine and is the full file too.
EDIT: Won't be flashing

Yes, there is something weird with all the direct HTTP download mirrors for the TF201 (yes, all)... as @hakarune said, use the torrent link... it works and so does CM9... been using this since the previous nightly and loving it so far!!! That said, can't wait for more features like notification power widgets...

hakarune said:
The direct DL for the nightly is bad for some reason, but the BT link works just fine and is the full file too.
EDIT: Won't be flashing
Click to expand...
Click to collapse
It seems like the build bot has been having some trouble. The Galaxy Nexus nightlies have been iffy at best lately.

hakarune said:
The direct DL for the nightly is bad for some reason, but the BT link works just fine and is the full file too.
EDIT: Won't be flashing
Click to expand...
Click to collapse
Sorry, do you mean that you won't be flashing because it doesn't interest you, or are you running into an error when flashing? I ask because the file size does not match the size (about 125 MB) does not match what is listed on the CM download page. In the past, I downloaded directly from the URL or within ROM manager, not BT, is it normal for the .zip file to differ in size?
And thanks for pointing out the BT option, I tried searching for a torrent, but always ended up at the CM download page... I didn't realize that the torrent link was right there!
This is why I wish the OP could be collaborative... I can update what other people post, but it would get updated so much more quickly if others could edit the OP. How about I make a google docs file, give the link to people interested in helping, you can edit whenever, and I'll just periodically copy and paste the google doc into the OP?
I don't have time to try this right now, but I can't wait to try the April 3 nightly!

Komodo Rogue said:
Sorry, do you mean that you won't be flashing because it doesn't interest you, or are you running into an error when flashing? I ask because the file size does not match the size (about 125 MB) does not match what is listed on the CM download page. In the past, I downloaded directly from the URL or within ROM manager, not BT, is it normal for the .zip file to differ in size?
Click to expand...
Click to collapse
Download sizes do vary, but not by that much. The size deviation should be somewhere around 2-5mb. That's a guess. If the file size is much different, there is a problem. Basically each nightly is the same with minor changes that shouldn't amount to much more than a couple of megs.
Edit: I should add that, in my experience, if the nightly is bad CWM won't flash it at all.

Fan of Cyan..
Ok so being a Fan of Cyanogenmod, Hell my Evo shift still runs a modded form, Is the 125mb torrent flashable? or not? i would love to get this on my prime, Anyone?

Related

[ROM][CM7] 2.3.7 - PENGUINGURU'S ROM for SGSII AOSP BASED - v0.07b - [9th Dec 2011]

My Second venture into the SGSII Rom world, this is my CM7 Based ROM, i will also have a Stock based ROM
I present Penguinguru's ROM for SGSII CM7 v0.07b​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Please keep in mind this is a HUGE work in progress and im doing this as a side project and NOT a full time development thing
So changes will happen and i will try and get a nice little release cycle going.
This is built from the the awesome work of the Cyanogen Teams Nightlies tree!
Built straight from the GIT CM7.2 RC0 sources and compiled, BIG THANKS TO TeamHacksung!!!! for the hard work in porting to this wonderful device
- CM7 Nightly Based Rom CM7.2.0 RC0
- Added Custom boot animation - [BOOT ANIMATION] The Droids - Thanks Dysgenic
- Changed back to 240Dpi
- Removed some CM apps left ones that i found useful to me (let me know if other should be included.)
- Added some extra APKs from AOSP and Launcher 2, Google Music Player v4.0.9 - UPDATED
- Updated to the recent Nightly trees
- Improved Power Managment
- Altered Mount points for External_SD from EMMC
- Major Performance Tweaks
- UI speed improvements
- Return of the Theme Chooser
- Included the Extra Theme
Click to expand...
Click to collapse
*Things to do*
- Custom Wallpaper
- More Custom apps
- add Dmesg boot screen option
Instructions
REMEMBER THIS IS BASED ON CM7 NIGHTLY TREE at the time of release so all bugs from those come in the lunch-box
But im all for AOSP
So congrats to you all you are gonna be the best testers im sure
As Always with a new ROM Flashed ZIP via CWM 4+ , WIPE EVERTHING Before you start!!
TEST AT YOUR OWN RISK: I Take no reponsibility if you brick your phone or there is a fire or your cat turns demonic and you cant flash you phone again.
Click to expand...
Click to collapse
Download links
Download version 0.07b (Based on CM7.2 RC0)
Download Google APPS (No Longer Included, Flash After Rom)
Download default kernel v0.07b(CM7.2 RC0)
Previous Versions will also be left Here:
Thanks:
Teamhacksung - for the sources used
-atinm
-codeworkx
-coolya
-jt1134
-koush
-pawitp
-tjstyle
-Unhelpful
-GuiPerPT
Cyanogenmod Team - for CM7 Sources
-DvTonder - For the kernel
Click to expand...
Click to collapse
Sources:
https://github.com/CyanogenMod
http://cm-nightlies.appspot.com/?device=galaxys2 CM7 nightlies changlog for SGS2
https://github.com/teamhacksung
https://github/dvtonder
Changlog:
v0.07b
- Added some extra APKs from AOSP and Launcher 2, Google Music Player v4.0.9 - UPDATED
- Updated to the recent Nightly trees
- Improved Power Managment
- Altered Mount points for External_SD from EMMC
- Major Performance Tweaks
- UI speed improvements
Click to expand...
Click to collapse
v0.05b
- Changed back to 240DPI
- Removed some CM apps left ones that i found useful to me (let me know if other should be included.)
- Added some extra APKs
- Updated to the recent Nightly trees
- Return of the Theme Chooser + The Themes
Known Issues:
- DSP and EQ Forceclosing in certain situations using Headphones - Resolved
- External_SD Card Mount point not set correctly. - Resolved[/B]
v0.02b
- CM7 Nightly Based Rom CM7.2.0 RC0!!!!
- Added Custom boot animation - [BOOT ANIMATION] The Droids - Thanks Dysgenic
- Changed to 186Dpi for more screen realestate
- Removed some CM apps left ones that i found useful to me (let me know if other should be included.)
- Added some extra APKs from AOSP and Launcher 2, Google Music Player -
- Updated to the recent Nightly trees
- Return of the Theme Chooser
v0.01A
- CM7 Nightlies base #101
- Custom Boot Animation
- Sparks KERNEL
- DE-OXED
- Removed ADW Launcher, CM Themes and Theme Settings, Other smaller apks
- Added:
- Original Google Based Apps - Launcher2, Music App, Google Videos.
Rom is running very well I must say, very smooth, and nice to have the bloatware removed. Very promising, and has the lovely Aosp clean feel. Also nice to have the Extra Device settings.
Many thanks, and Regards.
tobias_r33per,
If you are using my SPARKZ_2 kernel as part of this ROM you should stop!
The version you have is outdated and no longer supported. Current CM7 source includes several updates subsequent to the kernel version you are using. If you are indeed building from source you should know this already.
Would also have been the decent thing to do to give credit to TeamHacksung for all the work they did in bringing CM7 to this device and myself for the kernel you are using. Especially since you are clearly not in a position to be providing the support for this ROM - I will have to deal with the SPARKZ related questions that will come up (and they will come up, there are bugs in it!).
I caution all who would install this rom - stick with the real CyanogenMod, at least then you get the latest and know what you get.
DvTonder said:
tobias_r33per,
If you are using my SPARKZ_2 kernel as part of this ROM you should stop!
The version you have is outdated and no longer supported. Current CM7 source includes several updates subsequent to the kernel version you are using. If you are indeed building from source you should know this already.
Would also have been the decent thing to do to give credit to TeamHacksung for all the work they did in bringing CM7 to this device and myself for the kernel you are using. Especially since you are clearly not in a position to be providing the support for this ROM - I will have to deal with the SPARKZ related questions that will come up (and they will come up, there are bugs in it!).
I caution all who would install this rom - stick with the real CyanogenMod, at least then you get the latest and know what you get.
Click to expand...
Click to collapse
Thanks for your feedback, i realize that the kernel is outdated, this build was made sometime ago and i know the current build from git are using an updated kernel version for #106 and higher, it was merely included for testing and thus being an alpha build.
Especially since you are clearly not in a position to be providing the support for this ROM
Click to expand...
Click to collapse
This is rather a bold claim to make though, my bad if i dont live up to high standards
I do love your kernel and all the work TeamHacksung have done getting CM to run on this device, i am in full support and donate to the cause.
Builds after this will be based on higher nighties and NOT include the version of kernel in the alpha, i made this ROM NOT to take away from the work of the TeamHacksung team but rather add some more things that I used to make CM7 something for me, i decided to share this with others and will continue to to so as the greatest thing people can have is choice
I would no worry about the support factor mate as the kernel wont be in the next build.
Hi there.
Found a problem, Battery was not taking charge, but battery was Red Hot. A full wipe was made previous to flashing. Never had this problem before and may have been a "One off', but worth mentioning. I have reflashed Oxygen, and charging is fine.
Regards
tobias_r33per said:
This is rather a bold claim to make though, my bad if i dont live up to high standards
Click to expand...
Click to collapse
Let me give an example or two:
In your first post you state you did the following:
- CM7 Nightly Based Rom - To quote you: in the beginning you say: "Built straight from the GIT CM7 sources and compiled from scratch" then, when I point out you are using an outdated kernel, you respond by saying "this build was made sometime ago..." - which is it? Which Nightly is it based on? If properly configured, one can build a completely themed and customized KANG in as little as 7 minutes, why would yours be so outdated?
- Rooted with latest SU and busybox - Why? CM7 is already rooted and both apps are included as part of CM7 already, built from source.
- De-Oxed for Themes - Why? CM7 comes with TMobile Theme Chooser and lots of theses are freely available in the market and on XDA.
- Zip-aligned - Why? This is done automatically by the CM7 Build script already
- Debugging on by default. - why would you do this? From what I can see, none of what you have done changed code.
If you are changing the code, where is your source? CM7 is GPL, and the source must be made available?
From your lists, all of what you did or want to do is either not needed, or can be done as an CWM flashable .zip "add-on" for a real CM7 nightly or a Theme Chooser Theme.
DvTonder said:
Let me give an example or two:
In your first post you state you did the following:
- CM7 Nightly Based Rom - To quote you: in the beginning you say: "Built straight from the GIT CM7 sources and compiled from scratch" then, when I point out you are using an outdated kernel, you respond by saying "this build was made sometime ago..." - which is it? Which Nightly is it based on? If properly configured, one can build a completely themed and customized KANG in as little as 7 minutes, why would yours be so outdated?
- Rooted with latest SU and busybox - Why? CM7 is already rooted and both apps are included as part of CM7 already, built from source.
- De-Oxed for Themes - Why? CM7 comes with TMobile Theme Chooser and lots of theses are freely available in the market and on XDA.
- Zip-aligned - Why? This is done automatically by the CM7 Build script already
- Debugging on by default. - why would you do this? From what I can see, none of what you have done changed code.
If you are changing the code, where is your source? CM7 is GPL, and the source must be made available?
From your lists, all of what you did or want to do is either not needed, or can be done as an CWM flashable .zip "add-on" for a real CM7 nightly or a Theme Chooser Theme.
Click to expand...
Click to collapse
To sum all this up:
1) It is nightly based but on #101 from what i remember
2) NO SOURCE CODE HAS BEEN CHANGED IN THIS VERSION! configs files yes and apks yes and kernel yes
3) I listed those things to help those who read and may not have seen or read or even used CM7, that way they know, people need info
4) It isnt finished i said there is a lot to do in this one, and i dont even know what the state of this rom build may end up being, it was built a while ago but i thought id share what i have done all ready
5) IM LEARNING its taking me a while to get used to this sorta thing, im sorry that im a not "seasoned" or "expert" at this yet and may never be, its a hobby.
6) Do you flame all new devs this way or am i a special case , im not made of time and i do this for a experience and if i could do this on a daily basis or so it would be more up to date
If this sorta thing continues, i will just stop touching the CM7 and stay with my first ROM built from stock modifiction, i must say your not making me feel like i should be doing this. I respect the team and the work but your making out like i am violating your space and NO ONE should touch the stuff.
buzzboy said:
Hi there.
Found a problem, Battery was not taking charge, but battery was Red Hot. A full wipe was made previous to flashing. Never had this problem before and may have been a "One off', but worth mentioning. I have reflashed Oxygen, and charging is fine.
Regards
Click to expand...
Click to collapse
Thanks for this info, interesting, i will see what might be causing this, i have an idea though.
Agreed the comments were heavy handed and unacceptable, and should have been PM'd as apposed to embarrassing the OP.
Everyone starts somewhere.
tobias_r33per said:
To sum all this up:
1) It is nightly based but on #101 from what i remember
2) NO SOURCE CODE HAS BEEN CHANGED IN THIS VERSION! configs files yes and apks yes and kernel yes
3) I listed those things to help those who read and may not have seen or read or even used CM7, that way they know, people need info
4) It isnt finished i said there is a lot to do in this one, and i dont even know what the state of this rom build may end up being, it was built a while ago but i thought id share what i have done all ready
5) IM LEARNING its taking me a while to get used to this sorta thing, im sorry that im a not "seasoned" or "expert" at this yet and may never be, its a hobby.
6) Do you flame all new devs this way or am i a special case , im not made of time and i do this for a experience and if i could do this on a daily basis or so it would be more up to date
If this sorta thing continues, i will just stop touching the CM7 and stay with my first ROM built from stock modifiction, i must say your not making me feel like i should be doing this. I respect the team and the work but your making out like i am violating your space and NO ONE should touch the stuff.
Click to expand...
Click to collapse
It is/was not my intention to flame you nor have I done so.
All I have done was point out originally that you should not be using my kernel with the new nightlies as it is outdated and has known bugs. Your description did not include the version of the CM7 base you are using and still doesn't. I was trying to avoid users with an unknown base of CM7 coming over to start asking questions in either the CM7 Q&A thread or my SPARKZ_2 kernel thread.
I am still a 'new' developer myself, this is certainly not my 'space' and I encourage anyone to take it on as well. It is a fun and rewarding hobby. We all had to start learning somewhere and are still learning every day. The XDA community is there to support and guide you.
I personally would not have started with publishing a full CM7 derivative ROM. There are known issues with both installing and running CM7, including buzzboy's phone heating/battery issue above, that you will now have to provide support for in this thread.
I've been using this rom since last Friday and it working great so far, haven't got problems with charging seem to be working fine.
tobias_r33per I do think you have to continue working on this rom its working great.
people need to start somewhere and I don't agree with DvTonder It can't be perfect the first time, although I do agree that you have report some credits to the
CM7 team and kernel creator.
keep on the good work.
- can you add the theme selector to the next version.
and maybe It would be nice to change the directory name of the external Sd card, I had SuperOSR rom installed and they changed the /mnt/emmc (external SD) location to the one used in the samsung stock /external_sd
it not a big problem but I think /external_sd is easier to locate
gr.
Sigma
Its a cool attempt to modify the CM 7. I like it.
Its quite stable and so far going on well. I know its not much different from CM 7 but still its cool with Siyah kernel.
DvTonder said:
It is/was not my intention to flame you nor have I done so.
All I have done was point out originally that you should not be using my kernel with the new nightlies as it is outdated and has known bugs. Your description did not include the version of the CM7 base you are using and still doesn't. I was trying to avoid users with an unknown base of CM7 coming over to start asking questions in either the CM7 Q&A thread or my SPARKZ_2 kernel thread.
I am still a 'new' developer myself, this is certainly not my 'space' and I encourage anyone to take it on as well. It is a fun and rewarding hobby. We all had to start learning somewhere and are still learning every day. The XDA community is there to support and guide you.
I personally would not have started with publishing a full CM7 derivative ROM. There are known issues with both installing and running CM7, including buzzboy's phone heating/battery issue above, that you will now have to provide support for in this thread.
Click to expand...
Click to collapse
I do see what you are saying, i have added all this now to the OP, CM7 Nightly version and more, and i do thank you for pointing these things out, it has made me think about what i need to do in future, cant imagine what would have happened if i hadnt changed all these things. From now on i will reference everthing and make sure others understand what i am exactly giving them
sigma.nl said:
I've been using this rom since last Friday and it working great so far, haven't got problems with charging seem to be working fine.
tobias_r33per I do think you have to continue working on this rom its working great.
people need to start somewhere and I don't agree with DvTonder It can't be perfect the first time, although I do agree that you have report some credits to the
CM7 team and kernel creator.
keep on the good work.
- can you add the theme selector to the next version.
and maybe It would be nice to change the directory name of the external Sd card, I had SuperOSR rom installed and they changed the /mnt/emmc (external SD) location to the one used in the samsung stock /external_sd
it not a big problem but I think /external_sd is easier to locate
gr.
Sigma
Click to expand...
Click to collapse
Thanks for the feedback, i will continue with it and see where it takes me, however in light of what i need to do this will be a COMPLETE rebuild for the next test release, im glad people are testing it other than myself
As for your externalsd card location, i can look into this as it is something i was interested in myself. time for some hunting.
bluheart said:
Its a cool attempt to modify the CM 7. I like it.
Its quite stable and so far going on well. I know its not much different from CM 7 but still its cool with Siyah kernel.
Click to expand...
Click to collapse
Thanks, im sure it will be better using the newer sources
Like your efforts can you include "theme chooser wallpaper" too? I'm too lazy to d/l it X(
Sent from my GT-I9100 using XDA App
khassanove said:
Like your efforts can you include "theme chooser wallpaper" too? I'm too lazy to d/l it X(
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Are you kidding?
I think I know the answer to that.
Regards
I'm trying too cool things down, but it seems your on fire
Sent from my SGS2
DarkyRom2 KI3
Siyah 2.1.1
Apologies.
But I still know the answer.
buzzboy said:
Apologies.
But I still know the answer.
Click to expand...
Click to collapse
Sent from my SGS2
DarkyRom2 KI3
Siyah 2.1.1

problem on my CM9 from codeworkx

i did search this . no luck .
i`m asking and hope some one know the answer and can help me .
i just flashed last version of codeworkx cm9 . but i don`t have the market app , and i don`t know how to get apps in my phone !
can u please help .
thanks
flash Gapps package included in Misc Download section of Post 1 in the CM9 Development thread. This has been discussed at length.
u mean this ? GoogleMusic_4.1.511.apk
no. it says Gapps 7.1
i don`t find it
No, this is the google music service....
as Braidonh said, flash GApps (the v7.1 zip.) this zip includes the market and a few other google apps.
/rant
if you aren't even able to read a simple Howto, you should firstly stay away of an alpha Rom....
/rant off
Link is in the first post... seriously....
If you can find the "Downloads" section, which I'm sure you are able to, seeing as you said you have the ROM installed... then continue reading. It will say Misc Downloads (Unsupported by us). Under that heading is where you will find the GApps 7.1 package. This is as SIMPLE as I can make it without telling you to put your underwear on first. If you are unable to follow these SIMPLE directions, abandon all hope of flashing CM9, and wait until someone puts it in a food processor and feeds it to you like an infant.
/rant
Your savior is that you didn't post about YouTube.
Braidonh said:
If you can find the "Downloads" section, which I'm sure you are able to, seeing as you said you have the ROM installed... then continue reading. It will say Misc Downloads (Unsupported by us). Under that heading is where you will find the GApps 7.1 package. This is as SIMPLE as I can make it without telling you to put your underwear on first. If you are unable to follow these SIMPLE directions, abandon all hope of flashing CM9, and wait until someone puts it in a food processor and feeds it to you like an infant.
/rant
Your savior is that you didn't post about YouTube.
Click to expand...
Click to collapse
Well I wanted to rant, and make him feel bad about being lazy (or worse), but you already did. So I'll be the food-processor.
CM9 dev thread (don't write in it)
gappsv7.1

[Q] Trouble with market

I am currently using CSROM http://forum.xda-developers.com/showthread.php?t=1846399
Excellent ROM, but when I try to get apps like Maps from the Market it says my phone isn't compatibly.
I have downloaded and installed the apk, but other apps are having the same issue and I would rather of my apps linked to the market for updates etc.
I did not install gapps has Market etc is included in the ROM. Could this be the reason?
Does the gapps zip do more than just install Google applications?
Go back to the ROM's thread and read the last few pages. This has been addressed already. Also make this your standard practice - always go through the thread before asking questions, as it is reasonable to expect others have had the same problem too.
ravilov said:
Go back to the ROM's thread and read the last few pages. This has been addressed already. Also make this your standard practice - always go through the thread before asking questions, as it is reasonable to expect others have had the same problem too.
Click to expand...
Click to collapse
Thank you. I did read back; just wasn't back enough. Thanks again :good:

[ROM][4.4.4][Build9]SlimKat Dec24[Unofficial]

Direct copy from gchild320's Slim Thread:
Lifted this image from GMillz's Flo Thread XD
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER : If you flash a custom kernel please don't post in this thread that things are broken. Things are not broken.
Hey all, here's SlimRom built from source for our i605. Umm, it flies! Obviously in not responsible for anything that happens to you, your, device, or anything else that may go wrong in your life.
I am also not responsible for the work done on this ROM, and so I do not want to take credit. I'm not a part of Slim Team, and am providing this because all I had to do was build a slim device tree (and keep it up to date) for i605...and because I like the ROM!
Download Link: (if it doesn't show up for you, disable ad-blocker, or try a different browser)
FLASH AT YOUR OWN RISK
Current build
12/24
https://www.androidfilehost.com/?fid=95887005526789538
__________________________________________________ ______
4.4 (Beta)
You need to be on the latest cwm or twrp recovery for this.
Previous Builds
http://www.androidfilehost.com/?w=files&flid=16897
Gapps (any 4.4 package should do)
-Description of Gapps packages can be found here: http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4
__________________________________________________ _______
Use newest cwm or twrp
Wipe Data, Cache, Dalvik, (even system if you'd like)
Flash ROM
Flash gapps package
Wipe cache
Reboot
Source
ROM:
https://github.com/SlimRoms
Kernel:
https://github.com/SlimRoms/kernel_samsung_smdk4412
Quick FAQ: (wip)
Q- This ROM won't give root access to my apps?
A- Yes it will, you need to enable it in developer settings for apps/adb.
Q- I click on the download link but there aren't any files for me to download?!
A- Turn off ad-blocker or try a different browser.
Q- Everything is smaller on this ROM than what I'm used to?
A- DPI is set at 245. You can change it in build.prop in your system folder. Make sure you set permissions back once you have messed with the file! 320 should get it back to how you see it on most ROMs with no tweaking. You can also use an app such as ROM toolbox to change it.
Q- What has changed since the last version?
A- Versions are clearly marked, please check slimroms.net for updated changelogs.
Q- GPS issues??
Here you go, GPS fixes that worked for me...<br />
<br />
GPS edits:<br />
Edit the file at /system/etc/gps.conf (I use root explorer). Uncomment these lines by removing the leading #:<br />
NTP_SERVER=north-america.pool.ntp.org<br />
SUPL_HOST=supl.host.com or IP<br />
SUPL_PORT=1234<br />
<br />
Save, and reboot. If you still don't have gps, download a Verizon based touchwiz Rom (I had alliance and used that), reboot into recovery and back up slim kat. Then, wipe and flash the touch wiz Rom. You should notice that your GPS is off even though it's a clean flash and it should be on. Turn on GPS, and get a lock - I used GPS status app so that I could verify the number of satellites that locked. Once you get a solid lock, reboot to recovery immediately while it's locked in. Now restore slim kat, then boot into it and now get a lock<br />
<br />
<br/>
Thanks so much to @gchild320 for all of his help getting me setup to keep this going!!
Special thanks to sbrissen for his t0lte device work, I based my i605 tree off his. Also thanks to prbassplayer, as I'm using his and the rest of slim team's work to bring this to our device.
Slim Thanks
Awesome CM Team- for device, vendor and great dev work
AOKP- Some cherry picks
Google - for providing source
PA & CM - for the inspiration of SlimPIE
Stratosk - for sgs kernels & mako kernel source
DT3CH and Melissapugs- for the boot animation
Eugene - for the speedy kernel source.
TeamWin - for the awesome TWRP recovery
Koush - for CWM
chad0989 - for the Fast Charge patch
KaliAmochz - for big mem patch without breaking video recording
ktoonsez - for ramdisk enabling myfluxi's kernel to work on Slim Bean (sgs2)
intermediaterepresentation - for One X device and vendor files
tortureduck - for providing a server to host
bedalus - for the crespo kernel
Myliferocks10 - for multidpi mod
Roman Nurik - Dash Clock
RaymanFX - nozomi kernel
iBotPeaches - apktool
theos0o - YouTube
franciscofranco - mako kernel source
showp1984 - mako kernel source
motley - mako kernel source
Ezekeel - mako kernel source
Faux123 - mako kernel source
nyt - Slim IRC app
car vs driver - Skyrocket & Hercules kernel
Imoseyon - tuna kernel
Kryten2k35 - Theming help
All our great testers for testing all our builds and providing great feedback.
Awesome! You have your own thread for this now! I will flash and report back my results here in a little bit. Thank you for adopting this project by the way, one of the best ROMs out there, and I appreciate the fact that you're keeping my (almost) two year old device up to date!
Also, side note, update the link to the Slim GApps... It seems to be broken. (Just update it with this one here.)
SonOfUncleSam said:
Awesome! You have your own thread for this now! I will flash and report back my results here in a little bit. Thank you for adopting this project by the way, one of the best ROMs out there, and I appreciate the fact that you're keeping my (almost) two year old device up to date!
Also, side note, update the link to the Slim GApps... It seems to be broken. (Just update it with this one here.)
Click to expand...
Click to collapse
Updated the link, thanks!
Wohoo! Thank you nwh , this is awesome and I will definitely flash and let you know.
Thanks again so much for keeping this project alive for us note2 users. This is by far my favorite ROM for this phone so it means a lot to me to be able to keep running it and getting updates.
---------- Post added at 12:34 PM ---------- Previous post was at 11:59 AM ----------
One suggestion for the op: maybe include a link to the differences between gapps versions? Slims site does not do a good job at all listing the differences between the three gapps packages so this could help us here. I know that's not device specific, but more just general helpful info.
Jarm3r said:
Wohoo! Thank you nwh , this is awesome and I will definitely flash and let you know.
Thanks again so much for keeping this project alive for us note2 users. This is by far my favorite ROM for this phone so it means a lot to me to be able to keep running it and getting updates.
---------- Post added at 12:34 PM ---------- Previous post was at 11:59 AM ----------
One suggestion for the op: maybe include a link to the differences between gapps versions? Slims site does not do a good job at all listing the differences between the three gapps packages so this could help us here. I know that's not device specific, but more just general helpful info.
Click to expand...
Click to collapse
added this link to the op: http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
Straight from Slim so they should be keeping it updated with future releases.
I've been running the ROM for a couple of hours now and everything seems stable and fast (as we all have come to expect from this ROM). Thanks again for all the hard work!
Also, brilliant idea posting the explanation of the GApps... I know someone had previously asked what all three packages included.
It's very rarely I create a post unless it's justified or paying compliment, however: I was running the SkyNote Rom for a few months and when I wiped (several times) and installed your Rom and Gapps I could not access data or even phone service, even after re-installing several times.
I mean NO data or service at all.
I even restored Skynote and another ROM from a TWRP backup and still no service.
To be aware Skynote is a 4.3 ROM.
Could it possibly be the 4.4 Gapps I installed causing the issue?
I'm (for once) bewildered.
ANY help would be MASSIVELY appreciated.
Pikeypete
Pikeypete said:
It's very rarely I create a post unless it's justified or paying compliment, however: I was running the SkyNote Rom for a few months and when I wiped (several times) and installed your Rom and Gapps I could not access data or even phone service, even after re-installing several times.
I mean NO data or service at all.
I even restored Skynote and another ROM from a TWRP backup and still no service.
To be aware Skynote is a 4.3 ROM.
Could it possibly be the 4.4 Gapps I installed causing the issue?
I'm (for once) bewildered.
ANY help would be MASSIVELY appreciated.
Pikeypete
Click to expand...
Click to collapse
This is really weird... I've had radio issues when I tried to install a KitKat ROM, but if i reverted back to a backup I made (4.3 JellyBean for book keeping), it always fixed the problem. My best guess, and I'm no expert, is that some important files got damaged during flashing - maybe files that pertain to the radio? If there are files floating around on here that have JUST the radio, I would try flashing one of those, preferably, the baseband version you had if you knew what it was. Though I have not seen any that have been readily available.
Fortunately/unfortunately, with that said, the only option that I know will fix the issue is doing a full restore to stock via ODIN. I reverted all the way back to the VRALJB stock ODIN image, rooted and ROMed and have had no issues since. This fixed the radio issues that I was having when installing an Android 4.4 ROM... So I'm confident that it will fix your issues. Of course, this is time consuming, and will take a couple of hours.
You can see how to revert back to stock using the files and instructions found in this thread. Someone else may have a [better] solution, but this is what worked for me when I had radio issues.
I will flash the new build tomorrow thanks for taking over this ROM is really great for the past week I been running it
SonOfUncleSam said:
This is really weird... I've had radio issues when I tried to install a KitKat ROM, but if i reverted back to a backup I made (4.3 JellyBean for book keeping), it always fixed the problem. My best guess, and I'm no expert, is that some important files got damaged during flashing - maybe files that pertain to the radio? If there are files floating around on here that have JUST the radio, I would try flashing one of those, preferably, the baseband version you had if you knew what it was. Though I have not seen any that have been readily available.
Fortunately/unfortunately, with that said, the only option that I know will fix the issue is doing a full restore to stock via ODIN. I reverted all the way back to the VRALJB stock ODIN image, rooted and ROMed and have had no issues since. This fixed the radio issues that I was having when installing an Android 4.4 ROM... So I'm confident that it will fix your issues. Of course, this is time consuming, and will take a couple of hours.
You can see how to revert back to stock using the files and instructions found in this thread. Someone else may have a [better] solution, but this is what worked for me when I had radio issues.
Click to expand...
Click to collapse
Firstly, SonOfUncleSam, thank you for your speedy reply and assistance :good:.
I was really trying to avoid restoring to stock (which I had to do) as I REALLY liked the look and feel of the SlimKat.
I Googled SlimKat and I discovered that I'm not alone in regards to SOME people who installed the ROM also faced the problem of having no data or any form of network connection, even though APN's where installed and edited.
If this issue could be fixed I will most definitely be ready to install it again (Actually I'm waiting for you to resolve it :silly
Looking forward to seeing the couple of minor fixes,
Pikeypete.
Commenting on the radio issue: I had a similar thing happen to me on a different KitKat rom (PA), when I flashed it and my baseband said "unknown" and nothing I did could fix it. I tried via recovery flashing new base bands and nothing.
What I eventually wound up doing that did fix it was like sonofunclesam said, restoring to stock, reroot, flash alliance 4.3, Odin mj9 baseband, wipe, flash slimkat.... And then everything was fine. Took forever but it did work.
I don't think this issue has anything to do with slimkat itself, more like its a general note2/KitKat issue.
I resolved the issue, somewhat.
I had to change the preferred network type from LTE to 3G.
I'm on AT&T. 3G isn't anywhere near as fast, however at this point I have the network connected.
I'm sure a few tweaks will get me back up to the maximum speed bracket.
Thank you both for your input :good:
Pikeypete
I agree with Jarm3r... It seems like when everyone WAS making the transition to KK ROMs, it was hit or miss as to who had radio issues. My phone had issues with the radio when my father's phone didn't when I decided to test his. After that, the only logical action (in my mind) was to try and restore everything to stock, using the baseband version he had on his phone. After that, I've had no issues and its been a couple months since I've done that.
And like Jarm3r said, once everything is restored, re-rooted and re-ROMed, you should be good to go. Sometimes it seems like when you re-flash so many times, files can get messed up, and you'll eventually have to do this. (I even had to revert back to stock on my Note 10.1 because it was acting wonky too...)
Is there a way to change per app DPI? I can't seem to find it anywhere.
Instien said:
Is there a way to change per app DPI? I can't seem to find it anywhere.
Click to expand...
Click to collapse
Install Xposed framework and then install the per app DPI module.
Sent from my SCH-I605 using Tapatalk
I love this ROM. The camera works unlike cm11 and pac. And super smooth!
Is there a way to make the volume pop-up always expanded? I can't find a slim setting and the few xposed modules I tried didn't work.
I'd also love a way to have have something like CMs profile feature. Is there a zip or flash or module that would add that?
guardianali said:
I love this ROM. The camera works unlike cm11 and pac. And super smooth!
Is there a way to make the volume pop-up always expanded? I can't find a slim setting and the few xposed modules I tried didn't work.
I'd also love a way to have have something like CMs profile feature. Is there a zip or flash or module that would add that?
Click to expand...
Click to collapse
Settings> sound>volume panel style.
Switch from expandable to expanded.
Been running build7 for a day now with zero issues, thank you @nwh5024 !
guardianali said:
I'd also love a way to have have something like CMs profile feature. Is there a zip or flash or module that would add that?
Click to expand...
Click to collapse
Is that like where you set it to "home" ... "Work" etc... And it changes a bunch of settings like volume and WiFi and stuff like the old blackberries used to do? I would love to have that as well if it is! I currently use tasker to kinda emulate that but its clunky.

[ROM] [Project ] Pure AOSP 5.0.2+Google Updates (1/01/2015)

The idea behind this project is to compile a Pure AOSP ROM. The difference is I have been little by little including and testing new changes and fixes added to the AOSP code from Google that has not yet been tagged or added to the release branch and will most likely be added into a future Lollipop update., hence the reason for 5.0.2_Plus. The only change added that was not committed by Google is that the ZIP can be flashed in TWRP without replacing TWRP with the Stock Recovery and that is it.
There is more coming but would like to first verify my testing on what has been done so far. The idea is to stay ahead of the curve with fixes and updates coming down from Google before they are released. As offered in the development Q&A Thread I started with this idea is that anyone who is able is welcome to jump on and help. All and all is just sifting over the AOSP Master branch adding new commits that have not yet been tagged as part of a release branch. Thought of the idea after reading a statement from Google true or not that allot of bug fixes have already or are in the process of being added into ASOP. These commits all come from the master branch developers do not build from and is more of a staging ground for future releases. A few of these commits are less than a week old. Anyhow so Instead of this being my Rom I would like us to just all have the most updated code base to work with so let me know and will give full permission to the Github organization. We wiil just need to set up separate branches for testing to insure our Master branch is stable at all times so it can be used and trusted by all our devs to use in their Roms. I am sure we can gather a team of testing volunteers. Otherwise this is again 100% AOSP code without any modifications outside what has been committed by Google and planned on keeping it this way. Although I am posting like stated above would not like to think this is my Rom but more for the community in general so our Developers have the latest stable code to work with when creating Roms and am not just posting because as Google has proven with Lollipop the more testers the better as we all have different set-ups and use are devices differently but I also wanted to give the project/idea a bit of attention.
A Few Added Update Examples.
https://github.com/Android-AOSP/And...mmit/a05556633ae5a6d1db164597b93f8b6cbbdf2608
https://github.com/Android-AOSP/And...mmit/e6beb1369165f97a4df24a1d1966c41e392c44e7
https://github.com/Android-AOSP/And...mitM/be42994b5a42914071adddfd5d989950e8e47bd9
https://github.com/Android-AOSP/And...mmit/0c89e1b9395093f71cf73508553d5e4058093ec0
https://github.com/Android-AOSP/And...mmit/4c53a7872b1f37ec184801f16d39584ca3b9bcce
https://github.com/Android-AOSP/And...mmit/9d2f14442f2e1d1507dbdc6cc7b9348513a907f9
https://github.com/Android-AOSP/And...mmit/905c6e72ecdc6e170744649b78e8fbb919f71efd
https://github.com/Android-AOSP/And...mmit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/And...mmit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/Android-AOSP_bionic/commit/eaf5aa7d22bd2f6b2eae4c81a60950f89e2d7df4
https://github.com/Android-AOSP/And...mmit/74574e8aa5a2de32e10364fd2f495023fff2a267
https://github.com/Android-AOSP/Android-AOSP_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
https://github.com/Android-AOSP/Android-AOSP_build/commit/1df3707a04651966ca17796f321d23ab3ed6ed2e
https://github.com/Android-AOSP/And...mmit/6fe9c73738e9da0192971576d120802d4c094556
https://github.com/Android-AOSP/And...mmit/44c1c3235d29095c4d987d19155c7260d1a33e0f
https://github.com/Android-AOSP/And...mmit/33baf53861712c3f84606a017943e36bdc680b50
https://github.com/Android-AOSP/And...mmit/a975a08cfb30ad6b2994647c0c6f09e2abd20e28
https://github.com/Android-AOSP/external_protobuf/commit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/external_protobuf/commit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/frameworks_base/commit/cc50afe3bdcc3adfa0f4121bf461996996e69a3e
https://github.com/Android-AOSP/frameworks_base/commit/1be740dd60f4d95e1f9ac4aac7e4d6148e3b2dd1
https://github.com/Android-AOSP/frameworks_base/commit/1cca2282dc9a3b7ecc08729af201923842ddfc86
https://github.com/Android-AOSP/frameworks_base/commit/7db1192e72b45111556631dba125a635edff3235
https://github.com/Android-AOSP/frameworks_base/commit/b29136581cc3181e59193e0b6448f0c3f5990081
https://github.com/Android-AOSP/build/commit/de655233a4308340fc71490e86fd0f218cc7fec4
https://github.com/Android-AOSP/build/commit/ab6f841841a0930c7e178a949ada39152e24540f
https://github.com/Android-AOSP/hardware_libhardware/commit/9ede7f730bca338cd3ccad8962e253f28ae17976
https://github.com/Android-AOSP/hardware_libhardware/commit/d4f431fec4136f6eeee919ac3190762fba832942
https://github.com/Android-AOSP/hardware_libhardware/commit/898bcd96e3d80e99d9200cceb4af754bae6d5f4a
https://github.com/Android-AOSP/bionic/commit/d90f39af35c1f2a9972198f92e803e3ca73ac910
Downloads
Download Rom
aosp_hammerhead-ota-5.0.2_plus_r4.zip - 191.35 MB
aosp_hammerhead-ota-5.0.2_plus_r3.zip - 191.35 MB
aosp_hammerhead-ota-5.0.2_plus_r2.zip - 191.34 MB
aosp_hammerhead-ota-5.0.2_plus.zip - 191.34 MB
PA-Gapps
http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
So far I have been using the "Mini Modular package" for testing without any issues.
Root
Root is optional but recommend SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053
Have had version 2.37 in storage and had been using without issue but updated to 2,40 with last test without any issues. What can I say Im lazy that way so unless having an issue just used what works but figured most would grab the latest so thought it best to give it a test before posting.
Kernel is also %100 stock but including a shameless plug for my Starship Kernel as in testing have worked well together and is the only other Kernel verified though am sure you should not have any problem with other AOSP/Stock Kernels.
Starship Kernel
Starship-lollipop_Kernel-3.4.36_r1.zip - 7.65 MB
Starship Kernel Source
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/tree/lollipop
As usual I am not responsible for your device and you are using anything posted in this thread at your own Risk.
Is %100 pure AOSP so no screen shots as am sure you are aware what it looks like at this point.
Change Log 5.0.2_plus_r4
Removed the below commit "Add ip6-localhost to /system/etc/hosts."
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
Looks like a few apps are not fans of having an ip6 entry for localhost. Transparent Weather Widget for example can not find the device location with the enty included.
In looking for the cause of the above issue also reverted.
https://github.com/android/platform_frameworks_base/commit/e4ec09da0b4a31e23f1a19bdd1ea99e0f87cadac
Honestly reverted looking for the cause and did not remember to restore once identifying the cause. Overall is an old commit and dont think will make any difference whatsoever or would have been tagged for use in a past release so not going to bother.
Before the ip6-localhost commit issue had been identified by a user from the Nexus 4 version of this project was testing newer commits. The following few had been in testing at the time and included with the N4 Mako build. They are just a few of what was intended but because updating to r4 for the bug fix these are included in the r4 release.
Add missing <string.h> includes.
https://github.com/Android-AOSP/and...mmit/718568d982f92a93da19bfb8d4ea6dd996913e25
Add missing <string.h> includes.
https://github.com/Android-AOSP/and...mmit/8cb6a047d89479e4f65e0bcfa1642b4891463c04
Fix missing parenthesis.
https://github.com/Android-AOSP/android_aosp_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
Remove superfluous OpenSSL include paths.
https://github.com/Android-AOSP/and...mmit/b9e7a844fc751b9fdda7d452dee361f15815199b
Besides this am about %80 done Starship L Rom and have offered to join a development team so lots going on but plan to keep this up and finish my new Starship L rom. Otherwise looking very much foreword to once again working as part of a team as since I started developing 3 years ago these last few month of Nexus ownership has been the first time I have worked alone and so much more prefer having a team to work with and discuss things with. Love my cat but pretty sure he doesn’t understand what I am talking about and my friends although interested are intimidated believing developing is so over their heads they could never do it .
woot woot
Vero good
Why 2014
Good ROM, but since I am a Sprint user, the update-device.zip fix doesn't seem to work on this ROM, nor does the update profile/prl zip fix, which is important for calls.
Like the idea! Only complaint us that you could hide some text like the github picks and downloads under a spoiler
Edit. Oh and first page woot woot!
Sent from my Nexus 5 using XDA Premium 4 mobile app
The only thing bothers me is the aosp dialer icon, so anti-material, can someone solve that out?
Any bugs?
iamterence said:
Good ROM, but since I am a Sprint user, the update-device.zip fix doesn't seem to work on this ROM, nor does the update profile/prl zip fix, which is important for calls.
Click to expand...
Click to collapse
I am on T-Mobile and looks like neither Google or myself had been thinking about Sprint users. Needs to take a look
chairshot215 said:
I am on T-Mobile and looks like neither Google or myself had been thinking about Sprint users. Needs to take a look
Click to expand...
Click to collapse
Much appreciated, good sir. If nothing can be done, all will still be well. Still appreciate your efforts.
iamterence said:
Much appreciated, good sir. If nothing can be done, all will still be well. Still appreciate your efforts.
Click to expand...
Click to collapse
Think if rooted with bussybox installed fix may then work. Otherwise think would need to either build the fix in before compiling or build non block based and add files into the zip. Took a quick look and the fix I downloaded called on bussybox in the update-script when flashing so installing bussybox may fix the sprint fix, lol. Otherwise does not look like a hard fix taking a quick look at cm12. Have a meeting at 1:00 and look into some time after.
Any other download mirror ?
It is hardly possible for me to download the rom from dev-host
hunzhang said:
It is hardly possible for me to download the rom from dev-host
Click to expand...
Click to collapse
?????????
chairshot215 said:
Think if rooted with bussybox installed fix may then work. Otherwise think would need to either build the fix in before compiling or build non block based and add files into the zip. Took a quick look and the fix I downloaded called on bussybox in the update-script when flashing so installing bussybox may fix the sprint fix, lol. Otherwise does not look like a hard fix taking a quick look at cm12. Have a meeting at 1:00 and look into some time after.
Click to expand...
Click to collapse
Forgive my noobness, as I'm usually on point with this stuff, but how can I root WITH busybox? Would I need to boot up and then download the app from the store? Because if so, I can't get past the setup screen without constant update device FC's.
Now, what IS interesting is that if I just flash the ROM and update-device.zip, o don't get the FCs. But as soon as I flash gapps, that's when things start to head south.
iamterence said:
Forgive my noobness, as I'm usually on point with this stuff, but how can I root WITH busybox? Would I need to boot up and then download the app from the store? Because if so, I can't get past the setup screen without constant update device FC's.
Now, what IS interesting is that if I just flash the ROM and update-device.zip, o don't get the FCs. But as soon as I flash gapps, that's when things start to head south.
Click to expand...
Click to collapse
Sorry maybe bad word placement on my part but had meant root the Rom and then install busybox which requires root. You should be able to download SuperSU and then flash it in recovery. Once SuperSU is installed can download busybox installer from playstore.
This is the version of SuperSU I have used the last few builds.
https://www.dropbox.com/s/1y5m5vvtp55o4f0/BETA-SuperSU-v2.44.zip?dl=0
Still may be hard if you are having FC issues on setup. I am honestly not an expert but would not think being on Sprint would cause FC issues but again I don’t really know. If you are experiencing FC issues would try a full wipe including data if not done so previously and install again. Not sure its the case but I first tried a dirty flash from 5.0 stock to an AOSP build and all my Google Apps which I believe set-up wizard is included but was OK for me would not work, Not the best solution but ended up un-installing and reinstalling all my Google Apps. After that everything was OK. Think the issue was caused by having flashed different versions of the Google Apps that did not vibe with the updates from the play store. After I dirty flashed again from 5.01 to 5.02 using same version of Gapps and did not have any issues. Not saying is the case but not doing a data wipe can cause some strange bugs not always seeming to be related to the bugs experienced. I once had an issue back in the days og GB that my wifi had stopped working. Had been on forums and bugging out for a few days and then for some unrelated reason wiped the MMS app data in application settings and performed a reboot. First thing I noticed was wifi was working. How bad data from the MMS app could have broke wifi is still an unsolved mystery but just to be sure restored a Nandroid with the bad wifi twice and was able to reproduce the fix both times by wiping MMS data.
Otherwise let me know if anyone else has experienced a FC during set-up but only if you have wiped the data partition. I have otherwise flashed about 15 times so far and have yet seen an app FC on me.
kowalsfee said:
The only thing bothers me is the aosp dialer icon, so anti-material, can someone solve that out?
Click to expand...
Click to collapse
Yeah not all of AOSP is Material. I myself after flashing download a root file explorer and remove the calendar, voice dialler, music and MSS apk's and then download Google Calender and the new Google Messenger apps from the play store. I also install the Google Calender and have been using Google Inbox in place of Gmail. Otherwise not much else from Google as I also have an N7 and N9 so in general keep the phone slim and load up the now N9. Was not a fan at first but now a days can no longer use the N7. Only thing about the N9 that still bugs me is they copied Apple with the 4:3 aspect ratio. Is awesome for old TV shows on Netflix but all others pretty much take the same space they would have on the N7 making the larger screen pretty much null and void. Otherwise had been pretty disappointed at first but has grown on me big time.
Added a bunch more updates. Still working on a fix for sprint users but have a good idea what needs to be done.
Also had added from Google a record bug report option with power off seems I forgot to remove before building but all it does is dump a bug-report in storage. Has no other effect. Otherwise smooth a butter and bug free.
Any chance for a Mako port? I have a Nexus 5 myself, but someone I know has a nexus 4 that's acting up (SoD) and so i thought that this might help them out.
I just flashed over to this ROM from stock 5.0.1 I am hoping that this build will fix the memory leak I've had on the official build. So far everything seems to work well except for the security settings. Anytime I try to open it settings simply force closes. Does anyone else have this issue? I usually use smart lock so I am sad to see this broken. I have a unlocked nexus 5 running on AT&T and I did a full wipe before flashing. I also flashed the recommended GApps package. Thanks in advance
Yeah thats my bad uploaded the wrong .zip including a stock file experementing for Sprint Users. Will recompile and post correct build. Everything else should be the same so once fix is posted should be ok to just wipe system & cache before install. Just need to also reflash same gapps package as before.
Also going to post manifest so can build for all Nexus devices. Can also build it special if needed. If you guys are seeing improvments with the Updates let me know and can start posting builds for all Nexus devices. I only have the 7 (2013), 9 and 5 for testing. I see a few big improvmets but curious what others think before starting to build for every Nexus. Know a few apps like messaging are still not material and was surprised to see old school Music first time building pure AOSP but wanted purity so have laft those things be.
Is r2 the release build with the Sprint fixes?

Categories

Resources