yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] espionage724:
It might help if the Q&A thread link was left in the first post just to direct users there
[Galaxy Tab  Android Development] ayysir:
knew posting slim build would cause mass chaos
[Galaxy Tab  Android Development] joethc:
I think the reason for the people posting ABOUT their builds here is because that was the approach by the te4m originally...if you wanted cm9 ...you had to build it...so people did....not anyones fault for asking if there are differences in builds or trying to get help for issues..btw asking people to build kangs themselves was asking for trouble, I said it months ago and I will say it again.

I started the IRC channel to clear up the useless chatter, not just in this thread but all the galaxy tab threads here on xda, rootz, anywhere..... there sure is a ton of posts here still complaining about everything..

Unless you are contributing to the development of the tab....keep it to yourself ...calling out people for building their own builds and discussing them...really?

Correct me if I am wrong but as far as kangs go....these are all kangs...period...the tab is not a CM supported device, so even the team builds are considered kangs ...lets get that straight...even cm7 was an unofficial port....

people posting stray kang builds they create is not right...but ...its not going to be stopped by you, especially when the te4m is asking people to build kangs instead of posting updated builds! ...check any other device thread for proof.....sorry to break it you but not everyone can build..if the te4m wanted it to be a closed dev environment they sure did not do it right, that is obviously not the case by the way the building process was thrown out to the public on a "if you want it build it " basis..

If someone wants to obtain someone elses build and post it, well that is on them not on the people building trying to push the device and commit changes and fixes. Please people lets get back on track here. PLEASE!
[Galaxy Tab  Android Development] _Derk_:
Time to re-post the link to the general discussion thread for any question which is not directly development related. ;)

Bye,

Derk
[Galaxy Tab  Android Development] joethc:
This is the tablet I am using....its the same as regular p1000....not n/l etc...
[Galaxy Tab  Android Development] espionage724:
This allows me to record, however, the video I recorded has artifacting and other glitches on it (sound sounds fine though)
[Galaxy Tab  Android Development] adi6262:
Try playing the video with mx player or any other software decoding player , it works fine . In default player ( uses hardware decoder ) I have glitches too.
[Galaxy Tab  Android Development] Andrew_Low:
The p1000r is basically the same as the p1000. The 02/02/12 pre built version referenced in post 1 or 2 of this thread works fine on my Rogers tab. Later builds should be fine too.
[Galaxy Tab  Android Development] espionage724:
Ah, software mode on MX player made it better :)

So functional rear camera for the most part :D, could use some improvement still (720p video recording, pictures in native camera app), but otherwise, works fine for general use imo :)

The front camera is the next challenge
[Galaxy Tab  Android Development] entengkhulet:
i use droidvpn to be able to use vpn..its working for me..
[Galaxy Tab  Android Development] phearus:
Hardly mass chaos...

As the "non Te4m" builds are built from newer versions of the Te4m's source than the "official Te4m" releases (eg. it is still the te4ms work being commented on) what is the harm in posting bug reports? Reading over the posts most are pointing out things that don't work - valuable info for the devs.

Now what is the difference between people who build stuff themselves and test - then report back, and people who are reporting back on another's build? We all know the dates they were built. The devs (and those of us that care to look at the commits in the repo) know what changes have been made since those dates, and what hasn't. In fact people struggling with their own builds have pointed out some useful information to the devs through this process.

If many more bugs are resolved between official Te4m releases through this method don't we all win?

People in this thread are too sensitive. A week ago these people were complaining about noobs asking stupid questions about the official releases (eta, camera fix, what is cwm etc), now these people are complaining about people reporting perceived bugs in non-official Te4m builds (something the te4m has been encouraging from the beginning). Why don't you ever stop with the complaining you lot?

Please if you are concerned about flooding the thread with noise - don't add to it yourself. And if you really think there is a problem - click the report button and get Andy Harney on their asses!
[Galaxy Tab  Android Development] Nordpolcamper:
Awesome Rom thanks for that, but is there a way to use the mass storage?

I just flashed the Rom yesterday on my GT-P1000 and currently have not internet on my tablet. When I connect it via the usb cable it doesnt recognize it or the external sd card.
[Galaxy Tab  Android Development] Potimto:
Theres an app called USB Mass Storage in the apps page that will activate the USB mass storage functionality (it will ask for root on startup i think)
[Galaxy Tab  Android Development] FC1032:
---silly remark on my part, removed---
[Galaxy Tab  Android Development] :
@spike

Did you really nead to quote all the long post?
[Galaxy Tab  Android Development] Nordpolcamper:
Thank you very much. Should have looked more throughly ;)

But it still doesnt recognize my external sd card for some reason
[Galaxy Tab  Android Development] ronak.super:
Please post all the these queries in general section !!!!!!!!!! Come on guys people keep reminding again and again not to post all these crap

Btw in op cdesai has already mentioned that no requests would be accepted during development

Let us get a stable build then request

Please stop posting crap and irritating developer who one day may be pissed off and stop developing

that's what happened during honeycomb development

Please guys do not reply to any of these queries
[Galaxy Tab  Android Development] alroger:
Toolchains

@ALL

Just wanted to point out that I was able to compile the kernel the first time using post and the sourcery toolchain: http://xdaforums.com/showpost.php?p=21097913&postcount=294

But I was missing the BLX stuff in /sys/class/misc, and talking to HumberOS last night I compiled the same kernel with the AOSP 4.4.3 toolchain (sudo ln -s ....../cm9/prebuilt/linux-x86/toolchain /opt/toolchains).

With the AOSP toolchain the BLX stuff came to life, and not only that, the kernel version name (in Tablet info) is now the nice one in my sig, by the Te4m. Using the other toolchain I was getting something like gaesff44xx.

If you get errors like in mkfs, ext4 and recovery... it's probably with the current initramfs, that is not done yet (another reason for so many peeps with CwM problems). HumberOS gave me this tar to extract on top of the initramfs from the git. Attached also his compile script, assuming the tree:

cm9/

cm9/Kernel <-- (K in caps)

cm9/initramfs

cm9/compile.sh

(dont forget to edit the compile.sh to choose your P1000* model and number of threads to use for compiling ie. -j6)

For reference, the kernel using that post that I used at first comes out to be 7.3MB.

Using this script it removes some debug stuff and comes out 5.2MB

Unfortunatly it doesn't let me raise the charging_limit above 96, like in the Nexus S.

Cheers!

UPDATE: 14/Fev/2012 - Just compiled the ROM again today. Generates a boot.img that doesnt work, CwM is strangely zoomed in. To compile the kernel I just used the kernel folder in the ROM's git, as the OP states. Did a make ARCH=arm p1n_cm9_defconfig, edited the defconfig file with the location of where I extracted HumberOS' initramfs that is attached here. Then just a final make to create a good zImage.
[Galaxy Tab  Android Development] FC1032:
I'm sorry :-( off to the general then. Thanks for the hard work, I'm sorry for posting in the wrong section.
[Galaxy Tab  Android Development] grukko:
Hi alroger. Did the new code from humberos resolve the initramfs issues?
[Galaxy Tab  Android Development] alroger:
Yeah, compiles fine, and CwM runs fine.
[Galaxy Tab  Android Development] trident0815:
Hi there ...

Just tested the build from 02/02 and the according kernel (from 01/31 i think). It works great ... but I also have found some issues I havent read of yet ...

- The Tab doesn't detect when placed inside the Samsung car mount

- Sometimes the launcher is a lil very slow. Didn't noticed it on the first te4m release. Maybe an issue with the bookmark widget?

- Youtube works a little better now - but the video is still stuttering. (WiFi only, not tested with 3G).

- The provided mass storage app doesn't work on my computers. Works sometimes on my Win7 Notebook, never works on my XP Netbook or my Windows Home Server 2003. Switched to the Samba Mode in Ghost Commander, works fine :-)

- Didn't test the camera - but when using IonRoad (augmented reality driving app) the camera just works fine. But sometimes no GPS Satelites are found.

But anything else I usually use works fine. Accu drain could be better, but I can live with it.

Over all: A great build ... and I am sure the next one will be better. Whenever it comes ... but I hope before 2054 :-D
[Galaxy Tab  Android Development] ayysir:
Yea yea we know this already
[Galaxy Tab  Android Development] CROrION:
Nova launcher is much smoother and faster and everything then default :)
[Galaxy Tab  Android Development] -=Android Man=-:
Guys tell me please that it is necessary to establish that the camera would have ceased to twitch?

And one more question: I have a slow browser renders the page? (Plugins disabled)
[Galaxy Tab  Android Development] humberos:
Excellent!

Thanks!

So, as I said, I will upload to my github space all sources with a simple script for zImage's compilation process.

Cheers!
[Galaxy Tab  Android Development] CROrION:
Did anyone compile anithing newer than 10/02? I need my fix :D
[Galaxy Tab  Android Development] -=Android Man=-:
At the moment this latest build. We look forward to
[Galaxy Tab  Android Development] ayysir:
Why compile a new build with one new fix? Just wait
[Galaxy Tab  Android Development] ayysir:
Wait for a new build from the te4m
[Galaxy Tab  Android Development] grukko:
No major changes since then. Just some recovery fixes.
[Galaxy Tab  Android Development] -=Android Man=-:
I'm waiting. I think in the new build from te4m will be HW acceleration and works the camera.
[Galaxy Tab  Android Development] espionage724:
For anyone at all curious, Time Lapse for Android still has corrupted front camera currently. Also, (this might just be) but I can't record at all due to it complaining of unavailable memory, on any resolution.
[Galaxy Tab  Android Development] alroger:
Nooo, that proves the quieter a dev is, the greater news we will get.
[Galaxy S II Q&A, Help & Troubleshooting] wayneywoo:
Hey all,

I'm trying to find a solution for recording calls using bluetooth. I've bought both Total Recall and CallRecorder, both work very well except for recording when using bluetooth.

I'm on stock Samsung Rom XXKI3

Anybody had any success?

Thanks for the help!

Wayne
[Galaxy S II Q&A, Help & Troubleshooting] wayneywoo:
Anyone?...
[Galaxy S II Q&A, Help & Troubleshooting] chicken_chicken:
Also VERY intrested in this!

Any tool which works with normal headset?
[Galaxy S II Q&A, Help & Troubleshooting] samokko:
bumb
[HTC Incredible S] Lennydk87:
Hey.

My moms Incredible S suddenly starts getting sms's about what cell tower she is connected to, it started after updating to 2.3.5/Sense 3.0 , and the phone is not rootet.

The messages comes in a pop up, and then she got the options to save it or cancel it, and the number that "sends" these messages is : 50 .

Anybody knows how to turn this **** off, cause she gets like 10-20 in a single hour.
[HTC Incredible S] katu2006:
Did you try to disable the notifications from the Messaging app>>Settings>>Notifications?
[HTC Incredible S] Lennydk87:
As far as I see there is not a thing called cell info nofitications in the htc messeage app.?
[HTC Incredible S] Lennydk87:
Problem solved. :D

Settings - Call - CB , it was activated and I deactivated it. :P
[HTC Incredible S] Rbth7e5:
hey im facing this problem too a few days ago. i flashed a few roms and it just disappeared by itself.
[Galaxy S II Q&A, Help & Troubleshooting] nekminit:
Hi,

Is there a way I can access the content of mini paper (on galaxy s2) after updating from 2.3.3 to 2.3.5 . Done a search in the xda forums and alot have had issues with mini paper since updating. I know the fix to make mini paper function normally again is to clear the data , but this wipes the content I had in there. Just wonder if there is a way I can access the content before I clear data so that I can use this widget again and restore previous content.

Cheers
[Galaxy S II Q&A, Help & Troubleshooting] nekminit:
Where would the data for mini paper widgets be stored in the Android file system ? I just want to back this up before I clear the data and use mini paper normally again.

Cheers
[Galaxy S II Q&A, Help & Troubleshooting] DJCarlos:
Hi, did you managed to find a way to recover the information on the mini papers?

I didnt see of this problem, before updating...

Thanks for the information
[Galaxy S II Q&A, Help & Troubleshooting] Mc80000:
I made the same mistake. I updated my phone from 2.3.3 to 2.3.4 and now I can't use Mini Paper and I hade some important notes there. Is there anyone who knows how I can recover my notes?

Thanks in advance!
[Galaxy S II Q&A, Help & Troubleshooting] Mc80000:
Is there anyone who can help me please? I really need the notes.
[Galaxy S II Q&A, Help & Troubleshooting] mhugh:
Solved !

Hi guys,

I've found a way to solve this problem after I upgrade my sgs2 to the v.2.3.5 .

First, you have to root your phone. There are plenty of tutorial on the web to help you. Then install a file explorer with root access (such as Root Explorer but it is not free). Finally, go to /data/data/com.sec.android.widgetapp.postit/databases and copy (in a folder you can access with normal user) the file postit.db

Connect your phone to your PC and copy the file. Then you can read it with Notepad as a .txt file.

:D
[Galaxy S II Q&A, Help & Troubleshooting] DJCarlos:
Thanks for the answer!

(too bad i was not patient enough and i wipe out everything hihi)

but it would be usefull for the next time.

And i am going to root my phone very soon also ;-)
[Galaxy S II Q&A, Help & Troubleshooting] nekminit:
Thanks mhugh I'll give this a try
[General Questions and Answers] RedHazy:
Hello, my phone-loving peers.

I have a dilemma. Financial based mostly...

Current wireless providers

WIND $40 MIRACLE PLAN - My business line, no associated phone - sold TMO HTC Sensation yesterday.

ROGERS $65 MY 10 STUDENT - Gf uses this w/ my old school bb 9000.

1st I wanted the Galaxy Nexus (PENTBAND was majority reasoning) but, unwilling to pay the full price, I'm considering 3-yr with Virgin or Bell to acquire this. Again I want this to use w. Wind then I'm stuck paying another bill though.

2nd. I was offered a HTC Flyer 3G (AWS and I've read does voice calls!?) for the Galaxy Nexus + $200 payment to myself. Again same issue stuck with bill.

3rd. Offered Galaxy Note (No AWS but, Does feature Stylus which is a HUGE need in my current business!) I could use either Rogers or Bellgin plan with this phone, then forward my phone calls to other number and have an AWS tablet/device with wi-fi tethering so I don't kill myself with the big 3's sh!77y data costs?

4th. I could buy a Nexus outright but MicroSD support is a must and USB OTG

Or Buy a Note and use it with Rogers but, then I must supplement my gf with a different phone!

5th. I could transfer my Wind to Bellgin for the Nexus then trade or maybe transfer Wind to Rogers but the Wireless data I go through with Wind alone is worth the $40 I pay (typically 5-8 gb a month) that and rumors of LTE coming to Wind keep me paying.

Please help me, any ideas, solutions, opinions... etc.

Cheers, Red
[Galaxy Note GT-N7000 General] SrAdama:
My first Galaxy Note had dead pixels, burn-in effects (don't know what you call them but there are pictures in the link below). The second one I got as a replacement had much more burn-in effects than the first one. The third Galaxy Note had burn-in effects but not as much as the first two, but the gyroscope isn't working on third one, yes I've calibrated it like a thousand times. All of these phones had the burn-in effects out of the box, so it wasn't I who was overheating the phones screen or something like that...

There were also other minor problems (with all three phones) like bad audio quality, bad Bluetooth connectivity, minor lagging and small blocks appearing when watching videos (yes, even of high quality videos) which doesn't appear on any other phone I've had.

I've never had any of these problems with another phone. I've mainly used Sony Ericsson and Apple phones. Off topic, or maybe not.. I also bought an Samsung Galaxy S2 for my girlfriend and it too had burn-in effects and a burnt in status bar (nothing she really cared about, I take it as does most of the people who have it), so it's not just the Galaxy Note suffering from this issue.

Now I'm here, with my third fricking defective Galaxy Note, really pissed off at these issues. If one pays ca. 500+ euros for a quality phone made by the "best" phone company in the world one doesn't expect to have these issues.

I will try to solve this by contacting Samsung. But I would ask of other owners of the Galaxy Note to do the following test on their phones and post a result.

Download the app:

1. Dead Pixel Detect and Fix

2. Start with choosing the colors white and grey

3. Within the app, go to settings, set brightness to lowest.

4. Be in a dark room and look for these burn in effects I'm talking about (dark vertical and horizontal lines + smudges).

Take a picture of the screen with another camera, taking a picture with the phone itself won't show these issues as it's not software issue but a hardware issue.

These were my results with the first two phones I bought:

http://imageshack.us/g/685/bild4ht.jpg/ (There is only one color displayed and there are lots of dark lines and smudges, ignore the grain)

Thank you.
[Galaxy Note GT-N7000 General] EarlZ:
Looking at your pictures they do look very bad, I cant even tell if that is supposed to be a white or grey rendering on the screen but thats an obvious defect.

Did you get your note from a retail store?

I've also had several replacements with my S2 and I ended up getting a refund.

IMHO, part of the cause of this really low quality control is not by samsung but from other users who accept obvious defects to be normal or tolerable, sure its gonna be a PIA to have it exchanged upto more then a dozen times but since a great majority of them are just accepting it so samsung is giving us sup par quality control.
[Galaxy Note GT-N7000 General] SrAdama:
Can't remember if the colors were white or grey on the first picture, but they were definitely the same on both phones!

I bought the first two phones from amazon.de, I got my money back from amazon.de. And I got my third galaxy note yesterday from handyshop.de...
[Galaxy Note GT-N7000 General] SrAdama:
Might be. It seems like the people who are buying Samsung phones doesn't know what quality is, so they just keep the phones and praise the company and the model.
[Galaxy Note GT-N7000 General] EarlZ:
They know what quality is, they just accept the defects as normal. For me I find it hard to accept some of the screen defects when I never faced this issue with first 2 SAMOLED devices. I guess its the flawless screens I had with my first 2 devices placed me in such high expectations especially on the SAMOLED Plus.

I'll try to see if I can also have mine replaced, the only issue I have is the faint horizontal lines, can be seen even when browsing. No effort needed to see it.
[Galaxy Note GT-N7000 General] SrAdama:
One does not necessarily need to do the test I've put up to see these defects, I can see them whenever the background image is grey or white.
[Galaxy Note GT-N7000 General] bigmout:
Sorry to read of your difficulties, but you do realize their are plenty of Sony and Apple owners with similar problems, right? You've just been lucky until now.
[Galaxy Note GT-N7000 General] OrionBG:
I have a SGS2 and My screen is perfect! Tried the app that is mentioned and all colors are perfect! Maybe there is a bad batch of Super AMOLED HD panels floating around. Don't know but I have never seen SAMOLED screen in such a bad shape! And I've seen a lot! Have somebody heard of Nexus Prime having this issues too?
[Galaxy Note GT-N7000 General] UpSpin:
Sorry, but may you take one picture and draw a circle around the defects? I'm honest: I don't see the banding/burn-in effects on your pictures, nor any dead pixels.

All I see is a poorly made photo, which isn't really sharp, sometimes shaken, and has a lot of grain, probably taken with a low cost camera at a too low brightness the camera isn't able to work with.

If I run the program on my HTC Desire (AMOLED) and on the Samsung Galaxy Note (Super AMOLED) I can't spot an failure. I see a minor burn-in in the notification area, which has nothing to do with quality control but rather it's a display technology limitation.

Else I can't spot any defects, no burn-ins, banding, ...

Just as I don't see this on your pictures, except a lot of grain caused by your camera.

One thing is obvious, that at the lowest brightness setting in a dark room, displaying a dark color, taken with a high exposure time, one can spot a difference in color reproduction between both models. But this is no failure at all, because the difference is minor and the frame conditions stupid. And you probably wouldn't be able to tell a difference without a direct comparison at such artificial frame conditions. And the question is, do other manufacturers allow such a low brightness? Do others have such an evenly lit display?

I really don't see any failure with your models.

So please, make a good photo, with a good DSLR, which is a necessity at such low lights, mounted on a tripod, and then draw a circle around the dead pixels, the banding and the burn-in.
[Galaxy Note GT-N7000 General] SrAdama:
I think you are blind.
[Galaxy Note GT-N7000 General] SrAdama:
Yeah I've never seen such problems on a screen before, hopefully just a bad batch, but on two different models?

Never heard of any screen problems with Apple and SE, (not saying it doesn't exist) but yes I might have been lucky until now. But what are the odds, 3 gnotes in a row (+ my gf's S2), more or less. It's like all my good luck has secretly been accumulating a lot of bad luck lol. Yeah but I can live with this third one, it's not as bad as the first two. But the problem is the gyroscope. It works randomly.
[Galaxy Note GT-N7000 General] eksasol:
This is a major feature of recent Samsung Amoled actually. People have been complaining of screen problem for Galaxy SII, Nexus and Note.

They might not want to make the same mistake with their new 2560x1600 ICS tablet.

I've been interested in other phones that uses Sharp's ASV panel.
[Galaxy Note GT-N7000 General] buk_grudziadz:
I think UpSpin is not blind.

Here you go:

These are pictures made at the same time and light with a DSLR camera and "normal" phone camera.

1. DSLR: http://dl.dropbox.com/u/12581372/DSLR Sony A55.jpg

2. HTC Desire Z : http://dl.dropbox.com/u/12581372/HTC Desire Z.jpg

Me and UpSpin can both see the difference :)