yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] locerra:
Just as an FYI, increasing the steps on the autobrightness won't do anything. We are still using a binary sensor hal (because we have signficantly different sensors from all other exynos4 devices), which only reports a stupidly tiny number of distinct ambient light values. The number of steps for autobrightness I included in CM9, CM10, and CM10.1 is the maximum number of steps that you can use with the binary hal, if you use any more then some steps will just be skipped (I'm pretty sure that the hal reports the lum values of 0, 7, 70, 700, 7000, 16000 or 0, 13, 130, 1300, 13000, 16000, depending on whether it is the 3.2 or the 4.0 binary).

Also, autobrightness on the i815 is borked until I (or someone else) can figure out why the kernel fails to start up the ambient light sensor on that device.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Thanks!

Really good to hear from you!

I'm new to this, really need your help once a while...

Hoping you are having great time at school.
[Galaxy Tab 7.7 Android Development] carlo67:
ok

I flashed CWM back on and restored cm9 ok than flashed TWRP back on ok I made a backup of cm9 with TWRP ok

I flashed pa2.55 without wipe nothing ok but the pa is stuck on [fist screen of pa ] for 15 minutes and still stuck
[Galaxy Tab 7.7 Android Development] keewee23:
can my now completely dead p6810 tablet be fixed with riff jtag? emmc, data partitions? now it does not show battery charging, no download mode anymore, no clockwork, nothing, pc wont recognize tablet anymore, it's completely dead :crying:
[Galaxy Tab 7.7 Android Development] long6688:
Flashed latest 10.1, heavy battery drain, 10% in 10 minutes using, maybe wipe battery stats?
[Galaxy Tab 7.7 Android Development] daniel_hk:
Continuously flashing may corrupt the bootloader...

RIFF JTAB can probably bring download mode back but if the eMMC has bad blocks, seems the only way is to replace it....:(

The one I'm fixing now have the same situation. I got download mode back with JTAB but still can't recover the bad blocks. I'll give the last shot tomorrow. If it is not running stable, the eMMC chips need replacement...
[Galaxy Tab 7.7 Android Development] maxfas:
Bye.

I'm from Italy.

I don't understud how can do to install this Rom Jelly Bean based.

Can you explane step by step how do?

thank you
[Galaxy Tab 7.7 Android Development] long6688:
Sorry for this updated info. Battery and everything is fine, devices charged full but actually not, only at 81%, maybe put a notice to wipe battery stats?
[Galaxy Tab 7.7 Android Development] Steve_max:
Samsung repair center is the only alternative. You MIGHT (emphasis on "MIGHT") be able to get it to work, barely, using an internal <--> SD remapping, but if your device is at the point where nothing works, I guess the repair center is the only alternative.

AFAIK, the repair is, or at least used to be, free. Not sure if your warranty ran out, though. It's a Samsung screwup; just say it crashed when you were updating through Kies or resetting to factory: if you can't get to download mode, they can't see your binary counter.

Some might say this is unethical, but this is a HARDWARE failure. The fact that you used non-Samsung SOFTWARE didn't cause the problem, so Samsung should fix it.
[Galaxy Tab 7.7 Android Development] keewee23:
i now did send email to samsung and to local samsung service partners here, i explained the problem, completely dead tablet, no react on any button, nothing on screen. I dont have warranty, maybe that will be the problem, will wait for answer from them.
[Galaxy Tab 7.7 Android Development] long6688:
Hey daniel did u implement pie control in latest cm? I seems cant trigger it
[Galaxy Tab 7.7 Android Development] d0shu:
2 problems with new cm, brightness sensor (hahahah) and CPU locked to 1200 initially.. It is also bit sluggish after installing v6 and pimp my ROM.. Also pie cannot be enabled. Battery life is much better!

Going to try paranoid android now.. Great job with kernel!

Edit* i815... Hence the brightness sensor..
[Galaxy Tab 7.7 Android Development] edan1979:
hmmm can you guys state what device you use... unless for some who reply using tapatalk and did no tcustom it... can see the device...

i dont have any of the problem you guys state... cpu is on 1400 as normal... i oc to 1600... brightness on auto working fine... and also pie control is ok...
[Galaxy Tab 7.7 Android Development] long6688:
How did u get pie control? I checked it in settings but can get it to open :(
[Galaxy Tab 7.7 Android Development] edan1979:
it might be because i reinstall the pie control again... i got some software that i usually use and pie control is among that... so i got one zip that contain all my usually use sotfware... flash after regular firmware.
[Galaxy Tab 7.7 Android Development] baustoff:
Same Problem Here...by activating pie control and extended desktop, the pie control won't open. Could you be so Kind and upload flashable ZIP oft pie control Software please?

Thank you in advance.

Kind regards,

baustoff
[Galaxy Tab 7.7 Android Development] edan1979:
i'm just kind of lazy... its here somewhere in the application dev forum...
[Galaxy Tab 7.7 Android Development] Edwrib:
Anything from official JB released for P6800 was useful to help CM?
[Galaxy Tab 7.7 Android Development] jimmbomb:
And just when and where was./. is the Official JB release for the P6800?
[Galaxy Tab 7.7 Android Development] edan1979:
errrr... its on several page...

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

http://xdaforums.com/showthread.php?t=2128160
[Galaxy Tab 7.7 Android Development] jimmbomb:
Well... I'll be dammed. Thanks Edan...

I haven't been looking lately.

Daniel_hk has my tab 6800

And is trying to get it working for me,

I haven't checked in a few days...

JB finally! nice to hear it
[Galaxy Tab 7.7 Android Development] sergani:
Hi Daniel, is this the definition of sleep of death? My Tab used to behave this way all the time, even before CM10.1. Sometimes with airplane mode on as well....
[Galaxy Tab 7.7 Android Development] daniel_hk:
What type of dead?

Just wifi broken or totally black and has to press power button to force boot?

If not just wifi, then it may help a bit.

The wakelock fix can avoid packet wakeups but p2p data transfer wakelocks (BT or large file downloading) are handled in different way. Need some time to study why.
[Galaxy Tab 7.7 Android Development] sergani:
Thanks Daniel. No, total dead. I need to force reboot...

I always read it's because of the processor, so I'm not sure if the new official JB will help. Our if anything can be done to CM to help.

I lost hope :D
[Galaxy Tab 7.7 Android Development] daniel_hk:
Well, I don't have this kind of dead at stock and cm10, pa2. I think this wifi issue came when CM update the kernel.

May be you need a super wipe to clear your eMMC.

Good luck!
[Galaxy Tab 7.7 Android Development] sergani:
I'm sorry, what is that? :)

Any steps/guides to read and/or follow?

Edit: excuse my laziness :) already did a search for super wipes.. however, if you'd be kind enough, i'm interested in knowing how this could solve SODs.
[Galaxy Tab 7.7 Android Development] daniel_hk:
First of all, I don't have this issue in stock ICS, cm10 and pa2.55. It is probably not rom related. There may be some bad block which will cause hang/reboot when being accessed. A super wipe will reformat every partitions which may not needed but simplier.

Or you can do it one by one. I assume you have try factory reset (which will format /cache but just delete the files in /data). That means /cache is ok. /data is most likely the next move. Format the /data partition will erase everything in internal sd too.

Back up your data and efs first if you like to try super wipe.

This may not work for you but is the only thing you can try.

Good luck!
[Galaxy Tab 7.7 Android Development] Sab3elbromba:
Daniel I owe you a big thank you, this latest version of CM10.1 it's almost perfect, I'm loving the response time almost no lag or major bugs. I'm tempted to try the new halo PA but I'm afraid to lose the goodness I described in the CM version, can anyone explain the response in the latest PA?

Just the WiFi tethering that I deeply missin both versions :( any chance of getting that to work?
[Galaxy Tab 7.7 Android Development] daniel_hk:
Don't know how tethering work yet but will try later. :)
[Galaxy Tab 7.7 Android Development] sergani:
Thanks for the pointers :)

I checked my dmesg output and found no bad blocks (i got this method while searching online for superwipe etc..) .. I'm not sure what the problem is, but so far i haven't had any SODs since the 07/05 CM10.1 version.

Will keep a look out.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Most of the kernel errors may not be shown in dmesg. It depends on the level of debug set inside the kernel at build. For a working kernel, no one will allow a lot of debug info. which will slow down the kernel.

Anyway, if you are good now, just sit back and enjoy. ;)
[Galaxy Tab 7.7 Android Development] sergani:
:$ clumsy me!

Yeah, will sit back and relax :)
[Galaxy Tab 7.7 Android Development] jkrell:
Why not just do a backup and try out PA 3.5? I'm curious to see which you like better.

Does CM10.1 have Phablet layout? Are you stuck with it?

Also, how is the battery life in 10.1? PA 3.5 still has the battery drain issue with WiFi.
[Galaxy Tab 7.7 Android Development] edan1979:
its basically the same thing... PA is made base from 10.1... PA has additional ingredient... :P
[Galaxy Tab 7.7 Android Development] Edwrib:
A small thing, not a big deal, but making incompatible with some backup manager apps:

CWM backup folder is going to /data/media/clockworkmod, should be /data/media/0/clockworkmod.
[Galaxy Tab 7.7 Android Development] daniel_hk:
What version is your CWM? 6.0.2.x or above should work.
[Galaxy Tab 7.7 Android Development] gvoima:
Flashed the newest 5/7 build. Awesome work! Rom works great, and even the avrcp metadata over bluetooth. But the avrcp playback doesn't. Any idea how it could be enabled?
[Galaxy Tab 7.7 Android Development] Edwrib:
CWM 6.0.3.0.
[Galaxy Tab 7.7 Android Development] daniel_hk:
Thanks, let me check it when updating the CWM. (probably next version. CWM6.0.3.2 is out but haven't check the backup issue in 6.0.3.1 yet)
[Galaxy Tab 7.7 Android Development] LSD DREAMER:
I find that in the last build wifi keeps dropping. I didn't have that problem in the previous build. I love the smoothness of the rom . Thanks lot to the developer
[Galaxy Tab 7.7 Android Development] gvoima:
So far, no drops for me.
[Galaxy Tab 7.7 Android Development] LSD DREAMER:
Lucky u had 10 drops today and it's not my D-link router
[Galaxy Tab 7.7 Android Development] daniel_hk:
Would you check the Wifi settings' advanced menu?

See if the "Wi-Fi optimization" is check.

Settings > Wi-Fi > (top right button) > advanced > Wi-Fi optimization
[Galaxy Tab 7.7 Android Development] LSD DREAMER:
No wifi optimization is not checked should I check it
[Galaxy Tab 7.7 Android Development] daniel_hk:
Yeah, check it will optimize the power of wifi. Connection will be better.
[Galaxy Tab 7.7 Android Development] GNUDroid:
Hi Daniel, just some news for you:

There is an new Mali GPU driver available for the Maili-400: r3p2-01rel1.

The people from i9100 dorimanx kernel forum, are still discussing, if implementation can be done. Dori ready took a fist look into the new sources and suggested that new HW-libs in the roms are necessary. For the i9100 not (yet?) available. The discussion is fresh, so investigations can change quickly. But maybe they will be able to port fully or backport some improvements to the the kernel.

I'll loosely follow the discussion and in case, dori and the other devs find a way to profit from that, I can give you a hint. - Or you simply follow from time by time on your own.

Best regards,

GNUDroid

btw: after 3 attempts of an broken download of the 7/5/13 build, I temporary switched from your cm10.1 builds to your PA 3.50. I always avoided Pa, because it felt less responsive, but there had been a huge progress. I would suggest nearly as good as cm10.1. - Without your work, I would have regret to buy my 6810, but with your work, you made it to my loved tab! :)

"...But the latest driver from Mali is r3p2-01rel1.

http://malideveloper.arm.com/develop...evice-drivers/

SO although the latest Mali drivers haven't set up for the i9100 by Samsung yet, would it be possible to merge some of the code from the raw drivers and see if they fix any of the problems?"

http://xdaforums.com/showthread.php?t=1617219&page=2374

"any way! when CM/AOKP will move forward, i will be ready!

i will put the patch aside for now... and drain from it all the can be good for us now without ROM code changes!

rom code and mali source are here!

http://malideveloper.arm.com/develop...evice-drivers/"

" Originally Posted by bluefa1con View Post

codeworkx said in the past that to update the mali drivers they need some proprietary libraries that samsung drops once in a while in official roms I already posted about the drivers in the cm thread, i guess it won't be useful."
[Galaxy Tab 7.7 Android Development] daniel_hk:
Thanks for you tips. That may be the one from note8. I'll take a look later.

I'm uploading all the roms to goo.im now. Don't know if the source or anything went wrong that you can't flash the latest (7/5) cm10.1 build. Please try downloading the one in goo.im. If this one still not work, I might have to rebuild the cm10.1 for p6810 again.

I had studied the kernel source of siyah and Dori too. Our wifi driver (ath6k) in both are outdated since these roms are for i9100. I don't know how the 400MHz GPU being tested in i9100. I'll include the source to the kernel in the next build. Hoping the tools for i9100 work for us too.

By the way, which are the most common tools for setting the GPU in i9100? "voltage control" is not working on our tab yet (GPU settings not shown).

Daniel
[Galaxy Tab 7.7 Android Development] lomniom:
Finally i can download directly from my tablet! Goo.im is excellent choice Daniel. :highfive:
[Galaxy Tab 7.7 Android Development] lomniom:
Try http://goo.im/devs/daniel_hk/rom
[Galaxy Tab 7.7 Android Development] Steve_max:
AFAIK, the 4210/4212 SoCs implements a ASV system. This means that each individual chip has slightly different default voltages both for the CPU and for the GPU parts, depending on its "level" (meaning, how far it couls be pushed in voltages). So, forcing the same standard voltages will make some devices unstable (the lower ASV/"worse" chips) and some devices use more power than they should (the higher ASV/"better" chips).

A quick search yields http://lists.infradead.org/pipermail/linux-arm-kernel/2011-October/070625.html

AndreiLux's kernel for the Galaxy S3 (Exynos 4412) was my source for this, https://github.com/AndreiLux/Perseus-S3/blob/master/arch/arm/mach-exynos/cpufreq-4x12.c (no idea where to find the GPU values, though)
[Galaxy Tab 7.7 Android Development] GNUDroid:
Yep, it is like CPUs in our PCs: Nevertheless they should have the same processor, one person can undervolt and at the same time overclock, the other can overclock and the next can't do anything.

The Dormimanx community is HUGE (nobody has an Tab, but millions have a S2), he and the other devs adjusted a lot of to find conservative values, who match 99,9% of the users hardware, so they are good evaluated values to start with. - Had luck, because I can UV my CPU a lot 50 mV for all freqenciws < 800 MHz. GPU: I have the described lag experiences, so I do not touch them.

Attached you find my backup of my current kernel-settings. Many parameters, which are adjustable by stweaks can be found in this 'normal' profile.
[Galaxy Tab 7.7 Android Development] Steve_max:
I don't think you understood my point...

The point is exactly that we DON'T have the same processors. We have processors made in a theoretically identical setting, by theoretically identical machines using not-even-theoretically-equal silicon.

Each processor is unique. This is why some people can undervolt and underclock a lot, while others run barely stable at near-stock settings. This is why Samsung did something smart with their chips. They test them, and put each of them in a certain "stability level" (or ASV). The default voltages for all chips on a given ASV are the same, but that set of voltages is different for each ASV. This means that you DON'T need a set of voltages that work fine for 99.9% of all the people: you can have a default set of voltages for the 5% who got awesome chips, another for the next 5%, another for the next 10%, and so on. This means everybody can get a more efficient set of voltages for everything (CPU, GPU, buses, RAM, body, etc) without sacrificing stability for anyone, even the 0.1% worst chips.

I think I remember you from the SGS2 community some time ago, so you'll probably recognize AndreiLux (the guy who physically measured the voltages on every single component of the board, to help Gokhanmoral with his kernel back on the GB days. He is the guy who developed the Perseus kernel for the S3 (and Note2), whose github I quoted. I'm not entirely sure if it applies to the Tab, though: for some reason I though the 4210 was only for the SGS2, while the Note and the P68x0 had the 4212. If the 4210 does have something similar marked on the firmware, the kernel can get more efficient by using it to separate the chips on different categories and therefore increasing efficiency for all.

Even if there is no ASV on the chips, you must remember that we have a different revision of the 4210 than the SGS2 (as the different default frequencies will tell you) and fewer thermal problems (the large area of the tablet + metal helps a lot), so whatever works best for the SGS2 will probably be under-optimal for the P68x0.
[Galaxy Tab 7.7 Android Development] sbalu:
Is there going to be any development on Paranoid Android for P6810, Daniel?
[Galaxy Tab 7.7 Android Development] daniel_hk:
already done in my PA thread for a long time...:p

Latest version is pa 3.50
[Galaxy Tab 7.7 Android Development] sbalu:
I've been using ParanoidAndroid 2.55cm (4.1.2) latest 2013 january version for a while.Do you suggest me to change for this pa 3.50 version?
[Galaxy Tab 7.7 Android Development] daniel_hk:
I've been using it all the time. I think at least you have to try it. PA3 has GPS issue. If you need gps, cm10.1 is the better choice.

With a recovery backup. There is no risk at all.

Good luck!
[Galaxy Tab 7.7 Android Development] sbalu:
I need GPS, than I stay at this rom as long as it will be repaired.Thanx!
[Galaxy Tab 7.7 Android Development] sas_sas:
Tried the both already.

The both have very good response..

CM10.1 has only phone UI and the rest is super...

PA3.5 is also verygood but has battery drain and GPS issue..

Plus there are HDMI complains from the both thoug it is not my own observation and care..

If you do not complain its speed and responsiveness of PA2.55 14.01 built, better stay with it till those troubles are resolved..
[Galaxy Tab 7.7 Android Development] sbalu:
Thank you very much for your informations!I stay on PA2.55 cm.
[Galaxy Tab 7.7 Android Development] d0shu:
Actually with ROM toolbox you can edit the build.prop / ro.sf.lcd_density field to 160 or 193 for tablet and phablet modes respectively without any problems under cm10.1.. Just make sure you download all your apps from play store before doing so as it might not let you download say an app like script manager for compatibility reasons even though the app works fine..

You can however avoid that as well by doing a factory reset, cache and dalvik wipe, install cm10.1 .. This keeps build.prop and/system intact so your fresh install starts up and boots with DPI you selected thus play store doesn't cause any problems..

Cheers for adding goo.im Daniel
[Galaxy Tab 7.7 Android Development] sas_sas:
Ths for your very helpful guideness.

You meant that modifiying the DPI to 160 turns it to Tablet and 193 to Phablet UI respectively..

I knew it How to modify DPI but I can not know how to place the both Nav soft buttons and Notifications in the same location meaning at bottom bar..

Are you sure when I make your way I will have bottom bar with both nav buttons and notification and no status bar at top...??

Playstore is not my trouble any more. I do resolve the possible DPI mismatch troubles by installing multi DPI playStore anyway...
[Galaxy Tab 7.7 Android Development] sbalu:
Thank you!Very usefull information, though I prefer status bar on the top on my tablet!
[Galaxy Tab 7.7 Android Development] d0shu:
I asked the same question myself, only paranoid android allows that, apparently android stopped that ui with jelly bean.. I quite like that as well.. I use PIE now because screen space is important to me.. The change is hard to get used to but it is awesome once u do..

---------- Post added at 02:57 PM ---------- Previous post was at 02:54 PM ----------

I wanted to answer this in a different reply to avoid confusion.. When you are using CM and you change your DPI to say 160 in short to tablet ui, your navigation bar remains in the bottom while status/notification bar remains on top.. Only difference now between tablet, phablet and phone ui with jelly bean apparently is DPI.. Everything else remains same..
[Galaxy Tab 7.7 Android Development] sbalu:
Yes right, understood.Compairing CM and Pararanoid Android, which do you prefer?Thanx again!
[Galaxy Tab 7.7 Android Development] daniel_hk:
I just uploaded a test kernel to fix this. Please test it. Thanks
[Galaxy Tab 7.7 Android Development] Sab3elbromba:
I've downloaded the new kernel then cleared cache and dalvik cache and installed the Kernel

WiFi is working and connected

I will monitor for battery drain and SOD and report back

Thanks Daniel

P.S. I'm running the latest CM10.1
[Galaxy Tab 7.7 Android Development] pemmoura:
Hello Daniel,

do you think there will be any advance in the GPU area (mainly vsync) with the release of the official JB?

I flashed the official ROM, but i'm missing the good "stockness" of CM.

Thanks for the works!
[Galaxy Tab 7.7 Android Development] daniel_hk:
Apps like Pimp my Rom has option to disable Vsync. I use it for sometime now.

The stock JB rom still use the old graphic driver. We are using a newer driver from note8 and I'm working on a higher GPU clock kernel now.
[Galaxy Tab 7.7 Android Development] swissd8:
I tried the latest kernel, without success to fix the frozen tab when torrenting, still the same after a couple minutes if not charging..

Haven't had a wifi signal drop yet so this seems better, I usually have to disable/enable wifi a few times a day.
[Galaxy Tab 7.7 Android Development] daniel_hk:
That means the driver still has other bugs...:(

keep on trying...:cyclops:
[Galaxy Tab 7.7 Android Development] Sab3elbromba:
I've Breen using the new kernel for about 8 hours now and I haven't had a single SOD yet which is good, the boot so good is the power consumptionit is much worse than before, see attached screen shot.
[Galaxy Tab 7.7 Android Development] Sab3elbromba:
Daniel can you please post the original kernel so I can flash it back? This new kernel battery drain is too much.
[Galaxy Tab 7.7 Android Development] daniel_hk:
I don't know why your battery drain. I'm using it for 15hrs. now and I still have 64%. Wifi is always ON and use it all the time to test.

The only thing I changed was wow_ routines which only call at sleep when there is heavy wifi activity. It was modified from the wifi chip manufacturer's latest driver.

If you want to have the old kernel back, flash the previous rom and gapps again. You don't need to wipe and may take a few minutes longer.

I'll release a new cm10.1 in a few hours...
[Galaxy Tab 7.7 Android Development] gvoima:
I don't have any drain with the 5/7 release. Did a full wipe and use my tab mostly for web and youtube videos (80% video, about). And my screen on time is nearly 5h and wifi is always on. Standby time is over 4 days and i'm at 17% battery.

Screen brightness is on auto.