yashsingh1/xdaforums huggingface dataset:
[Xperia Play Themes and Apps] sewer56lol:
That intent is not in the Xperia Launcher.

It is hardcoded into a system process that is easy to modify :

It needs ROM changes, Smali does not need to be changed either :)
[Xperia Play Themes and Apps] sheraro:
First Great work RozenTensai :good: that's the launcher that our Xplay deserves !

The roms listing takes ages for me (like 5min but i have only 3 roms) , is it normal ?

it keeps searching for them each time i enter rom folder again (loading icon)

Background picture is also cropped in right and left even if i set it to 854x480 like recommended (picture attached) :

summary didn't display too ...

Also could we have a dark background for texts ?
[Xperia Play Themes and Apps] Miles Wolf:
Just a little reminder, this app is in early stage of development, so some anomalies using it are normal.
[Xperia Play Themes and Apps] sheraro:
yes i know and so are feedbacks ;)
[Xperia Play Themes and Apps] Miles Wolf:
Oh ok. Sorry then. :silly:
[Xperia Play Themes and Apps] Luxxuor:
Interesting, could you point me to the file(s) that need to be changed? Thanks in advance for the explanation.
[Xperia Play Themes and Apps] mocool05:
MAN YOU ARE AWSOME. Works properly, on gb in landscape and potrait, tock and gamepad fully working. You DO NOT know how long I've been waiting for this. All hail Rozen!

From The god of gaming, the R800i Xperia Play
[Xperia Play Themes and Apps] RozenTensai:
Wow, seems like it was long time ago since my last post (well, really it was some weeks) but let me report what i'm working on. :)

As I thought about how to dynamically add items to the menu (actually they're sorta static, hence the need to load everything when entering submenus), I found that the way i was using to do it was not the correct (it was somewhat modular, and proved to be slooooow...), so I'm actually merging some code and extending other, so that's what's keeping me from releasing another test build. :silly:

Oh!, I'm finishing too the code that load themes, it should be, as I said some posts ago, compatible with uncompiled PS3 themes (that is, just the XML with the icons/pictures, zipped only, and uses just the icons and backgrounds for now), because I haven't the time to do some hacking and reverse engineering to the p3tcompiler and format itself.

Here you can find what I'm talking about, or if you just wanna see how it's composed.

About the ROM's summary, it showed along some region flags in early builds, but as the layout changed, they dissapeared, they sould appear in the future in a property screen as the PSP does with music properties, for example.

About the background issue, i'm aware of it, and it's caused by the recent layout type change (from an obsolete AbsoluteLayout to a RelativeLayout, I really hate RelativeLayouts, but I'm trying to keep from using 'obsolete' code). It should be fixed soon.

About 'open app on slider up', as they said, this event occurs inside a system service, so it can be modified somewhere in the system files, but i haven't investigated it so much, 'cause I'm focused on the app itself.

Thanks everyone for your comments and encouragement! Specially to those who kept reading around, doing some 'housekeeping' and aswering some FAQ's :D:highfive::good:
[Xperia Play Themes and Apps] abdel12345:
Awesome great to see your still here lol. I cant wait till this is a full app it'll be awesome. Great work :D:thumbup:
[Xperia Play Themes and Apps] clivejefferies:
For this you need to implement a service in your app. Not a trivial task.
[Xperia Play Themes and Apps] NewVegasTroop:
This is amazing, i love it
[Xperia Play Themes and Apps] Miles Wolf:
ROOOZEN! ROOOZEN! MAKE AN APP THAT LEAVES US FROOOZEN! (of impression, lol)
[Xperia Play Themes and Apps] RozenTensai:
Hello! Rozen here. Just an update.

In the screenshot you can see the same XPMB, but running on the new drawing code (and using icons directly from a theme! [a zipped one])

As it says in the screenshot, it takes around 20ms to draw an entire frame, with some system load (~7ms when idle), but this is only the proof that it worked fine, even at the first attempt.

I'm in the process of ditching the confusing DIP thingy towards pure pixel-by-pixel calculations, because aside from causing some system load (more procedures get called when using DIP), I don't want to get confused with it, and because I'm more accustomed to using plain Canvas objects, like back in the good ol' J2ME days. :p

This could lead to varied incompatibilities (like seeing smaller icons in bigger DPI screens), but I'm not interested right now in compatibility, remember the aim of this project is to have an XMB running on the XPlay. Even so, I'l try to do it as compatible as possible with other devices in the future.

The code's an entire mess so I'm not updating the repo until I do a bit of cleanup :)
[Android General] degsie:
I am starting this thread to hopefully encourage discussion on the Lenovo A2107A-F tablet variant.

I am aware there is an existing thread on the A2107 here:

http://xdaforums.com/showthread.php?t=1982334

but that thread is concentrating on the A-H (dual sim + wifi) variant which is somewhat different from the A-F (wifi only).

So far I have not found any custom rom development, which is disappointing as the stock rom leaves a lot to be desired IMHO. While the current OTA update is fine for web surfing, reading emails etc, HD video playback (particularly YouTube HD) is very poor. Also the recent OTA update forces an optimization of apps on bootup which leads to long boot times :(

You can root and install CWM by following steps 1-5 from the 1st post here:

http://xdaforums.com/showthread.php?t=2044496

Note that "-Update 3-" mentioned in the post does not appear to work for the A-F model!

So, has anybody any leads on possible development on this tab?

Any tips on improving performance?
[Android General] degsie:
My first tip:

If after installing CWM you cannot get to the CWM recovery screen after powering down the device, look for for the file "/system/reboot-from-recovery.p". If it's there, either delete it or move it to some other place. This file restores the default recovery on a system reboot.

I got bitten by this a couple of times :(
[Android General] abcdelmrs:
Thanks for starting a separate thread for the A2107A-F. I'm new to Android devices and just got this one two weeks ago. I'd like to get rid of several of the apps that I have no use for and from what I understand that means I have to root it. I got lost in the details of the other thread, but I tried reading all of it. I'm on Vista and somewhere along the line I installed one of the suggested ADB drivers via PDAnet. Device Manager is showing Android Phone and under that Android ADB Interface. I wasn't sure if that matched closely enough with the step-by-step threads since I don't really think of the device as a phone, so I've been holding off on going further. I've tried using a few other drivers that were suggested in the large thread and some other threads, but Vista always tells me the current driver is the most up-to-date one.

Do you know if it's okay for it to say Android Phone rather than something else?

Thanks. I've got some other questions about the specifics of some of the other steps, but this is probably enough to get started.
[Android General] abcdelmrs:
My apologies in advance if my posts are too long and my questions are too basic for these forums. Feel free to point me somewhere else based on what I'm asking for. I'd honestly appreciate any leads towards my goal of getting rid of the bloat on this device and making it more responsive. (Wow! The portrait to landscape lag is really bugging me now after reading around here).

Anyway, my primary purpose is to remove the seemingly unneeded programs, services and widgets that come with the tablet. Maybe I'm just ignorant about these things, but at this time things like messaging (IMO), mapping, and some of the other default features are of no use to me. They seem to be eating up a lot of resources. I can kill some of the services I think they are associated with, but they keep popping back up.

I did watch the "noob" video (color me a tiny ant to be squashed) and did try to search for an answer to get me even started. I've read the huge main A2107A thread (80+ pages) and tried three of the suggested ADB drivers with my Vista 32 setup for my A2107A-F. The only one that even seemed to connect was ADPnet and it showed the tablet as a Android Phone. Maybe I'm just too paranoid, but after the multiple "brick" posts I'd like to make sure I'm on the right path before trying to "root" the device which appears to be the first step in removing all the extra stuff Lenovo added.

Not that it matters, but I've had the tablet for almost two weeks now and my favorite things are Slacker Radio, Scrabble, Roll It and Zen pinball. I do play Words with Friends with my wife, but I don't like it since some of the words they allow are not valid in Scrabble (which I used to play as an expert competitively face-to-face).

If you are so inclined, feel free to PM me for a Scrabble game. I promise I will not use anything other than my brain and the built in dictionary to make my plays. (I'm a bit rusty since I gave up competitive Scrabble in 2006).

So, long story short... Thanks in advance for any and all advice you can give on slimming down the Lenovo A2107A-F. And if you want an honest Scrabble challenge feel free to PM me.
[Android General] degsie:
As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "shell@android:/ $". If you don't see this then you will not be able to root! You need to make that USB debugging is turned on on your device you have an entry in the device manager for ADB Interface (expand on the device which you have showing up).

I am no expert, and I struggled with this on my first go also :mad:

Once rooted you can then install Titanium Backup from the play store and use it to get rid of the bloatware! Proceed with caution however as it is possible to remove critical system apps!
[Android General] abcdelmrs:
Thanks! That's the type of test suggestion I was looking for to make sure I was on the right path with the driver.
[Android General] ShilohDaniel:
So has anyone tried creating a rom for this tab yet? I've been doing some research into porting another rom to work on the A2107A-F, but want to make sure there isn't one already.
[Android General] ssenemosewa:
I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.

Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
[Android General] Kevin147:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
[Android General] ssenemosewa:
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.

Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?
[Android General] Kevin147:
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".
[Android General] ssenemosewa:
Although I have my A2107A rooted and tweaked to my satisfaction, there are a few lingering issues that I'd hoped an update would correct:

1) The neutered Bluetooth stack. The tablet is supposed to work with Bluetooth keyboards, mice, etc. It doesn't. Although I've gotten it to talk to an external GPS module, other Bluetooth data connections simply will not work. Oh, and Bluetooth audio? Forget about it!

2) Some settings that are present in stock ICS builds are just omitted in this one. As an example, the ability to specify a default TTS voice. It's present under settings in my wife's tablet and every other ICS build I've ever encountered. Not this one!
[Android General] robk2544:
I was rooted too, lost root access (only with some apps!) after the 130221 update Feb 28. I'll try the same root procedure as before to see if I can get it back. Glad to see a thread on the popular US version A2107A-F. Maybe someone will port Jelly Bean to this tablet! Doesn't appear Lenovo wants to do it...

Rob
[Android General] degsie:
I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error :rolleyes: Anybody any ideas?
[Android General] ssenemosewa:
I'm in exactly the same boat as you. I'm getting the same exact error. except that I do not have CWM installed (I am rooted though). Perhaps there's a problem with the update.zip?

Something odd that I noticed however: After the tablet reboots into recovery mode, the update fails, and I go to browse for the update.zip, the sdcard/googleota directory is missing (along with everything that follows it alphabetically). They reappear upon normal boot. I've tried copying it to a directory closer to the beginning of the alphabet and it does show up while in recovery mode. But it still will not install.

Maybe I somehow do not have the available space to perform the update? Is that possible? I show plenty of available space on both sdcards. Could we somehow be below a certain ROM space threshold necessary for an update?
[Android General] degsie:
I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...
[Android General] ssenemosewa:
Well, I am running a stock rom. I am unwilling to "mess with success" until there's a 100% reproducible way of recovering if it fails. And, so far, everything I've read in the other A2107A thread has been hit or miss for the A2107A-F people.

Anyway, If the update is performing a verification test, then it my "virgin stock ROM" should certainly pass it. The only thing that I did is to root it. Hmmm...could the update be testing for that and refusing to install if it detects a rooted device? I would tend to doubt that, since the previous ota update went just fine. I lost root in the process but easily reapplied it afterward.

Thoughts?
[Android General] degsie:
Interestingly, I flashed the A2107A-F_S483_121115 rom (again, found in another thread) as I was having verification problems with the OTA update just released from lenovo which was available from the A2107A-F_S484_121211 flashed rom. While the S483_121115 rom appears to be older, I no longer get the option to update via OTA as the tablet is telling me that my s/w is up to date! Go figure.
[Android General] daoliverio:
It's really too bad this device hasn't taken off. If I actually knew how to dev then I would start developng ROMs for it. I'm enjoying it now that I have root and got rid of bloat.
[Android General] ShilohDaniel:
Hey guys. Just wanted to say if someone can send me a stock rom and be willing to test, I'll try to do up a good rom for the -f models. I'd use mine for the stock rom, but I've edited a lot of the system, so no go there. If you have the stock rom or want to be a tester, let me know.
[Android General] Ultimawar:
Does anyone know if degsie or ssenemosewa ever got the update working? I've holding out on rooting because of issues like these, but the stock lagg is ridiculous.
[Android General] ssenemosewa:
I never got the update to work. I abandoned the efforts after getting into a bootlooping situation the last time I tried. The only way to get out of it was to pull the battery. Which brings us to another point:

Unless you have no other choice, DO NOT TRY TO DISCONNECT THE BATTERY ON THESE MODELS! You have been warned. I have extensive experience working with microelectronics. I've done surface level circuit board work. I know my way around tiny components. The connector system they use for the battery in these models is complete JUNK. It completely shattered when I went to disconnect it from the circuit board. Luckily I was able to repair it, but even with my skills, it was mostly luck. Avoid messing with it if you can.

As to the stock lag, zeppelinrox's V6 supercharger script took care of that. He's arrogant, but he seems to know his stuff.

As to rooting, I'd go ahead and do it (you'll need it for the supercharger script and other lag reducing tools/techniques). It's a relatively easy and benign procedure.

Lenovo's official support for the A2107A-F is, in my opinion, lacking. In the end, getting a stable, useable tablet with minimal lag is the goal here. If I can accomplish that with third party techniques but must give up OTA updates from Lenovo to do so, so be it.
[Android General] Ultimawar:
Thanks ssenemosewa. I will make sure to avoid messing with the battery!

I'm on the fence with leaving the OTA updates, as Lenovo has put out 2 since I bought the device. I read somewhere that you could unroot but the procedure seemed unclear. Did you ever find out why you were getting the problems, or was still just a mystery?
[Android General] ssenemosewa:
It's still a mystery, albeit a moot one...for me, anyway.

Although Lenovo has released a couple of OTA updates for the A-F, I saw no real benefit from the one I was able to apply. Their technical support for this model has been, in my humble opinion, abysmal at best. Just look at their forums...it doesn't paint a pretty picture.

So, I've had to poke and tweak my way around to get it to perform properly. Right now, it works quite well. No lag, no crashes, etc. So Lenovo can keep their OTA's. They'd probably mess things up for me, even if I could get them to actually install.
[Android General] ShilohDaniel:
Just a heads up everyone, I'm cooking a rom right now for the -F models. Should save some battery and totally remove the lag. I'm working on a fix for the bluetooth also. Right now the rom is crashing and it's an issue with the build.prop file. I'll post a link once I get an alpha version working.
[Android General] ShilohDaniel:
Also, if anyone wants to, post your favorite build.prop tweaks. I'm planning on putting some tweaks in the finished rom.
[Android General] daoliverio:
How's everything going with the work on this rom? Thanks so much for doing this...I doubt we will ever get a JB update from Lenovo but we sure can make this tablet smooth.

Thanks again!
[Android General] ShilohDaniel:
The rom is at alpha 4 now. I'm about to release it to anyone who wants it. There's a thread dedicated to it where if any of you has suggestions, I'll listen to them and possibly add them to the rom.
[Android General] Ultimawar:
You can follow her development thread here: http://xdaforums.com/showthread.php?t=2213225
[Android General] dafever:
Android is upgrading/optimizing at boot up

Bought this tablet about two weeks ago and updated the firmware shortly thereafter. I'm now running 4.03 build A2107A-F-S486-130221. Since the update, every time I boot the tablet up, I get a message stating that Android is upgrading and then goes on to state that it's optimizing application "x" of 36. Not a big deal, hasn't hindered performance, but a bit annoying. Anyone else experiencing this?
[Android General] ssenemosewa:
Mine does this too. Same exact scenario as yours.

From searches via Google and on the Lenovo forums, we're not alone. I've found many references to this being an ICS 4.0.3 phenomenon...though my wife's tablet does not do it. Actually, to be more accurate, it may be doing it...but hiding the details. I've read that some ICS flavors simply show the boot logo during the entire process instead of showing the application count.

I've also read that this behavior is a result of ICS wiping the Dalvik cache upon each reboot. The "optimizing application X of X" is actually ICS rebuilding the cache.
[Android General] ShilohDaniel:
If you look in my sig, go to my Dropbox and flash the rom there. It is cwm flashable.

---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------

I meant to say the rom in my Dropbox doesn't have half the issues of the stock rom.
[Android General] dafever:
Well, glad to know I'm not the only one. It's a minor annoyance. Overall, I do like the tablet. I'm a bit reluctant to root the device, not that confident in my ability in that regard.
[Android General] ssenemosewa:
Agreed. It's a nice tablet for the price. It's remarkably stable, so rebooting (and waiting for it to optimize the apps) isn't an everyday thing.

I was too, but SO many great apps and utilities required it that I eventually decided to give it a whirl. It turned out to be a very easy and painless procedure. If you decide to do it, I (and I'm sure others here too!) will be happy to hold your hand and guide you through it.
[Android General] dafever:
Thanks for the offer, I may take you up on it. I have a Samsung Galaxy S2 that I rooted, mainly because I was so frustrated with the upgrade from Gingerbread to ICS and later upgraded to a leaked JellyBean ROM. That was pretty easy, followed steps outlined on this forum and videos posted by QBKing77.

I bought this tablet for my son, so I'm kind of on the fence with whether or not I need to root this device.
[Android General] Jinxwood:
I actually do need some help rooting this device, if you could :$

This is my first time rooting, I got this tablet for free and, like everyone else, decided that it simply had too many useless apps. I tried to go through the huge a2107 thread but it just makes me more and more confused...

I think I have the latest drivers (through PDAnet). I get the "shell@android:/ $" from cmd. I used the root file from 4.03root, (I get a stream of device not founds, click any key 3x, then it says the ROOT process is complete).

But when I open Titanium Backup, it says that it cannot acquire root privileges. What am I doing wrong??

Thanks a lot!
[Android General] ssenemosewa:
No problem!

The "stream of device not founds" looks suspicious. If the commands were successfully transmitted to the tablet, then it would have rebooted through each of those 3 key presses.

Just to be sure, install "Root Checker" by Burrows Apps from the Google Play store. That's what I used to confirm that I truly had root after the process.

Also, make sure that you have USB debugging enabled under developer options in the tablet settings before running the 4.03root. I seem to recall that it's essential in getting it to work.
[Android General] Jinxwood:
Root checker also says it's not routed. USB debugging is enabled. I do think it's the "device not found" part that isn't working, but I don't know what I'm doing wrong.
[Android General] ssenemosewa:
My intuition tells me that it might be a driver issue. Even though you mentioned that you have the latest ones via pdanet, I would switch to the Google USB driver for the best compatibility. That's what I used.

Other things that come to mind: Tell me you're not trying this from a Windows 8 (hate) machine...VERY problematic!

Are you running the 4.0.3root as Administrator? Running with non-admin rights might interfere with the process.

Headed to bed now (long day...exhausted!), but will check back in tomorrow morning to see where you are with it.
[Android General] Jinxwood:
Thank you! It must've been a driver problem after all, because I used google USB driver and now it's rooted :)

Thanks for your help