yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] CSP III:
Many, many apologies if my comments were taken as some sort of harsh critisism towards you. There was no disrespect meant. Only pointing out what I believe was/is the obvious as you were and have been the only user having such issues (I may be wrong on that) I too have been using it exclusively and have had only a few issues long, long ago. I fail to see how "if it doesnt work for you, choose something else" is the wrong attitude here. Thats the way its been around XDA since I have been coming here and that is part of the learning, experimentation and love of Android. I have always believed that with these Tab 2's, in particular, are all different in some way or another. Example being the notorious "battery drain" Some have had it and others have not. I have not, fortunately, on all of mine. That is why I said what I said. If its not working for you, and maybe only you, move on and try something else and as you said "find something that works for YOU" Anyways, again, I mean no disrespect to you, or anybody else here in this great community of Tab 2 users.

---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
[MENTION=5061733]CSP III[/MENTION] and [MENTION=283861]Shepguessed [/MENTION]

Perfectos los dos - Ok for both.

:good:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] ron12:
Regarding Netflix, it has been working fine with my P5113 running Omni ROM with the Apr 12 Dhollmen kernel. Also, the battery drain problem has not occurred with this this kernel.

My tablet seems a bit sensitive to over clocking. I have the occasional FC running at 1360MHz. But it is very stable at 1216MHz.

The previous March 20 Dhollmen kernel never had a FC at 1360MHz, but anything faster caused FC and random reboots.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] gspro2000:
its too late when i posted that. it comes up as a qual comm Dload in the device manager

any ideas how i can bring it back to life
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] CSP III:
You''re going to have to try getting yourself a stock ROM, flash the .tar with Odin and hope/see what happens. [MENTION=5153662]Android-Andi[/MENTION] may have an idea or two. Keep your fingers crossed and always, always double check anything and everything b4 flashing. Good luck!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] schurgatzi:
Any chance to get cifs / NFS support?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] nielowen:
Using the 0412 version on SlimKat 02-06 weekly - with or without additional blobs zip - results in "cannot connect to camera". I've tested this on two P5110s. With the default SlimKat kernel ther is no camera error. Not even Temasek's "restart camera" app can fix the problem when I've flashed the Dhollemn kernel.

Does anyome have any suggestions? I really do like running this is kernel and it had worked so well with SlimKat....
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Badwater55:
With CM11 there is no issue with the camera. (P5110)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
[MENTION=3638904]nielowen[/MENTION] the search function would have helped you :p we are using different vendor-blobs on SlimKat

As you can read in OP:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] nielowen:
Yes, thank you [MENTION=5153662]Android-Andi[/MENTION] for your interesting suggestion. Different from many others, I do indeed make use of the search and it is therefor quite infrequently that I feel the need to post about an isssue that I have not been able to sort out myself. I therefore confirm that I know about the different blobs - I subscribe to the P5110 and P3110 threads and appreciate the sterling work you have been doing. I also confirm that I have tried flashing the patch referred to in the OP, although I concede that I could have made that more transparently clear and obvious in my post above.

So, to recap, when I flash Dhollmen kernel with no "appropriate blobs & libraries" from OP also flashed, the camera does not work. When I flash Dhollmen kernel AND the "appropriate blobs & libraries" from the OP, the camera does not work. This is the case on two separate P5110s.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Try blobs from NEXT Kernel, should work if i am not wrong.

Gesendet von meinem GT-I8190 mit Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] nielowen:
Thank you [MENTION=5153662]Android-Andi[/MENTION] - I tried the blobs from the NEXT Kernel and they do not work either. If I try the Dhollmen kernel + blobs from OP of this thread, camera doesn't work. If I try Dhollmen kernel + blobs from NEXT kernel, the camera doesn't work. If I try the NEXT kernel & its blobs, the camera does not work.

I wonder if anyone else is suffering this issue with the P5110?

Anyhow, we're off on holiday from Saturday :cool: so there's no more time to try anything and the P5110s are back on the latest SlimKat weekly and stock kernel. :good:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
You need to flash the blobs DIRECTLY after the kernel, no reboot between both flashes. Should work ;)

Gesendet von meinem GT-I8190 mit Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] nielowen:
Oddly enough, I knew that, so that's what I did. Didn't work.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
I solved my fc and reboot problems with kernel oc'd at 1460. I lowered the voltage from 1425 to 1410 and now I can oc at 1460 no problem. Just thought I'd share in case anyone else had the same problems. Its funny, I had tried raising the voltage several times to see if that would solve it, and it of course didn't, and then just for the hell of it I tried lowering the voltage and surprise! Anyway, hope this info can help someone else if they have the same problems I did☺
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] gu5t3r:
Is latest version --> Dhollmen_Kernel-P51xx_20140412.zip compatible with official cm-10.1.3-p5100 ?

Thanks in advance...
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] CSP III:
Nope. Read post 1 towards the middle. You'll find link for CM 10.1 Roms
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] LelodasTshirts:
I'm also facing this camera issue on my 5100.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] John_Br:
You could try this? http://xdaforums.com/showpost.php?p=53238636&postcount=2882

Grtz,

John
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] LelodasTshirts:
Hi John.

I'm on Slimkat. This is for CM11 only or can i try it?

EDIT: Tried this fix, but didn't work. Still impossible to connect with the camera.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
:

Time will tell us if it is, but in principle, the camera is break for all 4.4.3 Roms.

Specifically in CM, on last 4th they updated repo, and the new code deleted references to a function from Samsung camera's code.

Because we can not recompile that module, the framework must will fixed for tab2 use 4.4.3.

EDIT:

Camera's module patch suggested, changing EXIF tag by HEAD tag, seems work well.

Tested on the latest CM-11 it works, once link is made form libjhead.so to libhead.so.

Therefore, this workaround is sufficient, I think, to reset proper camera's operation.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
See my previous post, please.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
.

New maintenance release 2014 06 10 uploaded.

:good:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] CSP III:
Welcome back Tux!!!! May I flash this within the Dhollmen Rom from 20140328. Or would it not matter??? And again welcome friend, its been too long. Hope you are well.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] fredy66:
Undervolting

Hi Tuxafgmur,

first thank you for your work!

I have a technical question about the undervolting in your kernel.

Like you know every cpu is unique, and there are some cpu´s which needs higher voltage to run stable.

Is it not dangerous to reduce the voltages of the mpu, because some cpu´s can also have undetected errors? That means the tablet works and does not reboot, but some datas are written wrong for excample.

For a user it´s very hard to detect such an error directly.

I´m using your kernel since 3 weeks, because this is the only one without battery drain. :good:

I do not overclock my tablet, that means my cpu is running with 1080MHz and the gpu with 307MHz.

In your new maintenance release you have reduced some voltages a little bit. Like i can see also for 1080MHz.

Is there a possibility to check the cpu reliable during undervolting?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
You can use Antutu's stability test. :)

Really I don't know until we can undervolt. :angel:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
You can if you like.

I'm well . I have been working hard. Next days I will upload new Stock Kernel, new Stock Rom and Mega-Update of Dhollmen Rom.

Best regards my friend. :)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
Hey tux, great to see you back here and looking forward to your new rom☺!

I am having some problems with your new kernel, I am not able to get past the Samsung splash screen. I have tried flashing the kernel on Markos cm and slim kat 5.8, I tried with clean installs as well as already installed versions, it just won't boot. I even tried with flashing without wiping cache and flashing your old 4.4 fix just so i could honestly say that i have tried EVERYTHING, I think my tab is very sensitive ?.

Any advice or suggestions? Anyone else having problems?

I realize now that I haven't tried it with 4.4.2 ROMs, just 4.4.3 so I will try that next. Will update with results.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] CSP III:
And to you as well, friend. Take time, ROM is great as is now.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] nachordez:
Great news!

Anyway, last Dhollmen rom is still making my tab behave much better than never ever before so, as CSP III said... No need to rush!

from Nexus 4
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] fredy66:
Thanks Tux!:good:

Is it possible to set the voltages for non overclock frequencies (300 to 1080 MHz) to default TI values by a switch, so user can decide to undervolt or not. I think for some "bad" OMAP this would be a good solution.

That means poweruser can overclock and undervolt and normal user who don´t want overclocking have a extrem stable and safe kernel.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
Same result with 4.4.2. Anyone have this problem or ideas?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] John_Br:
Hi Shepguessed,

I've got exactly the same on my P5110 with Slimkat 4.4.2 build 5.6 weekly 4544. Keep stuck on the splash screen. Went back to the previous kernel and all is working well.

Grtz,

John
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
Okay, that makes me feel better! Good to know its not just me. Thanks john.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] shakatu:
Omni ROM doesn't boot either. Previous kernel seems to be fine with Omni 4.4.3 it's booting at least so far...
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Just tried it with CM 2014.06.08 only.

I hope to install another Rom for the day and check. :p

EDIT: I think, must upload an install file without blobs.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Markox89:
Welcome back [MENTION=5117218]tuxafgmur[/MENTION] :)

Just built my ROM with your latest kernel release, everything is fine : highfive:

Only issue, Camera is still broken despite the changelog, I still have to install modified vendor-camera.piranha library to make it work :)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
.

No [MENTION=1597520]Markox89[/MENTION]. As I said before, camera lib patched work well, but it need a link:

ln -s ./libjhead.so /system/lib/libhead.so

You must recode your /DATA/META-INF/com/google/android/updater-script to add this line or so:

symlink("./libjhead.so", "/system/lib/libhead.so");

But this is a Rom problem, not a Kernel issue. :rolleyes:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] vgpclife:
How to increase speaker volume?

I don't know if this setting is related to the kernel or the ROM but I thought I'd ask here first. Is there a way to increase the speaker volume on the Galaxy Tab 2? Any help would be appreciated. Everything I've found with my Google searches don't seem to be related (files referenced are missing) or don't work. THANKS!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Kernel can nothing do here. This is a Rom issue.

Dhollmen ROM have high increase volume and quality level. :good:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
.

New maintenance release 2014 06 12 uploaded.

New installation file does not includes blobs, as in some Rom can cause side effects.

If your Rom have problems after installing the kernel you must install the new blobs.

Those running on 10th release, no need to reinstall.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Badwater55:
Battery drain fix (P5110) still valid with this maintenance update?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Konsumhaus:
Slimkat weekly 5.8 boot either with dholmen Kernel 2014 06 12 :(

Gesendet von meinem GT-P5110 mit Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
Sorry to say still can't boot any ROM with new kernel with or without blobs. Tried everything, literally.?

Its strange because Markos new cm has yesterdays kernel but still doesn't boot with oc kernel.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] spiderman1961:
+1

Inviato dal mio unknown utilizzando Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] fredy66:
Hi Shepguessed,

how did you change the voltage?

I have fc with 1460 too. (2014.04.12 Dhollmen kernel)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Of course :good:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
I wrote a simple initd script. Copy this text into new file named 99cpuvoltage or whatever you like.

#!/system/bin/sh

echo "1410 1395 1345 1305 1275 1215 1100 925 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

(That should only be two lines, I don't know how to post code on tapatalk. All that echo stuff should be on the same line)

Then put the file into /etc/init.d

Change the permissions to rwxr-xr-x reboot and it should work.

There are also many apps that can do it for you, android tuner in the CPU voltage gives you the ability to change voltages and save the changes and implement them with init scripts, but I prefer to just to write it myself so I don't have to run an app just to run a script. You can also use trickster app. It may be a good idea to change the voltage with the app first to see that your tab runs well at that voltage before you write the file. Also, nandroid backup is a good idea just in case you get a bootloop. When you are testing make sure that your performance settings are NOT set to set on boot, so if you get a forced reboot you will not get a bootloop.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
I have download SlinKat 5.8. The Rom not boot with my kernel.

Now I have make a new slim boot image with my kernel and then boot an work well.

Is not a kernel issue. Only an init script problem.

I'm investigating
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
New release 2014.06.13 uploaded.

ATENTION: Previous kernel 20140612 has been deleted, as replaced by current release.

:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Expanding the [MENTION=5212831]Shepguessed[/MENTION]' s explanation, next script do the trick.

As he says, you can include into /system/etc/init.d and give it 0755 permissions.

#!/system/bin/sh
# Tuxafgmur-Dhollmen

# Select values: 0 = Do nothing
# 1 = Execute

I_NO_WANT_OVERCLOCK=0
I_NO_WANT_UNDERVOLT=0

I_WANT_CHANGE_VOLTAGE=0

# If you set I_WANT_CHANGE_VOLTAGE to value 1
# for frequencies 1460 1420 1360 1216 1008 800 600 300
# replace standard values with your desired values

I_WANT_THIS_VOLTAGE="1410 1395 1300 1375 1374 1313 1200 1025"

########### DO NOT CHANGE NOTHING BELLOW THIS LINE ################

if [ $I_NO_WANT_OVERCLOCK = 1 ]; then
echo 1008000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
fi

if [ $I_NO_WANT_UNDERVOLT = 1 ]; then
echo "1410 1395 1300 1375 1374 1313 1200 1025" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
fi

if [ $I_WANT_CHANGE_VOLTAGE = 1 ]; then
echo $I_WANT_THIS_VOLTAGE > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
fi
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
Oh yeah! Running great! Thank you☺
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] nachordez:
Nice workaround! :good;

from Nexus 4
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] shakatu:
Newest kernel boots Omni ROM 4.4.3! Good job!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] BlackRenegade:
Same here, same ROM. currently using NEXT kernel till fixed.

Sent from my GT-P5113 with XDA Premium HD app
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
The newest kernel from 0613 works with both Markos latest cm and slimkat 5.8, I have been using both all day.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Markox89:
[MENTION=5117218]tuxafgmur[/MENTION], don't be mad at me please :D :angel:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Heavens!

What have I done? or .... .... what have you done? :o
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
For anyone having camera problems with 4.4.3 ROMs, the newest release of dhollman kernel 0613 has solved it. Camera front and back working good for me on p5113.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Markox89:
I was just feeling sorry for reports coming from my users :)
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] WDCdafbe:
Where can i find the New kernel Form 13/06/2014?

Gesendet von meinem GT-P5100 mit Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Badwater55:
... as always: spy into first post of this thread :thumbup:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Hey [MENTION=5117218]tuxafgmur[/MENTION] ! Here meight be a better way to fix camera on 4.4.3

https://gerrit.slimroms.net/#/c/9126/

I can not test myself ATM.

Gesendet von meinem GT-I8190 mit Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] dimirass:
Ι have slimkat 5.8 +0613 dholmen kernel but I dont see camera app! Which is the trick?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
I don't know. This is a Rom issue.

To test, I had to download a camera application from Google Play. :(
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Flash the blobs....

Gesendet von meinem GT-I8190 mit Tapatalk

Edit:

1.: Camera in Android 4.4.3 fixed in Kernel in weekly SlimKat 5.9, same in all other Roms now.

Hacked blob did the trick on weekly 5.8 or patched kernel (tux needs to add https://gerrit.omnirom.org/#/c/8025/1/rootdir/init.espresso10.rc )

but to use dhollmenkernel also needs 2.

2.: same issue (camera not working / missing) On SlimKat because of custom kernel, SlimKat kernel uses different blobs.

Flashing the correct blobs for dhollmen kernel fixes it. NEXT kernel always provides the right blobs to use.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
[MENTION=5153662]Android-Andi[/MENTION]

Next provides the right blobs to use.

Well

Why Rom?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
Rom?

Gesendet von meinem GT-I8190 mit Tapatalk

Edit:

I See, you also provides blobs now :)

Dhollmen_Blobs-P51xx_20140612.zip
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Yes

I ask if all AOSP ROMS use the same (right) NEXT blobs.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
ATM slim is the only one using different blobs, also my CM builds on stable branch.

Battery-drain seems to be still not fixed on CM and other Roms, only solution is to revert JB Update 1 on kernel, but then no new blobs working - you know about that bad Situation... :(

I patched SlimKernel up to 3.0.101 without JB Update 1.

Also, i don't ubderstand wich of the updates from Samsung opensource is the latest one :p the differents really funny between those :p

About your provided blobs: Contains hacked camera blob? Fixing in init.espresso10.rc much better solution.

Gesendet von meinem GT-I8190 mit Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Blobs not includes hack.

I never liked PRELOAD, because it can be a source of unexpected problems. Even less when a simple link will do the job.

However, think about it.

:good:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
You included tsjoklats fix, right? He made a flashable ZIP from my hacked camera blob :p

The symlink from libhead to libjhead is the 2nd part from that fix :p

https://github.com/andi34/proprietary_galaxy_tab2/commit/32b8f18b4fc280bed7a3ab54f6d2eecb69d5b8a4

Gesendet von meinem GT-I8190 mit Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Yes, this file and link is in Kernel install. This run in 4.4.2 & 4.4.3

When my Rom has the problem, I'll see what I do.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Android-Andi:
No Problem, your choice ;)

All 4.4.3 Roms for Tab 2 had this issue.

- First solution was hacked blob + symlink

- Second solution to patch libexif source (used on Omni, but got reverted now, reference: https://gerrit.omnirom.org/7899 and https://gerrit.omnirom.org/7884 )

- Third solution, fix on all Roms now, to add mentioned commit for init.espresso10.rc

Gesendet von meinem GT-I8190 mit Tapatalk
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] dweller417:
Update

Can we have also an update for the P31XX?
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Sure !

next days :good:
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] vcdwelt:
Hi, since one oft your last updates my p5110 reboots sporatic. Looks Like you lowered the voltage a bit too much :) think it was since the 10.06. Update. Did not have the time to test Mord the last days. But after flashing the default CM11 kernel Problem is gone. Im running the latest CM11 nightly
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Maybe you can try this app:

https://play.google.com/store/apps/details?id=com.darekxan.voltagecontrol

You can test with different voltages to confirm some issue.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] vcdwelt:
Maybe you could send me or post the configured Voltages (old/new) as an orientation for me.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] tuxafgmur:
Not problem here. This app show your actual voltages.

You must not upload more than one/two points. (You could even go up three or four more)

Still I can't think that voltage is your problem. There are much more one thousand tablets working with them.
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
Just thought I would share this. Running dhollman kernel 1306 with slimkat 6. Oc'd CPU 1460 and oc gpu 512 with lutzactive and row. Pretty amazing huh? And the best part is everything is super stable and temperatures are good.

Thanks again tux, this is as good as it gets!!!!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] CSP III:
Shocking, to say the least Maybe I'll give it a go on my #3 Tab, Slim 6 ROM. Are or did you flash the blobs with that as well???
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] Shepguessed:
Yep, flashed them with the kernel. I know, it was an amazing score, but what else can you expect when you mix a little andi with a little tux!
[Galaxy Tab 2 (Unified 7" + 10.1") Android Developm] CSP III:
Thanks man. Was thinking the same thing. Good guys, great Devs. ☺