Database Users

Roms, Kernal Patches, etc.

Alright lets get the record straight. Has anyone tried the kernal patch that puts your mem on a partition on the sd card. Supposidly this boosts performance out of this world. Please post here if you have tried this.
Secondly, we need to attract some developers. I'm willing to donate if anyone wants to code for us. We got a great user base and a really good product. Im conviced the captivate is by far one of the better phones from the galaxy s lineup. If any one knows some developers, introduce them tot his godly beast and let them know there are people out here willing to pay for good quality fixes and roms.
I was thinkin about asking for help from the guys running international s. We could post and ask in the xda area and also modaco and androidforums which have big communities as well.
Any other ideas on how to attract developers? Post here.

systoxity said:
Alright lets get the record straight. Has anyone tried the kernal patch that puts your mem on a partition on the sd card. Supposidly this boosts performance out of this world. Please post here if you have tried this.
Secondly, we need to attract some developers. I'm willing to donate if anyone wants to code for us. We got a great user base and a really good product. Im conviced the captivate is by far one of the better phones from the galaxy s lineup. If any one knows some developers, introduce them tot his godly beast and let them know there are people out here willing to pay for good quality fixes and roms.
I was thinkin about asking for help from the guys running international s. We could post and ask in the xda area and also modaco and androidforums which have big communities as well.
Any other ideas on how to attract developers? Post here.
Click to expand...
Click to collapse
I'm down to donate as well and do anything I can to add to the cause. I really hope this phone takes off cause it is great. I think we have a good chance that a lot of the N1 devs might just come over to this phone and if not they should be getting the Vibrant and I doubt that it will be much trouble to port over to Captivate.

Err why is it better lol? all the samsung galaxy S phones are exacly the same internaly...none its better than the other, the only difrence is the lack of flash/camera and keyboard from the other variants.

rafyvitto said:
Err why is it better lol? all the samsung galaxy S phones are exacly the same internaly...none its better than the other, the only difrence is the lack of flash/camera and keyboard from the other variants.
Click to expand...
Click to collapse
Image, Image, Image. If the galaxy lineup were real life siblings, the captivate would be the only one going to the prom. It also sports fewer gps issues than the vibrant and galaxy s. Ive also seen way less people complain about lag in these forums than the ones for the vibrant and galaxy s (and we have more viewers here than on the vibrant page).
When devs see this device they should be seeing potential.

systoxity said:
Image, Image, Image. If the galaxy lineup were real life siblings, the captivate would be the only one going to the prom. It also sports fewer gps issues than the vibrant and galaxy s. Ive also seen way less people complain about lag in these forums than the ones for the vibrant and galaxy s (and we have more viewers here than on the vibrant page).
When devs see this device they should be seeing potential.
Click to expand...
Click to collapse
All of these so called "issues' are software based, its samsung ****ty touchwiz UI that lags like ****ing hell, not the device hardware, and yes i do agree that the captivate is the sexiest of them all.

Im pretty sure it would be painless to port over Vibrant or Galaxy S fixes to the Captivate. Internally they are the same except for a few minor differences like rafyvitto said which wouldn't be that hard to fix. I'm brushing up on my Java skills and learning about the internals of Android right now. Ive been a iPhone person for a while. Hopefully soon I can be of some help and get hacking on Captivate. From what I've seen and read we have a good phone to develop for because its easily rooted and has an unlocked bootloader. I've also heard that the drivers for the Galaxy S lineup are encrypted, but I haven't seen any confirmation of that. What we need is a dump of the current ROM and also we need a better recovery system like Amon_RA's recovery. The source for his recovery system is on GitHub so we could try and port it over to the Galaxy S lineup.

shouldnt samsung be releasing source for drivers any day now? I thought the word around town was that they were being open with the community on this jazz.

systoxity said:
shouldnt samsung be releasing source for drivers any day now? I thought the word around town was that they were being open with the community on this jazz.
Click to expand...
Click to collapse
They have already released the source code for the Galaxy S here. They don't have to release the source for the drivers because they are proprietary, but from what ive read the binaries for the drivers are in that download so all someone would have to do in link them in. I just don't know if the drivers are encrypted meaning that it has to be an official samsung ROM for them to work. Hopefully not because that would make cooking new ROMs a hell of alot easier.

we should ask the modaco guys for help and info. I dont think we can use the source or drivers from the galaxy s international. I think someone tried doing stuff that way and bricked.
i could be wrong tho

Would also be willing to donate to the cause. The only reason I didn't buy an iPhone 4 is the developers for this phone.

@wesgarner is on the CyanogenMod team / TeamDouche and has ordered a Vibrant.
We might be able to encourage him to port the latest CyanogenMod build once he has the Vibrant's build completed.
He purchased a Vibrant and I think a laptop to do the work. I've already sent him an email about being a beta tester for the Captivate.
Just remember the devs have a life outside of working on phones! Don't ask for timelines - whether you donate or not!
Wes is working on a port for the slide and then he'll be working on the Vibrant.
While the hardware is similar - the software isn't exactly the same. I was messing around with the MMS.apk today and tried to replace my corrupted one with the one from the Vibrant - did NOT work.
Also, the device is capable of having a REAL FMRadio. The Euro versions have an FMradio.apk. I pushed it to the Captivate - but, the Captivate will need the drivers (to build into a kernal) for the FMRadio to work. But, this is entirely possible.
So, yes the hardware is basically the same or similar - it won't necessarily easy. If any of you remember, LOL - this will be akin to porting the N1 build over to the Desire - I think.

The first thing to go should be that awful samsung UI lol. I think the challenge will be porting ROMs for all these different Galaxy S models. I saw this coming when I read the device would make it to all four major carriers in the US plus.

thanks shane, i also heard another dev recently purchased a captivate, do you know anything about this? i'd like to support his endeavors.

Yea I read over in the Vibrant forums that a dev just got a captivate and is working on a recovery. They also have wes working on the Vibrant so hopefully they get cookin on some ROMs. It won't be that much of a hassle to port them over to the captivate. I would advise not fooling around too much with your phone because someone has already messed up his/her phone. They will either have to take it into ATT store and replace it or wait for a dump of the original ROM to come out.

I have tired the MoDaCo rom and it does (kinda - not brick) work with the SGH-I897 (captivate model), I was able to use it to remove the ATT crapware and nearly everything seems to be working. Phone reports its self as Model Number: GT-I9000 in the about phone tab.
One very IMPORTANT problem - I am having difficulty making outgoing phone calls.
Things that I can confirm work:
Bluetooth file transfer
3g data
GSM phone calls (incoming calls work)
Camera
Audible app, pandora ect.
SMS outgoing and incoming messages
Pretty much everything I have tested on the phone except making outgoing phone calls (important as it is a phone after all). So DON'T use this ROM yet, and if you do make a backup.
Hope this helps.

Why would you want Honeycomb (on a phone?)

Well there's the question, why would you want Honeycomb on your fascinate? I mean, it looks nice from what I saw of the xoom demo but it really doesn't look like it would be nice on a phone just yet, so why ask/want it, why not wait until something actually meant for a phone is developed?
I just don't understand the want/"NEED" for honeycomb on my fascinate, can't we just keep it to actual phone OS's for now?

gabenoob said:
Well there's the question, why would you want Honeycomb on your fascinate? I mean, it looks nice from what I saw of the xoom demo but it really doesn't look like it would be nice on a phone just yet, so why ask/want it, why not wait until something actually meant for a phone is developed?
I just don't understand the want/"NEED" for honeycomb on my fascinate, can't we just keep it to actual phone OS's for now?
Click to expand...
Click to collapse
Same reason everyone wanted DJ05, DL09 and DL30...they always want something new. Instead of optimizing what they have and being content, they rather complain and wish for something better to come along.

I get that, but whats with the wanting of this new thing if its not even meant for a phone; I mean I wouldn't want something clunky and literally designed for something bigger on a 'tiny' device. It would just be wrong. I fail to see how even those who continually ask for new shiny things would overlook the real incompatabiliteis with a phone. I can see asking for Gingerbread, but even that's a bit much. I mean, we have Froyo, and now my brother with his fancy incredible is actually jealous of my phone. I think things are great, and I understand the desire for new shiny things, but honeycomb really isn't for phones, so why be ignorant of that?

gabenoob said:
I get that, but whats with the wanting of this new thing if its not even meant for a phone; I mean I wouldn't want something clunky and literally designed for something bigger on a 'tiny' device. It would just be wrong. I fail to see how even those who continually ask for new shiny things would overlook the real incompatabiliteis with a phone. I can see asking for Gingerbread, but even that's a bit much. I mean, we have Froyo, and now my brother with his fancy incredible is actually jealous of my phone. I think things are great, and I understand the desire for new shiny things, but honeycomb really isn't for phones, so why be ignorant of that?
Click to expand...
Click to collapse
keep in mind though...froyo wasn't meant for our specific phones either...we're all running a leaked version. For all we know, after a year of addl development the next ota update may be honeycomb...

jenisiz said:
keep in mind though...froyo wasn't meant for our specific phones either...we're all running a leaked version. For all we know, after a year of addl development the next ota update may be honeycomb...
Click to expand...
Click to collapse
honeycomb is for tablets!!

ace5198 said:
honeycomb is for tablets!!
Click to expand...
Click to collapse
3.0's UI is meant to be able to scale down to phone sizes. The current developer preview doesn't work exceptionally well when that's done to it (it's buggy, but obviously meant to), but it's not anywhere near a finished product (it's really meant to show the APIs).
Android also isn't being forked, there isn't going to be a Phone version and a Tablet version, future phones will be running the 3 series (they might wait for 3.1, but they will run 3). They will pretty much have to if any of them want to use the newer dual-core CPUs that should be just about to hit the phone segment.
Also, don't forget that Android 3.0 adds a fair bit of new APIs, not all of which are meant exclusively for tablets (there's a fair bit of HW acceleration stuff, IIRC).

KitsuneKnight said:
3.0's UI is meant to be able to scale down to phone sizes. The current developer preview doesn't work exceptionally well when that's done to it (it's buggy, but obviously meant to), but it's not anywhere near a finished product (it's really meant to show the APIs).
Android also isn't being forked, there isn't going to be a Phone version and a Tablet version, future phones will be running the 3 series (they might wait for 3.1, but they will run 3). They will pretty much have to if any of them want to use the newer dual-core CPUs that should be just about to hit the phone segment.
Also, don't forget that Android 3.0 adds a fair bit of new APIs, not all of which are meant exclusively for tablets (there's a fair bit of HW acceleration stuff, IIRC).
Click to expand...
Click to collapse
im sure that it could be scaled down to use on a phone.. and actually i believe somewhere i seen that it was.. but everything ive read said its desinged specifically for tabs.. im sure there will be a 3.1 or 2.5,,6,7,8 or whatecer for the new apis.. but everything ive read says 3.0 is for tabs.. im not saying im right.. but thats just what ive read

ace5198 said:
im sure that it could be scaled down to use on a phone.. and actually i believe somewhere i seen that it was.. but everything ive read said its desinged specifically for tabs.. im sure there will be a 3.1 or 2.5,,6,7,8 or whatecer for the new apis.. but everything ive read says 3.0 is for tabs.. im not saying im right.. but thats just what ive read
Click to expand...
Click to collapse
The new user interface is designed for tablets, as well as parts of the new APIs. Nothing prevents you from replacing the launcher, and hopefully by the time Honeycomb stabilizes, the new Launcher won't just force close at lower resolutions (but this isn't meant to be a preview of the new interface, but of the APIs).

I don't understand you question.
Honeycomb is simply the natural progression of Android. Hence why its 3.0. Eventually all Android devices will be on 3.x of some kind just as iOS was able to merge its variant it made for the iPad with the rest of the family.
Google had a separate team continue to small upgrades in the 2.x line while the AAA team worked on a tablet enahnced 3.0 Honeycomb variant.
I'm sure as this year moves (early next) on we'll see a 3.1 version come out that has the appropriate scaling features to handle screens of all sizes.
This is evidenced by the same Gmail app being used in both. Just different views based on overall screen size. Also, 3.0 and 2.3 have code to allow devs to make different views based on screen size. The base code is there, its just now gotta be merged to be one line again.
So, why do I want honeycomb? I don't. I want to continue to be using the latest version of Android, what its build version is is not important. (2.3, 2.4, 3.0, 3.1) As long as its made to work with the hardware I have and adds improvements, I want it.

Stop the debate:
http://www.bgr.com/2011/02/03/google-will-not-bring-honeycomb-to-smartphones/

mexiken said:
Stop the debate:
http://www.bgr.com/2011/02/03/google-will-not-bring-honeycomb-to-smartphones/
Click to expand...
Click to collapse
All that says is 3.0 i.e. Honeycomb won't be on phones. I am sure a later 3.x version will once the code has been merged from 2.x.

I thought 3.0 is where we finally get hardware accelerated UI, is this correct?
Sent from my SCH-I500 using XDA App

superchunkwii said:
All that says is 3.0 i.e. Honeycomb won't be on phones. I am sure a later 3.x version will once the code has been merged from 2.x.
Click to expand...
Click to collapse
And this thread is about Honeycomb... Not 3.x versions.

crookshanks said:
And this thread is about Honeycomb... Not 3.x versions.
Click to expand...
Click to collapse
Honeycomb is 3.0

gabenoob said:
Well there's the question, why would you want Honeycomb on your fascinate? I mean, it looks nice from what I saw of the xoom demo but it really doesn't look like it would be nice on a phone just yet, so why ask/want it, why not wait until something actually meant for a phone is developed?
I just don't understand the want/"NEED" for honeycomb on my fascinate, can't we just keep it to actual phone OS's for now?
Click to expand...
Click to collapse
I'd want the built-in data encryption features.

-deleted-
Misread somethin'

Hmm alright; what I was asking is that where it stands now it is a Tablet OS, why would anyone want something like that on a phone. As shown in the link, google does not mean for Honeycomb to be brought to phones (3.0) but maybe at a later date a later variant of the 3.1 series will.
The original question I had in mind was why would anyone want it, in its current state, on a phone, as I've seen threads asking for it; and for the life of me I can't find a good reason.

superchunkwii said:
Honeycomb is 3.0
Click to expand...
Click to collapse
I was referring to your "later 3.x versions" comment. This thread was about why anyone wanted 3.0 specifically, not later versions.

crookshanks said:
I was referring to your "later 3.x versions" comment. This thread was about why anyone wanted 3.0 specifically, not later versions.
Click to expand...
Click to collapse
Absolutely right, my post was to the validity of the entire discussion as its obvious 3.0 is just the initial tablet offering and as Android continues through 3.x it will be on phones as well.
Basically, I find the entire constant discussion here, BGR, other sites about Honeycomb being a Tablet OS and why is Google diverging Android to just be stupid. To me the version "3.0" should have been enough to satisfy everyone that eventually features you see in Honeycomb will be on phones. Like Google's going to lock themselves in 2.x for the rest of Android phone's life.

Honestly I don't understand it. Other than a very small number of users, myself not included, do people really see a big difference in the use of their phones? I use mine for calling, texting, e-mail and occasional web browsing. Other than flash support, I haven't noticed any ground breaking improvements over DJ05 with DL30. I can't imagine Gingerbread, Honeycomb, Lucky Charms or Poptart making a huge difference in the day to day use of my phone either.
Or maybe I'm wrong and Honeycomb cures cancer.

Looking to get the A500...

Hello everybody, I'm sageDieu and I am a very active user in the Samsung Mesmerize/Fascinate forums as well as the general Q&A, Apps and Games, Development etc threads here at xda.
I have been exploring options thinking about getting a tablet, and I have used a lot of them at Best Buy. I was just looking around and found that i had a bunch of rewards points on my credit card, just enough to get me the Acer A500. So the first thing i did was head over to xda to see what the development was looking like for this tablet, and from what i can tell it looks pretty active which is promising. The main thing I would want to do when i get a tablet is get it rooted, wiped and on a stock honeycomb rom with as much performance and as little proprietary software as possible.
My questions for you guys are:
1. Do you recommend getting the tab? It seems to be my best potential option, and the hardware specs look great.
2. What is the process of rooting, CWM, roms, etc. in a nutshell for this device? I am familiar with terminal, linux, adb, all that stuff for my phone and lots of other devices I've played with. I'm assuming for this just grab and run gingerbreak then adb CWM over? I've never owned a tab before.
3. After I get to that point (if I do, still not even sure about buying the thing) can you guys tell me what your favorite roms are? There seem to be a lot that have active stable development.... mostly 3.1 with different options but then there's the 3.2 xoom one and some other ones... it's a bit overwhelming coming from my phone where we have stock, a custom debloated rom and then CM7 and MIUI. Just some quick recommendations would be great for things like speed, battery life, performance, bloat, stability, etc..
Thank you so much to anybody that takes the time to help me out. If I do get this device I assure you I will be very active in the forums and do my best to keep it going.

sageDieu said:
1. Do you recommend getting the tab? It seems to be my best potential option, and the hardware specs look great.
Click to expand...
Click to collapse
I don't have any experience with other tablets except seeing some being used. I have not used them myself. Thus I have a hard time giving anything concrete in the way of differences or opinions, but, well, I haven't had any issues with my Iconia and the hardware is just great; the battery lasts and lasts and lasts, the screen is pretty, the full-sized USB port is really daymn handy.. And I like the one thing Acer has made in their ROM: Dolby enhancements. It does make a difference
2. What is the process of rooting, CWM, roms, etc. in a nutshell for this device? I am familiar with terminal, linux, adb, all that stuff for my phone and lots of other devices I've played with. I'm assuming for this just grab and run gingerbreak then adb CWM over? I've never owned a tab before.
Click to expand...
Click to collapse
1. Install Iconiaroot.apk and tap on "root", you're done.
2. Install Acer Recovery from Market, tap on Install, you're done.
And that's that, you've got CWM installed and the thing rooted. Not too hard
3. After I get to that point (if I do, still not even sure about buying the thing) can you guys tell me what your favorite roms are?
Click to expand...
Click to collapse
I personally like the stock ROM the most, the others have this or that naggle..

i have been enjoying the minimal rom (albeit overclock would be nice). Going to be testing out lightspeed with thors kernel to see how well that one compares.
I looked at five different tabs; Samsung, xoom, HP webos tab, blackberry Playbook, and this one. The two downfals of the iconia are the screen and the processor. There are faster and better displays out there but the tablet had all theother features I wanted at a much cheaper price. A good competitor for this one was the Asus transformer, but I wanted better haptic feedback from using the keyboard.

1. I enjoy mine and would recommend it. That said, honestly you'd have to say exactly what you're looking to get out of the Tab so others can offer constructive recommendations.
2. You'll find rooting and installing CWM to easier and quicker just than just about any phone out there. Literally can do both inside of 2 minutes right on the Tab itself.
3. As far as roms go there are options. That said, since HC source code will probably never see the light of day the talented devs on here are pretty limited on what they can do. The good news is most stock roms are fairly bloat free in comparison to phone roms. I believe the Galaxy rom has the most customization you'll find. So.. check some rom threads on here and experiment. A few kernels are available too.
Hope that helps

By your numbers:
1. I think it's the best tablet out there for the money, and definitely in the running for best tablet period. There are faster, lighter tablets available, but there is nothing out there that completely matches the feature set of the A500. Depending on what you want from a tablet, you might end up like me with it being your "only" option.
2. Best way to describe the A500 rooting process: SCARY EASY. I can't believe how easy it was after what I had to go through to root my HTC Evo 4G phone. Everything on the A500 is like one-click. The IconiaRoot app roots it in one step, the Acer Recovery Installer installs ClockWork Mod in basically one click, and then you're able to flash away on whatever ROMs you want.
3. I'm no use here. I like the stock Honeycomb v3.1! You actually might, too. There's a lot less bloatware on tablets compared to phones, and even stock it's pretty smooth/fast. I definitely felt the need to hack up my HTC Evo phone, but my A500 is only rooted and tweaked a little.
Good luck with your decision!

Thanks for the feedback. In response to "what I want in a tablet," it would mainly be a media device, games, music, movies etc. and I might use it for development in the future.
Sadly, my Xbox broke and I have decided to use my points for a new one since it gets a lot more use than I think this would. I really appreciate the answers, and I will keep you guys in mind when I save up the cash to buy a tablet. Thanks
Sent from my MIUI SCH-i500

Fascinate bros!

sageDieu said:
Thanks for the feedback. In response to "what I want in a tablet," it would mainly be a media device, games, music, movies etc. and I might use it for development in the future.
Sadly, my Xbox broke and I have decided to use my points for a new one since it gets a lot more use than I think this would. I really appreciate the answers, and I will keep you guys in mind when I save up the cash to buy a tablet. Thanks
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
lol nothing worth playing on Xbox until MW3 comes out in Nov. COD Black Ops blows chunks, MW2 was the last good one of the series. Wait until November for your Xbox, and get your Iconia now!! lol

kjy2010 said:
lol nothing worth playing on Xbox until MW3 comes out in Nov. COD Black Ops blows chunks, MW2 was the last good one of the series. Wait until November for your Xbox, and get your Iconia now!! lol
Click to expand...
Click to collapse
Pfft, PS3 > Xbox anyways

WereCatf said:
Pfft, PS3 > Xbox anyways
Click to expand...
Click to collapse
+1
On topic: Hello, I hope to be a new member of the Iconia Community shortly. I was going to make one of these topics, but thanks to the OP, I didn't have to =p.
I've read the reviews by those big name reviewers on the Iconia, Galaxy Tab, Thrive, Playbook, iPad (eww), Transformer, etc.. but they'll never compare to actual users of the product in the real world. With that being said I have one more question to add:
What are the specific issues/concerns that have come up with the Iconia? I've read there are sleep issues with the unit? I haven't had the chance to read through the changelogs of the various roms for the Iconia yet, but have they fixed any of the stock issues?
Thanks in advance and hope to hang around here for some time to come =)

Athrun88 said:
What are the specific issues/concerns that have come up with the Iconia? I've read there are sleep issues with the unit? I haven't had the chance to read through the changelogs of the various roms for the Iconia yet, but have they fixed any of the stock issues?
Click to expand...
Click to collapse
Quite many people seem to have issues with WIFI not getting IP address, but apparently the fix is easy enough. I don't know if newer firmwares have fixed the issue.
Personally I have not had a single issue with the tablet at all so again I cannot comment much more than that.

i run stock rooted and have only 1 small issue.....occasionally I will install from the market and the apk will download but never move past "installing" i have to leave the market and come in again and redownload the apk etc.
Also if you are looking at purchasing, and have a cosco around do it there. 32gig version with case (a crappy one) and hdmi cable for $429 is very hard to beat. Also with the cosco you get 90 day return and 2 years warranty. (3 if you use amex to buy)

Aaron Camp said:
Also if you are looking at purchasing, and have a cosco around do it there. 32gig version with case (a crappy one) and hdmi cable for $429 is very hard to beat. Also with the cosco you get 90 day return and 2 years warranty. (3 if you use amex to buy)
Click to expand...
Click to collapse
There are afew private sellers that are selling the unit. I really don't care about warranty because i'll be rooting, and with my past history with devices and electronics, i've never claimed warranty anyways. I will, however, look into that, there's a costco near my work! Looking at a seller with a 16GB model at $350 Canadian unopened box. Seems like a good deal.

Hi -- Intro -- and Question on Rooting

Hi --- I just purchased my tab 7.7 this week and have been reading through this forum. I traded in My Galaxy Note (actually my Girlfriend snapped it up at a bargain trade in price).
The Note was my first ever Android Phone and I absolutely loved it except for the Music Quality. I decided to go with two Devices instead --- The Nokia 808 as my phone and the Tab 7.7 as my Tablet.
The Nokia 808 has outdated hardware, a mediocre screen, a soon to be extinct OS and horrible support in terms of Apps but it absolutely shines as 1) A basic Phone 2) A superb 41Mp Camera 3) Superb Music Quality made even better through USB OTG 4) Great Navigation (Nokia Maps is really Excellent).
So I use the Tab 7.7 to offset the Nokia 808's weaknesses 1) Photo viewing and management via its magnificent screen 2) Internet Connectivity 3) All the various apps I like to use
Seems like a good match so far and I do not mind having 2 devices as I have put a 64GB microsd in the Nokia so that it replaces my Music Player as well as my casual use camera.
What do I not like about the Tab 7.7 so far??? ---- well coming from ICS on the Note seems like a step backward but actually ICS is not the great Leap so many people think it is -- So I am learning Honeycomb and its not that bad actually.
Lagginess -- a bit slower rendering big catalogs of photos than I would like but other than that not really a big deal. I am not a gamer or a Power User so the lagginess is not a big deal and it is not that bad anyway (just a bit less Zippy than the note).
What I REALLY do not like:
1) The fonts -- Uggghhhh -- What were they thinking?! I have read the posts on this topic and am using "the "Big Font" app which is more like a band-aid that at least makes the Tab usable for my tired eyes --- but it really is a far from perfect solution and makes the Tab 7.7 looks screwed up sometimes when switching between the apps.
2) Cannot write to external SD from other Apps? Were they serious?! A major inconvenience for someone like me who is putting so many images on the device and hoping to use it as an on-the-go image manager.
So now the big question ----- to Root or not to Root?????
It seems there is little in the way of user-ready Custom ROMs.
ICS is supposedly on its way either July or August.
Do we think ICS will solve the problems above?
Is it worth rooting now? Any Real benefits?
If I update to stock ICS when it becomes available can I Root from there? Or will I need to Flash back to HC to Root?
Very much interested in everybody's input.

errr.... did you miss this topic about ICS release...
http://forum.xda-developers.com/showthread.php?t=1748745
btw... all the rooting and writing to external SD can be read from the development section... its all there... enjoy reading

Yep -- its kind of funny I just posted -- then saw the threads on ICS -- maybe I brought you guys some Goodl Luck :silly:
As to Rooting --- Yes I have read the threads there. I know already how to Root.
I am asking for OPINIONS as to whether it really make sense given the absence of Custom ROMs --- is it worthwhile?
edan1979 said:
errr.... did you miss this topic about ICS release...
http://forum.xda-developers.com/showthread.php?t=1748745
btw... all the rooting and writing to external SD can be read from the development section... its all there... enjoy reading
Click to expand...
Click to collapse

if you use some apps like titanium backup which required root... then its a plus... but there is many other option open when you root the device...
i like to tinkering with the build in setting... and some other thing... so root is a must for me... it give me full control over the device...

Ok Thanks --- If I am reading the ICS thread correctly it looks like you can root directly from ICS (Unlike the Note where I had to downgrade to Gingerbread first).
In that case I will let you early adopters test ICS out and see if any issues (does it have the infamous "brick bug") and maybe upgrade and root tomorrow.
edan1979 said:
if you use some apps like titanium backup which required root... then its a plus... but there is many other option open when you root the device...
i like to tinkering with the build in setting... and some other thing... so root is a must for me... it give me full control over the device...
Click to expand...
Click to collapse

yup... as my tab is using that damn chip with brick bug... currently got no problem with it... so if you want to check... can head to this thread and download the software by chainfire and install it on your device... it will show some info about your tab chipset
http://forum.xda-developers.com/showthread.php?t=1693704

Looking For Tablet ROM With More Complete S-Pen Support

Hello. I have written an app that helps to improve the accuracy of the S-Pen. It works only on Note phones because Samsung has compiled some S-Pen device driver interfaces out of the tablet ROMs. It is not clear why they did this. I have asked Samsung but gotten no replies. I have confirmed that parts of the kernel code is commented out in the open source kernel code (and you can see that some of the interface files found on phones do not exist on the tablets). It seems that the tablets suffer from the same issues related to the S-Pen as do the phones and I have many people asking me to make my app work on their tablets. I cannot do so with the stock ROMs because of the missing interface files.
So I am wondering if there any non-stock ROMs in which the S-Pen is more fully supported. The missing files are located on my phone in /sys/class/sec/sec_epen/ and the two files I need are called epen_hand and epen_rotation. If anyone knows of any ROMs for the S-Pen equipped tablets that provide these interface files, I would appreciate knowing and may be able to direct some folks to using them.
Thanks

I can confirm that neither are present in Baked build 8, it might be worth checking a dump from the note 8.0
Regards
Jack

JSale said:
I can confirm that neither are present in Baked build 8, it might be worth checking a dump from the note 8.0
Regards
Jack
Click to expand...
Click to collapse
Jack, some replies to postings in the Note 8 section indicate that the two files are present on the stock ROM there. Interesting... I am downloading a dump of the 10.1 now to see if I can see anything. Thanks

Any progress on this? It looks quite promising in the note 8.0 forums.
Regards
Jack

whitedavidp said:
I have confirmed that parts of the kernel code is commented out in the open source kernel code (and you can see that some of the interface files found on phones do not exist on the tablets). ... The missing files are located on my phone in /sys/class/sec/sec_epen/ and the two files I need are called epen_hand and epen_rotation ...
Click to expand...
Click to collapse
Well, since this is presumably a kernel issue, I'll look into it (PM me with your E-mail address) and IF there's anything that can be done about it (i.e., if the corresponding actions are available in the pen driver; it's not enough to just be able to integrate the sysfs entries) I'll add it into the kernels I release for the Note 10.1

kcrudup said:
Well, since this is presumably a kernel issue, I'll look into it (PM me with your E-mail address) and IF there's anything that can be done about it (i.e., if the corresponding actions are available in the pen driver; it's not enough to just be able to integrate the sysfs entries) I'll add it into the kernels I release for the Note 10.1
Click to expand...
Click to collapse
Hello and thanks for responding/helping out. I am certainly no kernel programmer. But I have downloaded the kernel sources for a couple official Note devices/versions. I have been reading files located in kernel/drivers/input/touchscreen/wacom paying particular attention to the file wacom_i2c.c. I cannot help but note that some of the functions which appear to reference the driver i/o files that are missing are #def'ed out of certain devices - see line 837 #if defined(CONFIG_MACH_P4NOTE).
I have no idea if the Wacom devices used in the various Note models are the same (except for size) or are similar enough to be treated as the same by programs like mine. Heck, I am not even sure if Wacom devices are being used in all the Note models. So I am afraid I am not much in the way of technical help here.
What I do know is that some custom ROMs for Note I and II phones seem to have been created with drivers that DO support and create the needed driver i/o files but which lack the device settings and other mechanisms which actually take advantage of these i/o files. Basically, they do not offer a dominant hand setting nor do they seem to communicate to the Wacom device when an orientation change is detected. I have been able, through my app, to compensate for these lapses on those devices and thereby improve the SPen's accuracy.
I have had users wanting to get the same effect on Note tablets with my app. So I presume they are experiencing the same type of problem on their tablets that I experienced on my Note I phone that led me to get into all of this. But I know that my app cannot help them unless the i/o files are there.
I was surprised to hear, over in the Note 8 forum that the files do exist on those devices. I know from a tester that my app at least runs on the Note 8. But I don't know if it helps any since that tester was not seeing the problem my app is designed to fix. But I read here that the files are not on the larger Note tablets. I don't know why and have asked Samsung and get basically no answer. My underlying assumption is that the Wacom devices are basically the same but I cannot answer why Samsung treats them as different.
I am sure all of this doesn't help much. Sorry. All I would like to do is try to find a way to offer support to the tablet users who want it.
Cheers!

Try this kernel: http://goo.gl/OBJ4O (PM also sent).

kcrudup said:
Try this kernel: http://goo.gl/OBJ4O (PM also sent).
Click to expand...
Click to collapse
Im going to quickly revert from baked to android revolution to test this
I will let you know what I think.
Regards
Jack

JSale said:
I'm going to quickly revert from baked to android revolution to test this
Click to expand...
Click to collapse
No, this is just a kernel- you won't have to change distributions to try this.

kcrudup said:
No, this is just a kernel- you won't have to change distributions to try this.
Click to expand...
Click to collapse
But baked is based on CyanogenMod, unless this kernel is compatible?

kcrudup said:
Try this kernel: http://goo.gl/OBJ4O (PM also sent).
Click to expand...
Click to collapse
Sadly, I don't own one of these tablets (yet). But I have passed this on to a user who previously asked me (and got this thread rolling as a result). So perhaps he can check it out and try my app on it. If he does, I will certainly report back here. Thanks for your efforts.

JSale said:
But baked is based on CyanogenMod
Click to expand...
Click to collapse
Oh, then yeah- as I suspect CM won't have any of the SPen goodies. My bad.
In any case, let me know. It was a very trivial fix and didn't appear to break anything. I don't use the SPen much at all, but a quick test with SNote appears that everything still seems to work OK.
(But I did notice that the stock Samsung ROM (CMD2) does set these variables, which is unusual as these sysfs entries "shouldn't exist", but it seemed to (re)set them to default values. I wonder if this is used as part of a version check of some sort?)

Well, after a little bi of testing, I can conclude that this fix has indeed improved the accuracy of the s-pen. It is hard to tell by how much, as I never had very terrible offsets myself, but at the edge of the screen, this has reduced the offsets by an observable amount.
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked rom ?
Many regards for all the hard work
Jack

JSale said:
Well, after a little bi of testing, I can conclude that this fix has indeed improved the accuracy of the s-pen. It is hard to tell by how much, as I never had very terrible offsets myself, but at the edge of the screen, this has reduced the offsets by an observable amount.
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked rom ?
Many regards for all the hard work
Jack
Click to expand...
Click to collapse
Wow! Thanks for the testing and for the feedback on your results. This is quite interesting. I am not quite sure I can integrate this sort of thing into my app although it may be possible. The kernels for the Samsung devices I have looked at seem quite monolithic rather than modular. But I do know that one app, TouchScreenTune, does something that fiddles with the kernel in some way I do not fully understand. So perhaps. I would sure need help and direction. But it would be very cool indeed.

JSale said:
Would it be possible to get the kernel fix implemented into the app so that I can use it on Baked ROM?
Click to expand...
Click to collapse
Well, the "kernel", the "ROM" and whichever app it uses are quite different things, but at least I can offer up the "commit" that makes it possible in the kernel (which has to then be pasted into a ROM). Have a/the Dev PM me.
whitedavidp said:
But I do know that one app, TouchScreenTune, does something that fiddles with the kernel in some way I do not fully understand.
Click to expand...
Click to collapse
Most likely via a "sysfs" file, which seems to be the preferred method for this driver.

kcrudup said:
Well, the "kernel", the "ROM" and whichever app it uses are quite different things, but at least I can offer up the "commit" that makes it possible in the kernel (which has to then be pasted into a ROM). Have a/the Dev PM me.
Most likely via a "sysfs" file, which seems to be the preferred method for this driver.
Click to expand...
Click to collapse
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them? Does the Kernel have a main web page? And if so, what version should I point them towards? Thanks

whitedavidp said:
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them?
Click to expand...
Click to collapse
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).

kcrudup said:
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).
Click to expand...
Click to collapse
Thanks very much once again!

whitedavidp said:
Thanks very much once again!
Click to expand...
Click to collapse
The app seems to work with this kernel :good:
kcrudup said:
Well, right now the only kernel that's got this particular support is the one I've posted here- but every now and then I post up a kernel boot.img file for the latest Android Revolution ROM and for Darkman's latest Stock ROM and this patch will be included in those going forward. Most boot.img files among the various Note 10.1 devices are close enough that they'll almost always work for any ROM, Stock or Custom.
I don't keep any seperate thread or site for my kernel, as I'm really just sharing my own personal (yet improved and faster) kernel for Note 10.1 devices (and frankly don't feel like dealing with the inevitable newbie questions that a standalone offering would generate).
But I have a number of commits I'm about to push to my GitHub page; once I do that (give me a day or two, I've made some major changes to the kernel source and I'll need to verify all's well before I make them Public) I'll come back here with the GitHub commit web-page URL, then you can pass that to any ROM/Kernel dev and they can easily incorporate it in their particular builds (it's a really trvial patch, too- I just removed the 3 "#else" directives embedded in the "#ifdef CONFIG_MACH_P4NOTE" conditionals).
Click to expand...
Click to collapse
I really want to know what are the features of this kernel ... would i keep it or there are other ones that have this functionality right now?? OR could just this changes be added to the Stock kernel to only have Spen support .. as i dont want any OC or custom governers :good: :good:

whitedavidp said:
If I want to point users of my app to your kernel as a means of gaining more SPen support, where should I send them? Does the Kernel have a main web page? And if so, what version should I point them towards? Thanks
Click to expand...
Click to collapse
May I ask you what application you are talking about?
@kcrudup Have you already decided to release your kernel in a separate thread or not?