The ROM is retired. The final version can be downloaded from here:
http://forum.xda-developers.com/showpost.php?p=58493801&postcount=339
Click to expand...
Click to collapse
This is a tweaked versions of CARBON-JB-UNOFFICIAL-B11 so all credit goes to killersloth for the ROM. Without his work this ROM wouldn't be possible. So if you like this ROM please go to the CARBON ROM thread and click the "Thanks" button.
Changes Made:
Replaced Trebuchet launcher with Nova launcher.
Replaced stock gallery with Sony Z Album and Movie app (Facebook & Twitter integration working.)
Added Sony Z Walkman app with UPNP/DLNA Media Server.
Replaced the default kernel with the kernel from CM10.1 Stable by verygreen.
Added BeatsAudio+xLoud+ClearAudio for audio effects and ViPER4Android for the sound engine. Settings I am using.
Added Mobile BRAVIA® Engine for improved video processing.
Modified Adobe Flash 11.1 with Hulu support.
Host level ad blocking. If you are having issues with adblocking see attachments to remove it.
Forced all rendering to be done on the GPU. Should help with gaming and make things more smoother. To help improve performance even further see this post.
GoogleEars.
Kick Ass Kernelizer
Auto-zipalign and defragdb on boot
Auto Calibration on boot. Only does a few programs each boot. So may take a few reboots to calibrate all of them.
Plus many improvements taken from this thread.
I also added some terminal commands.
Run each command with SU first then the command.
fixfc - Fix apps force closing.
sclean - Clean the dalvik cache and cache partition
v6 - run the V6 SuperCharger script. I would run this as soon as the ROM is setup..
Know bugs
Not a bug as such but something you should be aware of. It does take a few reboots to optimise all the apps.
V4A XHiFi may do a hot reboot when first getting root, same with Root Browser. This will only happen once and will work fine afterwards. This is only normally an issue if you try getting ROOT on first boot. On the second reboot this doesn't happen.
Wifi will turn off then back on while it is setting up wl1271-nvs.bin. Once the file is created Wifi shouldn't disconnect.
Any more issues please report them.
Xperia-2.3.9-CARBON-JB-B11-ovation.zip - 294.19 MB
MD5: 05483bc421eb793c9ccf0113323b406d
For the latest version using Google Now Launcher use this rom: http://forum.xda-developers.com/showpost.php?p=58493801&postcount=339
Wallpaper: http://blankid.deviantart.com/art/Escape2-347788407
If you would like to use the WALKMAN app from the Sony Xperia Z Ultra you can do so by flashing this: Xperia-Ultra_WALKMAN_SemcMusic.zip. Make sure you boot into the ROM before flashing. If you flash this without booting into the ROM first it will not work.
Most of the features in the Sony Xperia Z Ultra WALKMAN are working but "Music Unlimited" service isn't.
Thank you, I will give it a try.
Do we use the gapps from the original carbon threads?
And how do you flash the scrips? Just like any other zip file? Can it be done when installing this ROM ?
JDMpire said:
Do we use the gapps from the original carbon threads?
And how do you flash the scrips? Just like any other zip file? Can it be done when installing this ROM ?
Click to expand...
Click to collapse
I just added the scripts as a separate download so other devs can take a look at them without downloading the whole ROM. All the scripts are included in the ROM. Everything you need is built into the ROM. Just download it and install.
unstable
I installed on top of Carbon B9 without wiping anything and everything was forceclosing.Then I wiped cache partiion and Dalvick cache and reinstalled ,it was usable thistime but several apps still forceclosing including Chrome,I went back to Carbon.
akramarshad said:
I installed on top of Carbon B9 without wiping anything and everything was forceclosing.Then I wiped cache partiion and Dalvick cache and reinstalled ,it was usable thistime but several apps still forceclosing including Chrome,I went back to Carbon.
Click to expand...
Click to collapse
If you did not install with full wipe I am note sure it is fair to mark it as unstable. Did you even attempt to clear the app data for the apps foreclosing?
have not tried this yet but just thought labeling the effort as unstable prior to proper install is not fair.
akramarshad said:
I installed on top of Carbon B9 without wiping anything and everything was forceclosing.Then I wiped cache partiion and Dalvick cache and reinstalled ,it was usable thistime but several apps still forceclosing including Chrome,I went back to Carbon.
Click to expand...
Click to collapse
Just installed with full wipe restoring apps and data from TB. So far everything is ok.
Feels slightly less laggy than B9.
Dunno about battery life yet.
This is working great for me.
I did a dirty flash over RootBox and it's really nice.
Been the best rom for me on my Nook so far. Pinguy1982, please keep the thread updated mate.
Only issue I had was my usual
Android.process.acore has stopped
Which I resolved by following the text below. (cribbed from somewhere on the net)
If you go to Settings/Applications/Manage Applications/ then choose the All tab. Scroll down to Contacts open it and clear the data cache. Now do the same again but this time open Contact Storage and also clear the data cache. This issue is related to an Android bug and affects many devices. It's related to apps that use the sync function.
Works for me.
Cheers all
mcord11758 said:
If you did not install with full wipe I am note sure it is fair to mark it as unstable. Did you even attempt to clear the app data for the apps foreclosing?
have not tried this yet but just thought labeling the effort as unstable prior to proper install is not fair.
Click to expand...
Click to collapse
I agree completely and would urge the poster to revise his comment or certainly remove the subject. Way too hasty and unfair to make such a quick judgment certainly in the absence of a full or data wipe.
RustedRoot said:
I agree completely and would urge the poster to revise his comment or certainly remove the subject. Way too hasty and unfair to make such a quick judgment certainly in the absence of a full or data wipe.
Click to expand...
Click to collapse
Sorry if I offended you.My understanding is that you wipe data only if you are installing in place of different ROM.It was carbon on top of Carbonand I did not feel I needed to wipe data partition.
akramarshad said:
Sorry if I offended you.My understanding is that you wipe data only if you are installing in place of different ROM.It was carbon on top of Carbonand I did not feel I needed to wipe data partition.
Click to expand...
Click to collapse
Dude it's all cool. But I have changed a fair bit to the ROM so just installing over it probably won't work. I have made drastic changes to how dalvik works so using pre-installed apps from a previous install probably won't work.
Sent from my Nook HD+ using Tapatalk HD
Do you mind building a version for the Nook HD ?
so using apps from titanium backup would be a problem?
bckrupps said:
so using apps from titanium backup would be a problem?
Click to expand...
Click to collapse
Apps no, dalvik cache maybe. Restoring apps settings and the apps won't be a problem, but using the dalvik cache might be.
The cache is in /data/dalvik-cache. Using that maybe an issue.
pinguy1982 said:
Apps no, dalvik cache maybe. The apps settings and the app won't be a problem, but using the dalvik cache might be.
The cache is in /data/dalvik-cache. Using that maybe an issue.
Click to expand...
Click to collapse
thanks.I always clear out dalvik cache anyway when I try new stuff. I was thinking of trying it. the new build of cm 10.1 seems to match up with my tablet perfectly so we will see. thanks for the ROM. the more the better
akramarshad said:
I installed on top of Carbon B9 without wiping anything and everything was forceclosing.Then I wiped cache partiion and Dalvick cache and reinstalled ,it was usable thistime but several apps still forceclosing including Chrome,I went back to Carbon.
Click to expand...
Click to collapse
I did this too, but wiped dalvik, no force closes, but status bar is gone and can't get it back... going to try flashing again...
Just flashed a couple of hours ago and seems pretty rad so far. I'll give it some time to "settle" before passing judgement. Definitely like the idea!
Good to see more options around here. My hat goes off to all devs.
Sent from my Nook HD+ using xda app-developers app
Just flashed it ... Can't see the option "Reboot into recovery" when holding the power button. Is there anyone I can enable it ?
nocloo said:
Just flashed it ... Can't see the option "Reboot into recovery" when holding the power button. Is there anyone I can enable it ?
Click to expand...
Click to collapse
Settings-system-power menu-reboot menu
Battery drain so far seems to be no worse than B9 for me.
Definitely like this ROM, it is faster and smoother than any other I tried for my Nook, seems quite stable as well (no random reboots etc.)
I start with a fresh wipe of my phone and then install BeanStalk with gapps (I'm currently using BS version 4.4.275 with gapps 20140105. Everything is fine for months. Then a couple of apps will start to crash a few times (the camera, dialer, browser and google apps). I've stopped using titanium backup and clockwork mod to restore my data because they were causing issues. Then the force closes become more and more frequent. I ran fix permissions and i have know clue if it helped or not. Then finally all hell breaks loose and everything begins to force close and give errors of no space left on phone. No launcher will stay open everything just bugs out. This seems to be an on going matter. It doesn't seem to resolve no matter what rom I run. I've gone through every folder sizing it and my phone is not out of space. I am getting very frustrated with my Infuse. I don't understand what some of the stuff means in my catlog file. If someone could help I'd greatly appreciate it.
i found out that Google+ and Google Drive might be the cause (such as when you upload or backup your photos to those clouds)
if you have time, go read those last 10 pages of BeanStalks, you will see what others have offered to resolve this issues
as for me, I'd do full wipe, specially format the sdcard0 (keep the Rom and Gapps to your SDcard1), and stop using the two Google services mentioned above. and use another Gapps (I am using the minimal one) Good luck!
Same problem with Unofficial CM 11.2 also
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Unable to get RSA prompt
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
hemen_kap said:
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
Click to expand...
Click to collapse
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
joel.maxuel said:
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
Click to expand...
Click to collapse
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
hemen_kap said:
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
Click to expand...
Click to collapse
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
joel.maxuel said:
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
Click to expand...
Click to collapse
Unfortunately the infuse is the only phone I have (so my DD)...but the lure to test the ADB on carbon is also compelling for me. Let me try moving to a non smart phone and try this out.
OK. So i installed the Carbon KK nightly, and encountered the same issue. adb devices always lists the phone as
0123456789ABCDEF unauthorized.
Also i never received the rsa prompt...
Moreover the device key seems to suggest it is some default value as compared to an actual device key.
Got it Working !!!
Ok so finally got it working.
I moved away from Scott's Unofficial CM11_2 on my daily driver and moved to Carbon ROM. Loving the new rom so far.
Once i moved to this ROM, I started adb on my desktop (adb kill-server, adb start-server) and was waiting
then on phone enabled Developer options and Android debugging over USB and connected the phone to desktop, and zingggg I get the RSA prompt.
One important thing it read is that you phone should be unlocked when you connect it to your desktop, so in case you have things like PIN or gestures that lock your screen....ensure that your screen is not locked when the phone is being connected.
Not sure if this was the issue or if it was the CM rom,,,but issue is resolved, I am loving Carbon...so not going back to CM to check the lockscreen theory....but worth a try for someone who is pulling his/her hair out like i was.
Ciao !!!
---------- Post added at 05:00 PM ---------- Previous post was at 04:41 PM ----------
missed mentioning that do not worry about the device id of 0123456789ABCDEF....i noticed it does not change for me even when adb connects properly.
It is the unauthorised state that needs to change to device.
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
joel.maxuel said:
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
Click to expand...
Click to collapse
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
hemen_kap said:
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
Click to expand...
Click to collapse
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
jloibman said:
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Click to expand...
Click to collapse
Not sure about this, but I think CM 11.2 is referred to as KitKat 4.4.4, which would be latest in the CM thread. So you are probably already running it.
Sent from my Asus MeMO Pad 8"
jloibman said:
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
Click to expand...
Click to collapse
apart from the issues that i mentioned - my experience with CM 11.2 has been great. There are some obvious things like MHL etc that do not work, but those are known issues.
joel.maxuel said:
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
Click to expand...
Click to collapse
You can download the Nova Launcher from the google play store if you want to have the same experience as with Scotts Beanstalk. I love the carbon ROM but I am so accustomed to the Nova launcher that I cant live without it.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
-Hemen
hemen_kap said:
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
Click to expand...
Click to collapse
Hmm, don't think I kept a ROM on my Infuse long enough to encounter this problem (except for my several months with CM 10.1, no issues). As for other phones, I use Jellybean on my semi-retired HTC and did not have this problem (closest I came was when I tried out Fly-On mod - lag closures often). But I don't think It's a Jellybean problem.
I think (and this may have been covered already) this has to do with the piddly datadata partition filling up. One way to check is open a terminal emulator (app on the phone of adb shell) and type:
Code:
df
Look for datadata in that listing. If it is in the 90% range, that spells trouble. If that is the case, you could try one of two solutions.
I don't know what possessed the developers to separate the data partitions in KitKat (I know, for "performance reasons") but leave 1/2 a GB for it. Lower end phones these days give you twice that.
Over the past few years or so I've installed ROMs going back to ICS. 99% of the time there was absolutely no issue. I habitually do a (1) factory wipe, (2) dalvik wipe, (3) system format, (4) sdcard0 format, (5) install ROM zip, (6) install gapps, (7) wipe cache and (8) wipe dalvik.
In the hundreds of ROMs I've installed and tested, 1 or 2 were bad compiles, and everyone soon knew it. They were immediately removed from any host site. So, if you're having issues, (1) install you ROM as above, (2) perhaps install a smaller gapps, and/or (3) check that you're not overloading your phone from the PlayStore.
The last and rarest issue could be your phone, but rule of thumb that works 99% of the time is: (1) assume it's always your fault first, and (2) read, read, read, read, read.