Got bored again, this time I merged my device tree and fixes into CM7 Gingerbread ROM is built from the newest CM7 source code, and has been merged with the majority of my device specific fixes from previous ROMs. I love open source, so of course source code is available for everything, here (ROM), here (kernel), and here (initramfs). If you would like to follow the changes I make, check my github rss feed here.
*** WORKING ***
RIL (calls/sms/3g data)
WiFi
GPS
sdcard and USB mass storage
rotation and proximity sensors
screen on/off animation
haptic feedback
*** NOT WORKING ***
Camera/Camcorder
MMS
BT
most video codecs - Youtube playback (LQ & HQ) is broken for example - youtube does work from a browser if you use a desktop user-agent
Voodoo lagfix conversions
There are still plenty of bugs! and there likely will be until we have a true GB leak or official release to work off of.
PLEASE READ
It is considerably difficult for me to stumble upon every issue out there, and even more difficult to narrow these issues down, let alone fix them. That said, PLEASE do not clutter this thread with "thank you" or "X/Y/Z doesn't work" or "I'd love to flash this if..." type posts. I APPRECIATE THE THANKS AND THE FEEDBACK!!! Don't get me wrong. But these posts are not at all helpful in moving this ROM forward, and simply add more clutter to the forum. If you make such a post, don't expect a response.
If you experience a bug, PLEASE GET LOGS! I can't fix something simply by knowing that it does not work. A bug report without significant details is a useless post, it just is what it is. Logs help identify the code affected, and thereby help facilitate the fixes that we all love. PLEASE share your issues if you can provide helpful data in fixing them
THANKS FOR READING
The ROM package currently includes the base CM7 ROM, and a compatible kernel. Flash gapps from the package linked below. DO NOT FLASH ANY OTHER GAPPS OR KERNEL PACKAGES! The ROM package uses edify scripting, so it is flashable with any iteration of ClockworkMod recovery.
ALSO: devs and noobs alike please take notice : this ROM uses ClockworkMod recovery 3.x. I will no longer be supporting older recoveries!
Much thanks to the EpicCM and teamhacksung folks for code and ideas, and of course props to the CM team for all they do, it's their ROM after all.
If you appreciate the time and effort I have put into this ROM please click the "Thanks" or "Donate" buttons. Either one is fine by me
***** Update 4/26 - ALPHA2 *****
fixed USB mass storage
fixed haptic feedback
fixed TiBu 'whoami' bug
update to 3.x ClockworkMod recovery
sync'd with latest CM code
updated to latest Market
stubbed the camera (yes, I know it takes pictures of nothing but a green android )
** package still includes gapps and kernel **
** changed to new kernel that can be used with BOTH rfs AND ext4 - but it does not include the Voodoo lagfix code, so no conversions! **
** Make sure to wipe data even if coming from the previous alpha! **
***** Update 5/11 - ALPHA3 *****
updated to latest CM7 code (7.0.3)
enabled recent CM code to prevent "ring only once" bug (lightly tested)
made one of my sms hacks "optional" for easy editing by the mesmerize/showcase users (simply remove "ro.sms.padding=1" from build.prop to fix sms on these devices)
fixed some memory settings in kernel - should fix the lag experienced when using previous versions
added other tweaks to kernel for speed improvement (increased sdcard readahead cache/lowmemkiller/etc)
included punk-kaos' recent camera changes into kernel (cam not working, but getting there)
unstubbed camera (no more pics of a green android )
cleaned up my build tree a bit for a smaller download for people building themselves
removed gapps from ROM package, download from link below (kernel still included in ROM package)
ROM package will no longer flash a recovery
switched to bmlwrite for flashing kernel (screen will no longer wig out during kernel flashes)
Instructions:
flash with Clockwordmod recovery
flash ROM first then flash gapps package
WIPE DATA! if coming from ANY other ROM
Don't worry about disabling lagfix or any of that nonsense, ROM will work whether you are using ext4 or rfs
ALPHA3
http://www.mediafire.com/?ziawa7ot8dhdq4k
GAPPS
http://www.mediafire.com/?ogylu5w024148lt
Enjoy and remember: If your phone breaks after flashing, YOU broke it! Not ME!
You work pretty quickly for someone who gets bored.
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future
dw77x said:
This may peg my level of knowledge but here goes. . .What logs would be most beneficial? Assuming alogcat is the standard method, there are a lot of different options of logs in there. Any specific ones that would be the most helpful in tracking down a bug?
Not trying to clutter, hopefully avoiding more in the future
Click to expand...
Click to collapse
any random bugs can usually be picked up from the main log. anything having to do with the radio (call issues/sms issues/etc) need the radio specific log
I'm not familiar with alogcat (market app right?), but the logs can be dumped using adb from a pc. ex:
adb logcat > logcat.txt
will dump the main log
adb logcat -b radio > radio.txt
will dump the radio log
thank you for your concern
Hey JT, I was talking to you on twitter today (@ScottColeBCS). I sent my email addy, I don't know if you got it. Let me know if you figure out a way for me to do that for you. Thanks Bro.
EDIT: Nevermind bro. I'm stupid. I just checked my email and saw that you sent the info I needed. Be expecting it.
I need to clean my keyboard...great job jt!!
Sent from my SCH-I500 using XDA Premium App
Thank you JT. You are a boon to this community. Have a beer on me.
Thanks Jt....good stuff
Sent from my SCH-I500 using Tapatalk
Sweet. So what are the chances this will bebe compatible with the Mesmerize eventually? I assume it is not currently.
Sent from my MIUI SCH-i500
What's the difference between this and the one you released on Twitter last night?
Hey JT, I know there are many thread junkies (like myself) who are constantly checking for bug fixes and updates. I also read in the OP that you said there will plenty of bugs still until we get an official leak. Does this mean that with what you have available to you at the moment the functionality will remain as is, or are you still plugging away at some of these issues? I ask this simply to see if we should be checking for updates. Not complaining one bit! I love this rom so far. Thanks a ton!!
running great
Sent from my SCH-I500 using XDA App
kidserious said:
Hey JT, I know there are many thread junkies (like myself) who are constantly checking for bug fixes and updates. I also read in the OP that you said there will plenty of bugs still until we get an official leak. Does this mean that with what you have available to you at the moment the functionality will remain as is, or are you still plugging away at some of these issues? I ask this simply to see if we should be checking for updates. Not complaining one bit! I love this rom so far. Thanks a ton!!
Click to expand...
Click to collapse
I will still make do with what we have. As far as what that entails, who knows. One thing I'm relatively sure of is the fate of the camera. It's likely to remain non-functional until we have a GB base to work with.
You are the man, man! Thank you so much that you do for us. You guys are awesome! Thank you again!
Sent from my SCH-I500 using XDA Premium App
jt1134 said:
I will still make do with what we have. As far as what that entails, who knows. One thing I'm relatively sure of is the fate of the camera. It's likely to remain non-functional until we have a GB base to work with.
Click to expand...
Click to collapse
Ok, Well I will take that as there is a definite possibility you will be able to fix some of the non-camera bugs. It lets me know that fixes for these issues are not out of the realm of possibility with current sources. JT, your new name is Mr. Fascinate (with a thunderbolt) Lol. Keep doing what you do brother, you're making a lot of people happy.
Did Punk.kaos stop working on CM7 too? If not, why don't you guy help each other?
What will be different between This rom and the Kaoscinate?
Sent from my SCH-I500 using XDA App
deaffob said:
Did Punk.kaos stop working on CM7 too? If not, why don't you guy help each other?
Click to expand...
Click to collapse
Apparently kaos has been MIA for quite a while now.
kallell said:
Apparently kaos has been MIA for quite a while now.
Click to expand...
Click to collapse
maybe he just likes the thunderbolt people better
Works damn good for an alpha.
Related
This thread is now for bug reports/development only. Do not post in this thread any more until you have fully read the first four posts of this thread, and the first two posts of the Q&A Thread. If you post in this thread and it is clear that you have not read the posts indicated above, your post will be reported. For other discussion and "Is this a bug?" type questions, go to the Q&A Thread
Heeeeere we go! As LinuxBozo, one of the most talented developers in the Infuse community said, "Welcome to a new and sick, twisted world!"
Over in the Infuse community, we had an oddball device that had little in common with anything else. As a result, it was not easy to port ROMs from the I9000/Captivate. However, after LOTS of work, LinuxBozo pulled it off and came up with an automatic porting package that could get most I9000/Captivate ROMs running on the Infuse. As a result, it opened the Infuse community up to a massive variety of ROMs.
For the month since the I777 came out, people keep asking about I9100 ROMs. In general, the answer has been, "It should be possible, but no one other than designgears has done it yet." - I didn't have the time as I had too much kernel work to do. However, as the kernel is at a fairly mature and stable state, when someone asked for SensatioN to be ported, I figured it was time for a challenge.
I was successful, but encountered a few glitches. Tethering was broken, fortunately the Infuse community had the same issue and the same fix worked. Mic in calls was broken, just like CM7 - I finally got atinm's list of the blobs to swap out. As a result, nearly all of the challenges in porting an I9100 ROM to the I777 have been identified.
This is a package that should automatically port most I9100 ROMs to the I777. It has been tested by myself as follows:
SensatioN 1.8 by Crysis21 has been manually "Hellraised", and was the basis on which this package was developed. Do note that the author of this ROM tends to be unresponsive to porters. I asked for permission to release a ported ROM but never heard back.
VillainROM 3.0 was the first ROM to be tested with the attached package - it seems to work, if there are any problems, it is likely because I missed something in the permissions settings of the updater script. - Also, I have tested JKay's Deluxe Themes on VillainROM successfully - his thread is at http://forum.xda-developers.com/showthread.php?t=1154278 - You need to use the XXKI3 theme packages.
In general, XXKI3-based ROMs work. XXKI4-based ROMs may have issues with WiFi (see Known Issues below). I am working on compiling a more complete list in the Q&A Thread.
Please don't report bugs with ROMs to the upstream author of the ROM in the event that the bug was caused by Hellraising - unfortunately, it is going to be very difficult to identify when Hellraising caused a bug and when the ROM itself has a bug.
Instructions for the package:
Download an I9100 ROM to be Hellraised - must be CWM-flashable Gingerbread (ICS will NOT happen until after kernel source code becomes available, and if you spam me with 10000 "did you see this" links when it does I'll just go watch some TV. You have been warned.), and must be Samsung-derived (not CM7/MIUI/AOSP-based), ROMs distributed as Odin .tar files like Litening won't work. (I've tried...)
Download the package above
Unzip the ROM, check to make sure it does not have bootloaders. If it has Sbl.bin or param.lfs in it, RUN AWAY. No ROM developer should EVER include a bootloader without explicit warnings of this, if a ROM includes a bootloader it's a sign that it'll be **** in almost all cases. Similarly, param.lfs corruption can lead to a device that won't boot and I believe it can even break download mode. ROMs shouldn't be messing with this either without warning users.
Once you've done your safety check, put the ROM zip and the Hellraiser zip onto your SD card
Enter CWM
You should probably do a Nandroid backup here...
Wipe Data/Factory Reset - Some ROMs write apps to /data and you'll lose these if you wipe afterwards
Flash the ROM, DO NOT REBOOT, STAY IN CWM
Flash the Hellraiser package
Reboot and enjoy!
Known issues:
NFC files are included, but enabling NFC requires smali modifications to Settings.apk on some ROMs. (Starting to look like this is only for I777 stock-derived ROMs - VillainROM doesn't actually need any smali.)
Touching an NFC tag containing NDEF data will cause the NFC service to crash due to being unable to obtain STOP_APP_SWITCH permissions
Wifi tethering settings are not persistent and keep resetting themselves (At least on SensatioN and VillainROM) - Workaround for now: Enable tethering, THEN set the SSID and password, OR see http://forum.xda-developers.com/showthread.php?t=1335377&page=24
When initially setting up the ROM, it claims that network time is not available, and takes you to Settings - where you can check it to enable it and it works fine... Infuse Hellraiser had the same issue. Happens only once per flash so it's a very low priority.
When flashing other ROMs that do device compatibility checks (such as CM7), they will think you have an I9100 instead of I777. You need to flash an I777 ROM first.
Download links have been moved to the ChangeLog post (Post #2 below)!
Alpha 0.3.1 Release, 12/3/2011:
Download: http://www.multiupload.com/NUV8KDF9OZ or http://dev-host.org/4up if MultiUpload never comes back
Changes:
Only one - actually include Daily Driver 12/1/2011. People who flashed 0.3.0 only need to reflash Daily Driver from my kernel thread, no need for a full flash of Hellraiser.
Alpha 0.3.0 Release, 12/1/2011:
Download: PULLED, BAD RELEASE: Use 0.3.1 instead. If you already flashed 0.3.0, flash the 12/1 release of Daily Driver
Changes:
Update to some random kernel pulled from the wrong location on my hard drive
Overwrite /system/etc/apns-conf.xml with a "known good" one
Overwrite the CSC with a "known good" one
Home button haptic fix, courtesy of LinuxBozo of Infuse Hellraiser. Thanks to amtrakcn for pointing out that LinuxBozo's fix works on our device
Alpha 0.2.2 Release, 11/10/2011:
Download: http://www.multiupload.com/C1W5S6XW0R
Changes: Update to Daily Driver 11/10/2011 kernel (disables autoroot which broke root for a bunch of people), tiny installer script cleanups.
If root is working well for you, it is not worth flashing this
If root is broken for you, I recommend installing Daily Driver 11/10 and flashing ChainsDD's latest su package (linked from the DD thread's first post now). If you flash this it will remain broken, this only fixes new installs
Alpha 0.2.1 Release, 11/08/2011:
Download http://www.multiupload.com/ORQESFHVBT
Changes: Only one, replace Nfc.apk with the correct one. Fixes NFC service force closes.
Alpha 0.2 Release, 11/07/2011:
Download - PULLED due to excessive fail. Use 0.2.1 instead!
Changes:
Should now flash without the mount workaround trick after ROMs that unmount /system
Added NFC files from the I777 and one permissions XML - These combined with a small mod to Settings.apk will allow NFC to work. Will post details for ROM devs on making these mods soon. NOTE: Right now this only supports reading tags! Google Wallet support requires a LOT more work, if even possible! (Edit: I'm fairly certain it'll only be possible in CM7 - but I think I also know what's needed for the CM7 guys to get the rest of the way there.
Initial release, 11/06/2011:
Version - Alpha 0.1
Download - http://www.multiupload.com/9RJKKSBFZ0
How it works
Here's the details of how this package works.
1) This package replaces the modem with a known good I777 modem
2) It also replaces the kernel with an I777 kernel (Right now, Daily Driver 11/03 release) - This is half of the keymap fix. Also, DD 11/3 contains a fix that allows wifi tethering to work on both I777-derived ROMs and I9100-derived ROMs
3) It replaces two of the keymap files in /system/usr/keylayout/ - see http://forum.xda-developers.com/showthread.php?t=1313050&page=56 for details - thanks to MikeyMike01 and Dungeon47 for this one
4) It replaces most of the audio library files to fix the issue with outgoing mic audio in calls - this is the same fix used by Cyanogenmod 7 - see https://github.com/koush/proprietar...12f711197665edeb28522386a77a62da24bab#diff-28 for details, thank atinm for this one
Attached:
Hacked settings APK for VillainROM 3.0 - This, along with Alpha 0.2.1, should allow you to turn on NFC. May work on other XXKI3-based ROMs
For ROM Authors:
To get NFC to show in Settings, baksmali the Settings APK and open WirelessSettings.smali
Look for the line below:
Code:
invoke-static {p0}, Landroid/nfc/NfcAdapter;->getDefaultAdapter(Landroid/content/Context;)Landroid/nfc/NfcAdapter;
Delete the next two instances of lines that contain the word removePreference
NFC should then show in Wireless settings
Great work! I can't wait to try this out when I have some free time.
well aren't you awesome bro. Thanks a lot. This opens the door to a lot of good things.
this looks awesome i have to find a rom i want to try from their forums though since lite'ening doesnt work
Dude you freaking rock! Thanks so much for this! What is your donate link?
Sent from my SAMSUNG-SGH-I777 using xda premium
jgrimberg1979 said:
What is your donate link?
Click to expand...
Click to collapse
Under his Thanks Meter.
THANKS!!!
about to test it out with the sensation rom! Really appreciate the effort you have been putting in lately!
Entropy
What about Roms that have a different version of cwm recovery, for ex some of them have 4.x cmwr. Does your kernal that you including relash cwr 5.x?
Sent from my SAMSUNG-SGH-I777 using xda premium
Awesome, just awesome entropy
Let the flashing and testing begin! You are a genius sir.
Sent from my SAMSUNG-SGH-I777 using XDA App
jgrimberg1979 said:
Entropy
What about Roms that have a different version of cwm recovery, for ex some of them have 4.x cmwr. Does your kernal that you including relash cwr 5.x?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
CWM is in the kernel, and this replaces the kernel.
Entropy512 said:
CWM is in the kernel, and this replaces the kernel.
Click to expand...
Click to collapse
Awesome, what would be some of the reason why this would not work with some roms, since the package addresses most of the differences between the two phones? Is there something we should look for besides bootloader, that may stick out as a possible incompatibility?
Sent from my SAMSUNG-SGH-I777 using xda premium
jgrimberg1979 said:
Awesome, what would be some of the reason why this would not work with some roms, since the package addresses most of the differences between the two phones? Is there something we should look for besides bootloader, that may stick out as a possible incompatibility?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Thank you Entropy, can I use this with i9100 MIUI rom as well?
Sent from my SGH-I777 using xda premium
Entropy512 said:
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Click to expand...
Click to collapse
Home button is not working. I've went and flashed sensation twice, following your steps of course. Did you have the same issue?
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Home button is not working. I've went and flashed sensation twice, following your steps of course. Did you have the same issue?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
You need to map the keys correctly...
Sent from my GT-I9100 using xda premium
Entropy512 said:
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Click to expand...
Click to collapse
Still not workin
Edit; to clarify audio issue on the sensation rom is still there
Sent from my GT-I9100 using xda premium
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
WANTED: Users to port SGS roms to the 4.0. You will need to know how to complete a full restore if something goes wrong, but that's it. I cannot go through the forums searching for good SGS roms, as I have several threads to manage, and a rom to work on. The steps are easy for you though, and if you port a rom I will add it in the OP.
First of all, I want to say that I take NO credit on any of these roms. All I did was port them over and add speed tweaks, or added ones that users have ported. If the rom creators or mods have any issue whatsoever with this thread, I will happily take it down, even though I think it would be a large contribution to the 4.0 community. I will continue to update this forum with info as I go along.
I, after a fortunate afternoon of boredom, have managed to successfully begin porting I9000 roms to our devices! Fortunately, they are similar enough that it boots without any modifications. I will put up here any ports that I make, and any that the users create. Note that these WILL NOT BE UPDATED! These are one-time ports, to be used and improved upon by the community. Anything that is broken now will stay broken, unless a user decides to fix/update it, then I will include it in the OP.
What *should* work in all ported roms:
wifi
GPS
home buttons
everything else
What will probably *not* work on ported roms:
Bluetooth
Camera
backlight on buttons
Ported roms:
~GamerzRom odexed V11-~
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1656081
Added:
V6 supercharger, and build.prop tweaks from it.
init.d tweaks from my rom
ext4 filesystem
Advanced mount options
Auto zipalign and Database optimize
Removed apps that do not work on our Player (such as the Dialer)
Download:http://www.mediafire.com/download.php?ctuu2w295w2xlk6
~Saurom~
Original thread:http://forum.xda-developers.com/showthread.php?t=1388342
Ported download link:http://www.mediafire.com/download.php?csua40hkg1r3m86
~JellyBeanRom~
Original thread: http://forum.xda-developers.com/showthread.php?t=1260709&highlight=gb
Ported download link:http://www.mediafire.com/download.php?mgec81f3ifck221
~Ario Rom (ported by ChaosChris)~
Ported thread link : http://forum.xda-developers.com/showthread.php?p=29950015#post29950015
Original thread: http://forum.xda-developers.com/showthread.php?t=1536558
To use these Roms:
You MUST use a Gplayer kernel! GT-I9000 kernels will not boot!
A full wipe may be necessary with some roms if you encounter issues.
Converting (for porters)
Steps:
1. Download wanted rom (must be GB)
2.Move the zip to the internal sdcard
3.Reboot into recovery
4.Flash zip, then boot into download mode
5.Flash a SGP kernel
6. apply my mod pack to the rom, by either copying/pasting the system directory over the SGS rom's system directory, or by pushing it via adb, (eg. adb push /path/to/modpack /system).
7. Profit!
NOTE: after applying this, porters may want to remove non-working packages such as the dialer and mms, as they may cause issues with the end result if they are kept in. Do not delete phone.apk though!! This is required for the camera and some other things, and breaks stuff on certain roms. You have been warned.
NOTE: If you use this modpack, please give me credit, and link back to this thread so that more people can use it. Also, you should probably link back to the ported rom's thread as well, to avoid "ripping off" those devs.
Modpack:
Changelog
V1-
Preliminary release
Fixes wifi and GPS
Includes v6 supercharger and init.d tweaks
V2-
fixed vold.fstab so sdcard is mounted properly.
Download:
ModpackV1:
http://www.mediafire.com/download.php?diaq6im4i18ktf7
NOTE:Note that this is preliminary. It fixes everything listed, and attempts to fix some broken things. Your mileage may vary. This is not a cwm flashable zip! you much extract and adb push this over the existing system directory. This is mainly intended for porters, so users apply at your own risk. This will work, but is a very early release.
Modpack V2 (thanks to ChaosChris):
https://docs.google.com/open?id=0B9OVlH2Pl76DZk5Pa3lJVXlrYzA
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
iJimaniac said:
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, it says that because it includes semaphore's kernel, which raises the max rom to 380, which we could do on our kernel's, but apparently that breaks a lot of stuff if you go much further then 350 (according to klin).
is the wifi fixed in your port or do we have to do your fix after flashing?
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
check over in the operation: ics for the 4.0 thread I believe they are already attemping to use the cm7 kernel to boot a cm9.
daniel644 said:
is the wifi fixed in your port or do we have to do your fix after flashing?
Click to expand...
Click to collapse
Yeah, it is fixed before you flash. Once I manage to iron out a few more bugs, I will probably release a "conversion pack" that fixes all the issues. I already have one that fixes wifi and gps, but bluetooth and camera have me stumped, and I do not want to replace the entire hw/lib folder, because some of these roms have lib optimizations, but I may have to.
Sent from my GT-I9000 using xda app-developers app
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that zaclimon has tried it, and he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable. I also believe that he said the issues may have been rom based, so here it goes, and wish me luck.
Sent from my GT-I9000 using xda app-developers app
hanthesolo said:
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that daniel has tried it, abd he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
zaclimon said:
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
Click to expand...
Click to collapse
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course . A lot farther out there, but maybe I can use a SGP5.0 kernel to get it booting. A LOT less likely, but hey, i'm experimenting .
EDIT: I cannot try ICS, since I need to reboot into recovery a second time, and I cannot do that, as I have the intl bootloader on my US device, and it would require it to be booting first.
hanthesolo said:
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course .
Click to expand...
Click to collapse
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
zaclimon said:
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
Click to expand...
Click to collapse
Well, thet camera shows a preview, but fails when a pic is taken, for some reason. Bluetooth does turn on, but is not seen by any other devices, and cannot scan for others either. I did do a little tweaking with Gamerz, so it will be even faster than it was already, which is pretty blazing! I have 2 more that I can put up (I have a preliminary package that I just adb push over the system files that works for now). I have also gotten the camera apk onto my rom, and it works really well! It doesn't take 5 MP pics, or record 720p video (which may be because I am using Terrasilent, which reduces the amount of Vram the system can have), but tap to autofocus and everything else works pretty well. I have a sneaking suspicion that the camera is soft limited, not hard-limited.
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
zaclimon said:
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
Click to expand...
Click to collapse
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
hanthesolo said:
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
Click to expand...
Click to collapse
Here's the vold.fstab if you need it
Okay, it seems that the zip hosed my partitions (converted them to yaffs2 and mtd), so I am going to perform a full restore, and just keep porting GB roms. As soon as you can get the usb gadget driver working, zaclimon, I guess I can keep working on it, but for now I will just keep to GB.
Two more roms up! I will probably not port any other unless I see an especially good one, but I will put up my mod pack tomorrow.
has anyone found out if the ported roms enable tv out or has someone found out if tv out support is in the i9000 kernal?
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
iJimaniac said:
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
Click to expand...
Click to collapse
what hardware does the galaxy s i9000 have that allows for tv out? I thought the galaxy s i9000 and the galaxy player 4.0 had the same gpu?
This is simply AOSP compiled from source. I am using the binaries provided by Google and the stock kernel provided by Google.
Instructions.
1. Download ROM- https://www.androidfilehost.com/?fid=95784891001615065
2. Downloas gapps- http://d-h.st/jzr
3. Reboot recovery
4. Wipe data and cache.
5. Flash ROM and gapps
6. Reboot
source for device tree
Github.com/papi92/android_device_moto_shamu
Issues
Video playback
Recovery is overwritten (I know the fix)
Feel free to submit fixes or just compile with your fixes.
Thanks!
papi92 said:
This is simply AOSP compiled from source. I am using the binaries provided by Google and the stock kernel provided by Google.
Instructions.
1. Download ROM- https://docs.google.com/a/droid-hive.com/file/d/0B0yE3jDMsld7dWZPck5sRXU1T28/edit?usp=docslist_api
2. Downloas gapps- http://d-h.st/jzr
3. Reboot recovery
4. Wipe data and cache.
5. Flash ROM and gapps
6. Reboot
source for device tree
Github.com/papi92/android_device_moto_shamu
Issues
Video playback
Recovery is overwritten (I know the fix)
Feel free to submit fixes or just compile with your fixes.
Click to expand...
Click to collapse
Your download is permission-only, FYI.
Let me change it
https://www.androidfilehost.com/?fid=95784891001615065
Added to Dropbox. I'm mobile so its hard to upload. Mirrors would help. I think I'm missing binaries (not on googles site) I'll look later. Would love to make this a community effort. AOSP is a lot faster then stock.
I ran a build myself. Haven't had the chance to see what may be missing. Would you mind sharing the fix for recovery being overwritten?
papi92 said:
Added to Dropbox. I'm mobile so its hard to upload. Mirrors would help. I think I'm missing binaries (not on googles site) I'll look later. Would love to make this a community effort. AOSP is a lot faster then stock.
Click to expand...
Click to collapse
Encryption enabled by default?
Yes. And Milly7 its in BoardConfig.mk I can do it later today.
Added an androidfilehost link.
This may be a dumb question but how different is this from the stock lolipop on the Nexus 6? I've used AOSP before but it's been a while.
You'll lose all the proprietary google apps as the default options. But you can download them from the play store. I am noticing a huge difference in performance tho. I'm hoping to fix the video playback soon. I want to just add a battery percentage option tho then I'll just optimize without touching hardware or kernel.
Would someone mind uploading the gallery.apk from this build? Currently using an older one which force closes on the editor screen and don't want to backup->flash->pull apk->restore.
Thanks for this papi92. I compared the vendor folder from the stock image to aosp and it appears quite a few files are missing. I really don't know how to add them and have always relied on devs such as yourself. Can upload the stock vendor folder if you need it.
That'd help a lot but those won't be the only ones missing. Some go in weird spots. I just need the missing ones.
Here is my vendor file for anyone who can help https://github.com/papi92/android_vendor
...and it begins. Thanks OP!
Here are the vendor files from the stock image. http://d-h.st/XV7
I was looking at them on 2 different computers so it was hard to tell which were different, but there are quite a few missing.
Ya I'll try to figure it when I have time. My daughter was born on the 21st so I was just trying to help people get started. I'm hoping the community helps with this. It'd be nice to get a solid base for the Nexus 6
papi92 said:
Ya I'll try to figure it when I have time. My daughter was born on the 21st so I was just trying to help people get started. I'm hoping the community helps with this. It'd be nice to get a solid base for the Nexus 6
Click to expand...
Click to collapse
Congrats on your newly born and thanks for your work.
I pooped my pants once, it's a long story....
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?