yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 7.7 Android Development] Androguide.fr:
REQUEST

I need one (or more) dedicated testers to help me

trying

to port Paranoid Android.

What I mean by dedicated is :

- Obviously be willing to flash builds that are likely not to work

- Being available on gtalk

- Having free time : I can work on this from about 11am to 11pm (gmt+1 brussels time)

- Having basic knowledge about how to flash a rom and use logcat

- If possible, having already tried a Paranoid Android rom (on any device).

I am willing to begin tomorrow if I got testers by then.

Please pm me with your model, the schedule of when you're free and your google talk email

I'm counting on you guys to help me out on this one.
[Galaxy Tab 7.7 Android Development] iOStoAndroid:
Not sure what's going on ...

flashed v1.3 from stock(rooted)

stuck in bootloop, unable to get into recovery ...

(oh is the boot animation supposed to be in landscape?)

please help
[Galaxy Tab 7.7 Android Development] lsherif:
1. have you wiped data, cache & dalvik before installing V1.3 ?
[Galaxy Tab 7.7 Android Development] iOStoAndroid:
yep wiped twice (factory reset before going into revovery too)
[Galaxy Tab 7.7 Android Development] lsherif:
try re-installing CWM again through odin & do a data wipe once more.
[Galaxy Tab 7.7 Android Development] iOStoAndroid:
having to reflash firmware via ODIN na d will restart?

is the boot animation in landscape (original is in portrait)
[Galaxy Tab 7.7 Android Development] LBN1:
Testing p6810

Testing on my p6810, so far so good. Wi-fi connected without issue at first, rom is smooth. Did have one Wi-fi disconnect and some difficulty reconnecting, had to manually turn it off and on

Ran V6 supercharger. Seems since it is baked into rom, it will only report 50% supercharge.

LCD screen density at 213 does not look good IMO. Changed in build.prop to 196 which is the actual pixel density for our 7.7, and it looks much better for me at least.

Thanks for the development, please keep it up.
[Galaxy Tab 7.7 Android Development] adinis78:
Installed with no problems except with the playback of videos someone needs to fix the codecs.
[Galaxy Tab 7.7 Android Development] iOStoAndroid:
how long does it take to boot?
[Galaxy Tab 7.7 Android Development] Maverick777:
Another 6810 user here. Upgraded from 1.2 to 1.3 no problem. Installed V6 Supercharger and can confirm it reads 50% which according to previous posts is normal I suppose.

So far no issues. Thanks for the update and for continuing to update the rom. You've done a great job and provided a great service to all Tab 7.7 owners. :D

---------- Post added at 06:18 PM ---------- Previous post was at 06:15 PM ----------

Try BSPlayer.
[Galaxy Tab 7.7 Android Development] adinis78:
I did on loceras CM10 and same issue
[Galaxy Tab 7.7 Android Development] iOStoAndroid:
Awesome

finally got it to work

Thanks
[Galaxy Tab 7.7 Android Development] wintermute000:
Has anyone tried DPI other than 213 or 160 successfully?

I want to get rid of phone UI but ideally I want DPI around 213 mark as I find it perfect. 160 would be far too fischer price big.

I tried 215 but that broke soft buttons
[Galaxy Tab 7.7 Android Development] Maverick777:
196 works, but it's still the hybrid phone UI.
[Galaxy Tab 7.7 Android Development] fasiok:
Can you please show screenshot on 196 dpi?

Thank for advance !!!1
[Galaxy Tab 7.7 Android Development] Maverick777:
Here you go:
[Galaxy Tab 7.7 Android Development] sundazetoo:
Are we sure that the Hybrid Phone UI is not how Jelly Bean should be? Its only rolled out to the Nexus and no other tabs! I kinda like it on my P6810 7.7, just wish you could hide the status bar at times for more screen real estate!! But no biggy!! :o
[Galaxy Tab 7.7 Android Development] songmeesay:
Get gmd gestures on market. Toggles the bar and you can create custom gestures like 5 pinch to bring you back to home screen.
[Galaxy Tab 7.7 Android Development] Maverick777:
Yes, the Hybrid Phone UI is how it's supposed to look if you want the Nexus 7 look. It's the JB UI that''s optimized for tablets smaller than 10". There's not necessarily a "standard" look. JB adapts based on the device. There's now a phone UI, tablet UI, and hybrid phone UI. The "still" part was in response to wintermute000. He/she wanted to know if other DPI's work and have the Tablet UI. As far as I know, only DPI set to 160 enables the tablet UI.
[Galaxy Tab 7.7 Android Development] sundazetoo:
Oh didnt know there were 3 UI's now! I'm on 196 DPI at the moment, not sure if I want to try 160 DPI! Has anyone tried this to see the UI?
[Galaxy Tab 7.7 Android Development] SS2006:
i dont think CM10 has 'project butter' working properly (HW Composer not 100%)

cm10 and cm10 based roms are still veryyy slow compared to Nexus 7, or Galaxy nexus

bringing down the notification bar, swiping from screen to screen, it is very jittery compared to nexus 7 etc

do a side by side comparision and the difference is night and day
[Galaxy Tab 7.7 Android Development] kenkiller:
Of course...such things take time. But is it better than ICS? (or heavens forbid, Honeycomb).
[Galaxy Tab 7.7 Android Development] sopheaknhek:
After flash GAPPS I got Play Store and other App but when I restart Table it gone. So I must flash it every time? Guide please...

Thanks
[Galaxy Tab 7.7 Android Development] kenkiller:
Your videos most probably relies on closed source codecs that only exist in stock Samsung roms. That means it won't ever be "fixed" in CM, no matter how many times you ask. :(
[Galaxy Tab 7.7 Android Development] SS2006:
Muchhh better than ics and hc .im just pointing it out tho not complaining !
[Galaxy Tab 7.7 Android Development] dzeikei:
p6810

Installed on P6810 And I love the tvdpi from nexus 7.

Gonna have to flash back to stock though, because it doesn't share internet via bluetooth tethering to my S3 (same issue exists in locerra' s original)

Wifi hotspot takes a toll on battery on both devices.
[Galaxy Tab 7.7 Android Development] sundazetoo:
Installed v1.3 on my P6810 and haven't had any daily driver functional problems (that i use it for). Videos work, YouTube, Facebook, Instagram and even Zen Bound 2.. Actually all apps i have installed work! By the way, i use Dice player for videos, does smb streaming too, there hasn't been much mention about it..

Keep up the good work :)

Cheers

Sunny
[Galaxy Tab 7.7 Android Development] adinis78:
So if many other people have the same issue and the devs acknowledge the issue they still will not fix the issue, I don't see how this is helpful. I guess those of us are SOL and we just have to deal with it and just move on.

PS. Is there anyway to just install the codecs for those of us that need them? If they will not implement them as an official part of the custom rom maybe having the option to install them should be available just as they offer the gapps to be flashed separately.
[Galaxy Tab 7.7 Android Development] songmeesay:
You're not sol. You have the option to redo your movies in h.264 in a mp4 or mkv container. You can even throw dts audio in there and bs player will handle them no prob on cm builds. I know this may take a lot of time but I believe if things can be remedied by us users in any way, then we should do it.
[Galaxy Tab 7.7 Android Development] adinis78:
Yeah I have started working on one of them to test out and see how it goes. My Library is not the big so I guess it's not that bad. If the one video works then ill get to work on the other ones.
[Galaxy Tab 7.7 Android Development] Fking1:
so if i have done my research, this rom is the only way to get JellyBean on tab 7.7

(other than the unstable CM10 port)?

what's the easiest way to flash CWM on this tab? (i suppose there are no toolkits like for galaxy nexus :) )
[Galaxy Tab 7.7 Android Development] s28:
Just wondering, is there any dpi that is quite stable that's lower than 160?
[Galaxy Tab 7.7 Android Development] Androguide.fr:
OK guys, the Paranoid Android porting is going better than I thought. Still lots of bugs but at least it boots.

I guess you can expect a (very) experimental public release within a few days. Stay tuned !
[Galaxy Tab 7.7 Android Development] fasiok:
Fighting !!!!!!
[Galaxy Tab 7.7 Android Development] s28:
Hey sir,

I may have a lot of queries and questions but i really appreciate your work. Thanks for all the hardwork that you put into this tab. You have truly turned my tab, and im sure there are more, into a truly working one. Thanks so much!
[Galaxy Tab 7.7 Android Development] deani77:
I think 160 is the lowest... because for Nexus 7 look the dev used 213 ;)
[Galaxy Tab 7.7 Android Development] adinis78:
Converted one of the videos using those settings and still nothing, might as well and just give up
[Galaxy Tab 7.7 Android Development] s28:
Im sorry, what i meant is a higher dpi then 213! I got the values messed up sorry..
[Galaxy Tab 7.7 Android Development] Androguide.fr:
You can try 320 which is Phone layout.

213 is Phablet ui (somebody said 196 works too, cannot test as I still don't have my tab)

160 is regular Tablet ui (stock in Sammy roms)
[Galaxy Tab 7.7 Android Development] Fking1:
ok i went ahead to flash this on my P6810

and when i start flashing from CWM i get

----------

Installing update...

symlink: some symlinks failed

E: Error in /emmc/Nexus.7.7......filename-signed.zip

(Status 7)

Installation aborted

Back menu button disabled

--------------------------

i'm installing from microsd, because i guess CWM removed the .zip file from the internal memory when doing full wipe

what to do?

p.s.

i rooted with p6800 root.zip file if that matters

i understood that just when applying the root file, in the tutorial they didn't mention it's for 6800 specifically, so i guess it doesn't matter?
[Galaxy Tab 7.7 Android Development] Josvaz:
Press up n down button u can get menu button enable.
[Galaxy Tab 7.7 Android Development] Fking1:
the disabled button is my smallest problem atm :)

how to flash the rom?

Ive already wiped the current system
[Galaxy Tab 7.7 Android Development] Androguide.fr:
This is most likely to be a corrupted download.

Try to re-download the rom.
[Galaxy Tab 7.7 Android Development] Fking1:
i'll try but the zip file opens just fine on the pc

can i flash it via odin?

---------- Post added at 04:48 PM ---------- Previous post was at 04:45 PM ----------

another odd thing is that when i boot in odin mode

i see

PRODUCT NAME: GT-P7500

and it's definitely a P6010 (even if a pre-release one)

---------- Post added at 05:29 PM ---------- Previous post was at 04:48 PM ----------

re downloaded both 1.3 and 1.2 version, both give the same error :(

can i flash it via odin and what are the advantages/disadvantages of that

might the reason be taht im trying to install it from microsd card instead from the internal memory?

if thats the case how to upload it to the internal memory once i don't have OS anymore?
[Galaxy Tab 7.7 Android Development] tama_dc:
nice ROM, I just had one issue with the wi-fi, seems like it won't connect to a router that is not broadcasting SSID (since I set to disabled SSID broadcast for my wireless router), when I change it to broadcast SSID like usual, it will connect and everything goes just fine.. Don't know if its the issue from CM10 or this ROM only or my tab only, anyone had the same issue? ;)

but anyway, thanks for your work! :)
[Galaxy Tab 7.7 Android Development] Fking1:
here is the log file from CWM

i've wiped everything and it still says there is no space? :(
[Galaxy Tab 7.7 Android Development] enemix:
Have you tried to mount USB Storage through CWM?
[Galaxy Tab 7.7 Android Development] Fking1:
mm, why I should do that? I mean how it's different than the microsd card

i don't have the hardware to do that anyway
[Galaxy Tab 7.7 Android Development] enemix:
Because that's the only way (that I know of) to access the internal storage without a working rom.

To be clear, you connect USB cable to computer, and then select the Mount USB storage option in CWM and your Tab's internal storage should show up as an external drive on your computer.
[Galaxy Tab 7.7 Android Development] Fking1:
ah i thought you want me that way to mount external flash drive

so i can use that to mount some of the internal partitions?
[Galaxy Tab 7.7 Android Development] enemix:
Yup, just like you can do in Android. System partitions are not available that way but the internal storage (/mnt/sdcard) is.
[Galaxy Tab 7.7 Android Development] Fking1:
that didn;t work, it's unable to mount it

but still, since i can see the rom from the sdcard, why i should do that?

The problem is that it doesn't want to flash the rom.

Might that be because i've flashed root.zip for 6800 on a 6810 device? Does it matter?
[Galaxy Tab 7.7 Android Development] freaksamael:
it does...the partition layout IS different:

P6800 (3G)

mmcblk0p1 EFS DO NOT TOUCH

mmcblk0p2 BOOTLOADER DO NOT TOUCH

mmcblk0p3 BOOTLOADER DO NOT TOUCH

mmcblk0p4 param

mmcblk0p5 kernel

mmcblk0p6 recovery

mmcblk0p7 cache

mmcblk0p8 modem/radio

mmcblk0p9 system

mmcblk0p10 data

mmcblk0p11 hidden/preload

P6810 (Wi-Fi)

mmcblk0p1 EFS DO NOT TOUCH

mmcblk0p2 BOOTLOADER DO NOT TOUCH

mmcblk0p3 BOOTLOADER DO NOT TOUCH

mmcblk0p4 param

mmcblk0p5 kernel

mmcblk0p6 recovery

mmcblk0p7 cache

mmcblk0p8 system

mmcblk0p9 data

mmcblk0p10 hidden/preload
[Galaxy Tab 7.7 Android Development] enemix:
I only told you that because you asked how to put something on the internal storage.

The root.zip shouldn't matter. Root has nothing to do with the radio.

Maybe you should try flashing stock firmware with Odin and start over from the beginning?

-edit- Just saw the post about partitions, does that mean the wrong root.zip will flash the wrong partition?
[Galaxy Tab 7.7 Android Development] kenkiller:
Because you have to understand, it's not an issue. You cannot use the same standards of Samsung's ICS roms in comparison to CM. Samsung paid good money for those codecs to use in their products, while CM basically cherrypicks what Google releases in AOSP. If Google doesn't include those codecs (because they didn't pay for it), CM doesn't have it. If there was a way to shoehorn those codecs in there (not that it's possible anyway), firstly, you can expect CM to face some legal action from Samsung. Devices (non-Samsung included) that don't initially have the support will suddenly gain that support, which in turn leads to point 1 again, because Samsung paid for those codecs.

You have to understand the pros and cons of CM vs stock. There's always some things gained and some lost. In this case, it's something proprietary to Samsung that is lost, and is NEVER coming back. What we gain, well, it's plain to see.

Technically, those codecs rely on the Samsung framework, so it's nearly impossible to just put in a zip to flash. Maybe someone with balls of steel might be up to it, but said balls isn't going to dangle free for long before the legal letters start a fluttering. :( Or pray someone port from CM9 as you requested in the official CM10 thread. But you have to pray no one breaks that in every update. :D

The problem here is either a) you're using DRM-ed files that requires stock rom support, or b) encoded in a much less supported codec. A) is basically unsolvable unless you return to roms based on stock, B) is much more solvable but requires a re-encoding of your files.

Whether you like it or not, the sad fact is that you will never see those proprietary codecs baked in on CM roms. Whether you wish to move on or harp on it every single update is up to you. :D

---------- Post added at 05:17 AM ---------- Previous post was at 05:15 AM ----------

Known issue from CM10. Broadcast ssid or else..... :D

---------- Post added at 05:18 AM ---------- Previous post was at 05:17 AM ----------

What application and setting did you use. Don't give up so fast. :D
[Galaxy Tab 7.7 Android Development] Androguide.fr:
@Fking1 : Your problem sounds like a bricked emmc to me. Especially those two parts :

Did you come from stock when flashing this rom ?

However this part here makes me think you did something wrong with odin :

Do you have the android sdk installed on your computer ? If not, do so, adb to your tab and post the output of this adb shell command (each end of line means "press enter")

parted /dev/block/mmcblk0
print

.

Have you tried flashing back a stock firmware through odin ? Did it get stuck on factoryfs.img ?
[Galaxy Tab 7.7 Android Development] adinis78:
Thanks for that, I have come to the conclusion that it will be easier, albeit take forever, to just convert the original source using accepted codecs that CM10 supports. Just need to learn to adapt with changing technology/formats. :)
[Galaxy Tab 7.7 Android Development] freakmax:
Thanks for a great rom.

I love it.
[Galaxy Tab 7.7 Android Development] wintermute000:
Thats disappointing then. I prefer tablet layout even @ 213DPI and 7" form factor. In fact at 7" there is even less valuable space to waste on a statusbar, conversely I find the back/home/switch buttons large enough to hit comfortably without having to stretch them across the entire bloody bottom bar.

Whats super disappointing is how samsung didn't settle on 213DPI for their stock build, and none of their baked in apps (dialer contacts etc.) work when you change DPI from 300 stock to 213. I'm amazed their usability testing didn't tell them that 300DPI was way too small and fiddly.
[Galaxy Tab 7.7 Android Development] Fking1:
Hello

I have no idea how i could have bricked it, i did everything correctly and according to tutorials

With odin i flashed just the CWM and it went through flawlessly

however, i'm gonna try to boot some stock rom today

I just connect with odin and flash from there as normal, right?

p.s.

yes i was with stock rom but an early one since my tab is a pre-release sample Samsung gave me to test

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

btw if i have root is there a problem to use odin to flash unofficial rom? :>
[Galaxy Tab 7.7 Android Development] Androguide.fr:
Well to explain it very quickly, MMC_CAP_ERASE (which is the cause of the brick) can be triggered by stock kernel while wiping a relatively big amount of data, like for example a /data partition stuffed with apps.

So, as bad as it sounds, the only fact of wiping while you were still running stock might have bricked your tab (this happened to me by wiping /system).

I really do NOT recommend to wipe anything while still on stock kernel.

If coming from stock, don't wipe anything, flash Nexus 7.7, reboot recovery, and then wipe data, cache & dalvik, and then reflash Nexus 7.7

This will get you safe from brick, as locerra had the kindness of removing MMC_CAP_ERASE from his cm kernels.

Flashing the P6800 root wasn't a goo idea too, as the /data and /system partitions don't have the same number on both models (P6810 = 8 & 9 / P6800 = 9 & 10).

Try to download stock firmware from SamMobile.com and then try to flash it in Odin, then tell us what happens.

If it won't flash, then I guess only a manual adb repartition (or if you're lucky a simple PIT file) will help you revive your tab.

Being able to see the output of this would be handy to try and help you :

adb shell
parted /dev/block/mmcblk0
print

Odin is in no way an alternative to cwm. What can be flashed in cwm can't be flashed in Odin, and the same goes the other way around, apples and oranges.

Odin flashes *.tar (and other formats i.e *.pit), while ClockWorkMod Recovery flashes *.zip files
[Galaxy Tab 7.7 Android Development] Fking1:
thank you for the detailed input man, much appreciated

it sucks to learn that the full wipe might have bricked it, since it's the first instruction in all flashing guides :)

anyway i'm downloading the official rom as we speak and will try with that first, if doesn't work will figure out how to do adb shell thingy :)

btw the internal memory was like 95% full when i started flashing
[Galaxy Tab 7.7 Android Development] Androguide.fr:
I'm updating the OP with instructions if coming from stock. Hope for you it ain't what I think it is.

This is the story of my brick :

I had been able to revive my tab for like a month after the brick with adb (parted and e2fsck mainly), even though I had to do the whole unbrick process everytime I wanted to flash a new rom, quite annoying for development... But about two weeks ago, the routine I used to apply through adb wouldn't make my tab flash and boot anymore. So I finally had to bring it to a Samsung-certified repair shop, which is going to charge me to repair it...

Keep us updated, will try to help.
[Galaxy Tab 7.7 Android Development] theerachai:
Hi, Thank you for your superb rom

I'd like to ask some questions.

If I want to change some system apps : Phone contact calendar and Camera . Which apk file should I replace.

I saw calendar.apk and calendarProvider.apk ,do I need to replace both or just calendar.apk

Also contacts.apk , contacksProvider.apk.

Phone.apk : I think it only one to be replaced.

I couldn't find camera.apk which system app control camera.

Thank.
[Galaxy Tab 7.7 Android Development] fasiok:
I have a question , My tab cannot see Music file , Video fie , Pictures on App "Music player , Gallery , Mxvideo" i have cpoy them in internal memory 16gb . But i use ex file explorer it can see them. Two hours earlier. i can play music .

I wipe cache / factory / delvilk and reboot it not working T_T

some one help me

I Flash 1.3 and run script

Thank for advance
[Galaxy Tab 7.7 Android Development] Fking1:
odin flash with stock rom failed :(

here is the odin log

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> recovery.img

<ID:0/004> NAND Write Start!!

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Completed..

<OSM> All threads completed. (succeed 1 / failed 0)

<ID:0/004> Removed!!

<ID:0/005> Added!!

<ID:0/005> Removed!!

<ID:0/005> Added!!

<ID:0/005> Removed!!

<ID:0/005> Added!!

<ID:0/005> Removed!!

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> P6810_CODE_P6810ZSKL2_CL594601_REV01_user_low_ship_16G.tar.md5 is valid.

<OSM> GT-P6810-CSC-MULTI-ZZTKL2.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> boot.bin

<ID:0/004> NAND Write Start!!

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Tab 7.7 Android Development] Androguide.fr:
Bad news. Though it doesn't look like my bricked tab's behaviour with odin.

Being able to see your partition table would be very helpful to guess what's wrong.

Here's what you should do (seems long but it's because I tried to detail it as much as I could) :

-Install the android sdk : http://developer.android.com/sdk/installing/index.html

-Go to the folder where you installed the sdk (let's assume you're on windows and you installed it here "C:\android-sdk")

-Open the folder called "platform tools" (So in the example "C:\android-sdk\platform tools")

-Press shift and do a right click anywhere in that folder, then select "Open command prompt here" (Or something like that)

-Boot your tab into recovery and plug it in one of your computer 's usb port

-Wait a bit, maybe it'll install drivers

-In the cmd window, type this :

adb shell

It will say something like "daemon started on port XXX" then return this ~#

- type this (after the ~#):

parted /dev/block/mmcblk0

- it will return this : (parted)

- type this (after the (parted)) :

print

- copy and paste the result here, or make a screenshot on which we can see the full output.
[Galaxy Tab 7.7 Android Development] s28:
based on what happened to me before, what i did was i just left my gallery open for a while cause sometimes it takes sometime to scan everything.