yashsingh1/xdaforums huggingface dataset:
[Thinkpad Tablet General] pisuke2012:
Lenovo s2109 rooted

@Jittery Jim: Rooting following polakko's (or el_fuego's) guide is straightforward. I did it yesterday and found no problems, you should only consider luckyjay's post regarding the adb driver.

@all: As I imply above the rooting process was free of problems and I have successfully installed CWM. However, after rooting I've run into some other problems:

First:

I rooted before performing a Software update (i.e. I still have the original version 4.0.3). I was planning to make a backup of the system after CWM installation and then update to 4.0.4.

When I try to backup the system using CWM everything works fine until the step "Backing up data..." I get the following messages:

- No /sdcard/.android_secure found. Skipping backup of applications on external storage.

- Backing up cache...

- No sd-ext found. Skipping backup of sd-ext.

- Generating md5 sum...

- Backup complete!

After backing up, I find in the internal sd card 4 files (in total 500K) and a directory called "blobs" with several subdirectories. In total about 2000 files. Is that the backup?

Furthermore, when I try to update to 4.0.4 using CWM, I get the following:

- Finding update package...

- Opening update package...

- Installing update...

- Mount partition

- Verifying current system...

- assert failed: apply_patch_check("/system/app/Launcher2.apk", .....

- E:Error in /sdcard/update.zip

- (Status 7)

- Installation aborted.

If I try to update from the normal system (i.e. outside CWM), CWM stops the update upon reboot.

Any ideas of how to update to 4.0.4 after CWM has been installed?

Second:

I have installed Super Manager from the market. When I try to enable ROOT, I get a message telling that ROOT functions are nor supported in my device. As it could be expected, Superuser does not inform that there is an app trying to get root priviliges, and Super Manager does not appear listed in the superuser's app list.

Third:

It appears that in newer Android builds, it is not possible for third party apps (apps that were not preloaded on the device, but you manually installed or downloaded from Android Market / Google Play) to gain write access to the external SD card. This was not an issue on Android 2.x but it became a problem on Android 3.x.

The implications of this (at least in my cse) is that I can not create folders, copy files or move apps to the external sd card. That even happens with the preinstalled ES Explorer. The solution to this problem is easy if root access is available. One just needs to add the line <group gid="media_rw" /> within the WRITE_EXTERNAL_STORAGE section of the file /system/etc/permissions/platform.xml.

I have pulled the file platform.xml with adb and updated it accordingly. However, I can not push it back because the directory /system/etc/permissions is read only. Any ideas of how to circumvent this problem?

Cheers,

Pisuke
[Thinkpad Tablet General] Jittery Jim:
Thanks, I'll see about giving it a shot.

The main reason I am interested is I would like to install a mod of Jelly Bean on the thing, but now I am not sure there is a build that the tablet will support. Anyone know?
[Thinkpad Tablet General] Jittery Jim:
Well...Rooting seemed to go ok, but I got a little too ambitious and attempted to install a JB build that turns out wouldn't work. So I had to restore to factory as CWM wouldn't load my recent back-up. Not sure if I now need to re-root or not.

If there is no JB that will work on this I really have no point in rooting, I guess.
[Thinkpad Tablet General] pisuke2012:
Well, one of the points of rooting would be being able to write the external SD card with apps which are not preinstalled. Or even move apps from internal to external SD card. The problem is that you need to modify the file platforms.xml (see my post above). Unfortunately, I haven't manage to do so yet. I can not remount the system directory with write permission.:(

Did the tab with JB boot at all? or you had to restore factory defaults with CWM?

Did you update to 4.0.4 before rooting?

Where did you found the JB mod? is there a project porting JB to the Medion s9215/ Lenovo S2109?

Cheers,

Pisuke
[Thinkpad Tablet General] Jittery Jim:
I was/am on 4.0.4 and was there before attempting root. Despite following the directions a root checker app continues to tell me I do not have root access. :(

The JB mod was a mistake on my part, not paying attention I grabbed one that was built for the Kindle Fire. I could not get it to install at all; not sure now if it was due to the mod or due to actually not having root.
[Thinkpad Tablet General] lorenc75:
Bricked my s2109

Well, me like the previous people and Jittery Jim above, being too ambitius after rooting s2109 tried JB customs rom's. I did try to flash JB because I have installe CWM V.6.0.1.0 and did make a back up. I used that back-up to restore my ideatab s2109 and it worked fine!

Now after trying to flash JB, which failed :crying:, I can not make a succesfull nandroid back up using CWM . I tried advanced restore and I can restore succesfully : boot , system, cashe, sd-ext, but I can not restore data.

Now my S2109 just boot loop :crying:

Also, I did try the factory reset and it is not working. The same result as boot loop...

Any help available?:angel:
[Thinkpad Tablet General] Otamay:
Jeje I have a reboot-loop too.

I've installed CWM and gained root access with this useful guide.

However, recently the s2109a tablet showed me a message about "Encryption Unsuccessful", and with a button to do a factory reset. The factory reset process fails everytime it starts.

I've read some guides regarding this problem, and in all of them mentions that I need the latest build of ICS for my device. Where can I find that build for the IdeaTab s2109? Or maybe we need to compile our own ICS?

At least CWM works, but I don't have a backup :S. Any help, too? Thank you in advance.

--

Nevermind, I solved the problem.

The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.

In short I will upload my IdeaTab s2109a /system and NANDROID backup.
[Thinkpad Tablet General] freewheeling3:
All I can find is the adb interface driver for the thinkpad tablet, is that the same as the ideapad?

Also, I downloaded the SDK tools but there wasn't an option for Android 4.04 , just 4.0 (API 14) and 4.03 (API 15). Will it go ahead and install the revision for 4.04? (I assume that I'm supposed to install the SDK tools on my Windows 7 Pro 64bit device, though the instructions just say to download them.)

Thanks.

---------- Post added at 02:55 AM ---------- Previous post was at 02:05 AM ----------

I downloaded the Android-SDK that was on their site and installed it, but I'll be darned if I can find the files that your instructions say to modify. There's no such directory anywhere on my system. I finally used the exe to install SDK tools thinking that would place the files in the appropriate place but there aren't any. Perhaps the instructions are for downloading the German version? Could you provide a link to the appropriate download site?

Update: I have now downloaded and installed the ADT package and have run the SDK installation standalone (not sure why I need to do both of these steps, but what the heck). I found the correct inf file and did the modifications. However, I did get an error when installing the adb driver so assume I have to install a different fdriver. I have a win7Pro x64 box and am trying to root an S2109 with Android 4.04 installed. I've set the developer tools to enable debugging mode when connected to usb. But is there another adb driver I should download? Is there a driver located on the device itself that might be more appropriate? Again, couldn't find a lenovo s2109 tabet driver, just the thinkpad tablet driver, and it's files don't look right.

Update2: Took a few educated guesses and it worked! I installed the thinkpad tablet adb files after modifying them, by just overwriting the files that were already there. Worked perfectly when it came time to define the drivers and after that it even identified the right device name (rather than Blaze). The rest of it went pretty smoothly. Thanks for updating the instructions on the German site, that was helpful.
[Thinkpad Tablet General] freecicero:
Anyone Making progress with CM on S2109?

Or happen to know where there is an active forum discussing the S2109. I also have an HP touchpad running CM9 and it performs much better than my 2109. I'd really love to get CM working on the 2109.
[Thinkpad Tablet General] snaganalf:
Did this get uploaded?

I'm needing a clean copy of this. I bought a display unit that was monkeyed with and the rom is corrupt on it.

If you would be willing to share it with me please contact me at snaganalf@cox.net.

Thanks.
[Thinkpad Tablet General] lakerstyle:
Has there been any work on getting a Jelly Bean Rom for this tablet? Would be nice if we could get CM10.2.
[Thinkpad Tablet General] freecicero:
I am having the "Encryption Unsuccessful" message and cannot break through to a solution. I saw the post above where the user seems to have gotten past the error by formatting the data partition via ADB. Can someone tell me how that was done exactly? I am getting a device not found error when I try to use ADB (from the screen entitled (Encryption Unsuccessful) and I cannot for the of me (or google) figure out how to issue the mke2fs and tune2fs commands!

Thanks to anyone who can help!!!

<<<Nevermind, I solved the problem.

The /data partition was corrupted, and any attempt to format it via CWM wouldn't work (maybe it uses mkfs.ext2 which fails sometimes). So I've formatted the partition via ADB with mke2fs and then modified the filesystem with tune2fs to add ext4 support. Then the reboot worked.

In short I will upload my IdeaTab s2109a /system and NANDROID backup.
[Galaxy S III Accessories] pwned101:
Hi,

Sorry about the title being so long :). But yea, anyone know if i can buy just the silcone/soft shell of the trident aegis case? Right now I have a black one. I was thinking of getting red or green. Is it possible?
[Galaxy S III Accessories] Blaze03:
I'm sure they're going to have them available at some point I'm waiting on it too..... Want black, and red.... Already own blue!
[Galaxy S III Accessories] pwned101:
Do they usually have them on sale seperately? It would have been awesome if they did... :)
[Galaxy S III Accessories] aturyan:
I don't think Trident sells the silicon separately. You should contact them and ask if you can set up a special purchase.
[Galaxy S III Accessories] Blaze03:
If you check the Site you can see they sell the silicone by itself for other products so I'm guessing they will for the s3 aegis!
[Nexus 7 Q&A, Help & Troubleshooting] saryu:
so, i have installed PDAnet for tablet to enable bluetooth internet connection and foxfi on my nexus s for free wifi tethering and bluetooth DUN.

i just wonder, which 1 is better for battery? is bluetooth DUN or WIFI tether that takes more battery on my phone and on my tablet?

Just for the sake of knowing, i will try to test both, but if any of XdA member have more knowledge on this, please share your knowledge.

edit : when connecting through bluetooth DUN, it says "no internet connection" on the N7 side but it actually connected to the internet. I wonder if it's normal
[Nexus 7 Q&A, Help & Troubleshooting] MatAuc12:
I believe bt is the best way battery wise.
[Nexus 7 Q&A, Help & Troubleshooting] WinDroidGuy:
Under tethering...more...enable bluetooth tethering and pair phone with tablet, you don't need any extra software and it will work fine. Using bluetooth tethering made my battery last wayyyyy longer and my phone doesn't get hot like it did via WiFi tethering
[Nexus 7 Q&A, Help & Troubleshooting] Verixx:
Bluetooth all the way, if you can. Though pairing can be a bit tricky with some devices, it's worth it for the superior battery life and lower heat.
[Nexus 7 Q&A, Help & Troubleshooting] raznalab:
I agree Bluetooth is best if you could get it working. It took a few tries but it works as he says, no additional software needed.
[Nexus 7 Q&A, Help & Troubleshooting] saryu:
I'm under tmobile usa, are you sure the carrier won't charge extra if i don't use any software to bypass carrier detection?

Edit :

I've dig in google and found this

"Except with Phone-as-Modem plans, you may not use a phone (including a Bluetooth phone) as a modem in connection with a computer, PDA, or similar device. We reserve the right to deny or terminate service without notice for any misuse or any use that adversely affects network performance.[7]" so i guess i still need that software. Sucks to be me
[Nexus 7 Q&A, Help & Troubleshooting] raznalab:
I also have tmobile USA, I'm on the 5gb plan and it includes tethering. After 5gb they start throttling but I don't get extra data charges or over ages. I just recently opened my account so maybe it wasn't offered before.
[Nexus 7 Q&A, Help & Troubleshooting] WinDroidGuy:
That's not true, you don't need it. I've been doing this for ages

Sent from my SCH-I535
[Nexus 7 Q&A, Help & Troubleshooting] gbroon:
Bluetooth is much better on battery.

What i found on my phone when i tethered at work all day for 8.5hours is that bluetooth used maybe 10% extra battery, wireless i had to start charging about halfway through my shift when the battery fell below 20%. Normally i leave work with about 50-60% battery left if not tethering.

So I'd say bluetooth is definitely a lot easier on the battery.
[Nexus 7 Q&A, Help & Troubleshooting] ov_darkness:
(slight OT) Here in Poland we have government agency called UKE. It manages band lease for operators.

With LTE (2600MHz band) contest there was a condition: free of charge web access until certain (about 75% for HSUPA and 50% for LTE) coverage is reached + 2 years :D

Ad rem:

Almost any phone doing HSUPA 900MHz cat 10 or more should work with Aero2 (thats how Polish LTE operator is called)

Any phone offering Bluetooth PAN should work with Android tablets, Nexus & included :)

I'd prefer Nokia C3-01 for that task :)

It cost less than most other phones (less than 100USD), and it has good battery.

It also has WiFi, but I'm not sure if WiFi tethering is possible.
[Nexus 7 Q&A, Help & Troubleshooting] joy01804:
C3-01 Tethering issue

Hi, I have owned a C3-01 and purchased a Nexus 7 specifically because I can tether. Everything works great until last Friday tethering stopped working for me. I tested it and my C3-01 can still tether to my laptop, but whenever Nexus tries to connect to the internet via the phone, the bluetooth connection just disconnects.

Any ideas?

Joy
[Nexus 7 Q&A, Help & Troubleshooting] jasdinggo:
I'm sure that wifi takes more battery than bluetooth.
[Nexus S Q&A, Help & Troubleshooting] superng888:
Hey guys :) May i know how do i change voodoo colours setting on slim bean + air kernel r171 voodoo colour enabled? I tried downloading voodoo control plus but couldn't find the voodoo colour settings :eek: Can anyone help me out? Thanks in advance. :angel:
[Nexus S Q&A, Help & Troubleshooting] Drizzy xS:
Try a different kernel first.. could be a dodgy kernel.
[Nexus S Q&A, Help & Troubleshooting] ciaastek:
There are options for this. See bottom part of voodoo sound. And the kernel is good

I feed my Nexus S with jelly beans.
[Nexus S Q&A, Help & Troubleshooting] Drizzy xS:
No.I think he's saying the settings aren't there therefore he might of flashed the kernel wrong or something so voodoo colours aren't showing up. He should try bedalus kernel that supports voodoo too. If it doesn't work on that then he's done something wrong.
[Nexus S Q&A, Help & Troubleshooting] ncblackout:
Maybe someone can explain some about voodoo colors to me... After flashing Air 171 voodoo, my screen looks awesome. The blacks are super dark and the whites are super bright and the colors pop. It's like night and day compared to other kernels I've run before (presumably without voodoo color). The other day after running the kernel for a few hours, everything turned this nasty grayish greenish color (I mean every dark color looked washed out and nasty). I tried a bunch of things to troubleshoot including wiping and a different ROM, and came to the conclusion that it was the kernel. After I flashed back to Matr1x, the problem went away, but so did the nice looking colors.

So my question is: is voodoo supposed to make the colors darker/more vivid? When I flashed Air 182, it looked just like the phone had always look, kinda bland in comparison. So now I'm back on 171 but I'm scared it's going to goof up the colors again...
[Nexus S Q&A, Help & Troubleshooting] 309041291a:
The dark, nice colors come from changing the gamma hacks. The amazing, deep, crisp colors do however come with a price. What price? Well you experienced a little of it, the green flicker. Turn your brightness a little up to avoid it, no big deal. That's not the major problem. Changing the gamma hacks causes your phone to "age" quicker. Meaning it will basically get worn out faster and eventually will lead to damaged colors and OLEDs (permanent). Not for a LONG time, UNLESS you max out the gamma (-50+ is dangerous). I had mine at -59 and -60, now my screen is damaged. Forever. I have piexalted errors and over saturated colors, especially noticeable on black and whites (and now reds). And i have some overheating issues too. Lower gamma = more heat. If I change my gamma settings, nothing happenes because I've broken the screen (then again, I recently had a cheap screen replacement done so part of the reason is the cheap screen just sucking). Lesson is be careful when you mess with the gammas!!!!!!!!! The reason the newer air kernel had different colors was because r_data changed the gamma values (but be did it to get rid of green flicker, I presume) from his last build.Now I am looking for a job to by myself new phone And of course have some money.

Nexus S. (GSM i9020a)

Paranoid (1.97a - 4.1.1)

Air Kernel (Week 182 - Voodoo)

SmartassV2 (1200/200)

Deep Idle (On - Deadline)

Black Exodus (Inverted apps)
[Nexus S Q&A, Help & Troubleshooting] ncblackout:
So I'm curious why it's called "flicker" then... for me it's consistently green until I flash a new kernel. I kinda figured that was what I was experiencing, I was just confused by the verbiage. Anyway, it's a shame that these screens have the potential to look that good but dong so ruins them...

---------- Post added at 10:09 AM ---------- Previous post was at 09:24 AM ----------

I spoke too soon... it's back to looking good now

---------- Post added at 10:36 AM ---------- Previous post was at 10:09 AM ----------

Also, his long did you run those gamma settings before it screwed IP your screen? I know you said a long time but can you give an educated guess?
[Nexus S Q&A, Help & Troubleshooting] 309041291a:
Using the stock OEM screen I had gone for 8 months of perfectly fine colors. A week of the new screen replacement I had then it was dead. If you used gamme values that are lower on the stock screen it'll last a VERY long time, you'll get a new phone before anything happens for sure.

Nexus S. (GSM i9020a)

Paranoid (1.97a - 4.1.1)

Air Kernel (Week 182 - Voodoo)

SmartassV2 (1000/200)

Deep Idle (On - Deadline)

Black Exodus (Inverted apps)
[Nexus S Q&A, Help & Troubleshooting] ncblackout:
Well in that case it looks like I'm running it this way if I can get rid of the green...
[Nexus S Q&A, Help & Troubleshooting] 309041291a:
You can lower the values, just do NOT go passed -50, stay -45 and above.

Nexus S. (GSM i9020a)

Paranoid (1.97a - 4.1.1)

Air Kernel (Week 182 - Voodoo)

SmartassV2 (1000/200)

Deep Idle (On - Deadline)

Black Exodus (Inverted apps)
[Nexus S Q&A, Help & Troubleshooting] polobunny:
I can't see how changing the gamma make the screen wear out faster. We're not talking about multipliers here, or refresh rate or anything of the sort. We're not going out of spec but simply changing the already available settings. Burn in exists already even on the stock settings, so don't be too quick to blame the problems on Voodoo.
[Nexus S Q&A, Help & Troubleshooting] 309041291a:
The creator of the Voodoo app warns people not to max out the gamma settings, because they can destroy your screen faster.

Nexus S. (GSM i9020a)

Paranoid (1.97a - 4.1.1)

Air Kernel (Week 182 - Voodoo)

SmartassV2 (1000/200)

Deep Idle (On - Deadline)

Black Exodus (Inverted apps)
[Nexus S Q&A, Help & Troubleshooting] arborglen:
I am also sticking with Air Kernel #171 for the perfect color on my 9020T. I don't understand why the voodoo color default keeps changing with each update. :confused:
[Nexus S Q&A, Help & Troubleshooting] polobunny:
You wrote - and + though. Still cannot conceive how exactly it is possible to break something faster while operating it in the normal range. Are you sure he is not talking about the multiplier settings and not the gamma settings?

The gamma settings only affects the level, from darkest to lightest of every separate color (RGB). Think of it as deciding on 100%, how much of each color there is in the picture. You can't do 110%, maxing out every slider will only give you a white picture, but that's only every channel at 100% intensity.

I imagine that could make your screen "die" faster, but just as much as having a white wallpaper as opposed to a black one.

I cannot comment on the multipliers, not being sure of what exactly is touched when changing them.
[Nexus S Q&A, Help & Troubleshooting] 309041291a:
This is what I mean by your gamma offsets. I assure you -45 is not normal. 0 on all of them is 2.3.3 defaults. You're forcing your screen to display different, darker colors than normal. Which does use more heat on the screen. More heat = not good and can lead to permanent damage on any surface, let alone a glass screen.

Don't get me wrong, Voodoo can be complelt harmless. So long as you don't max out any of the settings. Never use -60, that's just... no. Slight changes like punchy settings -14 - -18 (I believe) really don't have that much affect. But when you start forcing the screen to get darker by using -45 and under.. Yeah, its not good.

Nexus S. (GSM i9020a)

Paranoid (1.97a - 4.1.1)

Air Kernel (Week 182 - Voodoo)

SmartassV2 (1000/200)

Deep Idle (On - Deadline)

Black Exodus (Inverted apps)
[Nexus S Q&A, Help & Troubleshooting] polobunny:
Except this is not how it works with most displays, and certainly not with an active matrix OLED one. To display black, the RGB channels are at their darkest setting, which uses the less amount of energy. If that, it would even be more beneficial for the panel to use darker settings than stock. Hence my questionning. ;)

Edit: To add details, I do not mean all type of displays, but rather OLED based ones, may it be PMOLED or AMOLED or any other branded product (Super AMOLED and so on). The cells are in off state when showing "black" hence why the blacks are so deep. Off cells = less power, and less power = less heat dissipation.
[Nexus S Q&A, Help & Troubleshooting] ncblackout:
So now I've realized another related conundrum... If I turn the brightness up, apparently the green goes away, but obviously that causes my battery to die faster. Normally, before I started messing with voodoo color, I kept my screen on auto brightness which generally kept it pretty dim. I got pretty awesome battery, at one point 30+ hours on a charge. So my question is, is there no way to have the nice looking gamma hack colors and also good battery and/or a dimmer screen? Do I just need to play around with the settings to achieve this?
[Nexus S Q&A, Help & Troubleshooting] polobunny:
Depends on how low you set those values in Voodoo colors. It's a mix between low values in Voodoo for the gamma offset settings AND the brightness.

Some kernels don't have Voodoo but have preset colors that are very good and vibrant and do not have the downsides of Voodoo such as green flash.
[Nexus S Q&A, Help & Troubleshooting] ncblackout:
Have any recommendations? I've tried matr1x and air on jb, didn't really do much with kernels before then.