[Q] Are all Android devices limited to 2gb of video recording? - Android Q&A, Help & Troubleshooting

My Galaxy Nexus and Transformer Prime both stop recording at a 2gb file size, is this true of all android devices? Is there any way around it, an app or something? I've tried a couple that didn't work but maybe I missed one that does. I'd like to be able to record at 1080p until the memory card is full. Any help is much appreciated.

I am not exactly sure if this is true for all, but my htc evo 3d is also limited to 2gb.

I've seen conflicting reports, some say 2gb limit, some say they can record until card is full. I'm starting to think nobody can get passed 2gb.

Well in any case you won't be able to record continuously till the SD card is full, because Android uses the fat32 file system for SD card which has a maximum limit of 4GB per file. But 2GB, that's weird, I would think that they at least limit it somewhere near the maximum. Maybe their intention was to keep it at a safe limit to avoid data corruption or something. Plus the Galaxy Nexus has a unified storage (no SD card) which runs the ext4 file system, and that has no small limitation on file size like fat32. So yeah, seems pointless to have a 2GB cap.
Sent from my Desire HD using xda premium

It doesn't make much sense, both the prime and Gnex can save file sizes above 4gb so I dont think they are formatted in fat32. There has got to be a way around it but I haven't been able to search it out.

Yeah, they're not fat32. They're formatted to ext4. I mentioned that previously. Stumps me too why the video size should be limited.
I'm guessing there are some custom ROMs which have this limit increased/removed? Try to search in the development section of GNex forum to find any posts related to this.
Sent from my Desire HD using xda premium

It doesn't make sense, bump one more time to see if anyone knows a way around this.

As sashank said FAT32 normally is limited to 4GB. I read somewhere, that integer which stores size is type unsigned int, so it has range from -2GB to 2GB.

So can galaxy nexus have the FAT32 limit removed on the camera, as it is ext4? Surely, someone has done this.

Did anyone tested video recording on the Nexus 4 ? Does it go over the 2GB limit (on an external EXT card) ?

Has anyone figured out a solution for this? I want to record long videos with the phone fixed at a position. But for me too the size doesn't go above 2gb. I am using a Galaxy Nexus running 4.2.2.
And sorry to bump an old thread.

AbhishekS said:
Has anyone figured out a solution for this? I want to record long videos with the phone fixed at a position. But for me too the size doesn't go above 2gb. I am using a Galaxy Nexus running 4.2.2.
And sorry to bump an old thread.
Click to expand...
Click to collapse
I'm having the same problem. I'm using GS3 i9305 with cm10.1, and the video recording stops at 2GB, full hd 1080p. In stock rom though, the video stopped at 4GB, and showed the message "maximun size reached" or something. I've tried 3rd part apps like Camera JB+ but nothing, it stops at 2GB.
I can transfer files bigger than 4GB to the phone though without any problems (I tried with an 8GB iso file), so I don't know what the problem is. I'm using the internal storage only, no sd card...

also would like a solution for this.
im having the same troubles with my lg thrill 4g.
would be nice to have something automatically split the video file into 2gb chunks as your recording and i could then stitch them together later..
(and no restarting the camera after it auto stops recording wont work as you miss several seconds of whatever it is you are filming )

finally found this thread full of posts from people facing the same dilemma and looking for answers. apparently, there isn't a great deal of interest in the scene for overcoming this limit, judging by the limited amount of threads and discussion on this issue and the fact that there isn't some customisations, mods, roms etc that include element that allow the video recording limit to be exceeded.
it is telling in a way, that the majority of smartphone users never bother or care enough for the issues to be raised and discussed more extensively in the community.

same oroech
hi,
i am still looking for solution the buildin camera apk, but if you are interested in third party apk then visit my thread
http://forum.xda-developers.com/showthread.php?t=2485063
all apk can record unlimited size and duration so it is the camerabuild in restricted from recording over limit and it is nothing to do with fat 32 format, because if it is why other 3rd party apk will work with no issue but i prefer the build in cam apk that is why i like to see solution for that and that is only possible by programmer to decompile . modify and recompile it again, i tired to decompile myself to see if i can get my head around, but i get error when decompiling it while i can decompile some other apk with no problem.
thank you

i think, it's the way how the apps create the file. The Camera app is recording in it's virtual memory backend. And as you know, a 32bit proccess can't allocate more than 2gb ram. I tested several dashcam software and they all crashed while reaching 2GB of recording data. Those apps let you choose to save the record to chunks of x minutes.
just my thought.... maybe i'm completly wrong

TrusterX said:
i think, it's the way how the apps create the file. The Camera app is recording in it's virtual memory backend. And as you know, a 32bit proccess can't allocate more than 2gb ram. I tested several dashcam software and they all crashed while reaching 2GB of recording data. Those apps let you choose to save the record to chunks of x minutes.
just my thought.... maybe i'm completly wrong
Click to expand...
Click to collapse
Probably this particular issue is not technical, although next to that there would be the 4GB limit on FAT32.
It seems that this is an Android limitation imposed due to legal reasons or financial ones, depending how you look at it.
There are several articles on this issue but not just Android, it covers all digital cameras, they have a 30min. recording cap which usually falls on the 2GB limit for most standard Android devices. This is due to a taxation on video recording devices which I'm guessing have one class for less than 30min. continuous recording time and a different class for greater than 30 min. continuous recording time.
According to a few articles I've read, the Word Trade Organization has specified these parameters in their Information Technology Agreement.
Google must have capped this to prevent a bigger taxation on the devices than it already is. I'm guessing the average person doesn't need more than 30 min. of continuous video but even if they do they just have to press 'recording' again. Of course that doesn't change the fact that this thread exists because some people really want the continuous and automated recording to go beyond 30 minutes. I wonder if some Android guru is able to find anything on Android kernel where this is set up as a limitation. Would be awesome to defeat the WTO with one line of code.

Related

MsgQueue Map File Microsoft Status Message SMS Protocol

Hello all,
i have around 10 Files with the name above in my XDA some of them with a size of 260k and some with 1,65Mb. What are they good for or where are they from.
I can´t delete them and I don´t see them in the memory usage.
regards
miba
Huge MsgQueue.. files in Windows directory
I have the T-Mobile Pocket PC with just the built-in 32MB of RAM (256MB SD card on order...)
In my case there are a bunch of MsgQueue-blah-blah files in the Windows directory, 7 of which are 1.65MB each. Plus a 3.83MB file called "rsupgrade.cp64". That's about 15MB.
Unfortunately I don't have an answer, only an additional question... hopefully someone can answer us both.
Are these eating into my RAM or am I seeing files from ROM? I suspect RAM since they change periodically. Are they critical or can I delete them? If the latter, is there a way to limit their size or prevent them from reappearing?
T-Mobile Customer Care level-3 support was relatively clueless as usual, but they did suggest that I could do the following to determine how critical those files were:
1. Perform a backup
2. Do a hard reset
3. Check and see if the offending files went away
4. Restore from backup
If the files went away, then supposedly you should be able to delete them yourself if/when they reappear later. But realize that's just the CC guy's theory, and he didn't sound too sure of himself. I'm sure the regulars in this forum could provide a much more intelligent analysis.
Any help?
Thanks.
(some?) T-Mobile MDA's have an rsupgrade as part of ROM, as they perform a phone upgrade as part of a ROM upgrade. Which has really surprised a few people with the 'wrong' phone (900/1800 as opposed to 900/1900) as they then had to struggle to get phone functionality back.
You can try deleting the file, it no longer serves a purpose after the phone is upgraded. But if it won't delete, I would suspect it's in ROM, and in that case it's not bothering you.
Odd
Emboldended by your advice (Peter Poelman) I prepared to delete the rsupgrade file by first backing up through ActiveSync. However, after doing so, the offending file was gone. Stranger yet, I don't think I reclaimed any memory as a result... (hadn't recorded "before" amount yet - was going to do that after backup. But I think I would notice a 4M difference)
Well, either way, that's one down... Could you (or someone) comment on the MsgQueue* files? They all seem to be SMS related. How MicroSoft could justify allocating nearly *half* of the unit's available ram for some SMS caches is beyond me... Well, for M$ I guess it's not surprising, given the alleged unholy alliance between M$ and the RAM industry.
these files are actually in ROM, not RAM but it's impossible for the end user to know that from the properties of the file. Likewise, according to microsoft, those files are not reporting what is actually being used, it may say 1.7megs but it's not really. Per MS, do not try to delete these files as doing so would render the device broken. I think they have to do with the messaging portion of the PPCPE.
Thanks
Useful info, thanks.

Android 3.0 Honeycomb Preview Image v04 - 2/7/2011

First of all I have to thank the CM people, especially mbm, nemith, fattire and cvpcs for their work on gingerbread which helped me a lot in understanding where to look and what to patch.
The whole thing is based on the honeycomb preview emulator images, some of the B&N modules+driver, pieces from the upcoming CM7 and manual patching ARM assembler in libraries, writing ugly scripts to hack around various issues, a lot of time and many brain cells.
Use this on your own risk. I'm not responsible for any damages. This is not meant as a primetime ready rom. This is a preview after all.
The unzipped image is around 3.5gb and fits on 4GB SD cards.
MD5 (nookhoney04.img.zip) = 27396e63396a59a25f5d6fdbe0341276
http://www.rbrune.de/nookhoney04.img.zip.torrent
http://www.rbrune.de/nookhoney04.img.zip
Changelog
v04 - 02/07/2011
increased touchscreen sensitivity and made touchscreen more usable close to the borders (kernel change)
fixed heap size issue to get much more programs running (e.g. nook app, kindle app, etc.)
v03 - 02/05/2011
fixed screen turning animations and previews in taskswitcher
sd card access and secure storage support
turned off the debug screen flashes and vibrator
added display timings
sd card image now usable on 4gb cards
changed to a self compiled kernel to make these things work
reduced compressed image size
v02 - 02/02/2011
sound support
patched in some graphics improvements. Can play non-hd videos from m.youtube.com
sdcard storage
v01 - 02/01/2011
initial release
Status
What works:
Graphics acceleration
Accelerometer
Wireless!
Touchscreen
Buttons
Sleep/Wakeup
Sound
Known issues:
The accelerometer behaves funky. Will try to fix this.
The Gallery app crashes when opening an image. Not my fault, it's broken in the emulator from google too.
Doesn't work:
DSP e.g. no hardware video decoding (and will possibly never work before the AOSP release)
FAQ
Q: Why?
A: I thought it would be fun. It was and still is. And now developers have an actual device to test their apps on instead of relying on the slow emulator.
Q: How?
A: I'm planning to write a blog post. Mostly learning how Android works, debugging, patching, reusing binaries from different sources, finding easy ways to reach a goal, try and error, a lot of brain power.
Q: During boot I get stuck at the Android screen with the blinking cursor.
A: It seems to be a timing issue with mounting the partitions. Sometimes rebooting helps to get it booting. If not a different SD card might to the trick.
Q: Why is there no Market app installed?
A: There's no legal way to distribute the google apps with a ROM.
Q: Angry Birds, Nook reader, Kindle app?
A: Yes.
Q: I want to port Honeycomb to device xyz... send me the instructions how to do that now!
A: I like the 'I' in that sentence - but there are no instructions, no source, no nothing. Learn and read about Android, Android porting, making custom roms, embedded systems, ARM assembly, driver programming, programming in general, the Linux Kernel and much more - and when you're comfortable and have experience with all of that come back and do your port.
Q: Can you port Honeycomb to device xyz?
A: I don't have xyz. And even if device xyz would magically appear at my front door doesn't necessarily mean I'll have the time and motivation to port anything to it.
Q: I want to use a different kernel what changes did you make in the kernel?
A: https://github.com/rbrune/nook_kernel
Q: Where can I donate?
A: I don't want any money. If you want to put your money to good use donate to a humanitarian organization and/or the EFF.
--
Rafael Brune
awesome, time to mess around with this.
Amazing work. I'm always impressed when people get an SDK image booting on a device and working properly, but this isn't even technically a tablet! It's an e-reader that was hacked. Unreal.
Keep up the good work.
deeper-blue said:
I decided to release what I have so far. May everybody have some fun with it.
But first of all I have to thank the CM people, especially mbm, nemith, fattire and cvpcs for their work on gingerbread which helped me a lot in understanding where to look and what to patch.
What works:
-Graphics acceleration
-Accelerometer
-Wireless!
-Touchscreen
-Buttons
-Sleep/Wakeup stuff
Doesn't work:
-Sound (sadly! Despite my efforts the last hours I didn't get it working properly yet)
-DSP e.g. no hardware video decoding
The whole thing is based on the honeycomb emulator images, the B&N V1.1 kernel+modules+driver, pieces from the upcoming CM7 and manual patching ARM assembler in libraries and writing ugly scripts to hack around various issues.
Use this on your own risk! I'm not responsible for any damages!
The unzipped image is around 4gb. I use it on a 8gb sd-card. In principle the image should work on a 4gb card.
http://www.rbrune.de/nookhoney01.img.zip
--
Rafael Brune
Click to expand...
Click to collapse
Dude, you are awesome!
in b4 thread explodes
great work, its running pretty nice
I'm going to buy an 8GB card on payday. My 2GB isn't enough for this, but that's amazing. Will definitely be using a lot. Thanks a ton for all of your hard work! Expect donations.
Looks like you're gonna make the front page of engadget and the other sites again
Heres a Mirror to v04:
http://android.stolenrobot.com/NookColor/Honeycomb/nookhoney04.img.zip
Here are some basic instructions on how to flash it:
Windows Instructions
Download Win32DiskImager.exe
Download the file in the first post and extract the img from the zip
Run Win32DiskImager and make sure you pick the drive letter corresponding to your MicroSD card
Click the Folder icon and locate the img file you extracted earlier
Click on Write and then wait...
Once its done remove the SD card from your computer
Power off your nook color and insert the MicroSD you just prepared
Power On your Nook Color and wait for it to load
Welcome to Honeycomb!
This makes you wanna buy a nook! GJ!
Robotic Clone said:
Looks like you're gonna make the front page of engadget and the other sites again
Click to expand...
Click to collapse
He already made it here: http://www.androidcentral.com/honeycomb-nook-now-available
cloud79 said:
This makes you wanna buy a nook! GJ!
Click to expand...
Click to collapse
nooo...
This makes you wanna buy a nook...
just a quick question, does anyone know if this does fit a 4gb micro sd?
its all i have on me at the moment.
urbanengine1 said:
nooo...
This makes you wanna buy a nook...
just a quick question, does anyone know if this does fit a 4gb micro sd?
its all i have on me at the moment.
Click to expand...
Click to collapse
It doest, 4gb img, formatted 4gb cards really 3.69gb, installing
Linux now just so I don't need to wait
Sent from a NC on [email protected] using tapatalk pr0z
Wow this is just incredible, downloading it right now. - Thanks
Who would of ever thought that a book store would be the one to release the goto android tablet?
what linux users do? to use it? just like booting other OS?
thanks
10 characters
Damn it. I only got a 2gb card
Nook Color via Xda App
can this be chopped up and used on the htc hd2
Thanks for this bro.
10076757 said:
can this be chopped up and used on the htc hd2
Click to expand...
Click to collapse
right now that seems a bit (quite a bit) pre-mature, also honeycomb is definately destined for tablets (atleast the pre-release is) so even if you could it seems that it wouldnt run (see http://phandroid.com/2011/01/28/and...ator-shows-signs-of-smartphone-compatibility/ for more info)
Dude you are so the man going to try this first thing in the morning. Words really don't express our appreciation for you.
mckooter said:
right now that seems a bit (quite a bit) pre-mature, also honeycomb is definately destined for tablets (atleast the pre-release is) so even if you could it seems that it wouldnt run (see http://phandroid.com/2011/01/28/and...ator-shows-signs-of-smartphone-compatibility/ for more info)
Click to expand...
Click to collapse
If you take a look in the settings there are a lot of references to phone features but yes I do agree this is will more than likely start out on tablets and large screen phones

[Q] Freezing on ezPDF reader

Hi,
this is my first post so don't kill me if I do anythong wrong
The main reason I bought the Archos 101 was to read and annotate pdf files as I have to read about 400 pages per week for my study. After a short research I found out that everybody dealing with the subjekt recommends ezReader.
Unfortunatly my device (with UrukDroid 1.5 on internl disk) keeps freezing sometimes when I turn pages. With sometimes I mean today it didn't happen for 3 hour of reading and then it I couldn't turn a single page without having to reboot due to a toal freeze.The purchase of the 101 became pretty sensless by this fact also I have to admit that the tablet has many advantages that I wouldn't miss. And I love it!
As i see it there are 3 ways of dealing with the problem:
1. It's the fault of the device because it has not enough RAM for reading large PDF files with text in backround and JPEGs of the scan beeing displayed: Buy another Tablet (I don't want this and I don't have the dough)
2.ezReader has a lot of functions but it's crap anyway because it's not stable: Buy another app for annotating (As I coudn't find anything on the internet about this problem and nothing about a comparable app this seems
3. It has to do with UrukDroid: No idea. I don't get crashes on any other app and I tried diffrent things in UrukConfig like turning of CPUgovenor and making swap files and swappiness first larger then smaler.
So as you see I really need your help. thx
Alright,
I just found out that to freezing correlates with the size of the file and the number of annotations made. So I suggest again that it's a problem of RAM. Anybody who ever printed a pdf with 60+ pages has maybe recognized that there are often sent 200-500mb to the printer also the file itself has only 2-5mb.
But why is the device freezing? There must be other apps with exploding RAM use there has to be some "mechanism" in the kernel to prevent crashing just because of full RAM, or not?

Droid Incredible 4G LTE FAQs

I've noticed a lot of similar questions around these forums, so I decided to collect some in the same place. This is by no means an exhaustive list.
I can haz root/S-OFF?
There are options for unlocking your bootloader by changing your SuperCID, also there are options for obtaining S-OFF.
Thanks to Team Fireballas for the root method, and thanks to unlimited.io for S-OFF.
Now, please, don't talk like that anymore. Proper grammar, spelling, and punctuation help us understand the question or point you're trying to get across.
My FriendStream (or another HTC) app is missing
HTC decided to remove the FriendStream widget from view in an attempt to de-bloat Sense. On the stock ROM, you can still access it via the lockscreen and somewhat through the Social Clock.
Lockscreen: Settings -> Personalize -> Lock Screen Style -> Friend Stream
Social Clock: Widgets -> Clock -> Social Clock
On the stock ROM, there are several HTC apps missing from our phone, including the beloved flashlight. However, not all the apps are truly missing, just hidden. If you have root, you can re-enable it in the default.xml file located in the /system/customize/MNS/ folder. Remove the listing for FriendStream or whatever app you want to view in the app drawer from the "application_hide" function. FriendStream might also require the listing under "shortcut_hide" to be removed, as well. If you are rooted, a custom ROM may not have this problem.
Why do I have this annoying Wi-Fi icon?
For whatever reason, HTC or Verizon decided to add an annoying Wi-Fi nag icon in the notification bar telling you that you should turn on Wi-Fi. Why Verizon wouldn't want you to go over your data limit and owe them more money is beyond me. If you have root, there is a pretty simple fix for this, or try a custom ROM.
Can I use 64GB MicroSD cards?:
Our phone lists 32GB as the largest capacity microSD card it is capable of utilizing. However, that is the largest capacity allowed by the SD 2.0 standard, SDHC. SD 3.0 currently allows 64GB SDXC cards to be backwards compatible with SD 2.0 ports. Since every single 64GB card isn't necessarily going to work, it's best to read around and find the specific models which do.
Why do the official specs say our phone has 8GB of internal storage but I have less?:
Due to the controversial naming scheme of hard drives and other forms of data storage, companies actually give you less storage than you anticipated. 'Giga' is an SI decimal prefix meaning 10^9, or 1 billion bytes. Before hard drive capacities were in the gigabytes, hard drives used the IEC binary capacity for megabytes (2^20), albeit with the SI prefix. RAM is still calculated with the IEC value but with the SI prefix. So, when your internal storage is calculated to be 8GB, it's actually 8 x 10^9 rather than 8 x 2^30. Since Microsoft has been around since the other standard was set, Windows still displays storage capacity in the binary fashion and labels it with the decimal format.
On top of that, the Android system takes up a sizable amount of storage space, which is included in our phone's internal storage capacity, so you're only allowed 4.15GiB of data storage, which is 4.457GB. In short, you've got 8 billion bytes, but only 4.457 billion bytes usable, which is 4.15GiB. A similar capacity change will be noticed on your MicroSD card size. For example, I have a 32GB MicroSD card, which is actually 29.7GiB. I have a 2TB hard drive, but I only have 1.818TiB available. That's almost 200GiB "missing" because of the naming scheme.
What's the deal with the SD card naming scheme?:
Android 4.0 introduced a new way that SD cards are handled by the system. Previously, the eMMC internal storage of the phone was in the '/emmc/' folder, and the SD card was '/sdcard/'. Makes perfect sense, right? Way to screw it up, Google. Now, the internal storage is in the '/sdcard/' folder, and the real SD card is '/sdcard2/'. There's nothing you can do about this without serious modding to the system. It was changed because Google considers our phones to be high capacity now, so the need for microSD has passed. Yes, portable storage isn't necessary. If you have root, there's a mod that can switch it for you.
Can I install apps to the SD Card?:
Unfortunately, if you are unrooted and on the stock ROM, as per the SD card naming scheme change mentioned immediately above, apps can no longer be installed to the SD card. Like I mentioned above, if you have root, there's a mod for that. Otherwise, when saved in the 'Internal storage', apps are saved in the normal location of apps, '/data/app/'. When saved in the 'Phone storage', apps are saved in the eMMC internal storage partition '/sdcard/.android_secure/' as a '.asec' file.
Can I use Google Wallet?:
If you are rooted, then there's an experimental method that may let you successfully run Google Wallet.
Is our phone capable of being used globally?:
The latest 2.17.605.2 update enabled global phone on our phone. Go to Settings -> Call, and change Preferred Network to Global.
These have been the most common questions I have seen, and I'll be updating this list with more pertinent information when it arises. There are plenty of other questions that have been answered, even more which haven't. Look around for questions, and if there isn't an answer, don't be afraid to ask.
FYI the debugfs root method doesn't look to be working... not sure if you saw that in the other thread or not.
Had to throw up a pic...64GB....the only way to go
Card is a Sandisk 64GB micro.
Is there a patch available for that Wifi thing? I don't have much of a problem doing it manually through the APK, but if there's a faster way...
Platypus222 said:
Is there a patch available for that Wifi thing? I don't have much of a problem doing it manually through the APK, but if there's a faster way...
Click to expand...
Click to collapse
Hey self, nevermind. If anyone else wants to just copy over the APK that you need to modify, just do what I said here -- http://forum.xda-developers.com/showpost.php?p=30679535&postcount=40. You will need root, though, and I understand a lot of people don't. All it is is removing a few images that for some reason stops the notifications as well.
Platypus222 said:
Hey self, nevermind. If anyone else wants to just copy over the APK that you need to modify, just do what I said here -- http://forum.xda-developers.com/showpost.php?p=30679535&postcount=40. You will need root, though, and I understand a lot of people don't. All it is is removing a few images that for some reason stops the notifications as well.
Click to expand...
Click to collapse
lol. I appreciate you making it readily available for us, but most of us don't have root. Here's to hoping our spamming Verizon works quickly!
I added to and updated a few things on the list. Hopefully people will read it before asking the same things over and over.
IceDragon59 said:
Hopefully people will read it before asking the same things over and over.
Click to expand...
Click to collapse
Ha ha. You funny guy...
Jafmf95 said:
Ha ha. You funny guy...
Click to expand...
Click to collapse
I know. The likelihood of that, right?
Bump
Please add the DirtyRacun s-off method.
I'm sure there's other stuff, too. Lots had happened since we received s-off.
Thanks
Sent from my Fireball using Xparent Blue Tapatalk 2
+1 sticky plz
IceDragon59, you've done a nice job with the FAQ, I wonder if you might also consider taking on the task of making an index post for ROMs, recoveries, unlock methods, scripts, themes, etc?
Oh, and it looks like you can remove the please sticky notice from the title.
mdmower said:
IceDragon59, you've done a nice job with the FAQ, I wonder if you might also consider taking on the task of making an index post for ROMs, recoveries, unlock methods, scripts, themes, etc?
Oh, and it looks like you can remove the please sticky notice from the title.
Click to expand...
Click to collapse
That's not a bad idea. I'll make it my weekend project. And thanks for pointing out the fact that this thread finally got stickied after 5 months.
FYI, the direct link in the OP to the post with the .apk for killing the wifi nag is outdated. It takes you to post #40 in that thread, but that .apk may actually botch things up for folks running the latest stock Sense. There is a post a few posts later with an updated .apk to match the more recent Sense.
Question
Is this an hpdi/mdpi device? sorry for being ignorant...
Thanks in advanced to whoever can answer this!
mr_dr_parker said:
Is this an hpdi/mdpi device? sorry for being ignorant...
Thanks in advanced to whoever can answer this!
Click to expand...
Click to collapse
hdpi
Thanks!
jose51197 said:
hdpi
Click to expand...
Click to collapse
Thanks!
My incredible dont work with samsung USB cable (I hawe 2), but works with LG G2 USB. why is that?
kobebryant said:
My incredible dont work with samsung USB cable (I hawe 2), but works with LG G2 USB. why is that?
Click to expand...
Click to collapse
Strange, my works with Samsung cable good, same like on original htc usb

[Q] Resetting Firmware on chinese Network Media Player

Hi, guys!
Please don't lynch me for being a noob, I have used search button and I have looked in the threads the forum offered when I wrote in the title, and still found nothing that'll help me.
I recently bought a generic media streamer from DX.com (SKU 112201).
It's compact, light and runs Android 2.2 on a 1GHz CPU, 256MB RAM and 2GB flash memory (though if I looked in the right place there are only about 200MB of storage space).
The little box is not only full of magic but also many chinese apps (some of which open up the same interface) that I have no use for, not to mention the whole OS is chinese/engrish with errors popping up every minute.
The streamer runs slow and often hangs and I can't for some reason find certain apps in the Play Store when they're on the top of the list on other devices (probably chinese censorship or something).
I can easily find a guide to reinstalling firmware on my htc sensation xe, but I got nothing on this device.
My question to you is: does anyone know how to install a clean-no-third-party-apps Android 2.2 on a streamer or knows where I can get the guide?
Also, do you think I should even bother getting this thing working at its optimal capacity given its specs?
Thanks in advance and again sorry for my noob!
Ok, nevermind rewriting the thing, I figured out it's just a weak mainboard that looks like it was taken from a phone and (poorly) molded into a Media Player interface. The programs that bug me I can remove or disable, all I have to do is find a proper TV app that would work on this hunk-a-junk.
I still have an issue though - the device is supposed to have a 2GB internal storage memory and indeed it says "2GB" under "FLASH Memory" in the storage settings, but I have absolutely no access to it?
Can anyone please help me with this?

Categories

Resources