Related
Is there a publicly available Fuze/Diamond/Raphael emulator that I can run on my pc? I've done some searches, but only find info on emulators that run on the fuze itself. I would like to test some ROMS I'm trying to cook up, but as an obsolute beginner, I would like to test things without installing them on the phone itself.
Thanks!
There's a generic Device Emulator available from microsoft, but you have to use the Device Emulator drivers, and as a result you can't test a number of things (like the navi pad, accelerometer, etc)
It's not realistic to emulate a device to the point where the drivers would function on it, it would be an extreme amount of work (for each device, too!)
dc41 said:
Is there a publicly available Fuze/Diamond/Raphael emulator that I can run on my pc? I've done some searches, but only find info on emulators that run on the fuze itself. I would like to test some ROMS I'm trying to cook up, but as an obsolute beginner, I would like to test things without installing them on the phone itself.
Thanks!
Click to expand...
Click to collapse
The emulator from Microsoft does not allow ROMs to be flashed to it. There isn't an emulator that allows you top test your own ROMs.
dwizzy130
Thanks for the answers! Maybe I'll just have to pony up and get a second phone .
I first heard of such a beast when I was on the phone with a tech from FireThorn trying to work out a cert problem. He mentioned he wasn't using a phone on his end... just an emulator. I wonder if he was using the Microsoft product.
Just suck it up and flash your phone with your own roms. As long as you don't do anything super-stupid, like include a radio from the topaz or something like that, you won't brick the device. Just keep another rom handy that boots up fine if you need it in a pinch. Seriously, it's not that big of a deal, and the first time or two that you flash with your own rom, you'll get a nice rush, like the first time you unlocked the phone and flashed someone else's cooked rom.
Now, there are things you can do if you're cooking a lot and want to see if something you added (like a reg key) is 'sticking.' Look in the temp\dump folder of the kitchen, and examine the initflashfiles.dat to see if your start menu is ok. Look at the .hv files with ceregeditor to see if registry changes were compiled a-ok. Look at config.txt to see if your add2configs were compiled (and look for the corresponding cabs, etc, that you want to run during compilation). Look around for annoying shortcuts you're trying to remove, and see if they're still there. There's a lot you can do without flashing, too. I've seen Arrupenthal say that he flashes a non-booting rom like 3 times a week. It's annoying (hasn't happened to me in probably 100 cook/flash cycles, but I'm pretty conservative), but it won't kill your phone.
Presenting Problem: Tablet is stuck rebooting itself once it gets to the booting screen animation, USB Debugging was not turned on on the tablet when it was working properly last time, and I need to turn USB Debugging on to fix my tablet. How do I do this?
Disclaimer: Yes, you'll think there are a million other threads about enabling USB debugging and whatnot, but this is totally different!
The Story: My device is a Grid10 tablet. It runs its custom OS built on Android Kernel (Gingerbread). Everything about it is android, except it's not android (and it's not a custom launcher or a skin).
... anyway
The Grid10: Almost nobody here own a Grid10 (I assume), so here's the thing... the Grid has only ONE button. The power button. No volume buttons, no home or back or menu buttons or anything... all those commands are gestures on the Grid (... if it started properly)
The Problem and its Cause: Now, It's stuck continuously rebooting itself once it gets to the the booting animation screen because I mistakenly deleted a file from system/app called SettingsProvider.apk
The Solution: I have the missing file on my laptop, and I need to put it back on the tablet. When I plug in its USB cable, I don't get a drive in My Computer. Obviously, it won't get into storage mode without being told to do so from the settings list (which I have no access to... because it's stuck rebooting itself at the booting animation screen... yes, I'm repeating myself so no one will tell me to "enable USB debugging" when I say that...)
So aparently, to get the file on my Grid, I need to use adb.
And since I didn't have USB Debugging enabled when the Grid was last operating properly, the adb can't see my tablet! (as shown by a 'adb devices' command).
The Sucky Recovery Menu: There is no fastboot on this thing (not that it would help with anything), but there is a recovery menu i can access (by holding down the power button while the tablet is booting), but it's no use. It looks like some kinda' custom recovery menu called "PBJ40 Recovery Utility". It has 4 commands:
reboot system now
wipe data/factory reset
wipe cache partition
apply sdcard: update.zip
I've tried all of these commands (selecting is done by pressing the power button, and when un-pressed for a few seconds, whatever command is highlighted gets executed).
My best bet would have been the update.zip as I created a signed update.zip with the missing file in it so it can put it back in its rightful place... but sd card in question appears to be the built-in sd card, and not the external (removable) sd card... the recovery tool doesn't even look in the external sd card for the update.zip
In Short: To get the file on the tablet, for now, the only way I can see how, is through adb, and seen as how USB Debugging was not enabled when the Grid was operational last time, I come here, to the XDA Forums, asking for advice.
The Question(s):
A) How do I turn on USB Debugging on the tablet so i can use adb and fix it?
or
B) Is there some alternative way for me to get the missing apk in system/app folder that does not require USB debugging?
Got you scratching your brain? Been trying to solve this for so long, I finished scratching mine, and started hitting it against the wall now!
I hate to tell you this man, but I am pretty sure that you messed up your tablet/bricked it.
Problem solved.
Not the USB Debugging thing, but I ended up fixing the tablet.
Can't disclose how I did it though... privacy issues.
So the system is fixed and the GirdOS is running perfectly on the Grid10, but I still can't use the tablet anyway, because of some kinda' server-side failure, because I need to register myself on the server before I gain access to any of the tablet's functions, while the server isn't responding to register my credentials... so yea... the tablet works, but it's still useless to me.
There's not much if any hope that the server will be fixed or get running anytime soon, because from the rumors/reports, FusionGarage (the producer of said tablet) has disappeared off the grid. Ironic, isn't it?
Maybe some day somebody will be able get ICS or Honeycomb running on the Grid10, and will share the knowledge-how with everybody.
I got one of those PBJ40 tablets too with 1366x768 , but no real android (just 2.1) on it.. do you mind sharing the one you got?
maybe you even have the Kernel source for this? could be nice having too
Dexter_nlb said:
I got one of those PBJ40 tablets too with 1366x768 , but no real android (just 2.1) on it.. do you mind sharing the one you got?
maybe you even have the Kernel source for this? could be nice having too
Click to expand...
Click to collapse
Explain yourself please.
What is this android 2.1 you speak of? The Grid10 (aka PBJ40) comes with its custom OS called GridOS that's based on Android.
So what's the 2.1 android you have? Is it pre-upgrade GridOS or what? After the upgrade, GridOS's kernel was made into Gingerbread.
Ghoymakh said:
Explain yourself please.
What is this android 2.1 you speak of? The Grid10 (aka PBJ40) comes with its custom OS called GridOS that's based on Android.
So what's the 2.1 android you have? Is it pre-upgrade GridOS or what? After the upgrade, GridOS's kernel was made into Gingerbread.
Click to expand...
Click to collapse
i guess hardware was tried sold to different parties, as mine is with Android 2.3 ( i made that ) but touchscreen is poor on this device, and Tegra2 got a tough time managing 1366x768 on it, compared to previous devices..
and lastly it was in development so drivers are not finished.
As your GridOS is 2.3 compatible it has a better kernel, and maybe a source for the kernel too, since i got no kernel source and no one that knows this hardware.
but maybe it'll show up with some totally different supplier, i seen talk on chinese forums where ppl compiles linux for it, so its still in the works.
Dexter_nlb said:
i guess hardware was tried sold to different parties, as mine is with Android 2.3 ( i made that ) but touchscreen is poor on this device, and Tegra2 got a tough time managing 1366x768 on it, compared to previous devices..
and lastly it was in development so drivers are not finished.
As your GridOS is 2.3 compatible it has a better kernel, and maybe a source for the kernel too, since i got no kernel source and no one that knows this hardware.
but maybe it'll show up with some totally different supplier, i seen talk on chinese forums where ppl compiles linux for it, so its still in the works.
Click to expand...
Click to collapse
I see.
Looks like whoever made the PBJ40 (aka Grid10) also sold some of its stock to other companies, and since the 'other companies' don't have a dev. team to compensate for the lack of drivers for the Tegra2 (I heard they're going to release the drivers in some 2 months), they had to sell it with Android 2.1 (froyo) on it, with lots of problems like screen responsiveness, poor power management, and the like.
I'm also guessing that you do not have Market, Talk or GMail on your tablet... or at least, you didn't have it at first (doesn't take much skill to install them... the tablet comes rooted).
I'm also guessing you have a serious gestures issue, am I right?
Do you have the 40 pin USB cable? (or did yours come with a regular female USB port??)
... I might be of assistance, if you're able to make your dev skills work in your favor.
So help me help you...
The only way this will work, is if you're able to reverse engineer the GridOS to:
1) Extract the programming that's responsible for the gestures so we can install it on any other device (like your PBJ40, which doesn't have gesture support as advanced as the Grid10), to make the device easier to use.
2) Override the sign-up screen for the GridOS. In case you do not yet know, once you boot GridOS for the first time, you're taken to a setup page (much like the setup page of Windows) where you register yourself on the FusionGarage server (people who made the GridOS) to gain access to the tablet... for some time now, the FusionGarage server has been down, and since the company recently went under, there's no way the server will be fixed ever again, so even with linux kernel 2.3 (aka android gingerbread... without the market) you can't have any kind of access to the tablet, because you'd be unable to proceed form the sign-up page forward! So if you can find a way to over-ride the sign-up page or 'delete' it from the equation altogether, we both win!
So: I can provide you with GridOS kernel version 2.3 (not android... GridOS! It's basically the same, it just doesn't have the Market, and its UI is different... still very nice... I like it).
So... you can't install GridOS on your Froyo tablet (just yet), even if you had the 2.3 GridOS at your disposal, because you'd be stuck there.
So the question remains:
- Can you reverse engineer a linux OS that is android based (but not truly android) to extract from it the gestures program so you can make your PBJ40 more responsive?
- Can you somehow customize GridOS to delete the whole signup page issue?
Both of these things will help me a lot... but only the gestures-solution will be of help to you, unless you have the USB cable for the tablet.
If you PBJ40 is not a regular Grid10, I'd like to see it from all angles + a picture of its cables and chargers... if possible, please upload them to this thread.
For now, to make your life easier, install the program called zMooth from the Market. Its gesture responsiveness will be much better than the 2.1 Froyo version your tablet is now running.
"swipe left to go back, swipe right for menu, gesture a up-arrow(^) for home"
Look at the screenshots to better understand.
While setting up the program sensitivity level, keep in mind that the lower the level, the more sensitive (it's in fine print).
... let me know what you get!
PS: It might also be of help if you can somehow get the gesture program from ICS kernel and adopt it to PBJ40!
Could be we should continue this OT, in a private PM and maybe exchange mails
I think i can do most of it, I even have Android3.0 running on it, but again kernel needed changing since touch driver is not supporting the way 3.0 works.
but it works even with highres..
I do not have 2.1 on it, i ported a CM7/2.3.6 to it, and it worked 95%, some issues with DSP manager and movie codecs, but i did not put my 100% in it, since i was doing it all for fun and my own interest, since i could not share with anyone anyways as no one had it. That was until i saw the design of Grid10, i knew it was 99% like mine.. Flash11.1 works great for movie playback here though..
I got the 4leds on it too and mine has USB HOST/device switching only by compal (writers of many tablets today), but i found the USBUTG tool to use with it, to make switching easier, than doing it in a shell.
anyways, lets maybe continue by PM.. and we can maybe exchange "partitions"
My vow of secrecy has been lifted!
To Flash your Grid10 (aka PBJ40), follow this tutorial I made:
http://www.thejoojooforum.com/viewtopic.php?f=17&t=49654
There's also more info on the general forum (and one or two other tutorials/suggestions I've made that could prove to be of benefit to anybody with a Grid10): http://www.thejoojooforum.com/viewforum.php?f=17
Ghoymakh said:
My vow of secrecy has been lifted!
To Flash your Grid10 (aka PBJ40), follow this tutorial I made:
http://www.thejoojooforum.com/viewtopic.php?f=17&t=49654
There's also more info on the general forum (and one or two other tutorials/suggestions I've made that could prove to be of benefit to anybody with a Grid10): http://www.thejoojooforum.com/viewforum.php?f=17
Click to expand...
Click to collapse
if you know how to use APX mode on it (Reset button on right side(if looking at front). I got android 2.3.6 (CM7) running on it, i think only difference is that i got 4 hardware button (soft light buttons on right side of tablet)
let me know, and i can maybe upload the kernel + system to a site.
I dnt even know what APX is!
I'm new to the android dev. scene, so i dnt know much yet.
I don't have much use for a Gingerbread ROM that's not going to be filly compatible with the Grid10. We don't have ANY buttons on our tablets.
To compensate for that, you might want to include the program Zmooth in the list of apps that the flashing-process will auto-install, so whoever flashes the CyanogenMod won't be left stranded without any buttons to use on the Grid10.
As mentioned in the flashing tutorial, V. is recompiling the original GridOS to make it skip the registration page, and it's Gingerbread too, one that's completely compatible with the tablet's specs, including gestures. It will be the GridOS as (previously) advertised by FusionGarage, only this time, no registration page, which means we can flash it and actually use it (up till now, whoever re-flashed or did a factory reset couldn't use their tablet because the registration could not be completed since the FG servers were down).
Maybe that could prove to be useful to you... I'll upload the file to the Grid10 forum once it's finished.
(i wonder if there's a way to open a Grid10 section in the xda forums...)
But what you have could be useful to somebody else out there!
How about you upload your files in Dropbox, and create a new thread on the above-linked forum, and share your ROM so other people might benefit from it.
https://www.dropbox.com/
Make sure you write your tablet's full specs, including the information about your soft and hard buttons, as our tablets have NO soft-buttons, and only have 2 hardware buttons: a power button and a reset button.
Edit: as the Grid10 doesn't have volume buttons, i don't think it's even capable of entering APX mode. It does have a recovery mode... but the only options in there are to factory-reset, delete cache partition, and install update.zip.
Ghoymakh: YOU ARE THE CLOSEST THING TO.... THX
Ghoymakh said:
My vow of secrecy has been lifted!
To Flash your Grid10 (aka PBJ40), follow this tutorial I made:
There's also more info on the general forum (and one or two other tutorials/suggestions I've made that could prove to be of benefit to anybody with a Grid10):
Click to expand...
Click to collapse
============================================
I'm one of the fortunate-unfortunates.
I previously reset my G10 and it has been useless ever since. I did however purchase the USB adapter with my device and I'm looking forward to making use of your extensive research and hard work.
Again, thanks and I'll let y'all know how it goes (within the next 7 days or so).
Praise and thanks to you and everyone else out here.
G
Ghoymakh said:
Edit: as the Grid10 doesn't have volume buttons, i don't think it's even capable of entering APX mode. It does have a recovery mode... but the only options in there are to factory-reset, delete cache partition, and install update.zip.
Click to expand...
Click to collapse
can you check when you got the tablet in front of you facing up. that on your right side a little hole is found just about center, 5-6cm above simcard slot (at least on mine simcard is on the right side)
if you turn it off, holding in the tap inside the small hole (you can feel the click when its pushed), press power and it goes into APX mode. but you will need the bootloader.bin to get it in full apx mode and ready to accept commands.
A small step for man.... My Grid10 is more than just a brick
- Using Ghoymakh's instructions from JooJoo Forum, I successfully flashed my Grid10 yesterday.
-- The identified 'tar' command didn't work on the compressed file but the Archive Mounter within Back Track worked just fine.
- Now, as time permits, I'm going to move forward and attempt to incorporate the Xmooth and Market.
-- If only I could get my JooJoo Forum account activated....
Again, Props to Ghoymakh, V, and any/all other contributors.
G
Hello,
I do hope my questions fit in here.
I recently bought the LC-Power MIRA-1 10.1" tablet. In google play it is called "unknown M105F"
the tablet has a 1,2 GHz A10 - ARM Cortex A8 CPU and a Mali 400MP GPU
i do have some experience with backup/root/uc&oc and even custom mods with my motorola defy phone (currently running cm7.2 stable)
when "playing" around with my defy i found it was sold in big numbers and is very well supported not only here but in any number of other communities. however, since my new tablet is pretty new to the market and no brand tablet, finding information on it is near impossible.
i do hope this will change in the future, especially since I really feel that my tablet is well suited for a number of tasks and with the price tag of ~150 EUR might even have a chance of finding its way in the hands of many people
anyway, even if the tablet is fine as it is now, it could be better. i am talking about modifications and this is what this thread is about.
1) BACKUP
in case i screw up, I really would love to have the possibility of resetting everything(!) back to factory defaults.
with my defy it is as easy as downloading the official sfb and flashing it with rsd lite
this wont work here for obvious reasons
is there a possibility to download the firmware to the pc (from the tablet) and later restoring it? probably not
so the only way left is nandroid backup?
easier said than done with a new device and without root...
also, i would very much prefer to have a backup without root / be sure to be able to remove all modifications i made like installing clockwork mod and rooting...
2) ROOT
for various reasons I'd like to have root. according to my information, rooting 4.0.4 is dependant on the device.
considering i have an unknown device, short of trying every possibility, what else could i do/try?
3) UNDERCLOCK/OVERCLOCK
I would LOVE to try to UC and OC the tablet. I know this might fail miserabely, but I could try.
IF i had root and any idea on how to find (again, short of trying every possible app) a working app.
any ideas?
4) GENERAL CUSTOMISATION
i learned that a well made custommod (like 7.2 for my defy) can make a huge difference in customisation and performance.
I would be willing to try a stable custommod but for now, I dont think that is viable since they usually are device specific.
So all I can do is use another launcher and hope for the best. I really like the performance, functions and especial the ability to customize the AWD Launcher that came with the cm7.2 for my phone.
According to google play the awd launcher is not compatible with my device. i cant imagine why, but there it is.
now, is there a way to still try it?
and what launcher comes closest to the performance, feel and customizability of the awd launcher (i do NOT care about special visual effects on which most launchers seem to concentrate)?
5) SIMILAR DEVICES
the best way to approach all those questions might be to find a (very) similar tablet and try to extrapolate answers from there onto my device.
however, I have no clue on how to figure out what chipset my tablet uses and what other information might be needed to try it that way
---
thats it for now
any and all help will be appreciated!
thank you for reading this
Catwiesel
Hello
okay, I have some news...
since no one had anything to say I went ahead and started trying stuff out...
Apparently, the tablet is rooted by default (or my measurement of being rooted is wrong):
- when i run the app root checker, it says it is rooted
- when i run adb shell / su the prompt is root:directoy #
- i can create and delete files from /system/app
still, something is up...:
- using the adb shell i can create a file in /system/app (touch test.tst)
- if i try to delete/move anything in the adb shell from /system/app apparently the file can not be found
- it works in terminal emulator
- ive installed superuser, but have yet to see the "application asks for superuser rights"
- with the default file browser or es file explorer i can not get to / (stuck in /sdcard) EDIT: Resolved, layer8 problem!
ive also tried some overclocking apps
- they either do not go beyond 1.2ghz (stock) - the apps however is more or less to uc, not oc
- they crash the tablet even with 1248mhz - maybe the scaling gouvanours fault?
- underclocking seems to work (by accident i set the mhz from 1200 to 60 and well... it was SLOW)
i also found out some stuff (quick info system pro)
- ARMv7 processor rev 2(v71) (ARM Cortex A8 1,2GHz - at least according to the tech sheet at the manufactorer)
- sun4i
so, i wonder:
- is the tablet actually sold rooted? then why do i not get superuser permission popups?
- is my hardware not overclockable with (those) apps (i have) and/or do i actually need a custom kernel (ive read abput self compiled kernel for sun4i and another tablet)
ive gotta say, even with a bit of experience in android (acutally, very little) and a bit of linux (not too much, but decent enough) i am sorta confused
...not alone
I´d bought 2 devices LC Power Mira 2 yesterday...they should be delivered on friday...so hang on...you´re no longer alone...
It could be that the device is rooted...as far as I know...
Google runs some kind of an quality assurance by denying some "nobrand" manufactures the total Android 4.0 compatibility.
For an example the Arnova (Archon´s budget line) 10b G3 is running 4.0 but without the Play Store, ´cause the device is not fully supported as an "Quality Android 4.0 Device" and you have to use a custom rom on that tablet.
That´s one reason to spend 5 Euros more for the Mira2 which have it all onboard...or am I wrong...?
thearclight said:
I´d bought 2 devices LC Power Mira 2 yesterday...say should be delivered on friday...so hang on...you´re no longer alone...
It could be that the device is rooted...as far as I know...
Google runs some kind of an quality assurance by denying some "nobrand" manufactures the total Android 4.0 compatibility.
For an example the Arnova (Archon´s budget line) 10b G3 is running 4.0 but without the Play Store, ´cause the device is not fully supported as an "Quality Android 4.0 Device" and you have to use a custom rom on that tablet.
That´s one reason to spend 5 Euros more for the Mira2 which have it all onboard...or am I wrong...?
Click to expand...
Click to collapse
Yes, indeed, at least the MIRA-1 tablet does come prerooted. This is of course nice (since I do not have to try root it myself) but also troubeling, since there is a good reason that android devices usually are not sold rooted. The bigger problem however seems to be that the superuser app is not working properly, i.e. I do not get the "this app is requesting superuser acess" question and probably for the same reason can not get my file browser (ES file browser) to go into the / directory.
what and if other apps could have trouble with the root access that apperently not every app is "finding" i dont know. i do hope not!
however, using the android sdk or shell emulator, all kinds of SU operations can indeed be executed.
concerning your google play store question (was it a question?), yes, the MIRA-1 tablet has google play installed and it can be used without any peticular limitation. its a safe bet that the mira-2 will be able to, too.
my experience with overclocking the tablet does not bode well. even a 48Mhz (smallest step) increase will freeze it. I have tried multiple apps.
i do not have any absolute answer so far. it could be that the oc apps have trouble with the root or are plain the wrong apps or simply that the cpu is already at its absolute limit and just can not be oced.
further investigation into this issue has revealed that apparently other tablets with similar hardware configuration may be able to overclock but apparently it would be neccesary to edit config files and with those compile the kernel. this is far beyond of what i can do and would be willing to do.
i am a bit sad about that, then yeah, the tablet is nice and good enough for me and worth the money, but a bit more speed could not hurt. it does happen that the tablet gets unresponsive for .5-1sec when browsing the web.
one last thought. the gpu does seem to be pretty "powerfull" (please, do not take me to literal.)
but i have yet to find any game that does not run smooth and looks good. according to my information i came across, the gpu is indeed well known for its good performance in 3d and full hd playback
(one exception. snes emulator is unplayable slow. but here i too blame the cpu, not gpu)
...
...sounds good to the fact that I won´t expecting more for this price. Hey 157€ is´nt very much for an 10.1" tablet...
...I´d got also my LG P990 as Android device and smartphone...believe Me...I know what it means being betrayed...no updates...Tegra ? - nVidia ?...I don´t wanna talk about it...lol
It´s rooted and I never got problems with some apps about this fact...ok it´s still on 2.3...thanks LG, by pretending the update comes in May 2012...
I´d send an e-mail to the support of LCpower, by asking about an list of compatible 3g Sticks...10min. later...Answer and an Exel-file with the whole list...great service...´til now...
I just hope that I´d bought 2 "nice" family tablets for a few funny games, sometimes a movie, some social networking...nothing more.
Hope I did´nt misunderstood something here...
...is it only possible with another Explorer (like Astro and ES) to get to the files of an external SD Card or not ???
thearclight said:
...sounds good to the fact that I won´t expecting more for this price. Hey 157€ is´nt very much for an 10.1" tablet...
...I´d got also my LG P990 as Android device and smartphone...believe Me...I know what it means being betrayed...no updates...Tegra ? - nVidia ?...I don´t wanna talk about it...lol
It´s rooted and I never got problems with some apps about this fact...ok it´s still on 2.3...thanks LG, by pretending the update comes in May 2012...
I´d send an e-mail to the support of LCpower, by asking about an list of compatible 3g Sticks...10min. later...Answer and an Exel-file with the whole list...great service...´til now...
I just hope that I´d bought 2 "nice" family tablets for a few funny games, sometimes a movie, some social networking...nothing more.
Hope I did´nt misunderstood something here...
...is it only possible with another Explorer (like Astro and ES) to get to the files of an external SD Card or not ???
Click to expand...
Click to collapse
well, the external sd card behaves a bit strange (at least for my understanding of android)
in short:
we have 2+1 memories in the tablet:
1 internal memory (small, i think 256mb, quite full with the android os and the apps)
1 other internal memory (the 8GB)
1 slot for the sd card, the +1 memory
now, everything begins at / (i figure this is the small internal memory)
the 2nd internal memory with 8gb is mounted under /mnt/sdcard and i believe /sdcard (where i would expect the sdcard!)
the sdcard itself can be found at /mnt/extsd
es file explorer has some trouble with that. if you launch it, it will start in /sdcard
since it does not recognize root, you can not go to /
since you cant type in the path by hand you can not go to /mnt
so apparently you cant browse the sd card with es file explorer (or i havent figured it out yet)
the preinstalled file explorer has no trouble with it at all. in fact, it even actually sends you to the right memory when you tap the corresponding symbols (as preinstalled file explorers go, it is actually not so bad)
ive tried setting up some symlinks but failed. maybe i did it wrong, maybe it just wont work.
another possibility to fix it could be editing fstab. but this could be dangerous and/or cause more problems then it helps
i filed that as a minor inconvenience to be adressed when im bored enough
...
Ok...this means...that I just hope that the Mira2 is accepting my microSD16GB and I can use it quite as normal...
In 2.3 it´s still the structure: " /mnt ---> /mnt/sdcard ---> /mnt/sdcard/_ExternalSD"
Is this structure changed in 4.0 ?
thearclight said:
Ok...this means...that I just hope that the Mira2 is accepting my microSD16GB and I can use it quite as normal...
In 2.3 it´s still the structure: " /mnt ---> /mnt/sdcard ---> /mnt/sdcard/_ExternalSD"
Is this structure changed in 4.0 ?
Click to expand...
Click to collapse
well on my mobile phone (motorola defy with cm7.2) i have /sdcard and /mnt/sdcard - actually being the sdcard
i also have /sd-ext which is empty
i dont know if that is the default for all android versions and/or if there are differences in sd-card mount points in android
however, the behaviour of the phone seems more logical (or its just that i am used to it)
whatever it is... the sd card of the tablet can not be accessed by /mnt/sdcard/ANYTHING
however, further research especially with the es file browser has shown that indeed you can browse the sd-card /mnt/extsd by switching the two in the favorites options.
so, maybe it makes sense, maybe it dont.
maybe its andorid 4.0.4 conform, or not.
what is important is that apps apparently dont mind (they do get installed on the 8gb internal memory mounted at /mnt/sdcard and /sdcard) and so far have yet to refuse to work/show strange behaviour
also, it is possible to move/copy etc files between /mnt/sdcard and /mnt/extsd and browse both directories, at least with the default android file explorer as well as es file browser.
So...a little update...the 2 devices are now in our hands...for about one week...
....and everything I can telling 'bout them...
,,.they're working great. Not a single bad issue, no freezes, and as far as we can see...
...for a price around 160€ there is no better tablet on the market.
Since yesterday I run the game Wild Blood (Unreal Engine 3 Game) which is most famous for an app who killed some tablets and phones...but nit the mira2 ...it's playable.
The device was also rooted "out of the box" but I can't find a single problem with the external SDcard or other USB Hosts I tested.
Sent from my MIRA-2 using xda app-developers app
Had the same issue thanks for the help guys
At the risk of being ridiculed off this forum, I have to, out of desperation, post this.
I have been off-and-on trying to solve this for three weeks. I have never before run into a problem that couldn't be solved or at least gotten some progress on with a full day of trying.
There seems to be no clear instructions anywhere on the WWW for how to get a simple and seemingly ubiquitous driver installed on my no-name Android tablet.
I have a USB GPS puck which apparently uses a Serial to USB thingy called Prolific PL2303. I have a no-name A13-based Android 4.04 tablet. (the build.prop file calls it a "nuclear_evb" from "softwinners"). Both were purchased at DX.com.
I have a package of files from Prolific (none of which explains how to get from their *.jar file to a *.ko file)
I have read about 50 threads which have led me to investigate about 50 different leads on how to do this. Apparently I cannot flash a custom ROM to my tablet since nobody has heard of it and doesn't release custom ROMs for it. I cannot find the source of the stock ROM. So modifying the ROM apparently is impossible.
Ok, but I read tons of threads that say I can just load the driver on-demand. Fine. Where's the driver? Nowhere. But remember that I do have a bunch of files from Prolific that seem to supposedly contain the source for the driver somewhere, though that's not clear either. Apparently I could compile it, but nowhere can I find instructions on how to compile it. And even if I could, there are still vague references to needing the source of the ROM in order to do it and get it working on my tablet.
I hope I sound frustrated. This seemed in the begining like something that would be plug-and-play.
I can't even find an all-purpose step-by-step guide on how to compile and load a driver for Android. I feel like this information should be readily available, but apparently I'm too stupid to find it
Please throw me a life line.
Greetings,
I am currently working on a 100% Android Marshmallow v6.0.1 variant for the Samsung On5 SM-G550T/1 (T-Mobile).
THIS IS NOT A THREAD ON HOW TO ROOT YOUR PHONE
This thread assumes you have already rooted and installed TWRP on your phone and have basic understanding on to backup and recover your phone.
If you need that sort of help, please see my other thread:
https://goo.gl/jWNVNX
Reasons for Project:
I started this project for two reasons:
- Frustration for the lack of support for an otherwise great phone.
- Stumbling across the Samsung Factory Test Rom doing research for other projects.
This ROM has a a 100% Native Driver Set for Android v6.0.1 on the SM-G550T/1. The driver set is identical for the TMO or MetroPCS variants, but the EFS folder will remain different for each.
I'm going to outright confess that I am not a programmer and this is truthfully the first ROM I am trying to develop on my own. I'm a Project Manager and Software Designer by trade, but I rarely get this deep into ROM developments. I figured it was a good project to take on to learn the nitty griddy of what a truly pure Android Experience looks like. That being said, I'd greatly appreciate any help anyone can contribute and will make all my work freely available to anyone wanting to help provided that everyone participating goes into it with good faith that they have no intent on making substantial gains from this project.
Usage of these ROMs/Files/Programs are subject to the following licenses:
- Google's Android Open Source Project Licnese (AOSP):
https://source.android.com/setup/start/licenses
- Google's Individual Contributor License Agreement:
https://cla.developers.google.com/about/google-individual
- Apache Software License, Version 2.0
http://www.apache.org/licenses/LICENSE-2.0
- Samsung Open Source Release Center (OSRC) License:
http://opensource.samsung.com/reception/
That being said, I believe this remains a good enough device, IMHO, to transition people into Android or to provide to people not requiring a fully featured phone.
KNOX Status:
The Factory Test ROM is mostly clean having all the drivers intact and lacks most Samsung Bloatware "tampering". It *DOES* have some preliminary containers for KNOX installed, but none of it is active and takes up less then 1 MB of total space after cleaning passes to remove as many traces as could be removed without breaking things. It is currently being "managed" by an init.d script that generates the folders. I haven't been able to track down yet.
Known Issues:
- 100% Pure Android Menus.
- Rooted/Super User.
- Sound, Camera, GPS, TMO Modem, Wifi, Bluetooth 100% working.
- 100% Native Tethering.
- Adblocker pre-installed (for both Apps and Websites).
- The smallest amount of KNOX installations outside of Lineage. >1mb of KNOX is present with the only items being present are installer containers.
- I'm trying to track down Init.d files that loads with Android and automatically disables/flushes WIFI.
- By default, the power button is set a 100ms push time to turn off (not show power menu). I'm trying to figure out a work around for this.
- I'm trying to find a compatible Contacts Storage file.
- There is no shutdown menu.
Please note that any released versions of this ROM will have makeshift ways to get around these issues.
Downloads:
Please see the second post in this thread.
How to Install:
#01.) Backup your device.
#02.) Download the zip file for the TWRP backup.
#03.) Unzip the TWRP backup.
#04.) Load the downloaded restore into your TWRP Backup Directory.
#05.) Boot into TWRP Recovery.
#06.) Restore the ROM copied into your TWRP Backup Directory.
#07.) Reboot.
Note: No personal data has been configured.
References:
Update Log:
https://goo.gl/CEGCx9|
Required System Apps for Samsung Phones:
https://goo.gl/emTvgX
Things I Could Use Help On:
- A very good way to figure out what Init.d files are doing what without reading through them.
- A good way to change the PIT so we can move 2 gig from the System Rom into the User Rom space.
- Easy methods for changing key button presses.
- A shutdown menu setup.
- A way to make this into an installer.
Note that all those things I'm working on ALREADY, but suggestions would be helpful.
Thanks in advance for any help anyone offers.
Donations Welcomed:
Dev elopement of this ROM is timely, I appreciate any contributions you wish to provide.
https://goo.gl/esVVqA
DOWNLOAD LINKS:
[2019-03-11] Android (v6.0.1) Build #13 [RC] - Google
https://www.androidfilehost.com/?fid=1395089523397913770
- Note, due to Google Now being installed on this one, I can't configure the home long press as the restart menu.
[2019-03-11] Android (v6.0.1) Build #13 [RC] - Diagnostics
https://www.androidfilehost.com/?fid=1395089523397913771
[2019-03-02] Android [v6.0.0] Build #10F [RC]
https://www.androidfilehost.com/?fid=1395089523397908668
i would love to test this rom
Its been taking a little longer then I expected to get it working correctly --- I've been having trouble tracking down some bugs, but with a little luck, I'll post the Google variant tomorrow.
Here is a "working" version to look at:
https://www.androidfilehost.com/?fid=1395089523397901430
It's a restore for TWRP (not an install).
It has all the aforementioned bugs, but is pretty clean only with a few basic utilities installed on it.
I'm trying to track down a number of things:
How to change the Power Button function:
In my most current build, I have made the power button simply put the device to sleep with a long hold of the home button bringing up the power menu. I can't for the life of me figure out where the power button menu lives at or how to define it.
Normally, you'd go edit /system/usr/keylayout/Generic.kl, however, editing it button 116 (the power button) for "Power" only makes it turn off. I can remap it easily as sleep. I compared several other ROMs who use the exact same parameter.
My current version, I just use an app to remap several of those functions; but I don't feel like that's a "release worthy" fix.
Factory Mode:
I can't figure out how to get this version of the ROM to get out of factory mode. The only real problem this causes is, on bootup, it will display a message saying as such and then disable WIFI and turn off the sound. Both, of which, can be immediately be turned back on. It also disables power saver modes.
At first, I thought this was an Init.d file, but after doing some digging I determined this has to the /efs/factoryapp/factorymode file. I may need to swap elements from another EFS to get this fixed.
Contacts Storage:
This is another one I can't seem to track down, but I have a working idea how to fix it. At current, anything that uses Contact Storage won't work. I wonder if the contact storage I have on the system is simply incompatible for some reason. I'm going to try to pull over those system apps from another working rom.
Storage
I've mapped out all the partitions but am having trouble figuring out how to actually change the partitions. There is a whole 2 GB being wasted on the system partition. I'm actually very surprised that no one has ever released a rom with this fixed.
I've tried using parted, but my ADB Install is messed up something major and I cant track down that problem. Reinstalled ADB hasn't fixed it. Its largely a PC problem on my end; a problem I'm dragging my feat going and trying to fix. This is an issue I REALLY wish I could use PC tools for :-\. I've done these changes a thousand times on Windows based machines, but never on a Linux based OS.
Now that I think about it, maybe I should try doing this from the terminal prompt in TWRP. I just wish the keyboard in TWRP didn't suck :-\.
Other Thoughts:
Beyond those very vexing bugs, I have to honestly say that I feel like this experience on this rom is vastly superior to that of the stock Samsung Experience. Sure, these issues are vexing, but I'm also seeing much less system overhead (CPU usage, RAM usage) with this Rom then anything else outside of Lineage.
Update
Here's an update for everyone who might be interested:
The last couple of week's I spent an ENORMOUS amount of time trying to track down as much as I can to get this ROM to work as intended.
For those interested, I've developed a completely new spreadsheet describing everything that's bloatware versus needed items:
https://goo.gl/emTvgX
This spreadsheet will probably be handy for EVERYONE working on Samsung related devices. When its a little more clean, I'll throw it some place better; but since this is specific towards this device, I'll keep it here for now.
It describes everything in /system/app/ and /system/priv-app/ in Samsung's default install and which of those items are actually needed for a 100% clean Android Experience.
I've also rolled through the architecture and have cleaned a lot of "junk" out of the system. Overall, I've pulled it the system from around 1.3 gb installed all the way down to about 800 mb and still feel confident I can trim more out of it.
I've also made it a point to install as much updated system apps as possible. Its been a game of juggling Google, Samsung and other ROM apps to find what works. In general, there are only one major programs left that are Samsung based in any way and that's the Samsung Phone Service app; which seems like its required to interface with the specific hardware on the phone. I've tracked down a number of native Google teleservice.apk-s and none have worked to date.
I am, sadly, still having the aforementioned problems:
- Contacts won't sync despite being able to connect to the contact services and seeing what backups are available. Manual restores work and updating contacts TO the server works now.
- The Power Button turns off the device immediately. The problem resides in a configuration somewhere that's telling the "Power" function to not bring up the power menu. The power menu is in the system, but appears to be renamed or something. I'm having trouble tracking this down. For documentation sake, in theory you should be able to just go to /system/usr/keylayout/General.kl and edit button 116, but that doesn't work.
- The phone is still locked into "Factory Mode". Various documentation says that if you go to /efs/FactoryData/factorymode and edit the contents to "ON", it should resolve this issue, but it doesn't. I feel that the problem resides in the CSC folder and EFS folder, but I haven't gotten around to testing yet. I suspect if you swap the CSC and EFS folders out and set all the correct permissions it might fix that. As it stands now, however, its only a minor inconvenience.
Overall, there's a lot more junk to sift through on the last two problems. The first problem I am kind of stumped on.
If you want to download the ROM and look at it or run it, you can follow the below link. It's currently setup with my "trouble shooting environment" making key places to tinker with easily accessible.
DOWNLOAD HERE:
https://goo.gl/MuPqE3
@LighthammerX
Im very grateful for this site where we can come and learn from one another. I just wanted to say thanks for taking time to work on this device and then sharing your findings. I've been using my on5 for 2 months now after other device died. I'm in the process of moving now but once I'm done with that I'm going to scope out this bad boy and see if I can figure out a few things. Appreciate you sharing your information with us all. Cheers.
Sent from my on5ltemtr using XDA Labs
Thanks. I'm glad to see there's some interest here. IMHO, with the right setup, this little phone is actually a very nice device today.
I actually took a lot of what I learned from hack this ROM apart and applied it to Super Starz to get it running a lot cleaning as my daily runner until/if I get these few bugs figured out.
Personally, I think the most valuable thing I've been learning is just how bloated Samsung Devices truly are out of the box.
I'm going to go ahead and dump my progress log here too so you guys can see what I've been toiling with in hopes someone has some specific feedback on issues and if I am in the right place or not:
https://goo.gl/CEGCx9
As of the writing of this post, I'm virtually confident any problems I am experiencing has nothing to do with /efs/ or /system/csc/.
I've found some inconsistencies in /etc/ and in a few other directories in /system/.
I still wonder if there isn't a init.d file I haven't tracked down yet, but personally I find folder compares faster and easier to try to normalize then I do init.d files.
When it comes to folder compares, I can do a fast reboot and see if things break. When it comes to lines of code, I have to do a bulk of edits, reboot and hope for the best.
Just as an FYI, I plan on completely rewriting the OP when things are at a place where things work.
For anyone following the thread, the Downloads Section has been updated.
This seems really interesting ? I've been trying to find a good ROM for a while with little success, so hopefully this might be the one. I just have one question: what are the differences between the Google and Diagnostics versions of this ROM?