Related
Hi all,
I have an Archos 70IT but, with an accident, the screen broke up, and now i wan't to know if I can do something with my Archos, like installing Linux on it, making a server or whatever else than letting it on the ground.
Thanks for your answer
eagleofdeath13 said:
Hi all,
I have an Archos 70IT but, with an accident, the screen broke up, and now i wan't to know if I can do something with my Archos, like installing Linux on it, making a server or whatever else than letting it on the ground.
Thanks for your answer
Click to expand...
Click to collapse
if it still runs then great - but how can you configure it to enable ssh, some kind of a share, or even usb access, without a screen?
can you use it by plugging an hdmi monitor to it? ( don' tknow if your model has hdmi out)
First of all thanks to reply ^^
Yes it still run (or it seems to run ^^) and the "how?" is the the question that i ask ^^
I will try to plug it to an HDMI monitor but I think it will not work (to make the external screen work you have to use a button, that i can't use without screen).
The only thing i've done is going in recovery and use the flash disk with my compute. If only we could make our self .aos i could make a one that accept SSH access, and then the work will be done, but we can't
hmmm.... that's a tricky one then.
Without trying to sound negative, all I can think of is to get another one, take both of them apart to get access to the screen connectors, attach working screen to yours and do whatever programming changes are needed so that when you power it on you can access it or vnc control it from another machine by default without having to touch anything. then put the other one together again and return it to the store or give it back to your generous friend who let you borrow it for the weekend
and no - I'm not that generous ;-)
There may be some other brilliant method but I certainly don't know of it in standard android.
I have bought another one (i was addicted to this thing ^^) but ... open it wil break the garanty so i'm not sure. Maybe i will wait some time before doing this (or wait another idea) but thanks, it's a really good idea ^^
If you can see anything on the screen you can get a wireless keyboard mouse combo to use the device. If you can't see anything you might have a pretty hard time and a lot of guess work flashing a custom kernel with SSH enabled by default. Does angstrom have SSH enabled?
Also not really android dev...
Sent from my A101IT using Tapatalk
Nothing visible on the screen, only white :S And for Angström I don't know.
(Could someone replace this subject on the right place!)
eagleofdeath13 said:
I have bought another one (i was addicted to this thing ^^) but ... open it wil break the garanty so i'm not sure. Maybe i will wait some time before doing this (or wait another idea) but thanks, it's a really good idea ^^
Click to expand...
Click to collapse
Cool, I agree about the warranty issue if you own the second 101 yourself.
My suggestions were slightly illegal (buy then return to store "I don't want it after all so would like a refund" LoL) or just not very nice ("thanks, I liked borrowing that over the weekend to play games" LoL).
Wait as long as possible in case someone more clever can help you out.
But I'm glad that my ideas weren't completely crazy anyhow
Cheers,
Don
But i'm also afraid to break something ^^
eagleofdeath13 said:
But i'm also afraid to break something ^^
Click to expand...
Click to collapse
that would stop me from doing it also. I was hoping you were more confident working insde tiny electronic devices than I am.
d31b0y said:
If you can see anything on the screen you can get a wireless keyboard mouse combo to use the device. If you can't see anything you might have a pretty hard time and a lot of guess work flashing a custom kernel with SSH enabled by default. Does angstrom have SSH enabled?
Also not really android dev...
Sent from my A101IT using Tapatalk
Click to expand...
Click to collapse
Hmm, seems like you could flash it with a cooked Uruk configured how you wanted it so that it would work with ssh/vnc from a straight boot. I'm trying to think of the steps that would be involved and if you would need a working screen.
If you knew the exact location of the menu items on the Uruk install you could do it without the screen (press vol down twice, then enter; next step press vol once, enter, etc - these are just examples, obviously). I think Uruk comes with ssh enabled by default. I could be wrong or missing a key step you can't do blindly, just thinking out loud here.
I've never used UrukDroid, but if someone here knows the steps it would be very, very nice! Thanks in advance and Thanks for your help.
Pull apart the broken one and see what the make/model of the screen is and then see if you can buy a new screen.
You could also contact Archos and buy a screen from them.
Thanks, yes I think i'll try to do that ^^
Same problem ...
Broke my screen too!
I'm trying this route ... EBAY - cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=230598268646
Cheaper but you have to use Western-Union: item.taobao.com/item.htm?id=9004146795
I dropped the http : //. I'm new to the forum and they do not let new members post links. I assure all that I have no connection to either link. In fact, I'm still waiting for my purchase from EBAY (it's only been a week or so from over-seas). I obtained the second link from forum(.)archosfans(.)com and had contact with them - they wanted $77 USD plus shipping and payment via WesternUnion. I chose EBAY because I felt I had more financial protection.
By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes? Suddenly you have dead spots, dead bands, ghost/phantom touches, stuck touches, broken drags, etc. Touchscreen works ok when held or plugged in, but is unusable on a table?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be using touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q, will work on LTE and custom ROMs also):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in this post.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
Settings->About tablet [tap "Build number" 7 times]
Settings->Developer options [check "USB debugging"]
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
wait until Android is COMPLETELY booted
Note: if you are on Android 4.4 the stock 4.3 kernel will not get past the BouncingBalls
wait 120 seconds for the boot to settle down
press/hold the Power button 10-15 seconds until the tablet reboots
proceed to next step
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
if adb reboot does not work for some reason, use the power button to shutdown/reboot
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
upon first reboot you will have the touchscreen software from the installed ROM/kernel
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.
very interesting! lots of FC after loading the file, cant really "Power off using power button" because of FC-windows, using adb reboot instead.
current ROM: [ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 10-TEST][2013/08/27]
ts-10: no more jumping in google maps while zooming/panning, but still jumping in other apps. after second reboot, starts jumping in maps again. after third reboot, no jumping on rightside of screen.
screenshot using two fingers
ts-20: lots of jumping on right side of the screen, zooming/panning in gmaps is still jumpy. after third reboot, still jumpy in gmaps.
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, same effect. after third reboot, still jumpy on right side of screen.
so what exactly are in those files?
neonlite said:
very interesting! lots of FC after loading the file, cant really "Power off using power button", using adb reboot instead.
tried ts-10. no more jumping in google maps while zooming/panning, but still jumping in other apps, will try others.
so what exactly are in those files?
Click to expand...
Click to collapse
When you say lots of FCs, can you tell me what ROM/version you are running?
You should IGNORE any instability in that first boot. While you can boot into android using the files I'm providing (and in some cases run fine), there could be mismatches in versions depending on what you have currently installed, which is why I say in RED you must reboot at least once before the system will become stable.
Once you do that reboot, you are back on your original software with just the touchscreen controller updated.
neonlite said:
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, seems most stable.
Click to expand...
Click to collapse
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
sfhub said:
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
Click to expand...
Click to collapse
yes, ignored all FC's. no problem.
ts-10 is running perfectly, no more jumpy stuff. maps/right side of screen, hold and drag working great too.
I really appreciate how much effort you've put into helping others with troubled devices here.
Could we get some clarification on what exactly the 3 packages are? Are these touchscreen settings customized by you or simply the settings from each of the 3 versions of 4.3 we have had available to us?
You sent me here from the other thread and i must thank you, the ts10 one worked fine and now no screen problems, cancelled my replacement. Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
It is the touchscreen controller software.
pashinator said:
Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
Click to expand...
Click to collapse
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
sfhub said:
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
Click to expand...
Click to collapse
cool i thought i broke it by bashing it to get the screen to work again
i've been a long time lurker at the xda forums and your multitouch fix made me register and become a member just to say thanks. ts10 fixed my multitouch issues, going to observer for a few more days and update you if there are bugs. thanks a lot!
My tablet was working perfectly on the JSS15J then JSS15Q came along and I found letters "sticking" while typing and the screen was unresponsive to touch while laying flat on a table. I flashed the ts-10-lock image and so far, so good. I have been typing for awhile now with no "sticking" letters, and while laying flat on a table. I have not encountered the unresponsive screen at all flat on its back or otherwise. I will continue running through scenarios that used to give me problems and report back if I encounter anything. Also, running Bulletproof kernel and no impact with kernel functions.
Thank you sfhub!
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
This is the video of my N7 placed on my MBPs' keyboard.
http://www.youtube.com/watch?v=H05N1P0dpTo
Can this really be only a software problem?
I am not really experiencing other touchscreen issues with my N7 except for some very rare stuck touches. This one I triggered by accident.
bandit_knight said:
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
Click to expand...
Click to collapse
So this guy goes to the doctor's office and says my head hurts everytime I hit the wall. The doctor says, then stop hitting the wall.
Couldn't you just slide it over and don't use the tablet on top of the keyboard?
Have you considered the MacBook Pro might be emitting interference? Stray currents and voltages? It doesn't take much to throw these capacitative touchscreens off.
On this thread, most people have it much worse than you making the tablet very hard to use. We are trying to get these units back into a state that is at least usable.
Your case, while an interesting science project really isn't something someone would feel any sense of urgency to help address.
Excellent.
I'll try these now and put them through there paces.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Great work
Incredible!! tried the ts10 and OMG everything is fixed!! Great work, sfhub!!
you should work in Google, seriously! shouldnt he, everybody?
My device is:
1) 4.3 JSS15Q
2) two finger touching registered as one finger, and muiti-touches ghosted. hold on the Left side of screen and the touch is registered repeatedly
1) TS10
Yea I booted 10 first and it is great. I can't reproduce any of the bugs I've seen before using YAMMT.
Google Maps Pinch/Zoom is working flawlessly. I couldn't even zoom in before.
The OP says to "fastboot boot boot-ts10-lock.img". Should we eventually "fastboot flash boot-ts10-lock.img" to make it permanent?
My N7 is:
HW rev_e
Bootloader....... FLO-03.14
15Q - CM 10.2 Kanged Build 9
Sitting the N7 on my Logitech Keyboard doesn't make it go crazy either! LOGITECH FTW
sfhub said:
It is the touchscreen controller software.
Click to expand...
Click to collapse
How do you "lock" it in so that it won't get updated? Is it just a file in the filesystem, if so how do you prevent "fastboot erase" from getting rid of it? I've looked at ektf3k.c and know where I need to make a change so that it will replace any non-matching version, but I don't really know where the actual firmware is stored. It doesn't seem to be in the vendor part of the kernel tree or in the actual ektf3k.c or ektf3k.h files. Where is it kept? kept in fw_data.b
I'm new to Android, but I'm not new to Linux or reverse engineering so please be patient with me. Just looking for a technical description of how you did what you did. What exactly is in the .img files?
EDIT: I haven't booted any of them yet, but I'm guessing these are Linux kernel images with a modified version of the elan driver. Sorry for being stupid, I'm just trying to put this all together in my head and I can't cope with anything that seems like magic. Thanks for your time.
EDIT: Ok, I figured out where the firmware is stored. I also successfully built a ROM with my compiled kernel and flashed them to the tablet. No brick, it booted the second try and seems to work. Of course there's no apps on it hardly.
I'm kinda thinking out loud here, please correct anything that I get wrong:
I started off with the assumption that there was a closed source driver, but that seems to have been incorrect on my part. After looking at the code a little more, I see that ektf3k.c appears to be the lowest level driver, outside the embedded firmware. The driver does only update the firmware in the case that the flash is empty (FFFF.....) or the firmware presented is a higher version (just as you said of course). It appears that a simple change will make it flash any version presented that is different than the one currently flashed in. I plan to try this on my tablet and see if there are any unexpected repercussions from doing so.
I wish I had a datasheet for the controller (hint hint anyone).
DISCLAIMER: I know that you have already solved this problem in an arguably better way, I just want to tinker around a little. Thanks again. :good::good::good:
sfhub said:
By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be able to get touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in the stickies.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.
Click to expand...
Click to collapse
So if we do this can we lock the boot loader backup. If for some reason it doesn't work will I be able to take it back for exchange. After unlocking the boot loader. Do people leave the boot loader unlocked . Is the software staying the same meaning will I be ok downloading future updates.
Is there a way to find out what variance is installed right now on the device? I got JSS15Q and my tablet is useable but sometimes there are ghost touches or the touch is stuck or gets interrupted and the likes.
An updating list to help give the Mad Catz guys an idea of what we want out of the OS. Please anyone post the features that you want and I'll update the list.
Read off of multiple USB flash/HDs ▬ currently recognizes multiple disk drives but does show mounted
Read and write support for NTFS file format
exFat Support
Webcam support(UVC)
USB audio input/output channel option
hide soft button bar on soft button bar or otherwise easily accesable
power off/restart/sleep menu button on soft button bar or otherwise easily accesable
screenshot button on soft button bar or otherwise easily accesable
HDCP Kernel
USB power management tool - for shutting down power to usb plugs while device is in sleep mode
Gamestreaming ▬ Its coming
Gamepad stick support in recent apps android view
system settings switch to change right click on mouse to back button instead of just being read as left click
Good thread, happy with the product, but still room for improvements!
Please, add webcam support(UVC) !
http://support.madcatz.com/Knowledgebase/Article/View/434/172/can-i-use-a-webcam-with-mojo
You can't clam to be a top-set box with out it!
Also exFat support would be nice
It's the standard for USB portable drives.
While I agree with this:
http://support.madcatz.com/Knowledgebase/Article/View/427/172/how-to-turn-mojo-off
It's a portable device, so yes, please let us turn it off
Hardware wise:
The controller's gamepad/mouse switch.. it should be a raised tab rather then an indedent at the very least, I don't have the nails to use comfortably, it should be switchable with your thumb not your nail.
Also the screws on the controller aren't your standard phillips (+) screws, nor allen keys.
I like to open my controllers with a Precision Screwdriver set and clean the contact points, I know of others that do also.
For an "open" hardware device, this is the only sore point for me.
Lastly, most TV's now have a USB port.. the power specs to me looks like it could run off USB power:
http://support.madcatz.com/Knowledg.../172/what-is-mojos-range-of-power-consumption
Like android phones, use a USB cable with a USB adapter.. I have too many bricks in my power adapter
Having the DC in and the headphone jack next to each other is a pain, I have make sure I'm not putting DC in the headphone jack.
Having the MicroSD card under the HDMI makes hot swapping next to impossible, very hard to get to with the plastic molding so close.
MC some more feedback,
The android UI works okay in gamesmart mode, but there's just one thing that's frustrating me.
When holding down the mojo button to get to the listing of the running apps, the CTRLR in gamesmart mode can't traverse nor select an app.
If this could be fixed, then changing from game/mouse mode wouldn't be needed at all while using the andriod desktop/UI :good:
Cheers
dheku-00 said:
[*]hide soft button bar on soft button bar or otherwise easily accessible
[/LIST]
Click to expand...
Click to collapse
I really second this point, it is so annoying to have those buttons when watching a film with xmbc. In games a bit less, but still it sucks.
Also, most people are probably going to plug in a keyboard, at least from time to time, but it would be nice to have a gamepad-friendly virtual keyboard, like the one of SteamOS. I.e. search "SteamOS Controller Input" as I cannot post links
HDCP + kernel
I wasn't expecting HDMI HDCP, but I guess it makes sense.
It's a pain when trying to capture HD gameplay, but I guess that wont change.
oh And while I'm here, it would be really really really .. really cool and open of mad catz to one day realese the kernel source of the mojo (or just the config settings) so we can compile our own hardware support
I know the shield had their kernel on github, not sure what happened to it tho, great idea too!
Kernel would be great so we can compile in CIFS support to mount network shares in the OS!
Huh I thought releasing the kernal source sounded pretty wild but after seeing stuff like Motorola releasing the Moto G kit kat kernel this seems like something that Mad Catz should totally do.
dheku-00 said:
Huh I thought releasing the kernal source sounded pretty wild but after seeing stuff like Motorola releasing the Moto G kit kat kernel this seems like something that Mad Catz should totally do.
Click to expand...
Click to collapse
If I'm not wrong, they MUST release the kernel source code. It is just a Linux kernel with the android patches and maybe some custom modification. Because of the Linux license (GPL v2) any of us can ask for the code and the vendor must provide it at no additional cost.
HOWEVER, if the bootloader is not unlocked and/or you do not have root access then you cannot do anything with useful the sources: you can recompile the kernel, you can compile all the modules you want, BUT you cannot load the new kernel into the Mojo and you cannot insert the new modules into the kernel.
Nowadays many hardware vendors publish a semi-official way to have root access or to unlock the bootloader. Let's hope that the "hacking friendly" promise that Mad Catz put forward is not just a dishonest selling point.
Controller Keyboard input Method
http://img.gawkerassets.com/img/17ynanc1qocy1jpg/original.jpg
add root access inside rom
add usb slave mode for adb
dheku-00 said:
An updating list to help give the Mad Catz guys an idea of what we want out of the OS. Please anyone post the features that you want and I'll update the list.
Read off of multiple USB flash/HDs ▬ currently recognizes multiple disk drives but does show mounted
Click to expand...
Click to collapse
I have a usb hub plugged into my 2.0 port with two usb drives attached. Both show as mounted in the settings (along with my SD card). Although I can read off of my usb drive via file explorer, I can't read off the drives with emu apps such as nes.emu and fpse etc. So I just use my usb drives for storage copy files to the sd when needed.
As a hard drive junkie, I'm gonna throw in a feature I'd like to see: Cut the power to USB when the unit goes into sleep mode if an external drive or thumb drive is detected. My tablet does this, and I'm able to disengage my hard drive without worry of data corruption...
Unfortunately on the MOJO my drive constantly runs (even after I unmount it)...Is there a way to cut off power when ejecting/unmounting a drive? Cut power when the system goes to sleep? Both of those are kind of important.
mherma said:
I have a usb hub plugged into my 2.0 port with two usb drives attached. Both show as mounted in the settings (along with my SD card). Although I can read off of my usb drive via file explorer, I can't read off the drives with emu apps such as nes.emu and fpse etc. So I just use my usb drives for storage copy files to the sd when needed.
Click to expand...
Click to collapse
When you say show up as mounted in the settings what do you mean? I have a usb hub and have 2 hds plugged in but since when a disk drive gets mounted and it's 'home directory' is mnt>usbdrive. Whatever disk drive was plugged in first gets to be in this folder and the 2nd plugged in drive while recognized has no home directory.Thats why other apps can't recognize multiple disk drives only one usb drive. What I want is a mnt>usbdrive>usb1, usb 2, etc directory setup.
What is the likelihood that in a future update (if it happens) that they will include an option to HIDE the soft button bar.
This is a deal-breaker for me. I like my movie-watching experience and game playing experience to be immersive. Having a menubar there ALL THE TIME might as well be a form of adware as far as I'm concerned.
What's the point of a micro game console experience if it always looks like YOUR SMART PHONE is streaming to TV because the menubar is there to remind you? How stupid can they be?? Did they just release this a proof of concept? To say, "Hey, look what we did! Screw the customer experience..."
Please tell me "not to worry" or a "future custom rom" or "mod" will be "released soon to address."
If not, I'm returning this hunk of junk when it arrives.
I'll have ur lady junk!
wow
I'll give you $150USD plus postage if it's unopened
Pleiades7 said:
What is the likelihood that in a future update (if it happens) that they will include an option to HIDE the soft button bar.
This is a deal-breaker for me. I like my movie-watching experience and game playing experience to be immersive. Having a menubar there ALL THE TIME might as well be a form of adware as far as I'm concerned.
What's the point of a micro game console experience if it always looks like YOUR SMART PHONE is streaming to TV because the menubar is there to remind you? How stupid can they be?? Did they just release this a proof of concept? To say, "Hey, look what we did! Screw the customer experience..."
Please tell me "not to worry" or a "future custom rom" or "mod" will be "released soon to address."
If not, I'm returning this hunk of junk when it arrives.
Click to expand...
Click to collapse
FYI: http://forum.xda-developers.com/showpost.php?p=49792211&postcount=7
Pleiades7 said:
What is the likelihood that in a future update (if it happens) that they will include an option to HIDE the soft button bar.
This is a deal-breaker for me. I like my movie-watching experience and game playing experience to be immersive. Having a menubar there ALL THE TIME might as well be a form of adware as far as I'm concerned.
What's the point of a micro game console experience if it always looks like YOUR SMART PHONE is streaming to TV because the menubar is there to remind you? How stupid can they be?? Did they just release this a proof of concept? To say, "Hey, look what we did! Screw the customer experience..."
Please tell me "not to worry" or a "future custom rom" or "mod" will be "released soon to address."
If not, I'm returning this hunk of junk when it arrives.
Click to expand...
Click to collapse
What's funny is I got in on a pretty could deal on it. On clearance for $160, free postage ;-p. There was only two but what surprised me (and made me cautious) is how does something go on clearance after only be out such a short time? There was only 2 left and I got in on the last one.
We'll have to see. Might actually think about that offer if I can break even. But if that work around works for me, then at least I fixed the deal-breaker for me. Hopefully the MOJO devs are listening and will fix ALL of this in their supposed update. My fear is will that update happen at all.....hopefully there is enough of a homebrew/mod community out there to at least squeeze out one custom rom that will give the users the experience they deserve. My 2 cents.
Please add this issue to the list!
from: http://forum.xda-developers.com/showpost.php?p=49512727&postcount=4
gwaldo said:
Mad Catz Nate said:
Bonus tip: Press and hold Home button for 1 sec brings up the Recent Apps screen.
Click to expand...
Click to collapse
:good: It's a great feature, I use it a lot, even in gamesmart mode it works!
Shame you have to switch to mouse mode to select an app.. is there any chance of better navigating the android UI in gamesmart mode in the new Android 4.4?
Click to expand...
Click to collapse
This is what I'm saying, you switch out to desktop, then go to tasks but can't pick an app in game mode.
You have to switch back to mouse mode, pick the game and switch back:
http://www.youtube.com/watch?v=H0PvKq1CcMo&t=21m0s
If there's one issue kitkat fixes, I really hope it's this one:good:
Hi,
I am starting this thread hoping to find a solution to backup the working tablets so we will be able to revive them despite the kill switch being triggered.
The only solution so far seams to be by using nvflash in apx mode.
So far I have managed to boot my tablet in APX mode, but I have not done any other testing.
The tablet (still not killed one) is recognized by computer as being in APX mode.
Requirements:
1. Rooted tablet
2. Terminal app from Google play
Commands issued for APX mode:
1. Open terminal app and write "su" followed by enter to get root
2. Write "reboot" and press enter while keeping the volume up key pressed
Let's continue!
OP's 2nd post deleted - no need for it. Just edit Post #1
LenAsh said:
OP's 2nd post deleted - no need for it. Just edit Post #1
Click to expand...
Click to collapse
where are or name from other post, this thread is very important for us research and i think could useful.
thanks for advance.
I just received my replacement tablet a few days ago. My device has never been rooted or anything prior. I turned on the new device and started using it. I went back to my old device (connected to wifi and everything) and it still boot and i was able to use it all night. 2 days later I tried to use it and it powered on and everything was fine. I just rooted the mofo and installed a custom rom. I never seemed to have received the "kill switch"
The note in my package said to dispose of the device. So... I guess I now have 2 shields. My battery has never gotten warm, I dont use it very often though.
JuStAdsor said:
Hi,
I am starting this thread hoping to find a solution to backup the working tablets so we will be able to revive them despite the kill switch being triggered.
The only solution so far seams to be by using nvflash in apx mode.
So far I have managed to boot my tablet in APX mode, but I have not done any other testing.
The tablet (still not killed one) is recognized by computer as being in APX mode.
Requirements:
1. Rooted tablet
2. Terminal app from Google play
Commands issued for APX mode:
1. Open terminal app and write "su" followed by enter to get root
2. Write "reboot" and press enter while keeping the volume up key pressed
Let's continue!
Click to expand...
Click to collapse
I don't really understand the issue here, can you confirm that the tablet is still active cf. not hit by the killswitch? Why would you get an apx connected message? On a working tablet you would be directly send to an adb/fastboot interface? Usually only the killed tablets would be recognized as apx when you then connect it to a pc.. People are looking for a solution on how to nvflash via apx mode, which is an nvidia proprietary protocol and probably won't be pushed any time soon, if ever.. Possible solutions are moving to linux at the moment, where people try to connect their bricked tablets in apx mode hoping that linux would recognize the drivers, eventually, and maybe use open source universal flashing tools to recover their bricked devices..
doomedromance said:
I just received my replacement tablet a few days ago. My device has never been rooted or anything prior. I turned on the new device and started using it. I went back to my old device (connected to wifi and everything) and it still boot and i was able to use it all night. 2 days later I tried to use it and it powered on and everything was fine. I just rooted the mofo and installed a custom rom. I never seemed to have received the "kill switch"
The note in my package said to dispose of the device. So... I guess I now have 2 shields. My battery has never gotten warm, I dont use it very often though.
Click to expand...
Click to collapse
Yes, your tablet is still alive because you flashed another rom (and that's exactly what you should do to be sure to never get hit by the kill switch) - it is very likely that the kill switch isn't triggered immediately, and than the silent update might not hit immediately neither, you're very lucky, most of the people were hit in very few hours, they couldn't even get their research done before the trigger - that said: the best way is to root the old tablet before setting up the new one, and deleting tegraota.apk and its parent directory - as explained in bogdacutu's thread in this very forum, and/or flashing a new rom to not have any nvidia apps anymore.. You can do both if you even use multirom port for nvidia shield tablet.. I can manifest that all this is working since i did it - i tryed it all and do have 2x tablets now like many others too
This isn't cool man, why steal from Nvidia? Or from anyone. Stealing is not OK.
Sent from my SM-N910T
not stealing XBlack, my tablet was getting hot before recall...I did researched and spent time and efforts to fix the issue which i did. Nvidia sends new tablets to cover their ass for potential law suites in case of a situation happening again. Specifically states to dispose or return and why return if they will dispose for you? Why dispose of a tablet when the user fixed it by the user community. Is it taking advantage YES, we are smart people, we fix it. It was their choice to send new tablets without having to receive old ones prior. In no way is it stealing, tucking it in my pants and walking out of a Best Buy or FRYs without paying for it is stealing. We as a community with fixed tablets can be looked at as beta testers who get to keep their prototype and are given a NEW updated consultation model. Pretty much sums it up you can look at it in any way you like but we as a smart community in no way are criminals that steal from NVIDIA. Thanks NVIDIA i will forever be a loyal customer who buys your products since i think they are great. thank you for my new updated tablet.6
The problem is if you "fix" the tablet and then give it to else, and it catches fire, will nvidia be liable? They want the defective devices off the street, not disassembled and reassembled with non spec parts by potentially incompetent consumers.
Sent from my HTC M9 using Tapatalk
As the title says, the only how-to's I can find for rooting are for the LG lineup which can direct connect to a computer for ADB; which to the best of my knowledge the Fossil has to be either Wifi or BT Debug. I would like to remap my button into long press for theater but everything I have found to do so requires root.
BoredKender said:
As the title says, the only how-to's I can find for rooting are for the LG lineup which can direct connect to a computer for ADB; which to the best of my knowledge the Fossil has to be either Wifi or BT Debug. I would like to remap my button into long press for theater but everything I have found to do so requires root.
Click to expand...
Click to collapse
Well...I just got my Fossil Q Marshal a week ago and love it. but... I should've learned my lesson by now. to Checking the forums for root and recovery BEFORE I pick out my new device would have been a swell idea. Maybe I'll remember next purchase. As for now, I hope we see some work done for our new timepieces, but I don't think we will get much of anything aside from some very cool watch faces :crying:
Maybe one day I'll be able to do some rooting on my own but it's going to be tough the way it keeps getting harder and harder each new release.
Good luck my friend.
Have been trying to find a way to open it without gouging up the back so I can see if it has the contact pads like the Founder, but no success yet. We will make this happen!