yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] BlazinDANDAMAN:
Don't know if this issue has been reported yet.. When I try to update some apps, it fails to install, saying "Insuffiecent Storage Available". I have 16GB Free space. Just wanted to share. I'm on Beta Build 3.
[Samsung Galaxy Nexus] Az Biker:
Same issue with TiBu.. Fix is change directory from 0 to legacy... Not sure if that translates to apps, but it might be a place to start..

Atom, Carbon, Slim +AK / Golden =Bacon, Skittles, and Skulls!
[Samsung Galaxy Nexus] Sheetzie03:
I'm sorry bro, meant to post in another ROM, cataclysm. My bad ppl.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] BlazinDANDAMAN:
How do I do that? I've been searching and can't seem to locate how to change it. Thanks for your help.
[Samsung Galaxy Nexus] Az Biker:
With tibu issue you use file manager to locate destination folder (which is in '0' and change path to 'legacy') but not how to change destination folder for apps... Sorry...

Atom, Carbon, Slim +AK / Golden =Bacon, Skittles, and Skulls!
[Samsung Galaxy Nexus] cujo6801:
Tibu

Menu

Preference

Backup folder location

Detect

Whole device

Legacy

Use current folder

No....

sent from the DOG pound
[Samsung Galaxy Nexus] Az Biker:
That's the path for Tibu 'insufficient storage' , but he's asking about updating apps giving similar fail msg..

Atom, Carbon, Slim +AK / Golden =Bacon, Skittles, and Skulls!
[Samsung Galaxy Nexus] cujo6801:
O

OK...

Need to learn to read a little better.... Lol

sent from the DOG pound
[Samsung Galaxy Nexus] Bayhill Jacket:
Yeah, I am getting the "package is not signed correctly to update" message for any Google apps that have an update
[Samsung Galaxy Nexus] NeverSeparate:
If you are using modded Gapps then they won't work. You have to install the official ones from the store. Or from an unmodded Gapps. I haven't used the aroma installer but I think I recall you can choose which apps are modded and which are not.

From high upon the beanstalk
[Samsung Galaxy Nexus] Az Biker:
My wifi won't reconnect manually, automatically, after reboot, disconnecting/reconnecting, after wiping dalvik/cache and flashing rom and gapps. The available router is recognized and shows connected, but status bar icon remains on 3G no wifi symbol and no wifi service.. I wouldn't even mention it if it was merely a manual on/off fix... Again, what really stumps me is that it wasn't an issue initially, and happened without making any app/config/ changes to set up ...

Atom, Carbon, Slim +AK / Golden =Bacon, Skittles, and Skulls!
[Samsung Galaxy Nexus] Bayhill Jacket:
I am assuming the Slim Gapps are updated with each release ie., beta 3 from last week will be beta 4 with updated Gapps when released?
[Samsung Galaxy Nexus] Phazmos:
whenever I see something like this,I tell folks to disconnect all devices from the router, turn off mobile devices and unplug the cat5 from pcs so nothing is connecting, then unplug power from router for5 or 10 minutes, then plug power back in. wait another 5 minutes and connect 1 device at a time. wait till the device gets an ip address then connect another, wait for an ip address and connect another, so on till all are connected again, see how it goes. give it a shot, won't hurt anything, just takes a few minutes. I'm running an old liknsys wr54g with an old version of ddwrt and no problems reconnecting. but I don't have trouble with other routers either, so I may be lucky and don't have this issue. good luck, I can see where this can be a big pain in the arse.
[Samsung Galaxy Nexus] Nebucatnetzer:
Yes we normally update the Gapps with the new release.

However it's not clear yet if the next release will be Beta 4.
[Samsung Galaxy Nexus] bigbear6708:
Any tips? Tried to use gmusic on my chromecast. Would not connect... Restored cm, paired and worked perfect...
[Samsung Galaxy Nexus] audit2:
Baseband version

FC04/FC05

I notice that this is the radio for 4.0.4 is this the same everyone is using for 4.3? I wanted to update to the 4.2 radio but want to make sure it's compatible.

Thanks..
[Samsung Galaxy Nexus] Az Biker:
I515.09 V. FK01 / I515. FK02

Atom, Carbon, Slim +AK / Golden =Bacon, Skittles, and Skulls!
[Samsung Galaxy Nexus] audit2:
Thank you.
[Samsung Galaxy Nexus] TuxDroid:
Devs of Slim Bean: is a GitHub pull request the best way to submit a code enhancement or do you have Gerrit or what? Thanks
[Samsung Galaxy Nexus] Nebucatnetzer:
I would say yes. Or send kufikugel a link to the commit.

Our Gerrit is not public.
[Samsung Galaxy Nexus] TuxDroid:
Cool, thanks. I asked a question related to this at http://xdaforums.com/showthread.php?t=2425665

I would greatly appreciate it if you could take a look.
[Samsung Galaxy Nexus] Nebucatnetzer:
To me it sounds okay but I'm not really good with such things. I'll tell kufi he shall have a look.
[Samsung Galaxy Nexus] remicks:
I smell beta 4... already got the gapps downloaded lol

★ROM: AOKP 4.2.2 - KERNEL: ASKP 19 - MODS: BEATS+XLOUDER v7★
[Samsung Galaxy Nexus] midnightdevil66:
This ROM and tiny kernel = the shiznit! Thanks!

Sent from my Toro
[Samsung Galaxy Nexus] bigbear6708:
I spy beta 4 at slimroms.net!!!!! Thx team!!
[Samsung Galaxy Nexus] TuxDroid:
I guess they not only looked but also did what I was planning to do :) I was going to submit the eri.xml for toro from CM and just saw that the current code has that pulled in already. Guess that answer whether you all would be game for merging it ;) Can't wait to try out the new build tonight!
[Samsung Galaxy Nexus] TuxDroid:
My carrier label is blank instead of saying T-CDMA 64 after loading beta 4. I saw eri.xml had been added to GitHub in the Toro tree so this may be related.
[Samsung Galaxy Nexus] t1.8matt:
Beta 4 is working nicely so far except I can't get voice dialing to work with my Jawbone Era. It says voice dialing when I hold the button on my Era but nothing happens on the phone.
[Samsung Galaxy Nexus] TuxDroid:
Anyone having mms issues on beta 4?
[Samsung Galaxy Nexus] TuxDroid:
beta 4 = no MMS

So, just to validate this is a ROM issue, I did a FULL wipe, flashed the beta 4 without GApps, and still cannot send MMS on data or WiFi. I am going back to beta 3 but need to know if I can use the beta 4 GApps as I have deleted the beta 3 ones and they are not listed on the site now... at least as far as I can see.

EDIT: I have a nandroid of beta 3... whew!

---------- Post added at 10:46 PM ---------- Previous post was at 10:13 PM ----------

Disregard this part. When I flashed the rom after a full wipe the carrier label worked great.
[Samsung Galaxy Nexus] lesclark:
I'm running beta 4 with no MMS issues.
[Samsung Galaxy Nexus] TuxDroid:
Did you wipe /system prior to flashing the update?
[Samsung Galaxy Nexus] lesclark:
no .... I have dirty flashed since beta I
[Samsung Galaxy Nexus] TuxDroid:
Bet that is it. I kept data the first time but wiped /system
[Samsung Galaxy Nexus] Txwolf1980:
And, for whatever reason, my data held all the way through last week. I had one or two days drills, but only for a couple of minutes, and never where I was around my computer. Freaking odd

I'm beginning to wonder if it's the phone, or if we're just getting a rash of network carriers upgrading to Rev 10, or something
[Samsung Galaxy Nexus] Nebucatnetzer:
Whatever is buggy we need a logcat of it.

Voice Dialer is currently broken for some reason we break it after every bigger Android update.
[Samsung Galaxy Nexus] TuxDroid:
I will try pulling one today.
[Samsung Galaxy Nexus] tshelby73:
I have never used slim yet but been lurking.

When I was on cm it had voice dialer and didn't like it as it had no voice confirmation before dialing. I would freeze it and use Google now for voice dialing and that worked better for me always confirms before dialing.
[Samsung Galaxy Nexus] remicks:
Unable to send MMS over lte/cdma/wifi on beta 4 here as well :(

On a side note my data is working great with 4.1 radios/bootloader

★ROM: AOKP 4.2.2 - KERNEL: ASKP 19 - MODS: BEATS+XLOUDER v7★
[Samsung Galaxy Nexus] TuxDroid:
If you are still on beta 4, will you grab a logcat of the MMS issue?
[Samsung Galaxy Nexus] remicks:
Yeah, lemme grab a logcat app and run one off real quick.

Here we go (logcat of failed mms): http://db.tt/oXncEOXI

Edit: Anyone got a copy of the MMS.apk from beta builds 3, 2 or 1?

★ROM: AOKP 4.2.2 - KERNEL: ASKP 19 - MODS: BEATS+XLOUDER v7★
[Samsung Galaxy Nexus] evilSuRGe:
Same here
[Samsung Galaxy Nexus] TuxDroid:
How can I get it to you?
[Samsung Galaxy Nexus] remicks:
Just dropbox it/them or use copy or some other free hosting lol

★ROM: AOKP 4.2.2 - KERNEL: ASKP 19 - MODS: BEATS+XLOUDER v7★
[Samsung Galaxy Nexus] TuxDroid:
http://db.tt/Q711bjQ1 direct from the beta 3 download zip.
[Samsung Galaxy Nexus] Txwolf1980:
Has anyone tried changing the dpi on 4, yet? As soon as I reboot after clearing data, and agree to location, It won't let me get any further. Opening market just gives me a no connection. I know I have data, because browser works fine. Clearing data again, and Rebooting has no effect. It's almost like the old non dpi market issues that existed when changing dpi was first brought in
[Samsung Galaxy Nexus] remicks:
MMS still not working with beta 3 apk on beta 4 :(

[MENTION=526058]txw[/MENTION]olf I'm running 320dpi just fine on beta 4

★ROM: AOKP 4.2.2 - KERNEL: ASKP 19 - MODS: BEATS+XLOUDER v7★
[Samsung Galaxy Nexus] TuxDroid:
Did you notice anything in the logcat that might be the "why" for mms?
[Samsung Galaxy Nexus] Txwolf1980:
Hmm. It'll let me change the dpi to stock. Once I get past that step (clearing g market data, then Rebooting) is when it seems to break
[Samsung Galaxy Nexus] remicks:
Nah, I poked around a bit but whatever is wrong is evading my eye :(

★ROM: AOKP 4.2.2 - KERNEL: ASKP 19 - MODS: BEATS+XLOUDER v7★
[Samsung Galaxy Nexus] Nebucatnetzer:
The issue is fixed. We'll release a new build soon.
[Samsung Galaxy Nexus] remicks:
Hooray! You guys rock my socks! U should hang out on IRC Neb, never see ya in there :D

★ROM: AOKP 4.2.2 - KERNEL: ASKP 19 - MODS: BEATS+XLOUDER v7★
[Samsung Galaxy Nexus] Nebucatnetzer:
I'm not much of an IRC guy sorry.

Too busy for my taste :)
[Samsung Galaxy Nexus] TuxDroid:
Was it by chance an apn issue? I saw some lines in the logcat that made me wonder. Thanks for the quick response to this bug!
[Samsung Galaxy Nexus] Nebucatnetzer:
Don't know kufi fixed the problem :)
[Samsung Galaxy Nexus] remicks:
U guys gonna put the new build up on the site I assume when its done?

Edit: Just saw build 4 was taken down, guess that answers it haha

★ROM: AOKP 4.2.2 - KERNEL: ASKP 19 - MODS: BEATS+XLOUDER v7★
[Samsung Galaxy Nexus] TuxDroid:
Is it OK to use "Photosphere.4.3.build.beta.3" with builds newer than beta 3?
[Samsung Galaxy Nexus] Nebucatnetzer:
We'll upload the build once it's ready.

Yes.
[Samsung Galaxy Nexus] bigbear6708:
How about that Google music to chrome cast bug? I heard it was a known issue.. But do u need a log, or do we know the cause?
[Samsung Galaxy Nexus] remicks:
Was gMusic in /data/ or /system/ for that bug? I heard as long as its in /system/ it should be fine.

★ROM: AOKP 4.2.2 - KERNEL: ASKP 19 - MODS: BEATS+XLOUDER v7★
[Samsung Galaxy Nexus] bigbear6708:
/system. I even tried to delete it and install from market... gave me an install error. Guess my next step is to try standard gapps and see if it works
[Samsung Galaxy Nexus] remicks:
Uninstall/remove Google music and flash this zip in recovery (its blacked out, hope ya don't mind) and see if it works: http://db.tt/oXVKjNuu

★ROM: AOKP 4.2.2 - KERNEL: ASKP 19 - MODS: BEATS+XLOUDER v7★
[Samsung Galaxy Nexus] cuzzinz:
I had this problem. I hit retry like 30 times quickly in a row and it started working. Don't ask me why it worked it just did. I went into airplane mode, turned off data... Tried everything and that was the fancy solution. Lol
[Samsung Galaxy Nexus] KJW979:
Not sure if this is normal but first time using slim rom. Started on 4.3 nightlies. Running great, btw. When backing up this rom in recovery it takes up 8-9 gigs of space, Start out with 17 and after shows I have 8-9. Never seen this on any other rom. Not much on phone, no music cause haven't redownloaded on to phone yet and only 50 or so apps. Tried reflashing recovery to no avail. Just curious is that is norm back up size for this rom.
[Samsung Galaxy Nexus] TuxDroid:
Revised beta 4 has been posted, downloading now :)
[Samsung Galaxy Nexus] cuzzinz:
Downloading now.... Note to everyone they also updated the aio gapps.

Edit: Mms success
[Samsung Galaxy Nexus] kufikugel:
the mms error started because of some patches we included to handling the ICC card proxy....downside on this toro reports sometimes an unexpected value like it is on UMTS but is still sitting on cdma

whatever it is fixed like I see from the report above (thanks to Decad3nce who did the fix)

about chromcast and gmusic...we currently do not have an idea why it does not work with our gmusic.....seems to be that the new google permissions give us the problem. Still investigating

the updated AIO gapps should solve the voice dialer problem.

cheers
[Samsung Galaxy Nexus] TuxDroid:
Thanks for the MMS fix. It's working good now for me. The info that came in with toro eri.xml is showing up nicely now too :)
[Samsung Galaxy Nexus] bigbear6708:
Also, if I delete music.apk manually from /system it still will not let me install from play store..even after a reboot. Is it due to trds "left overs" somewhere else?

Fwiw: team blackout inverted didn't work either.
[Samsung Galaxy Nexus] lesclark:
has anyone tried to use the recent nav button o beta 4, for me it caused a system UI restart.
[Samsung Galaxy Nexus] t1.8matt:
I've had pretty much no problems with beta 4 including the recents button.
[Samsung Galaxy Nexus] TuxDroid:
No issues here but I did wipe caches & /system before flashing.
[Samsung Galaxy Nexus] lesclark:
my fault. nav key update went wrong. all better now :)
[Samsung Galaxy Nexus] Txwolf1980:
I just gave up left it on 245. Maybe I'll clean flash the updated b4.
[Samsung Galaxy Nexus] midnightdevil66:
Beta 4 running like a champ do far. Thanks devs!

Sent from my Toro
[Samsung Galaxy Nexus] remicks:
Only bug for me so far is that it somehow got stuck where my volume keys were adjusting media volume at all times even though that option wasn't enabled. Tried enabling and disabling the option and it was still doing it. A reboot fixed it but it was still quite odd.

★ROM: SlimBean 4.3 Beta - KERNEL: Fancy Kernel - MODS: None★
[Samsung Galaxy Nexus] t1.8matt:
i'm still having mms issues on beta 4. i'm trying to send a picture and it's not sending 5 minutes later. from what tuxdroid said it's supposed to be fixed?
[Samsung Galaxy Nexus] justen7723:
Is WiFi on?? Sometimes MMS gets Hung up when wifi is on.

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] t1.8matt:
yeah, it was on. i don't get a great signal in my house, 3g only, but i usually don't have problems sending MMS even when connected to wifi. i'll try without wifi and see what happens.

---------- Post added at 03:44 PM ---------- Previous post was at 03:40 PM ----------

No go with wifi off and strong 3g signal. Still won't send.
[Samsung Galaxy Nexus] cujo6801:
Did u clean install?

When I dirty flashed no go ..

Clean install all good...

Just a thought..

sent from the DOG pound
[Samsung Galaxy Nexus] t1.8matt:
It wasa clean install with minimal slim gapps. I pretty much never dirty flash anymore. To many problems can pop up. I rooted flashing an MMS fix from a CM10.2 ROM since this is somewhat CM based, but I kept getting a FC message as soon as it booted up, so it wasn't compatible. I dunno what else to do since I've clean installed this twice.
[Samsung Galaxy Nexus] Nebucatnetzer:
We are not CM based!

Why are people still thinking this?
[Samsung Galaxy Nexus] cujo6801:
Try the aio gapps... You never know

sent from the DOG pound
[Samsung Galaxy Nexus] t1.8matt:
Sorry, just looks that way to me. I'm wrong. Thanks Cujo, I'll try AIO and see if that does anything.
[Samsung Galaxy Nexus] Az Biker:
I started with a full wipe, clean install of Slim beta 2, aio gapps, photosphere, (then Golden kernel).. After that, I've just wiped cache/dalvik when flashing beta 3 and beta 4... Only issue was wifi and that's a 4.3 issue not Slim... Enjoying beta 4, mms working, all is well here... Slim is a fantastic rom!

Atom, Carbon, Slim +AK / Golden =Bacon, Skittles, and Skulls!
[Samsung Galaxy Nexus] TuxDroid:
Grab a logcat of your mms fail and post it please. Also, I know that you said it was a clean install but just to double check, did you wipe /system before flashing the ROM or just let the install script wipe things for you? No offense intended, just trying to make sure we are comparing apples to apples here.
[Samsung Galaxy Nexus] t1.8matt:
Nah, it's all good. Every time I do a ROM install I do the regular wipe in TWRP and then use the Galaxy Nexus Super Wipe Script which clears the system. I'll grab a logcat tonight.
[Samsung Galaxy Nexus] cujo6801:
Just a thought but what build 4 are you guys using?

1st or 2nd

2nd has the fix..

Just a thought....

sent from the DOG pound
[Samsung Galaxy Nexus] almahix:
New to this rom with Beta 4 today, and everything I use is working great. Nice work!
[Samsung Galaxy Nexus] heXacode:
I only see one build. Where are you seeing 2 builds?
[Samsung Galaxy Nexus] TuxDroid:
The first build got pulled down. It's name ended with 418. The fixed one ends with 493 and is the one now posted.
[Samsung Galaxy Nexus] chikimonke:
Posting in the Fancy thread too.

So I'm not sure if this is a kernel or ROM or gapps issue, but on the latest r41b2 and the latest Slim 4.3 beta 4, my phone reboots when connected to BT in my car. Everything seems rock solid otherwise, but without fail it reboots to the Slim boot animation when connected to BT.
[Samsung Galaxy Nexus] chrisexv6:
Read my posts in the commotio ROM and golden kernel threads. Having the same issue. Initial connection works OK but if a stream is paused the phone hangs and soft reboots on BT connection.

I think it's something with the 4.3 BT stack BUT fairct build of paranoid android did not seem to have the same issue

I don't think it's a kernel issue since I've tried multiple kernels on commotio and it still happened.

I wonder what commotio and slim ROM might have in common, and different from fairct paranoid build
[Samsung Galaxy Nexus] kufikugel:
yes it is our fault and already internaly fixed. Will be fine in next published versions. Sorry for that. We integrated some changes in the bt stack and did not saw that the bluetooth connection can be null for a short time. That leads in a dieing bt service = reboot :(
[Samsung Galaxy Nexus] chrisexv6:
Not a problem, if you dont mind Im going to refer DHO to this thread since it looks like the same issue exists in Commotio.

Are you guys using the same codebase?

(and I did notice your commit in the last couple days of the "check for null pointer" in the bluetooth code)
[Samsung Galaxy Nexus] chikimonke:
So if I flash back to beta 3 of the Rom but keep the latest gapps everything should work again, right?
[Samsung Galaxy Nexus] t1.8matt:
I got MMS working. I flashed the newer build with AIO Gapps and all is back to normal.
[Samsung Galaxy Nexus] midnightdevil66:
All was working well until today. Plugged in car charger and got a SOD. Pulled battery phone turned on to lock screen and started rebooting itself from the lock screen. That was on tiny kernel. I dirty flashed beta 4 with gapps and after an hour or so got another SOD. Pulled battery again and so far it's been OK. I'll see once I plug back in car charger later on.

Sent from my Toro
[Samsung Galaxy Nexus] midnightdevil66:
Ok definitely something up with beta 4 and normal/fast charge. I plugged in again car charger and almost instant SOD. Pulled battery, phone started rebooting from lock screen non stop. Dirty flashed beta 3, phone back to normal/fast charging in car. No issues whatsoever on bakedin kernel and tiny.
[Samsung Galaxy Nexus] audit2:
Yeah! I reverted back to beta3 also too many issues with 4. Beta3 is near perfect.
[Samsung Galaxy Nexus] TuxDroid:
So it's not my imagination, beta 4 seems buggy for others too? I just assumed that I had docked my phone up...
[Samsung Galaxy Nexus] xain713:
I haven't had issues at all with beta 4 dirty flashed from 3
[Samsung Galaxy Nexus] Az Biker:
+1

Atom, Carbon, Slim +AK / Golden =Bacon, Skittles, and Skulls!
[Samsung Galaxy Nexus] kufikugel:
for the one with issues you can test this build please:

https://dl.dropboxusercontent.com/u/106208842/Slim-toro-4.3.beta.4-UNOFFICIAL-20130904-0450.zip

with the normal beta.4 gapps. Should be working fine...just want to ensure that toro is fine with a public test if you guys do not mind

should be up in about 20min

thanks

PS. the other questions I will answer today later a bit in a hurry lol
[Samsung Galaxy Nexus] TuxDroid:
Happy to test. Will report back.
[Samsung Galaxy Nexus] chikimonke:
Which issues is this build supposed to address? I'll test if it's the BT one.
[Samsung Galaxy Nexus] TuxDroid:
Initial impression after letting the phone sit mostly unused for a couple of hours is that the smoothness is back with this build. I just put Golden back on and am going to put the settings that I have been using back in place. Will report back a little later.
[Samsung Galaxy Nexus] chikimonke:
Seems that BT is still a bit wonky. Phone restarted once and locked up another time while connect to my car's BT.
[Samsung Galaxy Nexus] chikimonke:
Have you tried BT yet?
[Samsung Galaxy Nexus] TuxDroid:
Still going good for me. No reboots and it seems smooth. Unfortunately this is all gut feeling stuff though.

I don't use bluetooth but had been seeing the reboots. As mentioned above, so far so good.
[Samsung Galaxy Nexus] chikimonke:
Do you have anything to try BT with? Everything felt good for me too, until I connected to BT.
[Samsung Galaxy Nexus] TuxDroid:
I'd like to help but the only bluetooth device I have is my laptop.
[Samsung Galaxy Nexus] chikimonke:
That may be enough. I don't actually have to do anything with my phone, it's just the act of connecting to BT that causes it to hang/reboot. The original build 4 did this almost immediately, the new unofficial build seems to do it after a short while, a minute or so. If you have the time/motivation to do so, it'd be nice to know that it wasn't just me. Thanks
[Samsung Galaxy Nexus] kufikugel:
can you do me a favour and get a logcat when this happens please?
[Samsung Galaxy Nexus] chikimonke:
I'll try, but like I said, the phone basically locks up until it eventually reboots. Not sure if I'll actually be able to get one.
[Samsung Galaxy Nexus] bigbear6708:
Kufikugel, I will install your new build and go to my truck and try BT...
[Samsung Galaxy Nexus] TuxDroid:
So, I paired my GNex up to my laptop that is running Debian 7 and pulled a logcat over wifi. I sent a picture and an mp3 to my phone from the laptop via bluetooth. I tried to send a picture to the laptop but it failed twice (I think logcat said something about protocol not supported). I also noticed lots of other errors and some java stuff that looked like it blew up. My phone never missed a beat and did not reboot. The logcat is attached (it ran from before the transfers until after I played the entire mp3 I sent my phone).
[Samsung Galaxy Nexus] TuxDroid:
BTW, I also saw some stuff scroll by about things having moved. It might have been related to auditd but I may be mistaken on that. Is that stuff a ROM thing or an app thing? Lastly, whenever I swiped down on the notification shade logcat went nuts... not sure if that's important or not.