yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] Ilithis:
Sadly I don't think the backup in Uberizer grabbed my original script.bin file. Judging from the script.bin files that I have seen, they're pretty similar to one another. I found this to be extremely useful when running through the script.bin:

http://linux-sunxi.org/Fex_Guide#.5Bproduct.5D

On a side note, I'm going to see if I can't tweak frequency/voltage settings after I get my ROM issues dealt with to see if I can't squeeze more battery life out of the tablet.

So last night I had a nightmare of a time getting VirtualBox with Unbuntu to work on my laptop, but I eventually got it to work and made it up to the point of the miniand guide where I was editing the init.sun5i.rc file before I passed out. I copied what was in the init.sun5i.rc that was backed up from my original ROM to the modified one in my VirtualBox. So now instead of making a whole new ROM, I can push this modified bootloader back to my tablet instead of creating a new ROM?

I'll recompile the boot.img and push it back using the command above. Hopefully this fixes it!

EDIT:

So before I got a chance to recompile the boot.img from my own work, Toxicro developed a solution for me and posted it on the techknow forums found here:

http://www.4shared.com/rar/07lqpo5V/ilithis.html

The g-sensor needs to be flipped in orientation and the buttons don't work, but I'm going to fix those and reupload the perfected copy later. I posted this now if anyone wants to tinker with it before I get a chance to have a go with it.

EDIT2:

Anyone have the original keyboard.kl file? I am having trouble identifying the capacitive button's key numbers. Once I figure them I'll upload the updated .rar file.
[Upgrading, Modifying and Unlocking] crmoody76:
great job guys! i just made a firmware back up of the original on the tablet i just got off ebay with the uberizer from technow. im goin to see if it can be made into a livesuite image so others can flash back if they need to. oh and tried the touch screen drivers in the link you got from toxicoro, VEEERRRYYYY nice.:good:
[Upgrading, Modifying and Unlocking] Ilithis:
You don't happen to have the original ROM still do you? I need the .kl files found in /system/usr/keylayout/ so that I can fix the capacitive buttons on the new ROM. The hardware buttons are just the volume buttons which are 139 (down) and 114 (up).
[Upgrading, Modifying and Unlocking] crmoody76:
yes i still have the original, thats why i tracked down one with the original firmware. if you can pull the file from the rom dump i'll zip file it and upload it.
[Upgrading, Modifying and Unlocking] Ilithis:
What ROM dump? I don't have the original ROM. We're most likely looking for sun4i-keyboard.kl which has the mapping for the keys.
[Upgrading, Modifying and Unlocking] crmoody76:
i mean i have a trio with the original firmware. i used the uberizer to make a ROM dump of the firmware. i think that will have the file your looking for or if not can i use es file explorer to find it and extract it.

EDIT: I used es file explorer and found it. I copied it to my laptop, so I'll upload it to 4shared and post the link.

EDIT2: heres the link,

http://www.4shared.com/zip/FyQduYdX/sun4i-keyboard.html
[Upgrading, Modifying and Unlocking] Ilithis:
Wasn't expecting that...

Hmmmm, well that wasn't what I was expecting. There was only mappings for the hardware buttons in that file, not the capacitive (virtual) buttons. Perhaps the other .kl files in that directory will hold the answer. Could you zip all the files in the directory and upload them?

To anyone else out there that knows how to map the capacitive buttons on this tablet, any idea how I can map them?

EDIT:

Sadly, looking at the .img files dolorespark has on his/her dropbox for the A10 version, their sun4i-keylayout.kl file has their hardware buttons mapped differently (like a normal tablet) where 114/115 is volume up/down rather than 139/114 for volume up/down (like the A13). This leads me to believe that their virtual key layout will be different but I will try it once I get a chance.

EDIT2:

Oh dear, silly me. The tkey_para (touch keys) was disabled in the script.bin. Once I edit this to enable the touch keys, it might work.

EDIT3:

*Sigh* Neither of the above solutions worked. I got a suggestion on the techknow forums to get the entire original rom and look compare/contrast the setup.bin files and the init files (init.sun5i.rc and other init.* files) to possibly find our answer. Is there a chance you could take the time to upload the entire ROM for me to dissect? I feel like we're so close to finishing this and having a completely function 4.1.1 tablet, but these touch keys are eluding me.
[Upgrading, Modifying and Unlocking] crmoody76:
I'm uploading now, i'll edit and add the link as soon as its finished.

EDIT: http://www.4shared.com/zip/mY_Meu1m/FW_BACKUP_20130405_0514.html
[Upgrading, Modifying and Unlocking] dolorespark:
You can only map them if the touchscreen driver (ft5x_ts.ko) supports them. With some versions of this driver, they just work; for others it may require some additional proprietary entries in script.bin; and sadly, some versions don't support them at all. If the driver supports them, you also need an ft5x_ts.kl in /system/usr/keylayout to map the keycodes to their functions.

The driver in the original 7C stock ROM appears to support them without any special entries. That ROM also has an ft5x_ts.kl but there's no guarantee that the driver you're using now generates the same keycodes as the original, so it's of little use.

To find out what keycodes your driver could generate, from an adb shell prompt run "getevent -p". It will list each driver that generates "input events" that the rest of the system will respond to, and what values are assigned to each event. Here's an example for my touchsreen driver:

add device 1: /dev/input/event3
name: "ft5x_ts"
events:
KEY (0001): 0066 008b 009e 00d9 014a
ABS (0003): 0030 : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
0032 : value 0, min 0, max 200, fuzz 0, flat 0, resolution 0
0035 : value 0, min 0, max 800, fuzz 0, flat 0, resolution 0
0036 : value 0, min 0, max 480, fuzz 0, flat 0, resolution 0
0039 : value 0, min 0, max 10, fuzz 0, flat 0, resolution 0

The "KEY" line shows the hex keycodes it should be able to generate. Unfortunately, mine doesn't actually generate any of them except 0x9e (158 decimal). This is the Back keycode, so all 3 of my capacitive buttons do the same thing: go back.

To find out what codes the driver generates for your capacitive buttons, run "getevent". This will list every touchscreen, gsensor, power, and physical button input event that occurs until you press "Ctrl-C" to kill it. Here's what I get when I touch one of the buttons:

/dev/input/event3: 0001 009e 00000000

In this example, the ft5x touchscreen controller (device "event3") generated a key event (0001) whose value was "Back" (0x9e). You'll want to press each button and see what code it generates. If you get anything at all, you can use ft5x_ts.kl to map the value(s) to the function(s) you want.

Note: Capturing those button values may be difficult if your gsensor is as jittery as mine: it generates several events per second. Shaking the tablet sometimes quiets it down long enough for me to see the value before it scrolls away.
[Upgrading, Modifying and Unlocking] Ilithis:
Thanks!

Thanks for the upload, once I finish downloading I will start to take a look at this.

Thank you very much. I don't think I would have ever thought to check to see what driver has what input. I thought all ft5x_ts.ko files were the same, but I guess not.

Between this ROM upload and DoloresPark's post about how to properly gather input data from the tablet, I should be able to get this working. First, I'm going to simply try to copy the ft5x_ts.kl file and the ft5x_ts.ko file from the ROM which should support the proper input. If that doesn't work then I'll work on see what input the drivers have and see if I can't get it to work that way.
[Upgrading, Modifying and Unlocking] xtreme113:
Thank you so much dolorespark

Hallo dolorespark

Thank you so much for your work .

I got my Trio Stealth pro 7c on vacation in the states in August (I am from Germany), I missed the Playstore so I played around with some custom roms .

With the result that I was stuck with GB .

It worked but not smooth .

So after a short time I gave up , put it in the box , ordered a ASUS Nexus (I love it) and nearly forgott about it .

When I found your Post I tryed it and it works perfect for my hardware .

So all I can say again is thank you , you did what Machspeed was not willing to do , a totall ****ty company when it comes to service and customersupport .

Ok the trio does not have the performance and the screen of the NEXUS but it is working smooth now ,because of your great work .

Best from Germany

Xtreme113 :good::good::good:
[Upgrading, Modifying and Unlocking] Ilithis:
ABS Events

So I tried simply copying over the original ft5x_ts.ko driver and the ft5x_ts.kl file to their respective directories. I pulled the files back after a reboot to make sure they were not messed with. That didn't get the capacitive buttons working sadly. I then pursued DoloresPark's advice and got that the ft5x_ts that came with the original ROM can do 102, 139, 158, 217, and 330 (all decimal values) according to the getevent -p command. However, when running the getevent command, all I got was 0003 (ABS) with a value of 30 (along with all the gsensor jitter). This looks like it corresponds to something with the ft5x_ts ABS (not sure what this is) events instead of a key event. All three of the buttons produced this event while pressing the areas inbetween the capacitive buttons resulted in nothing. Then I touched the screen and it came up with a load of events for the touchscreen.

I also edited the ft5x_ts.kl file to modify the values for the buttons listed in there from 1, 2, 4 to 102, 158, 217 and it still didn't work. Any idea why it just comes up with the ABS event when I touch the capacitive keys?
[Upgrading, Modifying and Unlocking] crmoody76:
after reading your status so far i poked around google looking for some help with the buttons and came across ButtonRemapper Beta v0.2.4, which is actually hosted here http://xdaforums.com/showthread.php?t=850464. upon installing this, the program maps the buttons as follows: 115(volume up) Volume up

114(volume down) Volume down

217(Back) Back W

102(Home) Home W

139(Menu) Menu W_D

tapping each individual button brings up an edit menu where you can swap the key functions and the resulting state of the key, none,wake, or wake_dropped. as they are the back,home,and menu keys are wake,wake,and wake dropped. the volume keys are in a state of none. setting the bottom 3 keys to a "wake_dropped" state makes the menu and home keys open google search, while the back key opens the mic application:eek:.......so maybe a solution can be figured from here since the keys work, just not with their intended purpose.
[Upgrading, Modifying and Unlocking] Ilithis:
That is strange because 139 is our volume up button, not 115. I don't think 139 can be bound to two functions, can it?
[Upgrading, Modifying and Unlocking] crmoody76:
i have no idea, but thats what i got when i ran the app. i forgot to mention that i only ran it on the trio i have the jb rom on. i'll run it on the one with the original rom and see if anything's different(should have done that to start with:laugh:)
[Upgrading, Modifying and Unlocking] Ilithis:
Different Button Remapper Results

So the few things I tried yesterday:

There is an ft5x_ts.idc file that I copied from the original ROM to the new ROM, no go.

I booted up that button remapper app and it only showed three buttons for me:

HOME

MENU

BACK

as 102, 217, 158 (not in that order but those three numbers). I changed them all from Wake to Wake-Dropped, applied the changes, and rebooted the tablet. Still, I got nothing.
[Upgrading, Modifying and Unlocking] crmoody76:
ok, loaded it on the tablet with the original ROM, got 3 keys:

HOME

BACK

MENU

with the buttons numbers as 4 2 and 1.:eek: my guess is that this program is hit and miss with certain ROMS. i'll keep looking for button info.
[Upgrading, Modifying and Unlocking] Ilithis:
Well that is interesting. I believe those were the values for the buttons inside the original ft5x_ts.kl file. I swapped mine from 1, 2, 4 to 102, 158, 217. I'm going to swap them back and give it another whirl.

EDIT:

I swapped those numbers back and couldn't get them to work. I'm not really sure what to check from here. :(
[Upgrading, Modifying and Unlocking] crmoody76:
did you check toxicoro's reply to your post. he said that he couldnt find drivers for the capacitative buttons in the original rom. which if thats the case then we to take a closer look at the key layout files some more.
[Upgrading, Modifying and Unlocking] Ilithis:
Quick Update

I saw that reply, but there really isn't much in those .kl files to change. I did notice that when I used Livesuit to start over (read the next section) and launched the button remapper app, that it showed all 5 of the buttons now (vol up/down, home, menu, back) instead of just the software buttons (home, menu, back). This got my hopes up slightly that maybe all I needed to do was start over, but alas, that was not the case.

So, I tried copying the entire /system/vendors/ contents from the original ROM to the tablet. After I rebooted from that the screen went black and the tablet never started up fully. I had to use livesuit to get back to a bootable state and repeat all my previous fixes. Then, I went on a tangent and did some overclocking.

I got my processor up to 1.2GHz, but anything over that mark broke everything and it set my frequency back to the default value. I used Antutu's tools to overclock and make sure the system is stable. I then started overclocking my RAM, but I'm not entirely sure that it is actually taking effect. I'm editing the script.bin and pushing it back every time I up the DRAM frequency and then testing for stability. I have taken it from 480 to 600+ MHz and it passes the stability test every time. Perhaps the change in frequency will change a benchmark score enough to let me know its actually changing the frequency. Once I ensure that the RAM is sufficiently overclocked I plan on overclocking the mali module in the script.bin as well, but I think I will run into the same problem where I am not sure that the changes are really taking effect. There are a ton of apps out there that monitor the CPU, but I have yet to find one for the GPU/RAM.

EDIT:

I started taking a look at the script.bin from the original ROM. There is little difference between the two versions, but it was interesting to find that they originally went with gt811-ts instead of ft5x_ts because they have commented out the lines for that section of the ctp_para section. Another intersting note was that they are using 3 different gsensors in their script.bin. I copied some things over that looks suspicious, but I doubt any of the changes in the script.bin will work. I'll delve deeper into other sections of the ROMs and see if I can't spot anything else out of the ordinary.
[Upgrading, Modifying and Unlocking] metime17:
need working rom

hey, i was wondering if anybody can post a stable rom for the trio7c tablet with wifi working and everything, i cant find anything on it, thanks! and im wondering if i can install cm10 on it too
[Upgrading, Modifying and Unlocking] crmoody76:
start here:http://www.techknow.me/forum/index.php?board=131.0 and sign up. they a whole section of roms for this and other tablets.
[Upgrading, Modifying and Unlocking] zokter:
Hello, I need help to install CWM in my tablet TRIO STEALTH PRO 7, please help me D: my tablet is locked ><
[Upgrading, Modifying and Unlocking] zimlokks:
what exactly are u planing to do?

Flowed Away From My Samsung GS2 E4GT
[Upgrading, Modifying and Unlocking] LazerFish:
please help

I am a complete noob with android, and I think i may have killed my Stealth Pro 7. It will not boot past the android screen, and I can't get it to go into safe mode. I installed an app, and when I rebooted it just hangs at the android screen. Is there anything I can do? I didn't make a backup. :(
[Upgrading, Modifying and Unlocking] Ilithis:
I'm not sure if this will help or not, but I encountered something odd the other day with my tablet. I was monitoring the battery temperature and battery charge level/life indicator. When it was around a 30% charge and was at a normal 30 degrees Celsius the battery life indicator went from good to bad. At that point I shut down my tablet and booted it back up except it hung on the little green android screen. I held the power button to power it back down and tried powering it back up, same thing. Then, I plugged it into my computer to charge and somehow that fixed everything. So try plugging it into a power source (mine worked with USB, I didn't try the AC power) and see if it boots up randomly like mine did. After I powered it up, I let the battery discharge to nothing and charged it back to 100%. It works fine now.
[Upgrading, Modifying and Unlocking] LazerFish:
thanks :)

I tried that, but it still won't boot. It did allow me to get into the android system recovery though, so thanks very much :)

I tried the factory reset, but that didn't work, so now I think my only hope is to "apply update from external storage"

Can anyone help me find the update I need to apply?

Edit: the chip is A10, if that helps :)

Edit #2

Well, I finally figured out livesuite and I installed "F1-4.1.1-20130319.2.0.6-A721_V4.2.img" and it seems to be working great now with 4.1.1 instead of the original 4.0.3. Wifi, Camera, and hdmi are working and so are the main buttons. Volume control buttons aren't working, but there are volume control icons on the taskbar now. There is also no "x" to clear notifications. Any way to fix that? If not, no biggie, it's better than a non-booting tablet any day. The page switch areas on the desktop do not work either, so you have to slide your finger to switch pages, but I actually like that better than before. lol

Also, I've been noticing quite a few apps say that they aren't supported now, when they were before. Most notably Firefox, Chrome and Instagram. Is there any way to work around that?
[Upgrading, Modifying and Unlocking] Ilithis:
The volume controls probably just need to be remapped. You can try using this: http://xdaforums.com/showthread.php?t=850464 I'm not sure what the numbers are associated with the volume buttons for the A10, but normally they are 114/115 IIRC. For the A13, it was 114/139.

I was never fond of ICS so maybe the 'x' to clear notifications ended with it. You can open the notifications area (bottom right) and swipe the notifications away left or right to get rid of them.

I've always swiped my screen to get at different pages of the 'desktop', so I'm not sure what this page switch area is.

Try uninstall the app and redownloading it to see if the that fixes it.
[Upgrading, Modifying and Unlocking] LazerFish:
Thank you, I will try to remap them :) And thanks for the tip about notifications, as I said I am a noob, lol. I don't know what the actual name for the page switch area, but on the old version you touch anywhere in the left or right empty columns to switch pages. It was actually pretty annoying most of the time, I only ever used it by accident. It might have been discontinued after ICS too.

The apps, though, I can't even download them from the play store. My device went from being named "Unknown SoftwinerEvb" to "Unknown F1" in the play store after the update, the store page says the apps are compatible with the old one, but not the new. I haven't tried any other way to install them yet though
[Upgrading, Modifying and Unlocking] Ilithis:
Original lsmod

I was wondering if anyone can post their original ROM's lsmod output. I'm trying to get proper drivers for the capacitive touch keys because mine do not work.

Thanks!
[Upgrading, Modifying and Unlocking] crmoody76:
here ya go!:)

lsmod

8188eu 621088 0 - Live 0xbf0b1000

rtl8150 10305 0 - Live 0xbf0aa000

mcs7830 7581 0 - Live 0xbf0a4000

qf9700 9152 0 - Live 0xbf09d000

asix 24601 0 - Live 0xbf091000

sun5i_csi0 33255 0 - Live 0xbf083000

gc0308 18408 1 - Live 0xbf07a000

videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf075000

videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf06b000

cedarx 9351 0 - Live 0xbf064000

mma7660 7193 0 - Live 0xbf05e000

dmard06 11443 0 - Live 0xbf057000

mali 151212 8 - Live 0xbf025000

ump 49486 15 mali, Live 0xbf011000

ft5x_ts 45201 0 - Live 0xbf000000

root@android:/ #
[Upgrading, Modifying and Unlocking] ersatzorama:
Stock firmware or FaaastJB v1 for A13

I have the A13 version of this tablet which at the moment is hardly functioning. After having tried several ROMS and being unable to restore my Uberizer firmware backup, I am currently at a loss as how to proceed. I currently have the FaaastJB ROM installed as downloaded from the Techknow website. With illithis' modifications to the TS and Gsensor drivers it is working, although on my tab the middle of the TS is way off.

I was curious if anyone (illithis perhaps?) got the FaaastJB v1 ROM working on the A13 version of the Trio Stealth Pro 7c. If so, any chance you could share the working drivers?

Otherwise, does anyone have a working stock ROM for he A13? I've tried several mentioned earlier in the topic, but most have them have TS issues.

Any other tips are also welcome, of course!
[Upgrading, Modifying and Unlocking] Ilithis:
At the moment I'm still on v1 of FaaastJB and have everything working besides the capacitive keys. The modifications that I got from Toxicro can be found here:

http://www.4shared.com/rar/07lqpo5V/ilithis.html

that had my touchscreen working perfectly. If that doesn't work, then I fear we might have different touchscreens somehow. I got my tablet from TigerDirect back in March, hopefully nothing changed since then that would have changed drivers.
[Upgrading, Modifying and Unlocking] apechto:
Hi, I'm working on a 7c, no hdmi and it is a a13 and now I'm stuck at the little android boot screen. the one with an android in a cube and a blue circle. I am a noob at all this and am stressing right now because this is a friends. The last things I did was flash faaastJBA13v2 and run a bat file in a rar called "ilithis". If anyone could help me go back to stock or something. I have read through this thread and searched and really can't come up with an answer. Any help would be appreciated.
[Upgrading, Modifying and Unlocking] Euclid's Brother:
Thanks for this! We have several of these at work just sitting on a shelf (useless).

The first one I looked, the screen went total white before i could do anything to it (broken). The next one is a A10 w/o the wifi issue. So i installed the ROM quoted above.

Everything is Great.... except.. Google Play seems VERY slow to download apps. Searching for apps is fine. Web browsing is fine. So it's not a wifi issue. I've tried to install a few apps, and so far none have downloaded more than a couple of kb's.

Any idea's what could be wrong? I've tried connecting to 2 different wifi routers.

Thanks!

James

Edit: It seems to have resolved itself. Working great now! Thanks again!
[Upgrading, Modifying and Unlocking] dpants:
Dead Link

The dropbox link for the CWM recovery is not working anymore. Does anyone have another link?
[Upgrading, Modifying and Unlocking] Alexminatl:
My mom just got one of these and I can't manage to root it, or even get it to show up for LiveSuite. Can I get some help?

I have got the tablet in the upgrade mode, I know it this because it shows up in my device manager. I have the LiveSuite usb driver installed for the tablet in upgrade mode, but when I try to run the system upgrade it says "No device available!"
[Upgrading, Modifying and Unlocking] JG:
here is some info you all might find helpful

https://www.schrauger.com/how-to-upgrade-a-trio-stealth-7-model-7c-a13-from-ics-to-jb

if i helped please press thanks!