I flashed Bigxie's OTA JRO03C deodexed rom onto my Galaxy Nexus recently, as well as Team Eos 3 Jelly Bean Nightlies on my Xoom, and just noticed an odd bug today on both of them:
When I go into Settings --> Storage, I see all 5 categories calculating their size, and the used space on my internal storage showing as a large white / light grey box. See the first pic gnex_calculating. Once they are done calculating, the "Misc." category disappears completely, and only four coloured segments show for the four categories remaining. However, the total size appears to have shrunken significantly, but the Available space remains the same. See the second pic gnex_done.
The only conclusion that I have is that the "Misc" category doesn't show up, even though there is space "allocated" to it. On other words, it is just missing from the chart and list. I see the exact same behaviour on my Xoom. See the pics xoom_calculating and xoom_done, and compare the categories and the total bar size.
I feel like this shouldn't be happening, and I don't remember it happening with ICS. So, here's my question: Is this a bug? Or is this supposed to happen? If this is a bug, should I report it at http://source.android.com/source/report-bugs.html, because I searched the list and couldn't find anything similar. Is anyone else seeing this behaviour, or is it just me?
Mike.
[note: crossposted to the Xoom Q&A Forum here: http://forum.xda-developers.com/showthread.php?t=1777882]
Really? 235 views and 0 replies? All I need is someone to say "yes, it's happening to me too", or a "no, mine works fine".
Thanks!
No, mine works fine.
interfreak said:
No, mine works fine.
Click to expand...
Click to collapse
Are you on Bigxie's OTA deodexed rom? If not, what rom are you currently using?
Yup, I'm on that ROM.
interfreak said:
Yup, I'm on that ROM.
Click to expand...
Click to collapse
Thanks for the info. Maybe I have some files on my internal sdcard that's causing a bug to manifest. Perhaps I'll start temporarily removing files to see if I can pinpoint it.
masterslacker said:
Really? 235 views and 0 replies? All I need is someone to say "yes, it's happening to me too", or a "no, mine works fine".
Thanks!
Click to expand...
Click to collapse
Yes its happening to me too (bigxie, with thyrus navbar /apm mod)
Clancy_s said:
Yes its happening to me too (bigxie, with thyrus navbar /apm mod)
Click to expand...
Click to collapse
Thanks for the info! I don't think it's something specific to Bigxie's rom, because it's also happening to my Xoom. So I think it's either a Jelly Bean bug, or a specific app that is creating a conflict somewhere in the OS, which would lead back to Jelly Bean anyways.
It happen to me, too
What I am using is a official upgrade of JB on Galaxy Nexus.
Could some one tell me why and how to solve this?
I had downloaded a manga reader and 2 gigs of mangas. I uninstalled the reader, and then I started noticing what you described. I had to hook up my phone to the computer and delete all the manga PDFs. Which I couldn't see on the file browser with my phone.
I'm seeing this too.
Could this be linked to the fact that ClockworkMod has this crazy new backup format that creates a folder full of 6000 or so "blob" files? I think Android becomes very unhappy with too many little files in one folder.
didn't this just mean you have no files in the categoriy "misc" on your device atm?
darkarvan said:
didn't this just mean you have no files in the categoriy "misc" on your device atm?
Click to expand...
Click to collapse
No. Misc refers to all files that are on internal storage which don't already fall into those categories. I have several gigs that should count as such.
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
I'm seeing this too.
Could this be linked to the fact that ClockworkMod has this crazy new backup format that creates a folder full of 6000 or so "blob" files? I think Android becomes very unhappy with too many little files in one folder.
Click to expand...
Click to collapse
It's not the CWM backups, because it was happening when I was on TWRP, and its also happening on my XOOM which uses a CWM based recovery. It has nothing to do with recovery.
masterslacker said:
It's not the CWM backups, because it was happening when I was on TWRP, and its also happening on my XOOM which uses a CWM based recovery. It has nothing to do with recovery.
Click to expand...
Click to collapse
Moreover I'm still using the old CWM and it's doing it to me too.
They did change the mountpoint for the 'sdcard' (user data) in JB. Various people have had trouble with apps loosing data, which hasn't happened to me, but maybe this is another symptom of it?
I've not installed much user data, and only one small docx since moving to JB, so I doubt it's a whole lot of lost items in my case.
I guess when the ultra-official Google stock images come out we'll have to re-evaluate based on whether the bug is present there.
I've got another thread on XDA for the same issue (link). It seems to me that it's definitely a JB issue. I have the same problem on both my devices. Gnex with Stock 4.1.1 (rooted with CWM) and my TF101 Transformer with CM10 preview (CWM variant). I haven't lost any files, but my storage is way down (8-10 GB on each device).
It's definitely not just large files. It also takes a long time (30-60 seconds) to finish calculating the space for both devices.
I've had this issue on every version of JB I've tried.
I think it has to do with the file system. the "misc" folder that should count also tend not to appear when connected to a computer via MTP.
Smeelious said:
I've had this issue on every version of JB I've tried.
I think it has to do with the file system. the "misc" folder that should count also tend not to appear when connected to a computer via MTP.
Click to expand...
Click to collapse
I don't think it's a Misc folder. Android is identifying the files based on type Misc not showing up is the problem. I actually did some deep searching using File Manager and found the culprit on my GNex. My CWM Backups (which would be classified as Misc.) needed to be cleaned up. Now I just need to comb through on my TF101.
I'm having the exact same issue as well, same ROM. I hope a fix is around the corner somewhere.
Related
I know everyone is so in love with Jelly Bean and this is not the final release. I'd like to know what bugs you are experiencing.
For me two things bugs me so much. Auto-Brightness doesn't work as well as ICS and when my Bluetooth headset is paired, none of the voice input works. It hangs on initializing in every where; voice input, Google Now, and etc.
What bugs are you experiencing?
Sent from my Galaxy Nexus using Tapatalk 2
Isn't it pretty weird to be listing bugs on software not meant for general consumption and was shoehorned into place?
Firstly, this should probably be in Q&A
Secondly, I am loving everything about JB, except for 2 things.
Switching to the keyboard after inputting voice using voice dictation is kinda buggy, sometimes I have to select outside of the text box then reselect it for the keyboard to work.
And for some reason, my recovery keeps getting removed. I boot into recovery, and get the picture of the Android on its back, it's chest open, and a red triangle with an exclamation point. I have to reflash recovery every time I want to use it, and I have no idea why this is happening, because it didn't happen to me with ICS.
hurrpancakes said:
Firstly, this should probably be in Q&A
Secondly, I am loving everything about JB, except for 2 things.
Switching to the keyboard after inputting voice using voice dictation is kinda buggy, sometimes I have to select outside of the text box then reselect it for the keyboard to work.
And for some reason, my recovery keeps getting removed. I boot into recovery, and get the picture of the Android on its back, it's chest open, and a red triangle with an exclamation point. I have to reflash recovery every time I want to use it, and I have no idea why this is happening, because it didn't happen to me with ICS.
Click to expand...
Click to collapse
Have you deleted the "Recovery-from-boot.p" file in /system?
hurrpancakes said:
And for some reason, my recovery keeps getting removed. I boot into recovery, and get the picture of the Android on its back, it's chest open, and a red triangle with an exclamation point. I have to reflash recovery every time I want to use it, and I have no idea why this is happening, because it didn't happen to me with ICS.
Click to expand...
Click to collapse
Just so you know, you need to delete two system files:
efrant said:
Just some background for learning purposes:
There are TWO files added to your system when you apply an OTA update: a script (/system/etc/install-recovery.sh) that applies a patch (/system/recovery-from-boot.p) to the recovery partition, effectively re-flashing the stock recovery every time you boot your device. These files do NOT exist in Google's factory images -- they are only placed on your device if you apply an OTA update. They serve no purpose other than what I just mentioned, and are not part of the stock ROM (in other words, deleting them is perfectly safe, and will not affect your ability to apply any future updates using CWM).
Click to expand...
Click to collapse
anton2009 said:
Have you deleted the "Recovery-from-boot.p" file in /system?
Click to expand...
Click to collapse
harveydent said:
Just so you know, you need to delete two system files:
Click to expand...
Click to collapse
Well ****. Thanks guys!
I guess I only have one issue with JB now.
Hi all. Got a problem with my One X where it seems something is using all my storage space.
Has anyone seen this before? Easy fix? Going to move to a different Rom soon but this is crippling my phone until I move. Will post my current Rom in a follow up.
Villan Rom 1.1.1 is what I'm running.
CueballUK said:
Hi all. Got a problem with my One X where it seems something is using all my storage space.
Has anyone seen this before? Easy fix?
Click to expand...
Click to collapse
Known problem prior to 1.29.401.11 (or equivalent). If your base is same or newer, just copy the data off the phone, format SD Card and copy it back on.
Ok thanks BenPope. Will give that a try.
CueballUK said:
Ok thanks BenPope. Will give that a try.
Click to expand...
Click to collapse
Yup. It's a known issue that HTC has fixed in their updates Just copy everything from your SD, format it through the phone options, then copy everything back. It's an issue where files aren;t "really" deleted, hence still taking the space that should have been freed.
Sorry for the late reply to this. Where can I get the base files from?
You can use MIUI rom,but it's not android 4.1
I just recently installed cm10.1 on my Sprint GNex and pretty much the only problem I have is that it moved everything on my sd card to a 0 folder. I've read that this has to do with the multiple user profiles used in 4.2.1. Is there a way to turn this off? Because it's not recognizing any of my music the way it is now.
This can easily be corrected by searching xda or Google
Really dude? Don't you think I've tried? This is exactly the reason why I posted this question. I searched but could not find an answer. Why even bother replying if you're not gonna help?
If you searched we wouldn't be having this discussion. You're not the first one to face this problem. There are a couple of guides out there that keeps your sdcard the way it was before 4.2
If you can't find the answer by searching go back to stock, give the phone to your mom, then give up on life.
Again, I have searched for the answer to this issue, but the only thing I found was needing to have an updated recovery. Which I do have yet the problem persists. So you can just go **** yourself.
I made you mad bro? Well that makes me glad bro lol
Options are to move your music files back using adb PC or file manager. Or Use a music app that allows you to direct it to certain folders.
I haven't tried flashing the sprint 4.2.1 image or getting the ota but judging by k786's guide flashing the stock image first will keep your sdcard unchanged.
namtombout said:
I haven't tried flashing the sprint 4.2.1 image or getting the ota but judging by k786's guide flashing the stock image first will keep your sdcard unchanged.
Click to expand...
Click to collapse
actually he cant use my guide as the 4.2.1 factory image for the sprint version hasnt been released yet
PS- yes this is k786, i changed my username :good:
Edit- oh i was looking at this page and saw that the latest was 4.1.1 but if its out then he can use my guide :good:
Sprint leaked it out awhile back
namtombout said:
I made you mad bro? Well that makes me glad bro lol
Options are to move your music files back using adb PC or file manager. Or Use a music app that allows you to direct it to certain folders.
I haven't tried flashing the sprint 4.2.1 image or getting the ota but judging by k786's guide flashing the stock image first will keep your sdcard unchanged.
Click to expand...
Click to collapse
Not mad but frustrated. I knew moving the files was the only thing I could really do to solve it but I was hoping that there was an easier solution. It's kinda bothersome to move 25gigs of music
Use xenoamp. Its a music app that lets you choose where to look for your music
Have been using exclusively mrRobinson's method (ODIN + pre-rooted images) ever since I got my S3. Have not paid close attention until recently, when I noticed the many empty folders with the _x (x = 1, 2, 3, etc...). Any idea if I could just get rid of them?
And a related question: if I would like to start "clean" with the next new image mrRobinson may release any time now, knowing that I have all my data backed up, what would be the best way to go after it? Wipe data/factory reset, prior to ODIN-ing the new? Else?
TIA
Those were in there even with the stock rom. I have no clue what they are for.
Sent from my SGH-T999 using Tapatalk
tokenpoke said:
Those were in there even with the stock rom. I have no clue what they are for.
Click to expand...
Click to collapse
I wonder if I can just blow them up ...
Make a backup and see. I don't really mess around with folders I don't know about. They could be places to store temporary files or something.
Sent from my SGH-T999 using Tapatalk
tokenpoke said:
Make a backup and see. I don't really mess around with folders I don't know about. They could be places to store temporary files or something.
Since some days I have this mnt_ directory on my S4 (Android 4.3). It came up with problems of directories in Locus - map software.
They can not be deleted or changed.
How can I get rid of them ???
Click to expand...
Click to collapse
silber1 said:
tokenpoke said:
Make a backup and see. I don't really mess around with folders I don't know about. They could be places to store temporary files or something.
Since some days I have this mnt_ directory on my S4 (Android 4.3). It came up with problems of directories in Locus - map software.
They can not be deleted or changed.
How can I get rid of them ???
Click to expand...
Click to collapse
You dont.
They are obviously vital to the system if they keep getting rebuilt. Like I said, likely just directories for temporary file storage.
Click to expand...
Click to collapse
Pretty sure some are knox related. Just ignore them.
Disclaimer: I am not a ROM developer. I am a developer and Linux user, but I know next to nothing about creating Android ROMs. Whole other world to me.
I'm wondering if all three of us Epic 4G Touch users left might be able to get a working port of LineageOS 14 on our aging handsets.
The good news:
I just loaded the Official LineageOS 14 for i9100 20170419 nightly on my d710, and IT WORKS
...almost.
The bad news:
The ROM boots up, everything works and looks normal except for:
Wi-Fi - Settings app spins with message "Turning Wi-Fi on..."
Menu Button
Home Button
Now, I'm wondering if there is a way to fix these problems. I prefer on-screen navigation anyway, so that's probably an easy "fix." But Wi-Fi will probably be trickier. I assume it's kernel related, but I can't find any Nougat kernels for this device, so that will likely be the most difficult part.
Thoughts? Anyone else out there have any input or want to give this a crack?
Links:
https://wiki.lineageos.org/devices/i9100/build
https://wiki.lineageos.org/devices/i9100/install
https://web-beta.archive.org/web/20161224202958/https://wiki.cyanogenmod.org/w/Build_for_d710
https://web-beta.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
https://github.com/LineageOS/android_device_samsung_d710/tree/cm-12.0
https://github.com/LineageOS/androi...4.1/arch/arm/configs/lineageos_d710_defconfig
https://github.com/Lanchon/TWRP-Patcher-SGS2
https://github.com/Lanchon/REPIT
https://forum.xda-developers.com/ep.../rom-cyanogenmod-11-official-nightly-t2852074
Can you pm me your rom you used, i may be able to figure out how to get wifi to work, i dont have access to a computer right now but i can take a look at the rom you used when i get to one
svaethier said:
Can you pm me your rom you used, i may be able to figure out how to get wifi to work, i dont have access to a computer right now but i can take a look at the rom you used when i get to one
Click to expand...
Click to collapse
Link is in the OP. Here it is again: https://forum.xda-developers.com/galaxy-s2/general/rom-t3555834
Direct link to the download page: https://download.lineageos.org/i9100
How did you get past the 07 error then? Ive tried clearing everything from system to dalvik cache and nothing gets me to install the rom to look into the wifi issue properly
svaethier said:
How did you get past the 07 error then? Ive tried clearing everything from system to dalvik cache and nothing gets me to install the rom to look into the wifi issue properly
Click to expand...
Click to collapse
I don't know what you're talking about. I don't get an error.
The ROM flashes without modification. Make sure you have an up-to-date TWRP with the i9100 crossflash patch: https://github.com/Lanchon/TWRP-Patcher-SGS2
Ive tried flashing twrp onto my device using the guide that tells you how, even after editing the installer script to have the SPH-D710 line in it it aborts the installation
svaethier said:
Ive tried flashing twrp onto my device using the guide that tells you how, even after editing the installer script to have the SPH-D710 line in it it aborts the installation
Click to expand...
Click to collapse
I followed lots of advice from this thread: https://forum.xda-developers.com/epic-4g-touch/help/help-getting-stock-rooted-4-1-2-to-cm11-t3384832
I believe the method that finally worked for me was: Odin to EL29 rooted, Philz recovery, TWRP, CM11.
That's where I was before I tried the i9100 LOS 14.1 ROM.
I can get a twrp with a different rom then cm11 but that twrp doesnt have the img installation feature on it
svaethier said:
I can get a twrp with a different rom then cm11 but that twrp doesnt have the img installation feature on it
Click to expand...
Click to collapse
If you have root in CM11, you can use Flashify to flash the new TWRP .img file.
My E4GT still works, more than glad to throw my hand in the pot to make something happen. Haven't used the S2 in years so it's not updated, currently running an old build of CWM and a CM11 nightly with iso-rec support. If you could bring me up to speed on what I need to get from where I am to a newer recovery(TWRP preferred) and your ROM I'll start playing around with it. Last time I searched all of this to update left me more confused than anything with it being mixed up with the i9100 and i777 information as well.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
My E4GT still works, more than glad to throw my hand in the pot to make something happen. Haven't used the S2 in years so it's not updated, currently running an old build of CWM and a CM11 nightly with iso-rec support. If you could bring me up to speed on what I need to get from where I am to a newer recovery(TWRP preferred) and your ROM I'll start playing around with it. Last time I searched all of this to update left me more confused than anything with it being mixed up with the i9100 and i777 information as well.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
You should be able to flash the latest TWRP (for i9100) using Flashify. Beware that I have not been able to get TWRP to mount my external SD card, so any files you want to flash in TWRP need to be stored on internal memory. Everything else works perfectly. Mounting USB storage in TWRP works well, and that's how I've been able to get new files on the phone when I needed to.
After installing TWRP, make sure you run Lanchon's crossflash patch on it: https://github.com/Lanchon/TWRP-Patcher-SGS2
I used
Code:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
to enable flashing d710 and i9100 ROMs.
flamadiddle said:
You should be able to flash the latest TWRP (for i9100) using Flashify. Beware that I have not been able to get TWRP to mount my external SD card, so any files you want to flash in TWRP need to be stored on internal memory. Everything else works perfectly. Mounting USB storage in TWRP works well, and that's how I've been able to get new files on the phone when I needed to.
After installing TWRP, make sure you run Lanchon's crossflash patch on it: https://github.com/Lanchon/TWRP-Patcher-SGS2
I used
Code:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
to enable flashing d710 and i9100 ROMs.
Click to expand...
Click to collapse
Yeah, I took another look last night, the information available now clarifies things that seemed a mess back when I first looked into this.
Have you made any progress with your ROM? If the hardware keys are still not working it's because key mapping is different on i9100, also rotation is backwards or at least it was years back when I flashed a i9100 ROM on my D710. You can remap the hardware keys so that they function correctly. Other than that there should be no differences.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Yeah, I took another look last night, the information available now clarifies things that seemed a mess back when I first looked into this.
Have you made any progress with your ROM? If the hardware keys are still not working it's because key mapping is different on i9100, also rotation is backwards or at least it was years back when I flashed a i9100 ROM on my D710. You can remap the hardware keys so that they function correctly. Other than that there should be no differences.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I haven't done anything yet except try to load the unmodified i9100 ROM and report what works/doesn't. Really the only thing I need fixed is the Wifi, and I have no clue how to do that.
flamadiddle said:
I haven't done anything yet except try to load the unmodified i9100 ROM and report what works/doesn't. Really the only thing I need fixed is the Wifi, and I have no clue how to do that.
Click to expand...
Click to collapse
I'll reach out to some developer associates and see what I can find out about the WiFi.
Sent from my SM-S903VL using Tapatalk
I'm not a developer, but I have a D710 lying around and I am willing to do testing if you need me
I also have an Epic 4g touch that im willing to test stuff
So... I guess nothing ever happened with this ROM? I have a SCH - R760 from US Cellular that AFAIK is compatible with d710 roms. I would still be interested in running Nougat on my device - even though my eMMC seems to have issues at the moment.
chrismin13 said:
So... I guess nothing ever happened with this ROM? I have a SCH - R760 from US Cellular that AFAIK is compatible with d710 roms. I would still be interested in running Nougat on my device - even though my eMMC seems to have issues at the moment.
Click to expand...
Click to collapse
Never had any real interest, and I don't know enough to do it myself.
flamadiddle said:
Never had any real interest, and I don't know enough to do it myself.
Click to expand...
Click to collapse
Understood. So you said that the buttons didn't work and the wifi wasn't turning on. Were there any other major bugs that you noticed? I might try and make it work for our device, because why not!
Thanks for still responding after so many months!
chrismin13 said:
Understood. So you said that the buttons didn't work and the wifi wasn't turning on. Were there any other major bugs that you noticed? I might try and make a for for our device, because why not!
Thanks for still responding after so many months!
Click to expand...
Click to collapse
Those were the only two things I noticed. Bluetooth worked. I didn't see any apps crash (but I couldn't load new ones because no wifi). I didn't try cell service because I don't even have Sprint anymore, but I suspect that probably didn't work for the same reason wifi was killed.
Thanks for looking into this! I'm still interested if we can find a way to make it work. I just don't know much about creating ROMs. I'm not an Android dev.