yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] OsitKP:
You are not alone. Camera Pro freezes too. :(
[Galaxy Tab  Android Development] sinan33:
Same problem as yours :(
[Galaxy Tab  Android Development] se_gila:
GPS?!?

GPS not working!! Foursquare failed to load !!
[Galaxy Tab  Android Development] sinan33:
Gps is working very well and connecting fast with navitel.
[Galaxy Tab  Android Development] se_gila:
Only "WIFI & mobile network location" work, "GPS satellites" failed !

Foursquare can't be started?!?

But, cm-10.1-20130506-EXPERIMENTAL-p1 ROM work perfectly ;)
[Galaxy Tab  Android Development] qm4n76:
0507 wont boot, stuck on galaxytab logo, any clue??

glad to hear that, do you make any change or patch for this??

for me, voice call doesn't work (sometimes).

FYI, i'm using JABRAWAVE bluetooth headset

thanks
[Galaxy Tab  Android Development] laxanoulis1:
I have big problem. After flashing the 20130505 my phone bricked!

Trying 2 days to fix it with Odin and Heimdall and nothing! With Heimdall (Windows Version) can flash pit but when is trying to upload kernel is giving me an error and then nothing!

Help! What can i do?
[Galaxy Tab  Android Development] OsitKP:
1. You shouldn't flash pit!!!

2. have you installed proper drivers for Odin and Heimdall?

3. I posted the kernel for Odin few pages ago. Try it.
[Galaxy Tab  Android Development] laxanoulis1:
I'm trying to restock to gingerbread man...

Edit: Nevermind.... my phone is on Gingerbread and now i'm gonna install latest (20130507) update and try it.
[Galaxy Tab  Android Development] doixanh:
Same here. My p1 is stuck on Galaxy TAB screen, no kernel logo, with alroger's build 20130507... Cannot get to CWM either. Perhaps it's a kernel problem.

/edit: I'm unable to boot on HumberOS's build 20130506 (stuck on Galaxy TAB screen too). CM nightly (3.0 kernel) does, though.
[Galaxy Tab  Android Development] alroger:
p1 kernel problems

[MENTION=3031478]humberos[/MENTION], is it possible there is a problem building the p1 kernel? I haven't had any problems since the first Kernel 3.0 version (p1n).

I figured out one of the problems mentioned... :facepalm: ((.-) my CwM ZIP files had an old update-binary, that's why it was giving Status 0 Error when trying to flash my CwM Kernel ZIP files.

So guys, old CwM Kernel ZIPs work only with kernel 2.6. I'm uploading a new build today, and the kernel ZIP files will only work with Kernel 3.0 from now on. Same with PDroid patches.

[MENTION=3546299]doixanh[/MENTION] and [MENTION=4313939]qm4n76[/MENTION], can you confirm if you can flash the p1 kernel (boot.img inside the ROM zip) through Download Mode, on top of that Soft-Brick (stuch on the GalaxyTAB screen) and if it works?

[MENTION=3380725]storm31[/MENTION] mentioned some kernel updates that might fix the p1 kernel stuck on GalaxyTAB screen problem... so please try today's build also.
[Galaxy Tab  Android Development] laxanoulis1:
I'm on Gingerbread GB_Stock_Safe_v5 with Overcome_Kernel_v4.0.0. Can I flash Kernel p1 (humberos 3.0) and then 20130507 via CWM?

Edit: Tried what i said and nothing. Stuck on Galaxy Tab logo.
[Galaxy Tab  Android Development] OsitKP:
It was posted here many times. When you flash the ROM you should flash the kernel right after ROM without booting!

It looks like no one have read last few pages. :(
[Galaxy Tab  Android Development] alroger:
[UPDATE 20130508] p1 kernel fix? Kernel Flash ZIPs fixed.

Hope it works for everybody now!

My Kernel and PDroid Flash ZIP files use the new update-binary made for Kernel 3.0. So they should only work on Kernel 3.0 from now on.

My Tab feels very smooth!
[Galaxy Tab  Android Development] laxanoulis1:
Man i read the last pages and i did that! Flashed the ROM but my mobile did nothing. Stuck again on Galaxy Tab logo. :(
[Galaxy Tab  Android Development] alroger:
Hmmmm, that brings up a question, that might be whole problem with everybody.

If you are coming from Kernel 2.6 you should flash the kernel first with heimdall, and after that flash the ROM and maybe flash the kernel again through recovery. But if you don't flash the Kernel 3.0 first, that's why the kernel inside the ROM doesn't get flashed, because update-binary will not run on Kernel 2.6 anymore.

[MENTION=3031478]humberos[/MENTION], please let me know if I'm saying something stupid here.
[Galaxy Tab  Android Development] laxanoulis1:
I'm coming from Gingerbread GB_Stock_Safe_v5 with Overcome_Kernel_v4.0.0. What should i do?
[Galaxy Tab  Android Development] alroger:
Flash the newest kernel using heimdall.

Reboot right into CwM Recovery and flash the new ROM and...

...before rebooting flash your kernel, GApps and PDroid if you want.

Let us know if it works and which kernel you are using!
[Galaxy Tab  Android Development] Mjoelnir77:
That theory would explain a lot - especially as i can flash an old kernel (i usually take your 5th april one) via heimdall, boot to that recovery and only then could flash ROM etc in one go. Then during the flash operation in CWM i was on old kernel and as you had the old binary in the zips it worked.
[Galaxy Tab  Android Development] laxanoulis1:
ERROR: "kernel" is not a valid argument.................

it gives me that when i type heimdall flash –kernel boot.img –recovery boot.img on cmd. (I'm on the directory where heimdall suite is)

Edit: The right way is heimdall flash --kernel boot.img --recovery boot.img but it saying to says to me when it go to CwM "No root" and it has "Yes" and "No"

When i press yes nothing happen. My phone reboots and go again on the same question. Root, yes or no? :( What the....!?
[Galaxy Tab  Android Development] alroger:
Sorry about that... the blog replaces the dashes (-) with other characters...

it's

heimdall flash --kernel boot.img --recovery boot.img

Those are 2 dashes (minus sign) before kernel and before recovery.

PS: you guys can also use the Heimdall graphical UI. Just select the kernel file... nothing else.
[Galaxy Tab  Android Development] doixanh:
Sorry for late reply, I didn't try heimdall/odin after soft brick. I tried to swap cm nightly's kernel on your 20130507 zip, flashed it and it boots. Your 20130508 build works for me now.

Thanks.
[Galaxy Tab  Android Development] jmpub:
Kernel 8.05 update zip, give me error, instalation aborted

Tryed right now via CMW
[Galaxy Tab  Android Development] alroger:
Is it the p1 kernel?

Which ROM/Kernel are you trying to flash in? Remember, it will only work with kernel 3.0.

EDIT: checking.. I also got error...
[Galaxy Tab  Android Development] jmpub:
P1, with the last that boot onde mine, nightly 06.05 kernel
[Galaxy Tab  Android Development] humberos:
[MENTION=535343]all[/MENTION]

The update-binary is an universal script. It isn' t the problem.

Also, is not a requirement to flash kernel before or after install process.

https://github.com/humberos/android_device_samsung_p1/blob/cm-10.1/p1ln.sh

We need to know if this script above is working for all variants:

I will set my tab as "P1" variant and test the install package before upload new one build.
[Galaxy Tab  Android Development] laxanoulis1:
I have to ask something else...

I'm using Heimdall 1.1 and when i go tab Flash on Kernel section it says that is have to select zImage. There i will choose the .zip or the boot.img?
[Galaxy Tab  Android Development] humberos:
Please, update your heimdall.

The correct kernel filename for P1 variant with Android 4.x.x is boot.img.

For P1N and P1L variant we have boot_p1ln.img as kernel filename.
[Galaxy Tab  Android Development] laxanoulis1:
Thanks for the answer and for the work! :)
[Galaxy Tab  Android Development] alroger:
Kernel Flash ZIPs fixed and uploaded now.

"mount" requires one more parameter in the script now. I guess it wasn't a update-binary problem... so forget all I said.

Dev-Host seems to be overloaded..... be patient, I'm trying to upload.
[Galaxy Tab  Android Development] goughymachine:
I had the same experience many here have - stuck at samsung galaxy screen, no booting, nothing. No cwm. Long press to shut down, entered download mode, using OsitKP's odin flashable kernel flashed just the kernel in Odin and it rebooted straight into the rest of the flashing process and has been rock solid since. Thanks OsitKP :)

The kernel is a .tar file in one of his posts on page 75 I think, or maybe page 74.

I had also read extensively before flashing (coming from cm9) and had also read alroger's site page, and flashed rom then kernel before reboot and still got stuck. The above worked sweet to get me going again. This was the rom from 5th may.

---------- Post added at 08:06 AM ---------- Previous post was at 07:54 AM ----------

I don't say much here, but thought I'd post an experience.

I'm not the most adept at all this stuff. If things don't work I'm not good at sorting them out. I had been on cm10.1 from nearly the start of it and one of my main uses of my tab is watch movies/tv shows, both from the tab and streaming my htpc. It had always been a bit flakey for me, lots of stuttering on many things. I know I could have re-encoded stuff to work better but I just couldn't be bothered. Was also getting freezes and random reboots daily. A few months ago I made the tough decision to return to alrogers last cm9, which always worked for me. Everything was pretty cool again.

Having not checked here much for a while, I noticed the new kernel and decided to give it a go again.

After the usual flashing drama many seem to have had (no drama really, odin kernel solved it straight up) I can say that things are running so well now, and so much better than a few months ago. I've tested a few of the vids I know were stuttery before and they are playing as smooth as. In general my tab now seems faster and smoother than on cm9, and certainly more so than the last cm10.1 I was on.

I would just like to say thanks guys. I was getting very close to jumping to a nexus 7 and know that in my financial situation it couldn't be done, so you have one again breathed new life into my tab.

The only thing I'd love to see is a quicker boot time, it's really a few minutes at least before I can use mine. But, maybe I just shouldn't turn it off ;) But can't expect miracles from this older tech.
[Galaxy Tab  Android Development] storm31:
[MENTION=3031478]humberos[/MENTION], [MENTION=4101982]alroger[/MENTION] I can now confirm that the kernel bug for P1 gsm should be gone. I compiled yesterday one build without this issue. I compiled now new build and flashed this without separate kernel flashing. It boots fine. CwM works, Bluetooth works, USB to PC and SD card mounting work, front camera problem still exists. If someone wants to try it: http://xdaforums.com/showpost.php?p=41198057&postcount=38.
[Galaxy Tab  Android Development] jmpub:
I tryed this and works

thanks

---------- Post added at 09:44 AM ---------- Previous post was at 09:14 AM ----------

confirm.. boots OK

thanks

---------- Post added at 10:07 AM ---------- Previous post was at 09:44 AM ----------

Antutu

ROM 02/05

ROM 08/05 (dont give SD score)

and the last, today,, Kernel 3.077 09/05 (dont give SD score)

---------- Post added at 10:29 AM ---------- Previous post was at 10:07 AM ----------

One thing i see, is now i cant overclock GPU like old rom..

give me that my device is not compatible..
[Galaxy Tab  Android Development] Chriss123456789:
Why are the settings messed up?

Some settings are in the wrong position...

-CM10.1 Alpha 4 GT-I8150-
[Galaxy Tab  Android Development] Seraphim:
[MENTION=958744]jmpub[/MENTION]

I didn't overclock CPU and still have a decent AnTuTu score (whatever that helps) with the last ROM compilation of [MENTION=4101982]alroger[/MENTION] (08/05).

I had short fling with the official CM nightlies yesterday and were under the impression that things were a bit snappier and battery drain a bit more economic. However, I liked the HumberOS version (differences with menue and settings options) a lot better - so I came home.

ROM 08/05

Cheers

---------- Post added at 12:23 PM ---------- Previous post was at 12:15 PM ----------

---------- Post added at 12:35 PM ---------- Previous post was at 12:23 PM ----------

---------- Post added at 12:53 PM ---------- Previous post was at 12:35 PM ----------

4320 (3D graphics: 1302) is now my personal highscore /w 1200MHz on my old P1... :D
[Galaxy Tab  Android Development] sinan33:
[MENTION=4101982]alroger[/MENTION]

The browser crashes above the resolutions of 160 dpi.

Would you please check this issue?
[Galaxy Tab  Android Development] Chriss123456789:
[MENTION=2463235]sinan33[/MENTION]: Did you try to clean the cache and the data of the browser in settings -> apps ?

--Sent from CM10.1 Alpha 4 GT-I8150--
[Galaxy Tab  Android Development] sinan33:
Yes, i have cleaned the cache and dalvik cache then cleaned the data though it crashes.
[Galaxy Tab  Android Development] Chriss123456789:
I don't know what you can do..

What DPI did you set?

--Sent from CM10.1 Alpha 4 GT-I8150--
[Galaxy Tab  Android Development] sinan33:
I first set dpi to 240, the browser didn't work,then tried 200 dpi, the browser didn't work again.

Then return to 160 dpi,it works now.
[Galaxy Tab  Android Development] Chriss123456789:
Try 180 or 120 dpi.

--Sent from CM10.1 Alpha 4 GT-I8150--
[Galaxy Tab  Android Development] Chriss123456789:
But why are some settings interchanged?

In CM10 the settings like the Google OS. Why are now the settings so changed?

Please tell me..

--Sent from CM10.1 Alpha 4 GT-I8150--
[Galaxy Tab  Android Development] sinan33:
I don't know why the settings are different.

But i want my tab to work at 240 dpi because the UI looks very clear at these settings.
[Galaxy Tab  Android Development] alroger:
First, this is not just Google AOSP. It's CyanogenMod, which already has much more stuff than AOSP.

Second this is the SGT7 Unofficial, not the official CM, so it's got even more settings for you to play with. :cyclops:

Settings "reversed"?? I have no idea what you mean. When in doubt, factory wipe and format everything for a clean fresh install. Don't try to keep your settings from CM10... CM10.1 is different.

CyanogenMod's default DPI for our Tab (since CM9 I think) is 160! Nothing garanteed above that... you can try other browsers from the market. I use the Naked Browser myself. I think not even Chrome works in 240 anymore. Of course the DEVs are watching, and if it's easy enough they will give it fix.

All works perfectly at 120 which is what I use.
[Galaxy Tab  Android Development] sinan33:
[/QUOTE]CyanogenMod's default DPI for our Tab (since CM9 I think) is 160! Nothing garanteed above that... you can try other browsers from the market. I use the Naked Browser myself. I think not even Chrome works in 240 anymore. Of course the DEVs are watching, and if it's easy enough they will give it fix.

All works perfectly at 120 which is what I use.[/QUOTE]

Thank you and other devs for all of your hardwork.

Mine is just a wish; if you can do that it will make me very happy.

Regards...
[Galaxy Tab  Android Development] Chriss123456789:
thank you and the other devs (cdesai, humberos, sbradymobile, and so on..) for the good ROM! :)
[Galaxy Tab  Android Development] Seraphim:
[MENTION=220146]sinan[/MENTION]

Me and my clumsy finers also enjoy the 240 dpi setting on my P1.

Unfortunately, the browser.apk in the recent ROMs force closes at 240 dpi.

I got myself another browser.apk from some thread in this forum which works perfectly at 240 dpi (link)

Either you copy it to /system/app on a running system and change rights to -rw-r--r-- conveniently in the CM file browser (system-folder needs to be set to Read/Write) or you copy it as is to /system/app in the ZIP-file of your ROM prior to the installation (I do that under Ubuntu). When you modify the ROM-file you can also directly change the dpi in the build.prop (at least in Ubuntu I can manipulate the ZIP-file easily w/o unpacking first).

A good addition to 240 dpi is the Xposed framework in combination with App Settings as it lets you define the DPI-settings per App. The calendar app is much more informative when run as 160 dpi application.

Have a go!
[Galaxy Tab  Android Development] Chriss123456789:
When the DPI is set on 240, the p1000 looks like a very big phone. :D

--Sent from CM10.1 Alpha 4 GT-I8150--
[Galaxy Tab  Android Development] khanhvu86:
How to change DPI?
[Galaxy Tab  Android Development] bravokylee:
use re to edit build.prop to change.

---------- Post added at 04:51 AM ---------- Previous post was at 04:49 AM ----------

launcher in setup is missing after reboot, anyone else has the same issue?
[Galaxy Tab  Android Development] pinguinolandia:
IN SCREEN LOCK IS NOT IN LANDSCAPE IN 240 DPI. AND BROWSER NO WORK.:confused:
[Galaxy Tab  Android Development] Seraphim:
[MENTION=2221532]pinguinolandia[/MENTION]

Concerning the browser read my previous post and with regard to the lock-screen, well, consider it a feature.

Portrait is probably the best orientation to present widget (cLock) and unlock options in a neat way. Will not kill you to turn the tab 90° when facing the lock-screen, will it?

Cheers!
[Galaxy Tab  Android Development] Chriss123456789:
when I use the phone ui, then the symbols such as wireless or battery are pixelated and blurry..

is it a bug or not?

--Sent from CM10.1 Alpha 4 GT-I8150--
[Galaxy Tab  Android Development] alroger:
[UPDATE 20130510] Kernel 3.0.77 and little fixes. You tell us.

TGi Friday!
[Galaxy Tab  Android Development] jmpub:
Tested and all ok

Only the 3D score is too slow.. About 730.. Very strange. With last rom o use, after several day that i test last days, is 02.05 with kernel 08.05,and the score is more than 1200

One more time.. Thanks for the goooodd work to all
[Galaxy Tab  Android Development] hfalahaty1:
usb debugging

hi

is there any problem about usb debugging

my tab didn't connect to QtADB
[Galaxy Tab  Android Development] _ck_:
Tablet came up with "encryption unsuccessful" out of the blue today so I took the opportunity to try the newest update

CM10.1 20130510 Kernel 3.0.77 tested successfully on p1c cdma (verizon)

hopefully these encyption problems will go away, tired of losing all settings

tethering confirmed working - I had to toggle it couple times before windows saw it, but it works and no crashing
[Galaxy Tab  Android Development] jmpub:
I try this morning, to put the Kernel 08.02 in the Rom 10.05, and boost the score antutu from 3450 to this:

and the 3D score give me 2 times the kernel 10.05

thanks for the good work..
[Galaxy Tab  Android Development] OsitKP:
This test is real crap. The results values jump from 3400 to 4100. It's more than 20% inaccuracy. I wouldn't trust it. (Imho).
[Galaxy Tab  Android Development] jmpub:
but you see that the cause is 3D score to low in new rom and kernel, but the new Rom and kernel from 08.05 boost 3D score.. maybe anything wrong with 3D in this new kernel

thanks
[Galaxy Tab  Android Development] alroger:
Ohh great! So my build for p1c is already working with the new kernel?
[Galaxy Tab  Android Development] levdave:
:)Hi, I can't find the parameter that allowed to open the application panel with the home button when on main screen. Did it disapear ?

(Sorry, it's difficult for me to explain that in english, I hope it's possible to understand :silly: !)
[Galaxy Tab  Android Development] doixanh:
My P1 suddenly refuses to boot (with bootloop) today @.@, CWM is unable to reach. Everything was fine yesterday. I've just used heimdall to flash alroger's newest 20130510 kernel, still bootloop.

Trying to flash CM nightly 20130510 kernel just now.

/edit: bootloop even with CM nightly. I still cannot reach CWM. Trying an older 2.x kernel now. Does anyone have alroger's last 2.6.x kernel build (20130405 or so)? Nevermind, found it.

/edit2: 2.6 kernel boots. 0% battery. I'll fully recharge then retry 3.0 kernel

/edit3: 3.0 kernel boots. All fine now. I didn't expect it to be out of battery this morning :D
[Galaxy Tab  Android Development] _ck_:
Ah my mistake, for some reason I thought the regular install included the new kernel.

About tablet shows 2.6.35.7

So I didn't test it yet. Maybe tonight.
[Galaxy Tab  Android Development] atomikhippo:
Don't waste your time. Humberos will make an announcement when the CDMA 3.0 kernel is ready.

I'm not sure if the sleep of death is occuring for those on the 3.0 kernel, but for those that are still on 2.6 you can avoid blue sleep by leaving your bluetooth on. It might drain your battery a little but you won't have to hard boot to a battery that's been draining for who knows how long.
[Galaxy Tab  Android Development] humberos:
Yep! I will try to port CDMA!

Now I am working on sensors and will get CDMA start after finish them.

Deep sleep works fine but the sleep of death no exists for me at moment.

I've noticed that we have some lag when we wake the tab by press on power button.

---

FINALLY, I got 1.4GHz@OC (at least for P1L) stable again. 13th hour and no reboots. (check img)

Let's move on!
[Galaxy Tab  Android Development] _Derk_:
I didn't try the 1005 but with alrogers 0805 my P1000 doesn't connect to the computer while when I take the build from storm31 there are no problems.

So alrogers might you check any influence of the PDroid to USB as this is the main difference...

Bye,

Derk
[Galaxy Tab  Android Development] Chriss123456789:
I think this ROM have a problem with the autorotation.

Because my Tab-screen don't rotate.. In the settings, the option is marked as on.

Or is this bug only by me?

--Sent from CM10.1 Alpha 4 GT-I8150--
[Galaxy Tab  Android Development] Seraphim:
I now run kernel 3.0.77 with the latest [MENTION=4101982]alroger[/MENTION] ROM and seemingly even Auto-Brightness came to life again!

It becomes increasingly harder to find things not working as intended!!!

However, now that I installed a second user I have "settings" reliably force closing on me whenever I'm not logged in as main user.

People on other devices seem to have similar problems using the official CM10.1. The thing that annoys me most is being unable to shut off the vibration feedback.

Would be cool if I could get any of the savants interested in this (luxery-)problem.

Cheers
[Galaxy Tab  Android Development] alroger:
Nope, the ROM doesn't come with PDroid, only if you flash the PDroid ZIP.

There is no USB problem in any of the versions mentioned.

Auto-bright has been working in CM10.1 for a while now...

Never had sleep of death in CM10.1..

No problems with auto-rotation in any of my CM10.1... at least for me (p1ln).

What else?

Check your configs!

Once was mentioned by humberos/storm31 that it's good to format /system and /cache and flash again with gapps. That will not wipe your data and configs.
[Galaxy Tab  Android Development] Chriss123456789:
It's very crazy. I have the navigon app started and stopped and the autorotation did not go after the navigon close.

I run the navigon app once again and then autorotation go well.

That is very crazy but now autorotation works! :)

--Sent from CM10.1 Alpha 4 GT-I8150--
[Galaxy Tab  Android Development] sinan33:
I have met just one issue; the front cam doesn't take photo.All the other stuff works very well.
[Galaxy Tab  Android Development] _Derk_:
Well, initially I flashed your 0805 plus PDroid.

I had no USB connection.

Then I flashed the build of storm31 and got USB connection.

So today I flashed again 0805 from your build but without PDroid and got no USB connection.

There is some significant difference between your build and the one from storm31. The sizes only differ by little but the result for me is really different ;)

Bye,

Derk
[Galaxy Tab  Android Development] hanjien93:
When I flash this ROM, why my tab said no external sdcard and because of that I cannot use the camera and things?

Can someone help me?
[Galaxy Tab  Android Development] frgo:
It's like that since early days of CM9. After running applications using sensors (compass?) autorotate stops working and randomly starts working again after running this application again a few times.

It's quite annoying...
[Galaxy Tab  Android Development] Chriss123456789:
[MENTION=4176980]frgo[/MENTION]: you said it! ;)

In CM9 this bug has make me angry...

That's the reason why I'm go to CM10.1 from alroger.

--Sent CM10.1 Alpha 4 GT-I8150--