FORUMS

Floating Apps with Rovers – XDA App Review

There are a lot of great launchers to help customize your phone. Some Launchers allow … more

What Features Do You Look for in a Gallery App?

With so many different options to choose from, finding the right Gallery app may be a … more

Google Photos ‘Unlimited’ Storage Reportedly Being Capped

When Google Photos was announced, many of us thought very highly … more

Sprint Moves to Lift Video Streaming Limit for All-In

Yesterday, Sprint announced a new unlimited scheme that offered customers an … more

[ROM][AOSP][Nightly/Release] CarbonRom KitKat [d2att/d2cri/d2mtr/d2usc]

425 posts
Thanks Meter: 3,039
 
Post Reply Subscribe to Thread Email Thread
14th June 2015, 07:01 PM |#581  
MJPollard's Avatar
Senior Member
Flag Wixom, Michigan
Thanks Meter: 757
 
More
Quote:
Originally Posted by ocd_amp

Why don't you just link to the Framework-res I made for this ROM so for those who are using it right now will be able to flash it and have their CPU go into sleep mode correctly - I did email you about it - It works, so until you figure out whatever it is you were trying to do, just link to my Framework for the time being to help these folks out.

Page 56 - http://forum.xda-developers.com/show...634641&page=56

I know, and I appreciate the work. Like I said, real life got in the way for a little while, and the PMs on this site (I have several) were on the list. This will be a good fix for the short term, and I'll see about getting that put together this week. Thanks!
 
 
21st June 2015, 11:35 PM |#582  
Right2Bear's Avatar
Member
Thanks Meter: 9
 
More
I am running an older nightly on mine
Carbon-kk-nightly-20140828-0903
Well the issue is the camera crashes when you try and open it. It used to work but at some point stopped. I only know because my daughter is using the phone since she broke hers for the third time. She also has had issues at times where the battery drains really quickly. Any ideas? Should I download and install the most recent nightly? help please
thanks
B3ar
22nd June 2015, 06:25 PM |#583  
MJPollard's Avatar
Senior Member
Flag Wixom, Michigan
Thanks Meter: 757
 
More
Quote:
Originally Posted by MJPollard

Weekly builds of Carbon-KitKat, dated 03/17/2015:

Samsung Galaxy S3 (d2lte):
Zip: http://www.mediafire.com/download/y5...0648-d2lte.zip
MD5: http://www.mediafire.com/download/73...lte.zip.md5sum

As always, these builds are provided without support of any kind, make a nandroid backup before installing, flash at your own risk, I accept no responsibility if your phone dies, blows up, or conquers the known universe, yada yada yada.

As promised, here's the link to the post which has a patch that eliminates the Google Play Services wakelock issue. If you already have this version of Carbon installed, simply download the patch file, copy it to your phone and flash it from recovery:

http://forum.xda-developers.com/show...&postcount=554

Much thanks to @ocd_amp who cooked it up and provided it to us! (I'll also update the post itself with a link to the patch.)

Now, I was going to compile another version of Carbon that had the fix cooked into it, but I ran into a problem: I can't get the d2lte version to compile anymore. It throws up errors that aborts the build. (The HTC One M8 version still compiles just fine, so it's definitely something related to d2lte.) Funny thing is, it was compiling just fine last Thursday, but when I re-synced the code and tried compiling on Friday, boom! it started failing. So, until I can track down the problem, further custom builds for the S3 are going to have to wait. (Not that there are any pressing issues that would warrant upgrading from my 3/17/2015 build; it's more of a "I'm gonna figure this out if it kills me, dammit!" intellectual challenge at this point. Since KitKat is now pretty much ignored, and Carbon-KK appears to be essentially abandoned, I'm not hopeful of a fix magically appearing any time soon, if ever, so if it's going to be fixed, I'm the one who's going to have to do it.)
23rd June 2015, 01:30 AM |#584  
Senior Member
Thanks Meter: 118
 
More
Martin thanks for you response - I have been very busy to reply in this thread lately.

IMPORTANT INFO. I advise all users to read Carefully before posting.

EDIT : WARNING : Samsung Has Backup Partitions where your NVData (IMEI EFS Etc) goes. In all their Wisdom, The Backup Partitions were Zeroed by Default from Factory, leaving only the Functional Partition with important EFS Data on your Devices. It is HIGHLY Advisable to use EFS Professional and ADB to do an NVBackup of your WORKING Set BEFORE You do any Flashing to ensure your IMEI will not get Wiped to Zero. If your EFS gets Corrupted, and an attempt is made to Restore from Not-Backed-Up Partitions, you will end up with headaches you are not ready for.

D2LTE has been deprecated - Cyanogenmod is now focusing on CM12 and have gone back to doing separate builds due to the differences in the way Boot/RIL operations were handled so it is back to D2ATT for Galaxy I747/M AFAIK.

Unified builds had many issues - One being the Radio from 4.1.1/4.1.2 - So although the Bootloader from Stock 4.1.1/4.1.2 allows for Cyanogenmod/based KK 4.4.4 to be Flashed without checking signatures (odd) the Radio will fail.

To update the Radio, YOU MUST Flash the matching Bootloader 4.3+ (4.4.2 Recommended, Check SAMOBILE Website) which essentially Introduces KNOX into the equation. However, the latest Official Samsung Firmware 4.4.2 - As far as I know for Fido customers does not lock the Bootloader and CM 12.1 Lollipop D2ATT Nightlies can be flashed Re-Enabling the RIL functions once again. You can check this by Dialing *#*#4636#*#*

So if by some anomaly, you were on 4.1.1-4.1.2 Bootloader/Radio - and you were able to get LTE Data, You need to do nothing. Just Flash Framework-Res I created and your Wakelock issues will be solved..

If you do NOT get Data, you will need to ODIN Flash to the latest 4.4.2 for your respective Carrier. Be Careful though, I do not have much information on U.S. based Carriers but AT&T, VERIZON, TMO are known to play Dirty and Introduce Locked Bootloaders. AT&T Radios are RAT Locked, while Roger's/Fido are NOT.

A Locked Bootloader will prevent you from installing ANY custom ROM. Also, Carrier/Manufacturer will NEVER Unlock your Bootloader and both Samsung and Carrier will give you a Run-Around-The-Round-About - But they can be defeated by going directly to a Third-party.
So Make sure you guys READ READ READ about your Respective Bootloaders.

A LOCKED Bootloader will Prevent you from installing Custom ROM and make it difficult to attain Permanent Root.
A LOCKED Bootloader after 4.3 WILL contain KNOX.
An UNLOCKED Bootloader is NOT the same thing as a CARRIER OR SIM UNLOCK.
An UNLOCKED Bootloader after 4.3 WILL contain KNOX.

Do NOT Downgrade your Bootloader / Modem if you are on 4.3+ - This means, DO NOT ODIN Flash an older stock ROM, and DO NOT Flash older Bootloader/Radio Zips from Recovery if you are on 4.3 Boot/Radio - The only way is UP after this. Downgrading will Brick the device. Upgrading will KNOX your Device. Stay or Move Up Only.

There is a Difference between Custom ROM Android versions vs Carrier or STOCK ROM Android versions. STOCK ROM Versions contain more than just the ROM. They can contain Bootloaders, Radios, CSC, Etc. So when I mention 4.x, I am talking about STOCK ROM, which is Flashable ONLY through ODIN. Be CAREFUL.

Once KNOX is Tripped, It CANNOT Be Reversed. If you are about Warranty, Leave it. Although everyone should already have had their Warranty expired by now.
You WILL Trip your KNOX by ODIN Flashing TWRP Recovery - I did it. I am not concerned about this at all. Other than that, it will have no Ill-effect on your Device if you are not using it in a Corporate Environment that Requires the use of a KNOX Enabled Device.

If you are SURE You need to upgrade - and you are on 4.1.1 - You can SIM Unlock your Phone First, but be sure to turn PersoSHA 256 back to ON position.
If you are on 4.1.2, you can Downgrade Flash to 4.1.1 to do this process. This information is widely available all over XDA.

Once you Upgrade to Carrier ROM 4.4.2 with its New Bootloader, and Radio, you will NOT Be able to SIM Unlock your Device. You will have to Pay to get it unlocked.

After your Radio update, LTE Data should work without issue.

Remember to Read carefully, and plan ahead in order to avoid embarrassing and costly mistakes.

Thanks for keeping it going MJ, best Regards!
Last edited by ocd_amp; 23rd June 2015 at 01:44 AM.
The Following User Says Thank You to ocd_amp For This Useful Post: [ View ]
23rd June 2015, 03:28 AM |#585  
MJPollard's Avatar
Senior Member
Flag Wixom, Michigan
Thanks Meter: 757
 
More
Another interesting thing: CyanogenMod appears to be removing builds from the CM11 tree that have official CM12 builds, including d2lte (now d2att, et al). However, I was able to hack an entry for d2lte into android_vendor_cm/vendorsetup.sh, and lo and behold, I was able to make a complete CM11 build without errors. So, whatever changed that's preventing a d2lte Carbon build from completing, it's affecting just Carbon, not CM. Just one more thing to add to the list.
The Following User Says Thank You to MJPollard For This Useful Post: [ View ]
26th June 2015, 03:46 PM |#586  
MJPollard's Avatar
Senior Member
Flag Wixom, Michigan
Thanks Meter: 757
 
More
MY CUSTOM UNOFFICIAL BUILDS OF CARBON-KITKAT

Changelog:
- all: All current commits that are common to both CM11 and Carbon-KK.
- m8: Fix for speaker squealing and then "buzzing" (until phone is rebooted) after a ringtone plays.
- m8: Fix for Google Play Services wakelog preventing phone from going into deep sleep.

----------

HTC One M8 (m8) - 06/23/2015:
Zip: http://www.mediafire.com/download/y7...23-0809-m8.zip
MD5: http://www.mediafire.com/download/ph...-m8.zip.md5sum

----------

Samsung Galaxy S3 (d2lte) - 03/17/2015:
Zip: http://www.mediafire.com/download/y5...0648-d2lte.zip
MD5: http://www.mediafire.com/download/73...lte.zip.md5sum

NOTE: Currently, I am unable to compile up to date d2lte releases due to a weird build error that I recently started getting. Until this is resolved, the 3/17/2015 release is the most up to date version that I can provide, with apologies.

There is, however, a fix for the Google Play Services wakelock issue in the form of a patch (thanks to ocd_amp) that can be flashed (via recovery) on top of the 3/17/2015 version. DO NOT FLASH THIS PATCH IF YOU ARE NOT RUNNING MY CUSTOM CARBON-KK BUILD DATED 3/17/2015!!!

Zip: http://www.mediafire.com/download/6n..._Flashable.zip
MD5: http://www.mediafire.com/download/g3...ble.zip.md5sum

----------

As always, these builds are provided without support of any kind, make a nandroid backup before installing, flash at your own risk, I accept no responsibility if your phone dies, blows up, or conquers the known universe, batteries not included, void where prohibited, yada yada yada.
The Following 2 Users Say Thank You to MJPollard For This Useful Post: [ View ]
Yesterday, 01:17 AM |#587  
Member
Thanks Meter: 1
 
More
Hi.
I just got an S3 (i747) and installed this ROM instantly. It's my favorite of all the ones I've tried (on other phones). I've noticed a glitch, however, when I use Wi-Fi then turn it off. I can go the rest of the day without Wi-Fi being on but when I check battery stats, it shows that Wi-Fi has been on all day long...even though the button is clearly turned off. Rebooting fixes the issue.
Any solution to this without rebooting? I can't confirm this yet but it seems it may lead to some battery drain. I have flashed the fix for the Google Services wakelock and the phone does sleep as expected....it just shows that Wi-Fi was on even when I know it wasn't.
Thanks for any advice, and especially for the ROM.
Yesterday, 08:58 AM |#588  
cLogic's Avatar
Senior Member
Flag Montreal
Thanks Meter: 127
 
More
Quote:
Originally Posted by mn1968

Hi.
I just got an S3 (i747) and installed this ROM instantly. It's my favorite of all the ones I've tried (on other phones). I've noticed a glitch, however, when I use Wi-Fi then turn it off. I can go the rest of the day without Wi-Fi being on but when I check battery stats, it shows that Wi-Fi has been on all day long...even though the button is clearly turned off. Rebooting fixes the issue.
Any solution to this without rebooting? I can't confirm this yet but it seems it may lead to some battery drain. I have flashed the fix for the Google Services wakelock and the phone does sleep as expected....it just shows that Wi-Fi was on even when I know it wasn't.
Thanks for any advice, and especially for the ROM.

check wifi advanced settings
it is probably "always on" and "never sleep" because this device and all newer devices should be set this way

turning wifi/data/sync off and on periodically does NOT save battery on modern devices running jellybean 4.1 or better

in fact it actually uses more battery cuz apps try to update/sync and stay alive/awake longer, using more cpu cycles, waiting for their request for wifi/data to timeout

I used juice defender and green power prior to jb 4.1 .. but they were just killing battery after that .. battery saver apps have been rendered obsolete by 4.1+
Yesterday, 04:45 PM |#589  
Member
Thanks Meter: 1
 
More
@cLogic
Thanks! That did the trick.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes