{
"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"
}
Cyanogenmod 10.1
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
How To Flash
Place ROM onto phone storage
Reboot to recovery
Make a Nandroid
Install Rom: Wipe INSIDE ROM
When you select "Reboot Not", you'll get a CWM error, IGNORE IT
Install Gapps
WIKI/FAQ Located: To be reworked
Click to expand...
Click to collapse
Latest Version Fixes:
Audio-including voice search
Camera Preview
Click to expand...
Click to collapse
Bugs??:
KNOWN ISSUES:
Bluetooth not working
Videocamera : Use VideoCam Illusion
Slight Lag possible on screen transitions
USB tether
The graphics related issues are due to not having proper drivers to use for this. Don't ask for an ETA on a fix. Moto won't be giving us the drivers, so there is no fix
If you need to report a NEW bug, report it once, and the next TWO people VERIFY it. I don't need everyone reporting same bug 20 times. I you can, provide me the following information:
Version you're using
What type of fwipe you did and what ROM you came from
Have you restored any data from something like Titanium Backup
What app is misbehaving and what you were doing when it started
Logcats<--THIS IS PREFERRED.
If you don't know how to logcat, go HERE and learn. This really nice guy took the time to write out a good how to
When you have a LOGCAT and would like to post it, please go to pastebin and post it in there, then LINK that location in this thread...I don't want to see them posted directly in here.
Click to expand...
Click to collapse
Downloads:
ROM file is Located HERE
My latest CWM: V1 as well as Aroma-Prep
can be downloaded HERE
Click to expand...
Click to collapse
Credits:
Cyanogenmod Team
scott.hart.bi=for helping me with source building and listening to me complain
Jokersax11-for being my initial inspiration on Photon, being a cool guy, and helping me when I get stuck
EPinter-for fixing some stuff
Amarullz=for creating the Aroma Installer
Spleef-for collaborating on those first builds that got me into Android
All my testers and users
Anyone else I may have forgotten
Click to expand...
Click to collapse
Kernel Source: HERE
Click to expand...
Click to collapse
mine
mine also
One thing i must mention is that i have not been able to test gsm or uscc, so i cannot guarantee 100% they will work. If someone can test, i would greatly appreciate it
Sent from my LG Optimus G
Thank you very much for this! I've been using your latest AOKP for over a week and it's been very solid, but I can't wait to try this.
Sweet! Thanks Bill for continuing to work on our MoPhos
Sent from my Nexus 7 using xda premium
Looking good
I'm very pleased to see it up and running. Good Work bill.
Btw, what gapps do we flash?
I did the one from goo.im for cm10.1 and voice search wont work
For those curious, here is my basic overview thus far;
I've been running it for just over an hour roughly and its fairly bug free (minus the wifi and bt)
Camera works great, minus the preview, which i still never figured out why it wouldn't work, you will just see a white screen, guesstimate where you are pointing. =P
Minor transition stutters, nothing major, just slightly more noticeable then on the 4.1.2 rom (give it time im sure it will improve)
I love the 4.2 feel, and all of the 4.2 features are working smoothly.
Overall, this a damn good place to start, You can tell when you flash this rom, bill put a lot of time and work into this, considering this is the first release, and it is so bug free.
Personally, i will be returning to PAC, as it is my daily driver, but im looking forward to what cm10.1 is bound to bring to our phone.
Thanks again Bill
T3HG00GLEG33K said:
I'm very pleased to see it up and running. Good Work bill.
Btw, what gapps do we flash?
I did the one from goo.im for cm10.1 and voice search wont work
For those curious, here is my basic overview thus far;
I've been running it for just over an hour roughly and its fairly bug free (minus the wifi and bt)
Camera works great, minus the preview, which i still never figured out why it wouldn't work, you will just see a white screen, guesstimate where you are pointing. =P
Minor transition stutters, nothing major, just slightly more noticeable then on the 4.1.2 rom (give it time im sure it will improve)
I love the 4.2 feel, and all of the 4.2 features are working smoothly.
Overall, this a damn good place to start, You can tell when you flash this rom, bill put a lot of time and work into this, considering this is the first release, and it is so bug free.
Personally, i will be returning to PAC, as it is my daily driver, but im looking forward to what cm10.1 is bound to bring to our phone.
Thanks again Bill
Click to expand...
Click to collapse
Voice Search is a bug I still need to work on. I was really working hard on the storage issue...in the end, it was an edit that came from the Capitivate Glide that fixed it...LOL
Of course, either by some edit that CM added in or one of my edits, I broke wifi (it was working in earlier builds. I'm trying to revert some of the edits to try to get it working again).
This is probably the 100th build of CM10.1 that I have done, so yes, there has been a LOT of time put into it. BT will be a bit of a pest to fix, but I am sure I can get it done. I already know the edit for the Camera preview, but I can't get it to build when I institute the edit...which is really odd. I'm still working on it.
Th3Bill said:
Voice Search is a bug I still need to work on. I was really working hard on the storage issue...in the end, it was an edit that came from the Capitivate Glide that fixed it...LOL
Of course, either by some edit that CM added in or one of my edits, I broke wifi (it was working in earlier builds. I'm trying to revert some of the edits to try to get it working again).
This is probably the 100th build of CM10.1 that I have done, so yes, there has been a LOT of time put into it. BT will be a bit of a pest to fix, but I am sure I can get it done. I already know the edit for the Camera preview, but I can't get it to build when I institute the edit...which is really odd. I'm still working on it.
Click to expand...
Click to collapse
Alright, yeah, i wasn't sure if it was just the gapps, or if it was a problem you knew about. Im glad you got the storage thing worked out, haha, i was getting desperate, found that rom i linked to (cm10 thread) that used 4.1.2 partitioning for 4.2
See, thats a problem i have when i was trying to work on the apks for the rom i put on hold. Its working just fine in the first one, but when i fix another part thats completely unrelated, it breaks the first. LOL. I feel like Wile E. Coyote trying to catch the roadrunner at times.
Holy Mother of ****. lmfao. In bow before you and your dedication. I feel if i was in your shoes i probably would have thrown my machine out of frustration.
As far as the camera preview goes, are you just recompiling the app with the edit, or are you building it from source and then adding the edit every time?
T3HG00GLEG33K said:
Alright, yeah, i wasn't sure if it was just the gapps, or if it was a problem you knew about. Im glad you got the storage thing worked out, haha, i was getting desperate, found that rom i linked to (cm10 thread) that used 4.1.2 partitioning for 4.2
See, thats a problem i have when i was trying to work on the apks for the rom i put on hold. Its working just fine in the first one, but when i fix another part thats completely unrelated, it breaks the first. LOL. I feel like Wile E. Coyote trying to catch the roadrunner at times.
Holy Mother of ****. lmfao. In bow before you and your dedication. I feel if i was in your shoes i probably would have thrown my machine out of frustration.
As far as the camera preview goes, are you just recompiling the app with the edit, or are you building it from source and then adding the edit every time?
Click to expand...
Click to collapse
The partition scheme is actually a step back to the old /mnt/emmc and /mnt/sdcard from ICS days . I found that it worked well on a few devices, but was having issues with emmc not showing up, as improper permissions were being indicated. I finally searched EVERY Tegra 2 device that had a 4.2 build to see what I could get working. The Captivate Glide had one that I hadn't tried, so what the hell, I figured. When it booted and I saw everything working, I almost cried
Yeah...I know what you mean about the fix one break another. Only issue is that since I was only checking storage, I don't know which edit broke wifi...lol. Could even be something that CM added in when they initiated wifi tether support...lol
Believe me...there were times when I looked at the Photon and considered it's aerodynamic properties and whether it could fly and how far...lol
I've tried both. Each way, I get the strange lot of errors...lol
Is wifi supposed to be working? I'm can turn it on and off but it never finds any networks nearby.
knG333 said:
Is wifi supposed to be working? I'm can turn it on and off but it never finds any networks nearby.
Click to expand...
Click to collapse
I forgot to put that wasn't fully working in the OP.
I'm gonna guess and say any issue with 4.2 gapps is due to this (via RootzWiki):
Does not include non-NEON libraries, as there have not been any non-NEON devices (Tegra and Tegra 2 devices such as the Motorola XOOM) which have received 4.2, and the 4.1 libraries are not compatible with 4.2.
Click to expand...
Click to collapse
bray424 said:
I'm gonna guess and say any issue with 4.2 gapps is due to this (via RootzWiki):
Click to expand...
Click to collapse
Epinter made a set of gapps for cm10.1 for atrix. Should work on photon
Sent from my LG-LS970 using Tapatalk 2
for the 4.2 keyboard, whenever I try to use gesture typing the word never shows
Also for anyone trying this rom out, here's a link to the new CM Chronus clock, which is 4.2+ only.
Great work! Thank you for keeping the mopho alive!
---------- Post added at 09:36 AM ---------- Previous post was at 09:13 AM ----------
Great work! Thank you for keeping the mopho alive!
+1
hightech316 said:
Great work! Thank you for keeping the mopho alive!
Click to expand...
Click to collapse
Once again you have done it. Awesome job brother. I am on CDMA and have no network connect. I did a full wipe and i am coming from liquid.
Sent from my sunfire using xda premium
I can confirm that GSM is working on straight talk! Albeit with the known ROM issues
Sent from my MB855 using xda premium
Related
First of all I want to make some things clear:
This is my own custom build I made with the help of this great tutorial: http://forum.xda-developers.com/showthread.php?t=775505
This has nothing to do with the offical nightly build from Cyanogen and his team.
I won't provide any support for this. If you want to flash this you should know what you do. Don't ask me anything like "How do I flash this?".
This could be even more unstable then the official nightly build since I add commits that are not merged. It's a great feature preview, but I can't guarantee anything. I can't tell you if the features you see here will make it into any official build.
What is it?
Its a custom build of the latest Cyanogen sources spiced up with some not (yet?) merged patches.
What's inside?
A basic ROM with "a2sd light" and without g-apps. I removed ADW Launcher too since it's lags, included is the stock Android Launcher2.
I also removed CMStats since this one isn't anything official and could be more buggy then anything else.
Whats "a2sd light"?
Its like the original a2sd from here: http://forum.xda-developers.com/showthread.php?t=715940
but I removed all things that handle the dalvik-cache. I tried the original a2sd and didn't like it since it moved the /cache/dalvik-cache/ back to /data. Don't know if thats the way it should be.
I don't know how often I will make new builds, it depends if I find new things I want to try. If there are no new commits that interest me I won't make a new build.
I will only upload builds that work for me. So the basic stuff should work for everyone, if it doesn't try to wipe before flashing. If it still doesn't work use the official nightly/RC/stable/whatever... (Thats the point with "I won't provide any support").
So whats inside today/night?
All commits that were made until 28.Nov 2010 05:00pm (look here to get some details: http://review.cyanogenmod.com/#q,status:merged,n,z)
+ updateted gesture support on Lockscreen
+ custom app for lockscreen messaging slider
- User can now define unlock and sound toggle gestures.
- Lockscreen tabs can now be fully disabled, but ONLY if there is
some other method of unlocking the device enabled. This includes:
Trackball unlock, menu key unlock, and gesture unlock.
- Changed default gesture sensitivity to 3
Allow the user to specify which application to launch using
the lockscreen messaging slider.
Link:
http://www.multiupload.com/P00AYOA42T
Thanks to the devs of CyanogenMod and all other people contributing in this!
{
"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"
}
So the only difference between this and the official buildbot nightly is you added some a2sd that we can install via recovery anyway?
awesome idea for a thread!
daedelus82 said:
So the only difference between this and the official buildbot nightly is you added some a2sd that we can install via recovery anyway?
Click to expand...
Click to collapse
Tada, the first one that didnt get what this is about. Try to find the lockscreen in the official nightly. Guess what, its not there yet. Because the patch is not merged yet. And the buildbot uses only merged things.
Maybe you start reading and thinking before posting next time...
Sent from my Nexus One using XDA App
simms22 said:
awesome idea for a thread!
Click to expand...
Click to collapse
Thanks, great some people read the whole post and understand it
Sent from my Nexus One using XDA App
g4rb4g3 said:
Thanks, great some people read the whole post and understand it
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
ive been flashing quite a few custom cm builds lately and been finding it very refreshing
btw... it looks like you picked up that stupid lockscreen grass wallpaper bug
g4rb4g3 said:
Tada, the first one that didnt get what this is about. Try to find the lockscreen in the official nightly. Guess what, its not there yet. Because the patch is not merged yet. And the buildbot uses only merged things.
Maybe you start reading and thinking before posting next time...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
Well, if support is your sticking point, then even using the cyanogen nightly is something you should avoid. This is just a user posting his creation if someone wants to play with the ROM. Happens all the time here. That's why this is a great site. Pick your poison. All about choice. Ignore what you don't want to use. I don't think the OP tried to pass this off as better than anything else. Just offering something to play with. I thought it was communicated very clearly.
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
some people, obviously not you, experience the joy of flashing a rom for the sheer pleasure of flashing a rom. you dont have to flash it, or even read the thread(thats an absolute right that you have). but, i do see the worth in it. if not for anything else, the op is learning about building roms and has other people, like me, to test them out. i believe that it brings the op joy in building them and sharing. since its his own personal build, he can not post them in the official nightly thread. i was posting custom cm nightlies in the official thread and was asked to make a separate thread, and never did. btw, there are nights that there are no nightlies, so does the name of that thread have to change also? anyways, if you do have a good idea for the name of the thread, let the op know. maybe he will change it
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
A lot of people are asking about the lockscreen options in the Nightly thread. This should shut them up for now.
There's also no real need to support this at all. It's based on a nightly that is oudated in a few hours and it only has a couple patches. If anything is wrong he's not the developer of this ROM so there isn't anything for him to fix. It's just CM 6.1 built from source with new commits that aren't yet merged.
Just a taste of whats ahead.
P.S. <3g4rb4g3 <3simms22
Thanks to the OP for posting this. I like all the other flashing addicts find it refreshing trying out others peoples builds. Plus I have serious respect for the time, energy and hard drive space that goes into making these. Nice job.
Great job, I love the lock screen!, works perfect.
Last time I checked, Cyanogen nightlys were not supported either! just saying!
daedelus82 said:
I read the entire post but still fail to see it's worth.
I would rather wait a day for it to be merged and in the official nightly, than use a build which has no support and is stated will only be updated when you see fit.
It doesn't offer anything other than a couple commits which have not yet made it into the official nightly.
Also unless you plan on building it every day/night you should probably take [NIGHTLY] out of the title, I think it's a little misleading.
Click to expand...
Click to collapse
I don't care if you think it's worth flashing or not. I make my own "nightly" builds for several weeks already. Since some people asked I started this. Seems like there are people out there willing to try it. If you want to wait do so and keep it for yourself.
It seems you have a bad life, complaining about things that you don't like/think they are not worth trying... Try to read only topics that you are interested in. If you aren't interessted in this shut up, stop posting, go away and hate someone else.
I don't want to call it the best thing ever or anything else. This is just a feature preview. Maybe the features make it into a official build, maybe not. I don't decide that. But I decide which commits I want to use...
And about the "nightly" tag, I use it since I use the same sources for it. It should tell the people that this is nothing that got tested several days and it could contain bugs. (Like the stupid gras wallpaper on the lockscreen)
i think its a great idea, there is no need to bash someone for posting a modified nightly, this is a common thing in the open-source community
also there are many things you can merge and play with.
i for one merge some webkit stuff (from official webkit repo) when i get the chance , you should look into that.
- 2 pages of spam only
- great idea "g4rb4g3" keep it up!
New version, updated first post.
g4rb4g3 said:
+ White energy widget icons if you select the STOCK_Black theme in Settings>CyanogenMod settings>User interface>Tweaks extras>Select a theme.
This patch was made by me, I commited it and hope it will get merged.
Click to expand...
Click to collapse
That's awesome! If I hadn't gotten swept up in the whole MIUI craze, I would give it a go
updated first post
Great work, but i think that is better waiting for RC2 official release for mod it.
matiu said:
Great work, but i think that is better waiting for RC2 official release for mod it.
Click to expand...
Click to collapse
Of course you can wait, I couldn't
{
"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"
}
CM10.1 is here for the LGE970, aka the ATT LG Optimus G.
This is a source build rom, which includes all the latest changes from cm.
Instructions
Download cm-10.1, and gapps. Put them on your sdcard, reboot to recovery. Flash, and enjoy!
Note: As of 0410 you must be on jb ota or lgnpst the jb bin.
The current version is:
20130703
The latest will be avaliable at:
http://downloads.codefi.re/shelnutt2/optimusg/att/cm10_1/
Gapps:
Currently BaNkS Seems to work best:
http://forum.xda-developers.com/showthread.php?t=2012857
Click to expand...
Click to collapse
Known Issue
USB tethering doesn't work
Click to expand...
Click to collapse
Change Log
Current Version: 20130703
Changelog:
20130621: Call bug is fixed
20130518: Bluetooth mac address is now persistent
20130517: Implemented a possible work around for end call bug
20130410:
New kernel base, updated device repos and vendor repos to bring unified sources.
20130401:
Easter edition! No easter eggs though just a resync and start of nightlies.
20130314:
EFS partitions are now backups by default on your first flash if they do not exist.
20130313:
Display optimization tweak thanks to chadouming
Other cm fixes, like better su support
20130311:
koush's superuse now build in to cm, many other cm changes now code freeze is lifted
Thanks to houstonn added hardware info to build.prop to show up in settings
caf_display
Thanks to sk8, switched back to caf display now that it works
03-06-2013
Fully synced and up to par with cfx. Audio is fully work, nfc, no gps or camera.
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the following people:
rlasalle15
chadouming
dvhexer
synergy
unknown2011 (and all his friends!)
thecubed
sextape
Click to expand...
Click to collapse
Source
Device repo, kernel and vendor blobs
http://github.com/TeamLGOG
Click to expand...
Click to collapse
Great work Shel! You're a true pleasure to work with.
sent from codefireX
Nice to see u here shelnutt2
Sent from my At&t LG Optimus G E970 running CFX
I wish I could hack the webcams of all the folks who said we don't have competent developers for the E970 when they figure out what ignorant f*cknuggets they are. Like my nerdy ass is going to buy a phone that isn't going to get ridiculously awesome AOSP within a reasonable amount of time, ha ha ha ha!
Man, I wonder how all those dudes who ditched their OGs feel. BTW this runs GREAT. The screens in OP are mine.
Much thanks to all of the developers of the E970 for sharing their talent and work! I try not to post much - still a noob with nothing to add toward development so don't want to take up space - but with all of the recent work added, simply wanted to say thank you.
I still have never flashed a ROM (ever); it's not that the ICS development was not interesting, I simply wanted to spend additional time educating myself first. With AOSP, AOKP, and now CM, time for me to step-up my reading!! I'm rooted, unlocked, have my nandroid, and almost ready to go - though do need the GPS working as I can't live without it.
BTW, great, in-context use of the word f*cknuggets, Deathmonkey!
lennyquai said:
Much thanks to all of the developers of the E970 for sharing their talent and work! I try not to post much - still a noob with nothing to add toward development so don't want to take up space - but with all of the recent work added, simply wanted to say thank you.
I still have never flashed a ROM (ever); it's not that the ICS development was not interesting, I simply wanted to spend additional time educating myself first. With AOSP, AOKP, and now CM, time for me to step-up my reading!! I'm rooted, unlocked, have my nandroid, and almost ready to go - though do need the GPS working as I can't live without it.
BTW, great, in-context use of the word f*cknuggets, Deathmonkey!
Click to expand...
Click to collapse
The best way to educate yourself about these things is to flash and play with them. Seriously, make sure you have a good backup, and then flash to your heart's content. Flashing a ROM and then flashing back to your good recovery each take a few minutes a piece. It's easy.
Sweetttt!! :victory: , will themes from playstore work with this rom?
Downloading now and excited to flash. Had problems with Codefire SR15, the power button caused a system crash. Hopefully that won't happen on this!
Sent with Hawleywood OG style
Digil said:
The best way to educate yourself about these things is to flash and play with them. Seriously, make sure you have a good backup, and then flash to your heart's content. Flashing a ROM and then flashing back to your good recovery each take a few minutes a piece. It's easy.
Click to expand...
Click to collapse
Thanks, Digil! Though I have not done it, I agree nonetheless. I knew I'd want to take advantage of all this phone (and developers) have to offer, so rooted and unlocked when I got it in December (thanks to Carret's instructions!) without issue. I have TWRP installed and did my first nandroid (though will do another to make sure I did it right, as mine was a bit large @ 3GB). Confident I can flash a rom, though not certain I did the nandroid right and want to make sure. I'm in sales and travel out of town quite a bit, so really need GPS working, so have simply been enjoying seeing the work, reading the comments, and trying to get better versed (after the wife and kids go to bed). Unlike many, I still do 1000-1500 minutes of calls a month, so needed to see the volume working as well.
I seem to be a pretty old fart by xda standards - 44, though still a heavy metal punk at heart (hair metal guitarist and singer back in the 80's). Though I love technology, I'm not as up to speed as most on these forums, so am taking it slower than I probably need.
yes finally we can get some good cm action going
lennyquai said:
Thanks, Digil! Though I have not done it, I agree nonetheless. I knew I'd want to take advantage of all this phone (and developers) have to offer, so rooted and unlocked when I got it in December (thanks to Carret's instructions!) without issue. I have TWRP installed and did my first nandroid (though will do another to make sure I did it right, as mine was a bit large @ 3GB). Confident I can flash a rom, though not certain I did the nandroid right and want to make sure. I'm in sales and travel out of town quite a bit, so really need GPS working, so have simply been enjoying seeing the work, reading the comments, and trying to get better versed (after the wife and kids go to bed). Unlike many, I still do 1000-1500 minutes of calls a month, so needed to see the volume working as well.
I seem to be a pretty old fart by xda standards - 44, though still a heavy metal punk at heart (hair metal guitarist and singer back in the 80's). Though I love technology, I'm not as up to speed as most on these forums, so am taking it slower than I probably need.
Click to expand...
Click to collapse
lennyquai, I definitely feel you about wanting to take it slow, and do your research first. In fact, I think XDA (and hell, probably the world in general) would be much better off if everyone took that approach. We seem to have some awesome devs here, so I know when you eventually do decide to start flashing some ROMs you won't be disappointed. Good luck! See you around.
Btw, thanks to Shelnutt for putting this up, and all your work. Can't wait to try it out after work tonight!
Sent from my LG-E970 using XDA Premium HD app
lennyquai said:
I seem to be a pretty old fart by xda standards - 44, though still a heavy metal punk at heart (hair metal guitarist and singer back in the 80's). Though I love technology, I'm not as up to speed as most on these forums, so am taking it slower than I probably need.
Click to expand...
Click to collapse
I got you by almost decade... But the kids in here are pretty tolerant of old farts.
I'll caution you that once you start flashing roms you'll get addicted and flash everything that comes out. Titanium Back Up Pro is more than worth the cost. You can not only back up then restore apps (incl data), but once your downloaded apps are restored, you can restore the data for the launcher, which automatically setups up your home screens (be sure to do a full back up of apps, before you start flashing).
Sent from my LG-E970 using xda app-developers app
Has anyone had problems with data not working randomly? Chrome would just sit there.....
Edit: I noticed when my data wasn't working it was showing H, Now even though it's toggling thru all types of data it's working. Not sure if it was because disconnecting from wifi or what but all seems ok now.
Sent from my LG-E970 using xda premium
Has anyone been able to find the "Enable USB Debugging" setting (I get a message to change it, whenever I use TiBu)? Usually its under the System section in the Developer settings. I don't find Developer settings and I think that I've been through every setting and haven't found it.
dbgeek said:
Has anyone been able to find the "Enable USB Debugging" setting (I get a message to change it, whenever I use TiBu)? Usually its under the System section in the Developer settings. I don't find Developer settings and I think that I've been through every setting and haven't found it.
Click to expand...
Click to collapse
Yeah same here
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
MysteryEmotionz said:
Imagine the mess your making by complaining. You should just ignore it n let it get burried
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
Why not at least say something productive. You doing this is rather annoying.
mrpanic7 said:
Yeah same here
Click to expand...
Click to collapse
Tap build number in settings -> about phone 6 times and it'll be enabled. It's a standard 4.2 feature that cm has kept.
Shelnutt2 said:
Tap build number in settings -> about phone 6 times and it'll be enabled. It's a standard 4.2 feature that cm has kept.
Click to expand...
Click to collapse
Thank you I had a feeling it was just hidden, knew it wasn't omitted.:good:
dbgeek said:
Has anyone been able to find the "Enable USB Debugging" setting (I get a message to change it, whenever I use TiBu)? Usually its under the System section in the Developer settings. I don't find Developer settings and I think that I've been through every setting and haven't found it.
Click to expand...
Click to collapse
Starting with 4.1 I believe, Google made it so you have to go to "About Device" under settings, then tap the "Build number" location seven times. A toast notification will show up when you start tapping telling you how many more taps you have to go. Developer settings will then show up in the "Settings" menu. Why they hid it like an easter egg is beyond me.
Edit: Dang Shelnutt2 beat me to it.
Shelnutt2 said:
Tap build number in settings -> about phone 6 times and it'll be enabled. It's a standard 4.2 feature that cm has kept.
Click to expand...
Click to collapse
Thank you. That's a very interesting set up.
well i try the new rom ice ice baby now but there is the problem that the drop down option and settings are gone...can anyone help for that??
ronald027 said:
well i try the new rom ice ice baby now but there is the problem that the drop down option and settings are gone...can anyone help for that??
Click to expand...
Click to collapse
I'm sure users here would be glad to help you if they knew what you're talking about, I.e. the notification drop down? Phone settings? how did you install it, etc. You should probably post your question in the Rom thread...
Edit: others reported settings issues, the Rom has been pulled for now.
That's because those Settings were originally modified to work on UnSenseROM and need to be modified to work by default on any other roms made from the new base.
I know Jester added a couple things, but that alone won't make them compatible on first flash of the rom.
I have been in the process of reworking them for my update to UnSense and am just about complete with that.
If he does not get them working before then, due to using my old settings, you may be able to first install the rom with Sense settings.
Then reboot once, then return to recovery and then flash his separate zip for the aosp settings and SystemUI and then clear cache and dalvik and reboot.
But those things need to be modified to work on first boot if they are gonna be cooked into his rom.
I have already reworked SystemUI for my desensed roms and as I said am almost done with Settings, so they will work upon initial rom flash.
santod040 said:
That's because those Settings were originally modified to work on UnSenseROM and need to be modified to work by default on any other roms made from the new base.
I know Jester added a couple things, but that alone won't make them compatible on first flash of the rom.
I have been in the process of reworking them for my update to UnSense and am just about complete with that.
If he does not get them working before then, due to using my old settings, you may be able to first install the rom with Sense settings.
Then reboot once, then return to recovery and then flash his separate zip for the aosp settings and SystemUI and then clear cache and dalvik and reboot.
But those things need to be modified to work on first boot if they are gonna be cooked into his rom.
I have already reworked SystemUI for my desensed roms and as I said am almost done with Settings, so they will work upon initial rom flash.
Click to expand...
Click to collapse
Yea what he said lol. Wish i could do more but I'm already a blind man running around here with nothing to look at to be sure if it does work or not. I r-uploaded it as a fixed version.
Yo santod add me on gtalk man, Did you ever get your sense settings or anything to decompile? They spit errors at me all day long
I'm sure you'll get it all working.
Jested, do you still not have a Thunderbolt? I'll send off my old one to you--the only problem is my aunt dropped it in water in Sedona, and now the rear camera doesn't focus, and the screen has some artifacts when on an all-white screen that you can see. I don't want anything for it--would be ecstatic to be able to help you out in any way. And Santod/Jester: Love your debloated/ICE ICE BABY ROMs, respectively!
Jest my friend's GF use to have a TB. I can see what she did with it.
Sent from my ADR6400L using xda app-developers app
smooth as silk
Jest, it was smooth as silk. I'm sure if you had a bolt, you would have made it rock solid.
Appreciate you!
Without starting a new thread, I am having major issues with this rom, I keep getting random reboots right after installing.
I checked the MD5 sum and it was correct, I used the 4EXT recovery, I formatted eery partition except SD card, and wiped data+ dalvik, and formatted cache nothing fixes it.
I get blue vertical lines on the reboot and the phone either reboots, or the screen goes black and the "house, menu, back and magnifying glass" stay lit up
any help?
f575gtc said:
Without starting a new thread, I am having major issues with this rom, I keep getting random reboots right after installing.
I checked the MD5 sum and it was correct, I used the 4EXT recovery, I formatted eery partition except SD card, and wiped data+ dalvik, and formatted cache nothing fixes it.
I get blue vertical lines on the reboot and the phone either reboots, or the screen goes black and the "house, menu, back and magnifying glass" stay lit up
any help?
Click to expand...
Click to collapse
Install the ICS radios from my Official ICS thread, link in my sig.
worked! thanks a million!
santod040 said:
That's because those Settings were originally modified to work on UnSenseROM and need to be modified to work by default on any other roms made from the new base.
I know Jester added a couple things, but that alone won't make them compatible on first flash of the rom.
I have been in the process of reworking them for my update to UnSense and am just about complete with that.
If he does not get them working before then, due to using my old settings, you may be able to first install the rom with Sense settings.
Then reboot once, then return to recovery and then flash his separate zip for the aosp settings and SystemUI and then clear cache and dalvik and reboot.
But those things need to be modified to work on first boot if they are gonna be cooked into his rom.
I have already reworked SystemUI for my desensed roms and as I said am almost done with Settings, so they will work upon initial rom flash.
Click to expand...
Click to collapse
Ummm, no there not? There from the NoNonSense rom for the EVO 3D hahaha I use the same ones in mecha rebirth
Remarks have been quashed.
There is no place on XDA for name calling, please refrain. Consider this the one time only warning.
Thank you for adhering to the rules.
Well so I it seems this is the end of TB development on this form, unless HTC releases the ICS kernel source, who know when that'll..if ever.
WELCOMETOOCEANIA said:
Oh no. Not my my whole 5 post account.
This whole childish hostility between developers is such a joke. And locking down threads because of it is pathetic. Ban me. I'll still download whatever the **** I want. I'll just be sure to not contribute when I can.
Click to expand...
Click to collapse
You know what, let me tell you a few things, maybe you will listen.
I happen to be a human just like everyone else that visits these public forums.
I am a single parent of a couple children and work very hard for everything that comes to me.
I did not and do not have to share anything I spend my few spare minutes doing with anyone.
When the ICS OTA came out, the only active developers for the Thunderbolt, were Twisted and myself.
I made sure that the very next day after the OTA was available to anyone unrooted via VZW, that I had not only one version of the stock rom rooted and ready for download in it's entirety, but 4 versions to pick from, of yes, a clean stock rom.
What you would get from Verizon, but rooted and ready for consumption.
I stayed up that entire night getting all that together and ready for every Thunderbolt user, everywhere.
I didn't have to, I wanted to and did and gladly shared it with everyone.
I also have made many and publicly posted and shared 5 custom roms, 4 of which are directly based off the stable OTA.
Is it fair that other devs should not have to do the same work to make their roms? Maybe, maybe not.
That's not the issue either. To me in this small world, we have a few things left to call our very own.
One being self respect and if I allow someone to continue using my hard work, meanwhile talking down about me, I should not sit on my hands and ignore it.
I actually tried that and I saw it continue regardless.
The fact that my base was being used wasn't good enough for some, they also wanted to use mods that I had spent other numerous hours working on that I did not have to or did I have to share in my own roms at all.
But since I had publicly shared them in my roms, somehow that should entitle anyone to use them in their own?
(Advanced Power Menu Mod)Hounded for over and over as an example. That only includes my entire framework
Because I was not willing to have them duplicate my own public roms, they lashed out at me.
They publicly talked about me in ways I did not like or care for and was not ok with the way they carried on about it, as if I owed them more.
I was doing nothing and still am doing nothing to anyone and just want to be left out of those types of "projects" completely.
That is all, is that wrong of me?
Should I have never posted the 9 roms I have posted?
I'm so sorry I shared anything then.......
Move on, let them do the same if they are so capable, that's great! :good:
But leave me be and out of it.
I have nothing to do with anyone else making or not making a rom.
A dev can make a base and a rom anytime they want.
If you hadn't noticed, we have few left if any.
Let the devs decide if they want to make roms.
If they want to, they will.
Crying about it doesn't make me want to do more and likely doesn't make any others want to do more.
It was crying that got us all here.
So please refrain from including me in any further posts of yours unless you are sending me a PM. Thanks!
As far as only having a 5 post account and "not contributing when you can", I believe you.
^ word. I can respect that.
Sent from my SCH-I535 using xda premium
Well i do respect you santod.. And i never begged for any mod. The Restart menu is based on android.policy.jar and stuff anyways theres tutorials but nothing for sense 3.6... I never asked for an entire menu or any other mod of sort, even said maybe a tutorial of how you did it for the bolt and you take the credit for that. That's all i have ever asked you about anyways... Don't know what anyone else has asked you.. But as i told everyone before i only did mine that way because well, please excuse me while i pull a base off a phone that has no screen...
{
"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"
}
The funny thing is it does still turn on and charge.. lol But it stays black
Jester-do you have any interest/were you able to work anything out with the person in this thread offering up their tb?
Hopefully you're able to keep working on this
Sent from my ADR6400L using xda premium
rrrrrrredbelly said:
Jester-do you have any interest/were you able to work anything out with the person in this thread offering up their tb?
Hopefully you're able to keep working on this
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I messaged them today i just now saw both of those offers, seein what they say. Might take both if possible and bring my old one back to life. After all it was the first tbolt with data on ics aosp Cant let it die like that
Hey sorry I no longer have that extra Thunderbolt anymore. Didn't mean to waste time, it had been a while since I offered it so I gave it to my friend after a few weeks. Again, my apologies.
Sent from my ADR6400L using xda premium
In case you hadn't noticed, cyanogen has been releasing nightly builds for our device. There has been a release almost every day. I'm running today's release 20130705 and no issues yet.
Sent from my EVO using xda premium
{
"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"
}
Sent from my EVO using xda premium
Neipas09 said:
CM might look pretty if you got a boner for Pure Google looking roms.
Click to expand...
Click to collapse
As a matter of fact I have a huge one for pure Google, plus other things.
There is work being done on the connection issues though.
Sent from my EVO using xda premium
NaterTots said:
As a matter of fact I have a huge one for pure Google, plus other things.
There is work being done on the connection issues though.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I don't blame you. I hate sense and touchwiz and all other skins out there for the phones.
But the connection issue is a bigger problem for me, so hopefully they will get it fixed.
But i highly doubt they will since they never did with the original EVO.
All they said was "we are looking into it / working on it"
ANYWAYS....
it exciting that the cm team is putting out nightlies. Also, I see that deck has been putting in work for this device and the newer kernel. As always, its fun and cool to watch development happening before our eyes.
If everything worked out of the box, and nothing was ever borked, then there wouldn't be much to develop and this website might not be here...
Thanks for posting, I was bummed when they stopped nightlies for our device and wouldn't have known that they started again if it wasn't for your post.
fwiw - I get great reception with CM. I am currently running meanrom and it seems to put the phone in 2g in areas where other sprint customers have strong 3G. Reboot (or flip airplane mode on-off) and I get a strong 3g signal.
I find that my reception doesn't differ from ROM to ROM if I'm in a good signal area regardless.
But in area that switch from 1x of 3g to LTE I find that sense ROMs offer more data stability....
Greetings!
I implore you to please try to keep this on topic and respectful. Civilized disagreements can certainly be had, but let us not stoop to sophomoric insults and puerile retorts.
Thank you for your participation, together we can make a difference
I had been looking for a CM ROM after all of the great things I've read about it, because the 10.0.0 stable release for 3.16 didn't include kernel updates for the touchscreen on my EVO, so I was glad to find the nightlies and give it a go.
Maybe it's only because I've gotten used to the stock Sense and MeanBean, but I really can't find any love for this ROM.
I really wanted to like it, too. I have often read about how its built-in tethering is first-rate along with a number of other advantages,
but I just can't discover them.
Signal strength for voice is abysmal; I can not get a data signal of any sort; USB tethering will not turn on; I can find no option to change the weather info from Celsius to Fahrenheit; some settings I have commonly adjusted are accessed in a much different fashion; and so forth...
The last straw was having an endless startup animation for well over an hour after restoring apps & data, rendering this ROM useless on my device. Granted, the backups came from a Sense-based ROM, so there's likely some incompatibility happening, but I've invested far too much time since I got this device a short time ago(May 10) into unlocking, rooting and S-OFF, and finding and installing apps and tweaks, just to start over from scratch as if I had never used the device before CM.
After all I have read about the CM mod, I honestly had high hopes and expectations for using it on my device. It's just not like anything I had expected, and maybe that's my own fault for not having researched it more fully, but it's been a major disappointment to me. I could also chalk up my disappointment in CM to being a complete N00B with Android devices, not really understanding much about the platform, but that's also a stupid n00b remark.
I truly appreciate all the time and effort that goes into compiling the CM ROM(and others), and understand a small bit of what it takes to accomplish it, but it's just not to my liking. Does that make me a bad person?
Not at all....
Like I said before the mods stepped in, don't knock it till ya try it, and if you don't like it then try something else.
My phone runs like a beast on AOSP ROMs , but that's my experience on my phone. I still run on sense though, because I like sense...
This is why we rooted and unlocked our devices, to make them ours.
NaterTots said:
As a matter of fact I have a huge one for pure Google, plus other things.
There is work being done on the connection issues though.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
do the CM nightlies fix or alleviate some of the connection issues (dropping down from 4g to 3g or 2g) or is it a hardware problem?
ppcpirate said:
do the CM nightlies fix or alleviate some of the connection issues (dropping down from 4g to 3g or 2g) or is it a hardware problem?
Click to expand...
Click to collapse
It's got to be a software issue, as the CM has given me almost no signal whatsoever, whereas MeanBean and stock has always provided usable signal strength. And I'm in a fringe area for 3G/4G signal.
ppcpirate said:
do the CM nightlies fix or alleviate some of the connection issues (dropping down from 4g to 3g or 2g) or is it a hardware problem?
Click to expand...
Click to collapse
What I assume most people don't understand is that "Nightlies" are by definition test builds. They are simply built automatically, regardless of whether they work.
kushdeck is the Dev that maintains CM for our device, and he is working on solving ALL of the outstanding issues. In fact, on the EVO 4G LTE IRC channel (#htc-evo-4g-lte), there is a build that has all but eradicated the data issues. That's really the best place to go for CM builds, as it takes a while for changes and updates to be merged once fixes are discovered. By flashing builds from IRC, you can also take an active role in helping to test the builds by providing meaningful feedback and logs that can assist deck to identify and fix issues.
While the CM Nighlies are back, they do not have all of the current updates, changes and tweaks that deck has made to the kernel source and ROM to add features and improve stability. So those of you that have tried CM and had a bunch of issues, that's why. The ROM is still in development. So your options are either to assist with that development by helping with the testing, or waiting until everything is fixed and merged to CM. The choice is yours.
P.S. AOSP and Sense are VERY different. CM is very close to what Google intended when they built Android 4.2.2. Sense is HTC's overlay on Android 4.1.2, so if you've gotten used to Sense, there will be a learning curve involved, as HTC has obfuscated, modified or removed a significant amount of the stock Android features. But if you can get past that point, the benchmarking and speed comparison of the ROMs isn't even close, since Sense is such an immense RAM hog. And with the 3.4 kernel being integrated into CM, available memory is at 790MB, which makes multitasking an extremely pleasant experience.
P.P.S. To answer the original question - no, the Nightlies do not fix the data connection issues. However, the latest build I previously mentioned on IRC does. But it's indeterminate when those changes will be merged. Once this ROM is stable and close to 100%, deck will update his thread here with a link to the stable build. That's when you'll know it's ready for prime time.
P.P.P.S. Speaking of hardware issues, though, the EVO 4G LTE is known for being notoriously unreliable for holding signal, especially in fringe areas, when compared to other LTE-capable devices. So don't be surprised by that if you're comparing it to a different device.
Thanks for the explanation, I've dabbled in AOSP on HTC touch pro 2 and used CM as a daily driver on my previous phone (galaxy s2). I'm a bit hesitant now because of a hard brick on the sgs2 (CM stopped working one day and couldn't flash recovery). but still wanting the improved experience stock offers. though nowadays some manufacturer's UI overlay do give you some useful features like the camera UI.
Captain_Throwback said:
What I assume most people don't understand is that "Nightlies" are by definition test builds. They are simply built automatically, regardless of whether they work.
kushdeck is the Dev that maintains CM for our device, and he is working on solving ALL of the outstanding issues. In fact, on the EVO 4G LTE IRC channel (#htc-evo-4g-lte), there is a build that has all but eradicated the data issues. That's really the best place to go for CM builds, as it takes a while for changes and updates to be merged once fixes are discovered. By flashing builds from IRC, you can also take an active role in helping to test the builds by providing meaningful feedback and logs that can assist deck to identify and fix issues.
While the CM Nighlies are back, they do not have all of the current updates, changes and tweaks that deck has made to the kernel source and ROM to add features and improve stability. So those of you that have tried CM and had a bunch of issues, that's why. The ROM is still in development. So your options are either to assist with that development by helping with the testing, or waiting until everything is fixed and merged to CM. The choice is yours.
P.S. AOSP and Sense are VERY different. CM is very close to what Google intended when they built Android 4.2.2. Sense is HTC's overlay on Android 4.1.2, so if you've gotten used to Sense, there will be a learning curve involved, as HTC has obfuscated, modified or removed a significant amount of the stock Android features. But if you can get past that point, the benchmarking and speed comparison of the ROMs isn't even close, since Sense is such an immense RAM hog. And with the 3.4 kernel being integrated into CM, available memory is at 790MB, which makes multitasking an extremely pleasant experience.
P.P.S. To answer the original question - no, the Nightlies do not fix the data connection issues. However, the latest build I previously mentioned on IRC does. But it's indeterminate when those changes will be merged. Once this ROM is stable and close to 100%, deck will update his thread here with a link to the stable build. That's when you'll know it's ready for prime time.
P.P.P.S. Speaking of hardware issues, though, the EVO 4G LTE is known for being notoriously unreliable for holding signal, especially in fringe areas, when compared to other LTE-capable devices. So don't be surprised by that if you're comparing it to a different device.
Click to expand...
Click to collapse
---------- Post added at 04:40 PM ---------- Previous post was at 04:36 PM ----------
SkedAddled said:
It's got to be a software issue, as the CM has given me almost no signal whatsoever, whereas MeanBean and stock has always provided usable signal strength. And I'm in a fringe area for 3G/4G signal.
Click to expand...
Click to collapse
another issue i've noticed is that when I'm on wifi and leave the phone idle for a while, the wifi seems to go to sleep along with any other data connection and won't wake up till i cycle either the wifi radio or toggle airplane mode. then get a flood of emails & messages. this is probably the most aggravating problem along with turrible 3g data speeds & not holding onto 4G connection.
Captain_Throwback said:
kushdeck is the Dev that maintains CM for our device, and he is working on solving ALL of the outstanding issues. In fact, on the EVO 4G LTE IRC channel (#htc-evo-4g-lte), there is a build that has all but eradicated the data issues. That's really the best place to go for CM builds, as it takes a while for changes and updates to be merged once fixes are discovered. By flashing builds from IRC, you can also take an active role in helping to test the builds by providing meaningful feedback and logs that can assist deck to identify and fix issues.
Click to expand...
Click to collapse
This sounds far more promising. Can I then assume that the URL displayed upon joining the channel(CM10.1: http://......) contains the build which is the most current, actively-developed one you mentioned?
evervolv
atheistevofreak said:
In case you hadn't noticed, cyanogen has been releasing nightly builds for our device. There has been a release almost every day. I'm running today's release 20130705 and no issues yet.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Evervolv never stopped releasing nightlies.
SkedAddled said:
This sounds far more promising. Can I then assume that the URL displayed upon joining the channel(CM10.1: <link was here>) contains the build which is the most current, actively-developed one you mentioned?
Click to expand...
Click to collapse
Yes, that is the latest - but please remove the link from your post, as it's preferred to go to IRC to retrieve the link than having it here in open forum. Thanks.
Captain_Throwback said:
Yes, that is the latest - but please remove the link from your post...
Click to expand...
Click to collapse
Done, and thanks for the confirmation.
I'm off to give the fresh build a try. :good:
CM10.1 running and working great here, including touchscreen kernel support.
As suggested by Captain_Throwback, whom I have thanked, go grab the latest build from the IRC channel as mentioned here: http://forum.xda-developers.com/showthread.php?t=1643396
Fixes for data, voice, and a lot of other functions are to be found.
Thanks, Cap'n!
---------- Post added at 11:06 PM ---------- Previous post was at 10:28 PM ----------
Hmmm....
Stuck in a bootloop after trying a WiFi tether to my desktop machine.
Doesn't happen when tethering to my laptop.
Wonder what's wrong?
---------- Post added at 11:56 PM ---------- Previous post was at 11:06 PM ----------
Nope. I'm giving up on this one.
I honestly tried to like it, but it simply doesn't work in the way I expected it to.
A WiFi tether shouldn't send it into an endless boot loop.
I'm really sorry that I couldn't find the love for this ROM, but it's been more headache than anything.
I'm going back to the MeanBean.
SkedAddled said:
CM10.1 running and working great here, including touchscreen kernel support.
Click to expand...
Click to collapse
Can you install the latest CM10.1 with s-on, then?
YOU HAVE NOW BEEN CARBONIZED
Built from the Carbon source, these unofficial builds will be updated weekly. Maybe more if time permits or there are any huge changes to be incorporated. Built specifically for our devices, no ports here anymore. This should allow it to run a bit better than a rom that was technically built for another device.
And now, on with the show!
About Carbon
{
"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"
}
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Carbon Features
All of our features can be found on our site here:
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
***NOW BUILT WITH ArchiDroid OPTIMIZATION STARTING 11/07***
Many thanks to @JustArchi for his commit regarding optimizations in Android builds. What are these optimizations? Check out THIS THREAD for more details on what this entails. In most basic terms, this optimizes code within the build a lot more than the traditional flags set by the code I build from. You may not see a doubled AnTuTu score, or doubled battery life. But this provides a lot more stability and smoothness than simply using the Sabermod toolchain that is also included in these builds. So props to him for this commit. Go give the man some thanks!
Special Thanks
Let me do this first and foremost before moving on with the downloads and installation instructions. This would not be possible without the help and guidance of a few other talented builders here in our community, and without the help of those who tested this before it was posted.
Thanks to @rogersb11 and @cyril279 for helping me out along the way. Their guidance and support have been most beneficial, and without that help, this thread wouldn't be here. So if you thank me, be sure to thank them too!
Thanks to the entire Carbon Team for the hard work they put into building such an amazing AOSP rom.
Thanks to my testers, @cyril279, @edwin270, @rogersb11 and @dsteele for being brave enough to be the first people outside of myself to take this new build for a spin.
To anyone else who has helped me along the way in my Android experience and journey from noob to only partially, just a bit of a noob. Your guidance and support has been appreciated more than you could know.
Download and Installation Instructions
As always, neither I, nor the people thanked in this thread, nor your neighbor are responsible for anything that may happen to your device including, but certainly not limited to: Soft Brick, Hard Brick, Exploding Batteries, One Fish, Two Fish, Red Fish, Blue Fish, raining porcupines, or male patterned baldness.
**IMPORTANT: If you are coming from ICS or JB, you MUST upgrade your recovery BEFORE flashing this rom. See below for compatible recoveries**
CWM - 6.0.4.4+
TWRP - 2.6.3.0+
For SGH-S959G
CWM - 6.0.4.5 from here
TWRP - 2.6.3.0 from here
1) Download the latest build from here (Current Build: 12/08 ). Older builds can be found here.
2) Download the Gapps pack of your choice. (I personally use Slim Minimal 4.4.4 which you can find here). But feel free to use whichever Gapps package you prefer.
3) FULL WIPE if coming from any other rom. If updating, wipe cache/dalvic before flashing, unless stated to do a full wipe.
4) Flash the ROM package
5) Flash Gapps package of your choice
6) (Optional) Reboot recovery, wipe dalvic/cache. (Recommended if you are coming from a custom kernel build.
7) Reboot device and enjoy the goodness.
SPECIAL NOTES
This will flash with the stock CM kernel with CWM Recovery, which many people find a little laggy. There are custom kernels in the forums that you can flash after the rom if you want more control, performance, stability, etc.
This is built straight from the source code found on the CarbonDev Github. The only things that have been changed are the removal of CarbonDelta and ROM Stats. Since these are unofficial builds, not supported by the Carbon team, these two apps really serve us no purpose. All updates will need to be flashed through recovery.
All bugs or questions should be reported to THIS THREAD ONLY. Do not send questions to the Carbon Team as this is not an officially supported device anymore. So don't bother them. Bother me instead.
For general CarbonRom questions, check out the FAQ.
That's all I have for now. If you enjoy this rom, please hit that thanks button and inflate my ego a little bit.
Happy flashing!
ROM: CarbonRom (Unofficial Builds)
Android Version: 4.4.4
Kernel: Stock CM Kernel Source
Built by: @TheGeekyNimrod
Reserved because you never know when you might want that second post spot.
Here we go...booting as I type...
desteele said:
Here we go...booting as I type...
Click to expand...
Click to collapse
Woo hoo!
Sent from my SAMSUNG-SGH-I747
TheGeekyNimrod said:
Woo hoo!
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
OK, I don't have a BT device, but almost everything seems very smooth and functional. USB connections/transfers seem fine, and mobile data almost seems fine. I can download web content in the browser, but never could get the playstore to download any apps. It pulled up and went through the steps to say it was downloading, but the app never actually got pulled down.
Pretty good stuff to this point though...
Also, it didn't set up my google account when I was setting it up, that's usually an included step. I didn't realize it til I opened the Play Store and then it went through the Google setup.
Edit: rebooted and a playstore download started up... it just seems a little finicky about beginning to pull. I don't have full signal at home, but was getting 3 of 4 bars most of the time.
That sounds more like just a bum install of Gapps. Especially if it didn't ask for Google Account right off the bat. I've had that happen before. Usually not a rom or Gapps package issue, but just something hanging in the flashing process.
Glad to hear everything else went fine. I'll do another fresh install on mine in the morning and see if the same issue crops up.
Sent from my SAMSUNG-SGH-I747
desteele said:
OK, I don't have a BT device, but almost everything seems very smooth and functional. USB connections/transfers seem fine, and mobile data almost seems fine. I can download web content in the browser, but never could get the playstore to download any apps. It pulled up and went through the steps to say it was downloading, but the app never actually got pulled down.
Pretty good stuff to this point though...
Also, it didn't set up my google account when I was setting it up, that's usually an included step. I didn't realize it til I opened the Play Store and then it went through the Google setup.
Edit: rebooted and a playstore download started up... it just seems a little finicky about beginning to pull. I don't have full signal at home, but was getting 3 of 4 bars most of the time.
Click to expand...
Click to collapse
For network I am always on 2g unless i do want to use the phone data( which i mostly never use, always on wifi). Sure 3g signal is not so strong from within your room.
When done with rom flash, I made it boot first. Then went ahead to set it up without google account, when back to recovery and flashed gapps.
Finally, after changing to "art" runtime I launched playstore then did setup my google account.
So far, so good............just about to pull my battery stat, to be sure it last as it should be. All my apps are running great so far.
NOTE: be sure to wipe/factory reset 3 times. Since previous gapps could be left untouched. I again make sure i wipe data, cache, dalvik cache again respectively, so to be certain.
Let me know how the battery stats look. I haven't really tested that, but mine is running with the RB11-Shift kernel so it would be different than if I had the stock kernel with it.
Sent from my SAMSUNG-SGH-I747
Well, baking overnight and possibly stronger signal downtown seems to have cured whatever mobile data issue I was having. I've done a couple of d/l's here at work, and it jumped on them fairly quickly, and the transfer rate seemed in line with what I normally get.
Did they include Heads-up?
TheGeekyNimrod said:
Let me know how the battery stats look. I haven't really tested that, but mine is running with the RB11-Shift kernel so it would be different than if I had the stock kernel with it.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Had I decent amount of random screen lighting up lol. I have a logger running now so we'll see what happens. Other than that I've been pushing this thing
desteele said:
Well, baking overnight and possibly stronger signal downtown seems to have cured whatever mobile data issue I was having. I've done a couple of d/l's here at work, and it jumped on them fairly quickly, and the transfer rate seemed in line with what I normally get.
Did they include Heads-up?
Click to expand...
Click to collapse
Yeah!, heads up is included though there is no "personal" settings for it anywhere. To enable pull down the notification drawer look at the top right. The first icon before the tiles icon.
Working perfect even for non-intrusive calls here.
edwin270 said:
Yeah!, heads up is included though there is no "personal" settings for it anywhere. To enable pull down the notification drawer look at the top right. The first icon before the tiles icon.
Working perfect even for non-intrusive calls here.
Click to expand...
Click to collapse
You can disable it for specific apps from Settings>Apps ... Go over to all apps. Select the app you want to disable it on, select blacklist, and select blacklist from hover.
Sent from my SAMSUNG-SGH-I747
rogersb11 said:
Had I decent amount of random screen lighting up lol. I have a logger running now so we'll see what happens. Other than that I've been pushing this thing
Click to expand...
Click to collapse
I've noticed that with Carbon on my S3 too. Let me know if the logger turns up anything helpful and I'll do some research and see what I can do for it. I'll be running another build off on Friday.
Sent from my SAMSUNG-SGH-I747
TheGeekyNimrod said:
I've noticed that with Carbon on my S3 too. Let me know if the logger turns up anything helpful and I'll do some research and see what I can do for it. I'll be running another build off on Friday.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Hmmmm............how come i have never seen anything of such.
Guess must be the lockscreen notification stuff, i reconfigured mine to turn on only when i have a notification, by default it is on and guess that has a sure trigger..............just my thought.
Have no screen issue. Even turn off screen animation is disabled
edwin270 said:
Hmmmm............how come i have never seen anything of such.
Guess must be the lockscreen notification stuff, i reconfigured mine to turn on only when i have a notification, by default it is on and guess that has a sure trigger..............just my thought.
Have no screen issue. Even turn off screen animation is disabled
Click to expand...
Click to collapse
Pocket mode is a lot of what's behind it I think. Using the proximity sensor and turning the screen on. I disable it right off the bat.
Sent from my SAMSUNG-SGH-I747
Pocket mode it was. Thanks for pointing that out, I had no clue
Sent from my SGH-I777 using XDA Premium 4 mobile app
rogersb11 said:
Pocket mode it was. Thanks for pointing that out, I had no clue
Sent from my SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perhaps I should change up the OP and second post and leave a list of features and such? For granted, the link in the current OP will take you to the Carbon website where it's all listed.
It didn't hit me until I messaged you about the pocket mode. It took me a while after first porting it to realize what was going on. By habit now I always automatically disable it right off the bat when I flash it.
I'm going to be running off a build tonight that, if everything goes as it should, means the ROM will be built with Sabermod toolchain. Thanks to @rogersb11 once again for helping me get the necessary changes done to be sure it's going to build right. I'll test it on my own device tomorrow and if all is good I'll post it up sometime tomorrow afternoon.
TheGeekyNimrod said:
I'm going to be running off a build tonight that, if everything goes as it should, means the ROM will be built with Sabermod toolchain. Thanks to @rogersb11 once again for helping me get the necessary changes done to be sure it's going to build right. I'll test it on my own device tomorrow and if all is good I'll post it up sometime tomorrow afternoon.
Click to expand...
Click to collapse
Don't start just yet
Sent from my GT-N7105 using XDA Premium 4 mobile app
rogersb11 said:
Don't start just yet
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
- I haven't yet. Won't start it till later tonight. I let it run while I'm catching my Zzzzs.