yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] Cjunior:
hi i am trying to install a app by pushing in to the system app but i keep getting a message saying not enough space, to delete some files and try again.

i don't know how to fix this anybody has any idea it was similar thread about this a wile back.

i can install apps from the market i just cant push anything in true root explorer it says is not enough space. please help.:confused:
[Samsung Epic 4G Touch] isaac2k10:
Ur system/app folder might be full, might have to delete some stuff

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] fatboypup:
id bet its the s voice ...... i ran into the samething yesterday :mad:

Im on a fresh install of FE21 and i have 489mb used and 14 free in system/app ..... lame s voice is 40 some megs
[HTC Amaze 4G] SHA0L1NSTYL3:
Sine I have been a long time lurker, and just registered I had to post this in the Q&A section, and not in NRG’s post, so I apologize for this. I did my due diligence and searched for the answer to this, and the question hasn’t been asked since the beginning of March so I thought I would see if NRG himself or someone else could answer the question on how to get Hulu to work with these ROMs. We all know that it is due to the ads being blocked, but from what I do not know. Anyone have any ideas?

T-mo HTC Amaze NRG’s March 10th, 2012 (3.10.2012)(GB) Rom flashed.

Thanks
[HTC Amaze 4G] glacierguy:
http://xdaforums.com/showthread.php?t=1303197&page=2

See if this helps
[HTC Amaze 4G] SHA0L1NSTYL3:
That didnt work, came close Hulu itself kept saying that my phone is not supported, I was not able to even get to buffering part.
[HTC Amaze 4G] glacierguy:
Maybe THIS ^^^ is your answer... Idk. I don't use it
[HTC Amaze 4G] SHA0L1NSTYL3:
I realize that it does not work "out of the box" I am using a modded version: http://xdaforums.com/archive/index.php/t-1449110.html The issue that I am having is mentioned in the above post, I just have no idea what Ad blocker NRG puts into his ROMs, and how to disable it
[HTC Amaze 4G] glacierguy:
SOME may take this as blasphemy, but with this phone, you're best off running stock rooted...
[HTC Amaze 4G] elwaxman:
+1 I agree stock rooted debloated ics is the best....
[HTC Amaze 4G] glacierguy:
And same goes for GB
[Galaxy S II Q&A, Help & Troubleshooting] reynardlingga:
Hi guys, request help from you who know how to reset google play apps so i can update all my apps

Usually my updated apps is 172, but now it is only 95

but when I do factory reset, wipe cache & wipe dalvik cache, flash rom and change dpi, the total apps change to 172 again, but after a few days it becomes 95 again?

Is it because I change the dpi of the phone? Is there any way to fix that or apps that can fix that?

Sent from my GT-I9100
[Galaxy S II Q&A, Help & Troubleshooting] budi.hermawan:
definitely... stay on your default dpi, some apps detects yours device resolutions before it will download data ... for example: g*meloft games..., dont bother factory reset just do this: setting - apps - manage - all - search google play - force stop - clear data, hope it helps..
[Galaxy S II Q&A, Help & Troubleshooting] ctomgee:
Yes.

Change your DPI back to the default.

See this post for reference. (found with a search)
[Galaxy S II Q&A, Help & Troubleshooting] reynardlingga:
yes I've done that but still didn't work

is there any other solution than that?

by the way did you know there's a modded google play store? using that will let you download all apps across platform and country restriction... have you tried that?

thanks... :)

edit 1: it works thanks, but few apps still showing "your device is not compatible with this version" and i can not update...

edit 2: just wait a few minutes and everything works perfectly :)

THANK YOU...

Sent from my GT-I9100
[Galaxy S II Q&A, Help & Troubleshooting] reynardlingga:
many thanks... do you know which dpi setting that still work so I can update my apps also having my high lcd density?

i heard that 182 dpi would do the trick

or is there any application that can fool google play store to think that I still using 240dpi without changing the dpi to 240?

Sent from my GT-I9100
[Galaxy S II Q&A, Help & Troubleshooting] petergab:
Perhaps you can use a modified play store apk. Just search for it in the Forum.
[Galaxy S II Q&A, Help & Troubleshooting] budi.hermawan:
playing with dpi is such a trial and error... some apps run.. some wont (especially games afaik), if you could tweak some setting in build.prop.. make it galaxy note, change the dpi be like galaxy note... it would be galaxy note, some apps would be fooled some wont... its not recommended thought.. but hey its a trial and error :)

Sent from my GT-I9100
[Galaxy S II Q&A, Help & Troubleshooting] reynardlingga:
currently I'm setting my dpi to 182 to see whether it works to fool the Google play store or not... will post to this topic about the result

no problem about trial and error as long I know how to fix and i still have nandroid backup :)

if i don't try I wouldn't know, would I? :)

EDIT1: today looking good, no issue :)

EDIT2: no issue using 182 dpi

EDIT3: have to set to 240 dpi, if i wanto to update all apps, not all apps can be updated using 182dpi

Sent from my GT-I9100
[Galaxy S II Q&A, Help & Troubleshooting] johnyute:
Search the forums and download a multi dpi playstore... solves problem instantly
[Galaxy S II Q&A, Help & Troubleshooting] ctomgee:
You do realize the last post in this thread prior to your was from May, right?
[AT&T Samsung Galaxy Note I717] magnumforce2006:
Is there a fullwipe type .zip that can be run in clockworkmod for the Note? Rather than having to go through all of the steps of wiping/formatting different things for flashing a new ROM?

There was one for the Inspire, and that was quite handy (didn't have to worry about messing anything up, lol).
[AT&T Samsung Galaxy Note I717] appdroid:
http://xdaforums.com/showthread.php?t=1477955
[AT&T Samsung Galaxy Note I717] magnumforce2006:
Thank ya sir. These things are so handy.

edit: Title of the thread and OP doesn't mention the Gnote... Has this been used with 17I7 users with safe results?

edit 2x: Just looked up a thread on this forum, and it looks like it's working well for people. Sounds good!
[Android General] plazzTT:
Looks great.

Seems like changing the CM Version always reverts back to CM9 after clicking on another link. Maybe thats intended.
[Android General] peterperfect:
Thanks for the report, the bug is being adressed! :)
[Android General] runedrune:
Shouldn't changes made to CyanogenMod/android_kernel_samsung_smdk4210 also show up in the Galaxy S 2 changelog?
[Android General] chadouming:
The changelog is updated every hours. So wait a little bit :P
[Android General] peterperfect:
There was a problem this repo was not synced. Its fixed now. Enjoy.
[Android General] scheichuwe:
CyanogenMod/android_kernel_samsung_smdk4210 is shown for Galaxy S (and some other Samsung devices which are not Galaxy S II ;)).
[Android General] XpLoDWilD:
Only device trees are filtered for now, not kernels. We're going to fix this in the next hours :)
[Android General] tsagi:
I hope it will be better than the old stuff because yahoo api kept crashing all day long
[Android General] peterperfect:
we will not crash.
[Android General] compact_wisdom:
Looks great, some inprovements and it will hopefully be a more stable alternative to the Yahoo API.
[Android General] XpLoDWilD:
What kind of improvements?
[Android General] imfloflo:
Very nice, already adopt it.

Nice to see French Guy in this project ;)

F.
[Android General] ellite:
It's great :)

Thnaks.

But the Samsung Galaxy Tab 10.1v (p3) is missing ;)

Grat job.
[Android General] zzandrewst:
Droid 3 is not on drop-down list.
[Android General] XlAfbk:
android_device_samsung_aries-common is missing for galaxy s devices in devices.xml (not sure what exactly are the devices it's used for, galaxysmtd and galaxysbmtd are definitly there)
[Android General] XpLoDWilD:
http://get.cm/

It is not there either. No nightly = no changelog.

Going to add it.
[Android General] Nebucatnetzer:
Is there a way to show multiple days at once? I kind of liked to see the changes from previous days to compare them with the current ones.
[Android General] zzandrewst:
Thanks, I guess the CM9 on the Droid 3 is not official then.
[Android General] cdmackay:
Great job, thanks very much for this.

Request, please: would you consider indicating the timezone when times are printed, e.g. MERGED, Built, etc?

thanks much indeed.

---------- Post added at 07:59 PM ---------- Previous post was at 07:46 PM ----------

Should CyanogenMod/android_dalvik project also be included?
[Android General] peterperfect:
We looking into bug reports and discussion suggestions that you guys are bringing. Thank you very much for all support.

@cdmackay yes, android_dalvik is being fetched. You noticed anything wrong?
[Android General] Raudi1:
Finally a changelog that doesn't depend on an API that is down 90% of the time.

I like it better than the old one so far, but there is some room for improvement, I think.

The build date and build name in the left column should be exchanged imho, because it could lead to confusion when you view the changelog from the 25th and the actual build is named update-cm-9-20120524-NIGHTLY-galaxys2-signed.zip

The multiple day view mentioned before would also be nice for me, but that could just be because it was like that with the old changelog when it wasn't showing the Yahoo API message ;)

An RSS feed would also be nice thing.

The time when the changelog was refreshed the last time could also help to clear misunderstandings.

That's everything that comes to my mind so far.

Keep up the great work! I like the idea of a lot of the OpenDesign features like the improved lockscreen and the text to email feature (that hopefully will also work the other way)!
[Android General] iXNyNe:
I agree to all of this!

The date thing is very confusing.

I'm because the build with 524 in the filename is released on 525 so that's always been a pain

I saw on gerrit that the build naming structure is being debated anyway, but the change log dates should reflect the build name, not date.

Also the multi day view would be awesome, and RSS would be sick.

I imagine RSS would make building the change log app easier.
[Android General] cdmackay:
Thanks very much...

I wondered about that project, because you don't seem to have, e.g:

http://review.cyanogenmod.com/#/c/16478/

http://review.cyanogenmod.com/#/c/16477/

unless I'm just not seeing them?

Edit: apols, should have said: this for galaxysmtd

---------- Post added at 11:54 PM ---------- Previous post was at 11:51 PM ----------

I note you're also including msm7k; why is that included for galaxysmtd? Surely we don't have the Qualcomm SoC?

Edit: does the galaxysmtd build include support for variant models that do have the snapdragon etc?
[Android General] chadouming:
Thanks for all your answer and suggestion ! I want personnaly to thanks everyone using it and mostly nebkat and xplodwild to have given so much time and effort on this ^^. I want to give you some stats all. On 4 days of service, we have 30k visits, 22k uniques visits and 160k page views. Thats a lot and this is far from the limit of our server. Our goal is to have everyone to come on it :P If you are a dev, you are free to use it as changelog. I even thank you if you do so. I want to give you some advice, dont forget to watch often as we have a few big thing coming soon. But you will see in time and place. I also wan't to tell you that one of the website dev is a troll and added an easter egg on the website. I wont tell you what it is tho :P. Finnaly i want to thank you again, and I hope you will adopt this changelog solution :)
[Android General] dylandylan1:
Hi, in regards to the old cm-nightlies.appspot.com, I made some changes to the code to no longer rely on the yahoo api, included more devices and relevant updates and improve filtering by device, which is at cm9log.appspot.com. But this new bbqlog looks great and will be better as it includes all github commits not just the gerrit ones.

After inspecting the .mk files for current CM9 nightly devices, I concluded the following list of device specific and/or shared repositories for my changelog; http://pastebin.com/i43kw1qC. I am not entirely certain but I think it's about right, although missing a few qcom_opensource repositories. Perhaps it could be helpful in filtering repositories on the new log.
[Android General] XpLoDWilD:
This will help what cdmackey said. There is no official list of links between devices and repositories, so we cannot really make sure some devices won't show changes for others. Dylandylan1's list will help that a bit, but it's not exhaustive either. I invite you to check devices.XML on http://github.com/bbqdroid/bbqlog and do pull requests when you notice a repository not filtered properly.
[Android General] iandol:
Hi, for Cooper, only ANDROID_FRAMEWORKS_BASE is being tracked. Compare:

http://cm-7-nightlies.appspot.com/?device=cooper

and

http://changelog.bbqdroid.org/#cooper/cm7/next

By the way, what a beautiful UI, really crisp web design and very well laid out, congratulations!!!
[Android General] cdmackay:
Thanks!

But I'm confused... we don't need any official list to know that, for example, msm7k shouldn't be included in galaxysmtd, surely? or am I wrong?

Also, I still don't see why some dalvik merges seem to be missing?

I checked devices.xml, but there's nothing there that explains either...

thanks much.
[Android General] chadouming:
I did add some missing repo in devices.xml, but as xplodwild said, there is no way to know what goes where. We know the basic repo for each, but we don't know what other repo are linked. I will try to find what repo are linked. Anyone who want to help is welcome. Simply send me what you know. Thanks !
[Android General] XpLoDWilD:
What dalkvik merges?

ICS branch had changes 2 weeks ago :

https://github.com/cyanogenmod/android_dalvik/tree/ics

And gingerbread was 2 months ago...

And again, for device-repos, the only way is to check every single device.mk for dependencies - which is a quite long task considering the hundred of devices we have here.
[Android General] cdmackay:
Thanks; I mentioned a couple of changes here:

http://xdaforums.com/showpost.php?p=26568049&postcount=24

that don't seem to show up for galaxysmtd.

---------- Post added 28th May 2012 at 12:02 AM ---------- Previous post was 27th May 2012 at 11:56 PM ----------

Also, a new regression, I think...

when you visit a CM9 build, e.g:

http://changelog.bbqdroid.org/#galaxysmtd/cm9/1338124492

The links down the LHS are to the CM7 versions. So every time you click on a link, you then need to also change it to CM9.

I'm sure this didn't do this a few days ago?

thanks much...
[Android General] XpLoDWilD:
https://github.com/CyanogenMod/android_dalvik/commit/a6cecb830d12f706138acd870abf0f4a73b31ffe

As I said the commit is back 16 days, way before any nightly shown. I can confirm you it's in our database.

As for CM7/CM9 switch, it's because the first nightly of the list is CM7, so the system switch automatically to CM7. It'll be fixed when a CM9 nightly show up. I'll look into this later to find a better way.
[Android General] XlAfbk:
would be great to have a /#device/cm9/latest url that just redirects you to the latest build as that's what you want to look at most of the time anyway
[Android General] cdmackay:
Oh, sorry, that's me getting confused by the dates on the review, sigh...

thanks!
[Android General] Kung-Fu-Tse:
very good job :)

can't wait for BBQDroid :D

Maybe gives a beta for try (testing) ?
[Android General] XlAfbk:
you guys planning to do rss? I wrote a php which generates rss from the same json sources the site uses, could easily be changed to get the data directly from mysql, would love to help you guys adding rss like that if you're interested.
[Android General] nebkat:
Done, thanks for the tip ;)
[Android General] Kung-Fu-Tse:
wtf is this :eek:
[Android General] chadouming:
We fixed some problem we had with individual changelog. You should all see the good change now. Enjoy it ^^
[Android General] Kung-Fu-Tse:
hmmm no, same :(
[Android General] chadouming:
Working fine here. Give it another try :P
[Android General] Kung-Fu-Tse:
@ chadouming:

ok, screenshot?

I try again and also 1970 :o
[Android General] chadouming:
We did some change at the time you posted you screenshot, but the fact is that the caching last for an hour. I was at work when we did it and no problem. Now i'm at home and still no problem.
[Android General] XpLoDWilD:
What browser are you using? Is there anything in JavaScript console?
[Android General] Kung-Fu-Tse:
I use Firefox (FF) v12

I have installed:

and java in FF (under plugins) I can see:

EDIT: only today I have this problem. Befor: NEVER with BBQlog :)

---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------

OK,

I refresh the site and I open "Web-Console" and I can find this:

---------- Post added at 09:21 PM ---------- Previous post was at 09:16 PM ----------

I refresh again and here full-copy (web-console):
[Android General] cdmackay:
Yup, still getting 1970 here, too.

Firefox Aurora 14.0a2 (2012-05-28)

Hundreds of warnings in error console, e.g:

Timestamp: 28/05/12 22:19:04

Warning: Error in parsing value for 'background-image'. Declaration dropped.

Source File: http://changelog.bbqdroid.org/css/bootstrap.css

Line: 2799

Timestamp: 28/05/12 22:19:04

Warning: Error in parsing value for 'filter'. Declaration dropped.

Source File: http://changelog.bbqdroid.org/css/bootstrap.css

Line: 2803

[22:19:04.193] Expected declaration but found '*'. Skipped to next declaration. @ http://changelog.bbqdroid.org/css/bootstrap.css:2813

etc, etc...
[Android General] scoffyburito:
There's no P4 (Galaxy Tab 10.1 3G) support. :D There are cm9 nighlties

And I have the same 1970 problem aswell
[Android General] Kung-Fu-Tse:
xplod... refresh this site, I add into my post the web-console LOG ;)
[Android General] chadouming:
Can anyone who have the "70's" problem try on chrome plz. I'm not at home currently and wan't to know if it's a browser problem.
[Android General] cdmackay:
Don't have Chrome, but can confirm it looks OK using Opera 12 Beta.
[Android General] iXNyNe:
Haven't viewed from desktop, but chrome beta on my phone shows correct dates. No '70s.

I've not tried any other browsers or desktop. Just chrome beta on android (sgs2 cm9)
[Android General] XpLoDWilD:
Tried on Firefox and yes, it's borked. Seems like it's something nebkat done recently because on my older personal copy of the system, dates looks fine.

Edit: Fixed.
[Android General] cdmackay:
Yup, confirmed looks good now on Firefox, to me.

thanks!
[Android General] Kung-Fu-Tse:
now it works good (correct date) :)
[Android General] peterperfect:
Xplod and nebkat fix all teh thengs!
[Android General] XlAfbk:
Maybe also change the links in device selector to point to /latest instead of /next?
[Android General] chadouming:
Nah, for this I believe having the next nightly information is more relevant than having information on the last nightly done.
[Android General] peterperfect:
I agree with chad.
[Android General] Kung-Fu-Tse:
changelog will not load, also no date (left site):

Web-console:
[Android General] chadouming:
We know, the problem has been fixed, but we need to wait that Get.cm get back online. Once it's back, we won't be down even if it get down.
[Android General] peterperfect:
the unbreakable log, we say!
[Android General] Kung-Fu-Tse:
oooh ok, I didnt see it, that get.cm is offline, because I dont flash every day the nightly (one or two times in a week) :)

thx ;)
[Android General] chadouming:
BBQLog is back :D

Edit : And faster than ever !
[Android General] XlAfbk:
hm, imho the primary usecase is checking the changelog of the latest build for device X. but ok..
[Android General] cdmackay:
Apologies if I'm being dense, as this may have been explained before, but I'm still confused, sorry...

For n7000, If I compare the "next" info showing on BBQLog, with that at http://cm9log.appspot.com, it seems that BBQ is not showing a number of changes, including those in:

android_device_samsung_n7000

android_kernel_samsung_smdk4210

Is this my confusion at the differences between the github commits and CM9 merges?

thanks much indeed...
[Android General] XpLoDWilD:
It shows them fine for me. It looks like cm9log doesn't take into account timezone. A few changes that are shown in "next nightly" are in reality in Friday 1st one.
[Android General] dylandylan1:
latest n7000 build...

Jenkins:

build: 2179

update-cm-9-20120601-NIGHTLY-n7000-signed.zip

Jun 1, 2012 2:57:11 AM (jenkins time zone is -5 hours) so 7:57:11 AM UTC

get.cm:

2012-06-01 08:25:45 (UTC) - that is the time it finished building ("took 28 min")

cm9log.appspot.com:

2012-06-01 08:25:45

bbqlog:

2012-06-01 08:25

--------------------------------------------------

So we can see that the nightly build times are correct all around.

How about all the commit times?

Well, choosing a random commit due in the next nightly;

"Added a summary and enabled description for owner info setting."

bbqlog, cm9log, gerrit, github, all display a commit time of Jun 3, 2012 12:55am UTC

So it seems commit times are also correct.

BUT, I've just noticed a few commits make their way to Gerrit a bit later then the original github commit and im not sure why. So the timezones are fine. I'm just not sure what the deal is in this case...

Compare these for example:

https://github.com/CyanogenMod/android_kernel_samsung_smdk4210/commits/

http://review.cyanogenmod.com/#/q/status:merged+android_kernel_samsung_smdk4210,n,z

------------------------------------------------------------

on github:

30th: px-switch: major update + cleanup from n7000 sources

30th: mach-px: clean up gpio keys code

31st: mach-u1: OTG related changes from GT-N7000 Update3

2nd: Merge "px-switch: major update + cleanup from n7000 sources" into ics

2nd: Merge "mach-px: clean up gpio keys code" into ics

on gerrit:

2nd: mach-u1: OTG related changes from GT-N7000 Update3 (MERGED)

2nd: px-switch: major update + cleanup from n7000 sources (MERGED)

2nd: mach-px: clean up gpio keys code (MERGED)

------------------------------------------------------------

not sure exactly what is happening and at what point these commits would actually be included in builds.....
[Android General] cdmackay:
Further confusion (for me) in that I would swear 100% that the BBQLog entries for 31st May have changed today, since I checked them yesterday (2nd June). Is that possible?

As to changes, consider:

n7000: Bring storage configuration in line with I9100/I777

Merged on Jun 01st at 03:19:25 in android_device_samsung_n7000

I would swear that this was not visible anywhere on BBQLog (for any date) when i checked yesterday. But it's there now, under 20120601.

Am I going mad? :)
[Android General] XpLoDWilD:
Changes are pulled every 15 minutes. Maybe you came at the exact wrong time ;)

Also, not to mention there is the commit AND the "Merging" added in BBQLog. A commit might be done on May 31st, but merged only a few days later. On github the commit will appear at the original commit date.
[Android General] renspoesse:
Works well, thanks for the work.

I do experience some problems regarding the CM version. I've selected CM9, but sometimes CM7 builds appear in the list. Screenshot attached, url was changelog dot bbqdroid dot org/#galaxys2/cm9/1338716895. I believe there are some more problems regarding the CM version when going to the Next Nightly page, but I'm not sure.