yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] OfficerJimLahey:
Or use the mention feature - start with an "@" (without quotes), then proceed to type the username - a list of usernames will appear below the editor. Click on the right one and you've added a mention! :cowboy:

Not quite. /datadata takes up ~500MB (or 1/2GB) of disk space. /data is allotted ~13GB! What this ROM is doing is saying "Hey, app data, you live on the data partition now", but the cups/partitions are not combined. There is an unused partition on the device now, but the likelihood of (accidentally) filling up /data, just because you didn't have 1/2 GB to spare seems pretty slim to me when you have 13GB to work with.

Of course, this is just me coming from current devices with 4GB ROM's and thus 1 to 1 1/2 GB /data partitions. :cowboy:

Your hard limit will be the ~13GB now. Unless you download a lot of games, you shouldn't run into difficulties. According to CM, there will be a performance hit by not using /datadata, but it's all the same SSD anyway.

The big caveat is that recovery still recognizes the /datadata partition (at least for any backups), so you will need to back up all your apps in Titanium, wipe, flash (the usual bit), and then restore your apps. Nandroid your entire system anyway for safe keeping before wiping, but you should find this build a bit more flexible than what was offered before.
[Samsung Infuse 4G] twiztid_:
I've switched back to Dalvik. Overall it feels faster than ART, plus the ROM seems faster than the 2014-11-02 builds. One thing I have noticed, I was on a call for around 30 seconds, and my battery dropped hard. It could be that the reading was inaccurate, and/or that it wasn't fully charged since my last install, but I have noticed this with another ROM as well. Some ROMs had good battery use during calls, others were bad. I'll look into this more and update the post.

As for the update checking, it seems to only do it once per day. I got two notifications yesterday, but it could have been on different installs. I unchecked the WiFi and Ethernet boxes, hopefully that stops the checks.

Either way, I'm loving the ROM so far. :) Thanks a million, Joel!
[Samsung Infuse 4G] PoXFreak:
Good, someone finally figured out how to disable the /datadata partition!

I'd flash this now but the infuse is my secondary device as of late.

But great to see someone making progress...

PoX
[Samsung Infuse 4G] CarbonROM:
We've recently brought our Gerrit online (http://review.carbonrom.org) and would ask that those pull requests be moved there if they have not been merged as of yet :)
[Samsung Infuse 4G] OfficerJimLahey:
Sorry, still down for me.

Unable to connect

Iceweasel can't establish a connection to the server at review.carbonrom.org.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Iceweasel is permitted to access the Web.

UPDATE:

Finally got connected, but now CarbonDev is no longer hosted in gerrit. Only CarbonROM github so only LP branches (and higher, when we get there). Sounds like if I do any other device builds with KK, I will just keep and use the local projects.
[Samsung Infuse 4G] PoXFreak:
On the subject of hard battery drain: which radio version are you using?

There are radios from the SGH-T959 that have been padded over to the infuse and they each have their benefits and drawbacks, but not one of them have hard battery drain in calls.

Search the development threads for infuse radio, I'm sure you'll find them.
[Samsung Infuse 4G] twiztid_:
Thanks for the info, I'll check it out.

It would seem that my initial battery usage was off a bit, and has "normalized" a bit since then. Battery use is a bit higher than the old one, but not significantly worse.
[Samsung Infuse 4G] oiphal:
The various modems are here:

http://xdaforums.com/showthread.php?t=1869159

I've used UCKD5, UCKI4 and UCLB3 (which is the default). I didn't honestly notice much of a difference with them but different areas are supposed to get different results. Battery/Performance does differ a bit but I can't say which is best. UCLB3 has seemed the most stable so I've stuck with it after some experimenting, but some of the others were definitely a bit faster or better battery life.

Same sort of deal with Dalvik vs ART, ART seems to offer some raw performance increase but it's still noticeably less stable than Dalvik even with the /data fix and we're not talking about a noticeable performance difference outside of benchmarks (8500 vs 7900 antutu scores aren't really going to blow anyone away). It also takes excessively long for any app to install or be optimized on ART and I had at least one random reboot using it.
[Samsung Infuse 4G] PoXFreak:
If you think app installs take excessively long on ART, try installing Facebook on a lollipop device.

I'm on the alpha team with them, and last night a 39mb update took over 15 minutes to complete.
[Samsung Infuse 4G] twiztid_:
I've had worse battery stats since installing Joel's new version, sadly. I don't think it's particularly a problem with higher usage, I think there's just something wrong with the battery monitoring stats... but with the auto-off feature, that distinction makes very little difference. Below are my battery stats for my overnight til afternoon. I had charged it til about 92% when I unplugged it, and had VERY little use with it after that.

I believe the issue is when it is not sitting on the charger "past" 100%, it doesn't actually fully charge. I noticed it a bit when I first installed the ROM, and the battery wasn't fully charged, but it got better after letting it charge overnight. But lately I've been charging it until it SAYS 100% and then removing the charger, and I think the pics I posted are the 'cumulative effect' of it not actually charging to 100% for a few weeks.

Has anyone run into this issue before? Is there a way to "reset" or "re-calibrate" it? Would using another battery monitor that is more accurate allow me to work around the phone shutting off when the built-in battery SAYS it is low? Or, could this just be my battery dying out?

While the % for Google Play Services and Android OS seem high, they're consistent with what I've seen in the past and had nearly 40hrs of battery time.
[Samsung Infuse 4G] OfficerJimLahey:
Hmm....the ROM would use the same battery stats as the official (CarbonDev), but there could be some additions to the ROM since the last official build that is throwing something off.

There is, however, an app for what you are looking to do. It's on Google Play, called something like "Battery Stats Calibration". It will delete the stats file and let the device sense where the 100% should be during the next charge. Works (IIRC) by charging fully (not just 100%), running the app, rebooting, draining fully, and then charging fully once more.

I had this problem for my other device a while back after getting a replacement battery. This app helped the situation to an extent.
[Samsung Infuse 4G] PoXFreak:
Listen guys and girls, the only reliable way to guarantee that you're getting the correct reading is to wipe battery stats when the device is fully charged, then let the phone "die". Then fully charge it and monitor the battery by dialing *#*#4636#*#*, then selecting "battery stats".

If the battery voltage drops below 3300mv before the percentage reads 0, then the stats are off or the battery is weak; try again. If the problem reoccurs, it's definitely the battery.
[Samsung Infuse 4G] twiztid_:
Thanks for the info.

The app I used, Advanced Battery Calibrator (Better, and more, reviews than the one Joel suggested), wipes the battery stats data, then shuts down your phone. It tells you to charge it to 100% before turning it back on. I've had it off charger for 17.5hrs and it's at 50% battery with light use, which is what I was getting before, so I think the issue is solved.

According to the Battery Info, my Level is at 49 of a 100 Scale, Health is good, voltage is 3718mV (36xx a min ago). I'll re-check on it later on as well to see if anything is out of whack. Thanks again.
[Samsung Infuse 4G] treehugger38294:
Anyone's GPS not working? I tried both the UCLB3 modem and UCKL2 and it doesn't seem to lock on. I can see satellites fine but it doesn't get a fix.
[Samsung Infuse 4G] mainwheel:
Help to go beyond 4.2.2

Hi,

In hoping to solve a Bluetooth messaging issue between my Infuse and my Subaru Starlink media system I have been walking my way up from GB 2.3.6 to where I am now. My last successful install is CM 10.1. I have had no difficulties with the upgrades, but they do not fix the Bluetooth messaging issue. All attempts to go further have failed. I have tried four different 4.4.x ROM versions, to include CM11, Beanstalk, and there were two slightly different downloads of CarbonROM KitKat, with the goal ultimately to get to CarbonROM kk and hopefully solve my problem.

The error I get with each of the failed installs is:

assert failed: run_program("/tmp/updater.sh") == 0

E:Error in /sdcard/CARBON-KK-NIGHTLY-20141102-0915-infuse4g.zip

(Status 7)

Installation aborted.

Of course, the error slightly different based on the ROM used. I have also tried placing the folder /Voodoo/lagfix/ to see if that helped. Same error.

Each time I am able to simply reboot into CM10.1.

If anyone has any idea of what might be going on, and how to fix it, I would greatly appreciate it.

George
[Samsung Infuse 4G] mainwheel:
I flashed the CarbonROM twice and that seems to have done it. The ROM installed.
[Samsung Infuse 4G] OfficerJimLahey:
Good to hear! Does the bluetooth sync with your car now?
[Samsung Infuse 4G] mainwheel:
No, messaging still does not work. Same response I've always gotten from the car, something like "the hands free device doesn't support this feature" when I try to select messaging. As before I started the upgrade process, the phone works fine, streaming audio works fine, apps work fine, and now the Starlink app, which did not work with GB 2.3.6 also works. Don't understand why messaging will not work. With everything else working so well, could it really be a hardware problem? Can't think of anything else to do. A setting to tweak perhaps?
[Samsung Infuse 4G] OfficerJimLahey:
Not sure if there is a tweak, maybe to see if MAP is disabled (shouldn't be). But maybe this is just a BT 3.0 vs 4.0 issue (like I presumed from the start).

After all, the specs for the device state:

Bluetooth v3.0, A2DP

Final thing to do (which is probably should have been the first thing) is check to see what your car supports and what it doesn't support.
[Samsung Infuse 4G] mainwheel:
What I found regarding Bluetooth requirements for the car system:

Profiles supported - HFP, SPP, OPP, PBAP, A2DP, AVRCP, MAP

Bluetooth versions:

Phone/Audio 1.1 3.0 +EDR

HFP 1.0 1.6

OPP 1.1 1.2

PBAP 1.0 1.1

MAP 1.0

SPP 1.1

A2DP 1.0 1.2

AVRCP 1.0 1.4

The first version number is the requirement, the second the recommended.

There is also a footnote that states, if the phone does not support HFP, using the other profiles individually may not work.

The info you looked at for the phone only lists the A2DP profile, but others are working, so I'm not sure what is or is not supported. Maybe it is HFP that is the issue. Is there a way to determine/test what profiles are actually supported on the phone? George

---------- Post added at 03:14 PM ---------- Previous post was at 02:19 PM ----------

Found some additional info on the Infuse:

Bluetooth®; Bluetooth® Profiles: A2DP, AVRCP, FTP, HFP, OPP, SPP; WiFi; WiF Hotspoti; HTML Browser; Flash®; Java™; GPS

The only ones not listed are MAP and PBAP. The phone book and contacts seem to load to the car (PBAP ?). Assuming it is MAP, is that something added by software?
[Samsung Infuse 4G] mainwheel:
Might be closer

After installing the CarbonROM I did not see any change in behavior regarding messaging with the car (hands free device doesn't support this feature). Today, I unpaired everything, then paired them again. I started getting an error message, and after some more work I realized it was asking permission to access messages on the phone. That is new. When I said OK it gave me the error and went into a loop of enabling and disabling Bluetooth on the phone. Not sure exactly what is was trying to do, maybe download messages? Starting the unpair/pair process over and saying NO to granting access avoids the error and everything else (phone and audio) works as usual. However, even saying NO, I now see that it at least thinks my phone supports messaging because there is a settings menu on the car system for messaging and email (didn't see that before either). I can play with the menu settings, but that's about it.

The message I receive on the phone:

Unfortunately, the process com.android.bluetooth has stopped

Any idea why the process is stopping when the car is granted access, and is there a solution?

Thanks. George
[Samsung Infuse 4G] OfficerJimLahey:
You could do a logcat to see what's happening, see where BT is failing. It would be a long output, so you can save it on pastebin and share the link if you like.

Btw, what version of Carbon are you running?
[Samsung Infuse 4G] mainwheel:
Will look into logcat.

In the meantime, the version is carbon-kk-nightly-20141102-0915, android version 4.4.4. This is the info reported under About Phone. I was doing something this morning, rebooting I think after clearing cache in an attempt to fix the Bluetooth messaging problem, when I got an "updating Carbon" message (not exact wording) and progress meter. So, I don't know what that was about.

Also (separate issue I believe), I don't know if this is specific to flashing Carbon, and if it is whether it occurred immediately upon flashing the ROM or happened at some point after (I don't use a lot of mobile data), but it seems I am not getting mobile data. It is checked in the settings, but every app I run says there is no internet connection. Phone and messaging work fine, and wifi. I don't know what else needs to be enabled, or if there is a problem.

George
[Samsung Infuse 4G] OfficerJimLahey:
"Updating carbon" is normal, as dalvik was wiped.

With regard to the network settings, your APNs are probably missing. Check them under network settings, and if necessary recreate them using info provided by AT&T (use your pc to search their site). ROMs rarely keep the APNs.
[Samsung Infuse 4G] mainwheel:
Thanks Joel.

Turns out the APNs are there (several ATT and SmartTalk), but for some reason it was using the "wrong" one, or one that doesn't work as well. I'm now using ATT Phone. There is also one just called ATT, which seems to work, although not sure they all work equally as well. The one it was set to when I was having difficulty was ATT LTE.
[Samsung Infuse 4G] mainwheel:
Joel,

I ran logcat, and as you say it is long. I saved it to a file and transferred to computer to work with, but I ended up with it all run together, so don't know if anyone could make sense of it. I did find the point where I think the error is happening, but I see a lot of yellow (orange?) entries throughout the log and have no idea what is normal. Anyway:

I know this is probably not useful:

D/BluetoothMapService( 1126): waiting for authorization for connection from: SUBARU BT

W/ContextImpl( 3080): Calling a method in the system process without a qualified user: This line begins several lines in yellow/orange

Followed by several entries, some of which seem to be permission requests, for example:

com.android.settings.bluetooth.BluetoothPermissionRequest.sendIntentToReceiver: 257

com.android.settings.bluetooth.BluetoothPermissionRequest.checkUserChoice:229

I can try to get an actual copy of the log, but not sure what is relevant. Maybe an HTML copy would work better. Also, what do the various colors represent?

Thanks. George
[Samsung Infuse 4G] OfficerJimLahey:
Try viewing it in Notepad++, or at least WordPad. The file will parse properly then, if using Windows. ;)
[Samsung Infuse 4G] mainwheel:
Well, maybe I don't know where in the log the error occurs after all. Stuff gets logged so quickly I'm not finding it, or for some reason I didn't capture it when I saved it to a file. Too frustrating trying to figure out what I'm looking for and what's relevant.

I had hoped it was a familiar problem with a known solution to try, but maybe it is not common.

Thanks for all your help Joel.
[Samsung Infuse 4G] OfficerJimLahey:
Should be able to search for "E/" and then look at the several lines above and few lines below. E/ are the error codes.
[Samsung Infuse 4G] Jammol:
You messages not showing up in your car is a software issue. Specifically that that feature is not enabled on your device's software. I found this out by doing some research into it because my wife's LG G2 does not support that feature in our Ford Taurus, however my Note 4 does. My Note 4 on KK when we first got it didn't support that feature either until I upgraded it to LP. Same thing with her G2 which is now on a custom T-Mobile Rom that's LP. Updated both phones and got in the car and suddenly text messages were being displayed and read out if we choose on the dash.

This feature will not work on AOSP based Roms unless it's baked into it. How to do that I have no idea.
[Samsung Infuse 4G] mainwheel:
Thanks Jammol for that info.

Funny that the car seems to recognize that it can do messaging with the phone running Carbon, but that's about all it does.

I have not found LP for the Samsung Infuse. I did read somewhere something about using ART instead of Dalvik as a possibility, but there are size issues, or memory, or something, and honestly I'm not sure I understand it all. And these were older messages (last year). George
[Samsung Infuse 4G] Jammol:
Yeah. I miss the Infuse, it was my very first android device. Man I miss GB look and feel. For me it's my favorite Android OS. I hope you can get it sorted out but I'm afraid it may be time to upgrade to a newer device.
[Samsung Infuse 4G] mainwheel:
You may be right, but although I am spending time I don't necessarily have to work on installing ROMs and trying to get this to work, I don't really have any other compelling reason to upgrade to a newer device. I do like the phone. Maybe I'll never get it working, but with everyone's help who knows. Maybe LP or some other fix? Fortunately, it is not something I have to have to survive. I don't do a lot of texting, but it would be nice to at least see the traffic/emergency alerts the County sends out without having to find a place to pull over to check it when I receive a text on the phone. Thanks for your help. George

---------- Post added at 02:03 PM ---------- Previous post was at 01:56 PM ----------

Hi Joel,

I must be a dope. :silly:

Don't seem to be able to figure out what is pertinent to the error. When I filter for "E/" there is a lot of stuff. Maybe normal, but it makes me wonder why anything is working. :D

And when I changed the preferences in logcat to just errors I thought it was logging everything but showing me just the errors. Apparently, I was wrong. I transferred to the computer to look through it and found I had only errors, so there was no context to help find my place. I may try again to get something useable, assuming it would be of any value, but don't have a lot of time to play with it.

Thanks. George
[Samsung Infuse 4G] treehugger38294:
This ROM runs great on the Infuse. My only problem is that there is a nasty kernel wakelock called STE-interface. Since I use the phone in Airplane Mode as a music player only, battery life isn't an issue, however.
[Samsung Infuse 4G] mainwheel:
I still fully use the Infuse as my phone. No issues except for not being able to get messages on my Subaru's media system. I had hoped upgrading would do it. I came from GB 2.3.6 up to this CarbonROM. While all went well, and I agree it runs well on the Infuse, it did not solve my problem. Maybe it is not solvable by upgrading software, but the interaction between phone and car have changed with the upgrades. The car now at least thinks the phone supports messaging. I probably need to get the logcat as recommended. Was having difficulty doing that, and haven't had time lately. If there was a version of Lollipop I would consider trying that.

Battery life is not as good as it was under GB, but it seems OK. I don't know what wakelock is. Can that be fixed?

Thanks for your input.
[Samsung Infuse 4G] OfficerJimLahey:
TBH, that one is new to me. I did find out that STE stands for "slide transition effects" (AFAIK), so you may be able to fix it by adjusting the animation scaling parameters (or reset them if already adjusted) in Developer settings?

Of course, I could be way off in left field (again) ;)
[Samsung Infuse 4G] treehugger38294:
The only stable version of Lollipop is 5.1.1. Even this version would put heavy load on the infuse and I think that Kitkat is leaner than Lollipop will ever get.
[Samsung Infuse 4G] PoXFreak:
Wrong...

Lollipop is slimmer and less resource hungry than kitkat.

Proof is in the HTC Desire HD/Inspire forums, where they get nightly builds of cm12.1.

I know this because I have one, and even when it's running at stock CPU speed, it's still faster and smoother than any kitkat rom I've flashed to it.
[Samsung Infuse 4G] GIL0802:
So that could be a chance to have Lollipop on the Infuses ? A port or something...
[Samsung Infuse 4G] PoXFreak:
If someone wants to put the time in, yes. I think it's possible, but like I said in an earlier reply, there's got to be a lot of kernel mods and patching done.

Most lollipop ROMs are looking to have kernel 3.2 as a base, and the infuse is still running on a heavily patched version of 2.6...
[Samsung Infuse 4G] GIL0802:
I think i need to change my phone :|
[Samsung Infuse 4G] treehugger38294:
Lollipop's animations put unnecessary strain on the GPU and while Kitkat was built for devices with 512 MB RAM, there's little indication that Lollipop was too.
[Samsung Infuse 4G] OfficerJimLahey:
Sorry to be a bother with something OT, but does anyone still have an Infuse that doesn't mind doing a "dd" dump for this user? Achieved.

Thanks! :cowboy:
[Samsung Infuse 4G] GIL0802:
I saw in the blog post http://carbonrom.org/its-time-for-a-change/ that anybody can build their own build of CarbonLP.

It is someone here that can test that on our Infuses ?

https://github.com/CarbonDev/android
[Samsung Infuse 4G] OfficerJimLahey:
Unfortunately the Infuse isn't part of Carbon's Lollipop guild. Further, Andros (Carbon's Infuse maintainer) has stepped down from what I can see.

I haven't heard much chatter in this forum about this device and Lollipop lately, I assume too many roadblocks were unearthed.
[Samsung Infuse 4G] GIL0802:
Ok, time to change.

So, there is no chance that anybody can build a LP ROM ?
[Samsung Infuse 4G] OfficerJimLahey:
I would not say no chance, but its looking pretty slim, as the developers that made major headway in the past have moved on.

Sent from my ASUS_Z00AD
[Samsung Infuse 4G] GIL0802:
I would like to try build myself but ain't know anything about building builds. So...