yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] deaddigitalangel:
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.
[Samsung Infuse 4G] g-noob:
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!
[Samsung Infuse 4G] hemen_kap:
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 .
[Samsung Infuse 4G] hemen_kap:
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 ?
[Samsung Infuse 4G] OfficerJimLahey:
This has been an issue for a while, if the problem is showing up like this:

http://xdaforums.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.
[Samsung Infuse 4G] hemen_kap:
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
[Samsung Infuse 4G] OfficerJimLahey:
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).
[Samsung Infuse 4G] hemen_kap:
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.
[Samsung Infuse 4G] hemen_kap:
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.
[Samsung Infuse 4G] hemen_kap:
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.
[Samsung Infuse 4G] OfficerJimLahey:
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.
[Samsung Infuse 4G] hemen_kap:
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
[Samsung Infuse 4G] OfficerJimLahey:
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.
[Samsung Infuse 4G] jloibman:
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..
[Samsung Infuse 4G] OfficerJimLahey:
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"
[Samsung Infuse 4G] hemen_kap:
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.
[Samsung Infuse 4G] mervinj:
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.
[Samsung Infuse 4G] hemen_kap:
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
[Samsung Infuse 4G] OfficerJimLahey:
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:

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.
[Samsung Infuse 4G] TulsaDavid:
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.
[Samsung Infuse 4G] hemen_kap:
Agree, if you read post http://xdaforums.com/showpost.php?p=55363372&postcount=18 , both posts are from me. the ROM (Cabon as well as Unofficial CM11 from scott) both start out rock solid. I have not encountered any issue on them and use my phone as a daily driver on these.

However after 3 months of continuous smooth experience, suddenly things go kaput, and everything starts crashing - such that the phone becomes unstable.

In the past when that happened i have noticed a new gapps package come out around that time. This time I have not seen that.

In any case I have found a method to come out of this situation quickly now.

I use Titanium Backup Pro to do a daily backup of my apps data. Also i took a Nanadroid backup some time back when I had a fresh install of Carbon and all apps i require.

I simply do a Nandroid restore and then restore all the data from titanium backup Pro and I am good to go in an hour.

However i would like to understand the root cause of this issue (why does it happen every 3 to 4 months) and can do a fair amount of technical debugging based on some guidance.
[Samsung Infuse 4G] PoXFreak:
What needs to happen, and I've expressed this MANY times already, is that the /datadata partition needs to be merged back to the /data partition. Writing a script to move cache files to yet another partition is just a workaround. If you look at the layouts for CM and even AOSP builds prior to 4.3, there is NO /datadata partition, and all the cache files are placed into /data. Speed is not an issue, as they're always placed on the same device, regardless of whether its /data or /datadata or even /data/data, which is the same as /datadata anyway.

I'm going to try a fresh install of Carbon Rom Nightly 20140907 and try the script above, but modify it to rm -r /data/data when done. If it works, I'll C+P the script here for someone to try. If it works for them, I might put the script into a post and let people test it at their own risk.

With Android L right around the corner, and ART becoming the ONLY runtime option, I think 4.4.4 is going to be the last "usable" daily driver option for the Infuse...
[Samsung Infuse 4G] rwaterspf1:
So......anyone willing to be a guinea pig on a Beanstalk build without /datadata? shoot me a PM.

-Vaughn
[Samsung Infuse 4G] hemen_kap:
You are correct. I used df -f to check the disk free space and for sure /datadata (or /data/data) was showing 350MB our of 350Mb utilized.....looks like i have found the root cause.

Now for the remedy. I searched and found EXT4all is possible solution and agree with you that it is just a workaround. I practically do not need /data/data as /data should be good enough for me. On infuse IMHO we are not getting any performance gain by splitting that up.

If you have something available and can share it i am willing to test it - as far as i can always restore from my nandroid backup and what we are doing does not impact that ability - I am game for it.

BTW, can you share additional details, reading material for you comment "With Android L right around the corner, and ART becoming the ONLY runtime option, I think 4.4.4 is going to be the last "usable" daily driver option for the Infuse..."
[Samsung Infuse 4G] PoXFreak:
Sorry for the long delay, I've been busy.

There's a few roms available for the Infuse that don't contain a /data/data partition, which I assume is why I can run those roms with no faults for weeks on end.

I did try building CM11 from source without the /datadata symlink, but I have to find a way to keep the signature the same when I go change the text in 'default.prop' and 'updater.sh' to not create the symlink when flashing.

My material for the statement about Lollipop is that L uses ART for it's runtime environment, which consumes more space in the /data partition because the apk files are pre-expanded after install and can take up twice the space of Dalvik runtime apps.
[Samsung Infuse 4G] PoXFreak:
I'm going to try using an updater script where the /datadata partition exists but is unused for any storage. If it fails because something else in the build actually requires that partition, I'll have to go further backward and build from AOSP with the symlink to /data/data removed.

I haven't built anything since ICS, but it looks to be easier now with all the support and advancements in the build environment.

Wish me luck... ;)
[Samsung Infuse 4G] PoXFreak:
So Vaughn beat me to it and built CM11 with /datadata disabled.

I've been running that build for what is now over 3 months, using ART as my runtime, with not a single issue that would happen when I was using /datadata!

It would seem that CM12 "might" be possible, given the fact that we really don't need any extra partitions on the infuse, so we gain back that extra 350mb.

Sent from my thumb magnet using Jedi mind control...
[Samsung Infuse 4G] oiphal:
Just a question I've wondered about for quite a while - do you recommend the ART or Dalvik runtime having used both of them? (As a daily driver, I mean). Both appear to offer practically the same performance (not surprising) with ART taking up more space. Without the datadata portion ART isn't filling up the phone and killing it anymore, though it still squeezes some apps to absurd sizes (antutu was 200 MB for some reason).

(I got 8890 with dalvik and 9048 with ART in antutu as my highest scores)
[Samsung Infuse 4G] PoXFreak:
As a daily driver I'd suggest ART, although dalvik has it's merits, one of those being a reduced /data usage.

If you keep a lot of apps on your infuse, stick with dalvik.

ART can and will make your device run slow at first because every app you install extracts to the /data partition and remains extracted, speeding up app loading once all the files are in place. Once it's done, it doesn't repack the apk like dalvik does.

Sent from my thumb magnet using Jedi mind control...
[Samsung Infuse 4G] _koffy:
I am!! am I too late? :(
[Samsung Infuse 4G] OfficerJimLahey:
Has already been implemented...in CM11, BeanStalk, and unofficially with CarbonROM (buried in the thread).

So you can use any of them at this point and have the datadata fix. Hope this helps.

Sent from my ASUS_Z00AD
[Samsung Infuse 4G] _koffy:
oh thanks a lot. Let me start digging then:)
[Samsung Infuse 4G] _koffy:
Sorry to bother you Joel, but i only found CM11 Unofficial with datadata fix...... I'd really love it fixed on Beanstalk or Carbon. Can u help with a link pls? :(
[Samsung Infuse 4G] OfficerJimLahey:
Hey, no problem. :)

CarbonROM:

http://xdaforums.com/showpost.php?p=61012641&postcount=1060

Maybe it was just my imagination that Vaughan did a BeanStalk build with datadata fixed...oops. :o

http://xdaforums.com/showpost.php?p=55574460&postcount=3801 (his proposal)

http://xdaforums.com/showpost.php?p=55567702&postcount=3799 (newest build afaict)
[Samsung Infuse 4G] rwaterspf1:
I just checked my devhost and things expire after too many days of inactivity and I no longer have any beanstalk 4.x sources synced. Maybe one of our other members have it saved somewhere?
[Samsung Infuse 4G] OfficerJimLahey:
Sorry, the only one I (may still) have saved is 4.4.285 (Scott's final). That won't be any good in this case.

Guess I should have been a little more aggressive with my mirror!
[Samsung Infuse 4G] rwaterspf1:
my last was 4.4.4065 but there was the same version with "nodatadata" in the filename that I sent out to half dozen folks that requested it via PM, but after a search on my server i must have deleted it at some point :\
[Samsung Infuse 4G] OfficerJimLahey:
Oh okay, it did exist at some point.

It's sad, for the devices stuck on KitKat (even via custom ROM's) because as far as I see the upstream isn't being maintained anymore (unless you are CM then there is still a slow trickle). CarbonROM seemed to have updated their gerrit so that older versions like KitKat aren't even shown. The last change I made to their source (to fix Google Play Services wakelock) I forked on github and used it that way.

Meanwhile, you have the StageFright vulnerabilities (I think there are seven now) that are left unpatched on the older ROMs (once again, CM may have got to these, but it looks doubtful).

My lamenting for the night. :p
[Samsung Infuse 4G] rwaterspf1:
I found a copy on the sdcard in my infuse of all places lol

Beanstalk-4.4.065-nodatadatainfuse4g.zip
[Samsung Infuse 4G] _koffy:
Thanks man.....am downloading your unofficial CarbonRom now :)

---------- Post added at 08:03 AM ---------- Previous post was at 07:54 AM ----------
[Nexus 5 General] filmaker:
Here's an interesting article I just came across on the Verge about a few sources saying the Google will retire the Nexus Line and reboot it with Android Silver handsets that will be sold in stores and highly marketed, but with presumably higher specs.

http://www.theverge.com/2014/4/29/5664702/google-nexus-to-be-replaced-by-android-silver

International Buinsess Article

http://au.ibtimes.com/articles/5504...-release-date-specs-features.htm#.U2LtifldV8E

"The rumoured "Android Silver" line will replace the Nexus program. The line included more high-end and more expensive devices. It was claimed that Google wants to focus on giving consumers devices that are bumped in the hardware side while enjoying pure Android experience." (International Business)

What do you think? I would be willing to go for a all around premium "Nexus" phone as long as the cost wasn't too much and it worked on all major carriers.
[Nexus 5 General] chambers7867:
I'm hoping that this is not true, if it is, we should start an online petition to keep the Nexus brand going.. I hate bloatware, carrier logos and all of the other nonsense that comes on phones from the carriers. My last few phones have been Nexus devices, and everytime i buy a carrier branded phone, i just end up selling it or returning it. Once you go nexus you cant go back..

Just my .02 cents.
[Nexus 5 General] :
I just posted two similar links here:

http://xdaforums.com/showthread.php?p=52289003
[Nexus 5 General] mauslbr:
I think that is only one more rumor surrounding Nexus brand
[Nexus 5 General] BirchBarlow:
Google can call the program whatever they want to call it. As long as they offer a device with vanilla Android, without carrier and manufacturer bloatware, with at least mid-range specs at a reasonable price I'm happy.
[Nexus 5 General] galaxys:
Rumors only...lock it before it spreads! eeek
[Nexus 5 General] Fataldesain:
Guys we have the last nexus Google can't keep making this phone it hurts its partners and now with the one plus one there is no point. I prefer a premium device instead of the cuts made to nexus like battery and camera
[Nexus 5 General] rayiskon:
Some of you guys are still in the negation phase :p

i mean, i love the nexus line too, but there are many indications that Android Silver is going to become a reality soon, some of the leakers of this news are credible sources and probably with direct connections in Google itself (well at least more credible than random people on a forum stating the opposite with no clues whatsoever) . You do the maths.
[Nexus 5 General] bozzykid:
I hope you are joking. The OnePlus is not even on Google's radar. I would assume the Android Silver program is true based on who is reporting it. At the end of the day, Google isn't going to stop offering an affordable Android phone with vanilla Android. It seems the silver program is just extending the GPE program to carriers. Surely, they aren't killing off the Play Store so there are no worries. Whether or not they call their phones "Nexus" phones doesn't matter to me because one will still be available from the Play Store.
[Nexus 5 General] onthecouchagain:
Cautiously optimistic about this. Could be interesting.

I hope they keep the competitive pricing...
[Nexus 5 General] Evo_Shift:
I feel the android manufacturers and carriers are never going to want a reasonably priced google phone that is heavily marketed next to their pricy flagships. Something about it doesn't add up. If they are GPe priced i'm sure the carriers and manufacturers wouldn't mind but then marketing that is much harder and they wouldn't sell many. I just can't picture them being welcome in retail next to the other phones.
[Nexus 5 General] akash3656:
Verge after the Galaxy Nexus era is as much bullsh*t as the rest. Their review for the Nexus 5 is a joke for an example.