Hello,
I own a Nook Color and plan to use it along with notebooks in school. I am getting a stylus, but the problem is the app. Is there a way to install SketchBookPro on the Nook Color? I'm running MIUI ROM. Thanks.
EDIT: Is there a way I can fake honeycomb to run this app?
You could use Sketch Book mobile but PRO requires Honeycomb.
Yeah you have to use Sketch Book Express (Free) or Sketch Book Mobile ($.99). Unless you install one of the Honeycomb roms.
Alright thanks. Boy am I sometimes dumb... figures. Thanks again!
joenathane said:
You could use Sketch Book mobile but PRO requires Honeycomb.
Click to expand...
Click to collapse
I purchased and use the Sketchbook Mobile application and find that I really like it. It scales well to the display of the NC.
I can recommend it as well.
Thanks, but I just installed Honeycomb. Just to use this app.
Just went back to MIUI for the speed. Now i'm wondering if there is a way to fake honeycomb to run this app? Or modify it to run on 2.3.3? Because I doubt it uses anything honeycomb dependent. Thanks!
ikingblack said:
Just went back to MIUI for the speed. Now i'm wondering if there is a way to fake honeycomb to run this app? Or modify it to run on 2.3.3? Because I doubt it uses anything honeycomb dependent. Thanks!
Click to expand...
Click to collapse
NO! How many times does this need answering? NO!
Right. Sorry for being a bother
/dumb
khaytsus said:
NO! How many times does this need answering? NO!
Click to expand...
Click to collapse
Instead of being rude you could explain why you can't. Things tend to stick when you explain why. I don't think we need comments like that in XDA.
Sent from my ADR6300 using XDA Premium App
ikingblack said:
... SketchBookPro on the Nook Color?
Click to expand...
Click to collapse
You can modify the AndroidManifest.xml file setting minSdkVersion="8" for froyo. I've done this for SketchBook Express free version and you can download it here: http://www.megaupload.com/?d=A5WAH4PJ
actorman46 said:
.. explain why you can't...
Click to expand...
Click to collapse
This modified apk will install fine on CM7, but force close when you try to run it because it calls on the ActionBar API, which is Honeycomb-specific. You can see this by following the logs.
ikingblack said:
... modify ... to run on 2.3.3?
Click to expand...
Click to collapse
To do this yourself next time follow these steps:
1. Use Madcat's sdk port running on Rack's SD card to install Sketchbook Express from the Market and retrieve com.adsk.sketchbookhdexpress-1.apk from /data/app
2. Get APK Manager 4.9: http://forum.xda-developers.com/showthread.php?t=695701
3. Update apktool to 1.4.1 (051511 release) for xlarge support: http://code.google.com/p/android-apktool/downloads/list
4. Extract Honeycomb framework-res.apk from any duodexed HC ROM, I used Xoom Tiamat 3.2: http://forum.xda-developers.com/showthread.php?t=1203635
5. Install HC framework for apktool per instructions here: http://code.google.com/p/android-apktool/wiki/FrameworkFiles
6. Use APK Manager to extract and decompile com.adsk.sketchbookhdexpress-1.apk
7. Modify the AndroidManifest.xml file with a text editor, I used Notepad++ in Windows
8. Use APK Manager to compile and sign apk.
ikingblack said:
... plan to use it along with notebooks in school.
Click to expand...
Click to collapse
Good luck in school.
Thank you very much. Yes, I hacked the apk before posting and it does FC. Thanks for telling me about why it FCs. Yes, thanks for the luck .
actorman46 said:
Instead of being rude you could explain why you can't. Things tend to stick when you explain why. I don't think we need comments like that in XDA.
Click to expand...
Click to collapse
It's been explained why in many other threads, including a couple others he has been involved in, possibly started. No need to waste my time regurgitating it here.
ikingblack said:
Hello,
I own a Nook Color and plan to use it along with notebooks in school. I am getting a stylus, but the problem is the app. Is there a way to install SketchBookPro on the Nook Color? I'm running MIUI ROM. Thanks.
EDIT: Is there a way I can fake honeycomb to run this app?
Click to expand...
Click to collapse
Don't bother with the stylus. They don't work well at all on the Nook... even the capacitive styluses.
khaytsus said:
It's been explained why in many other threads, including a couple others he has been involved in, possibly started. No need to waste my time regurgitating it here.
Click to expand...
Click to collapse
So i guess the rude comments you posted isnt wasting time either?
Ditto on the stylus issue...tried quite a few, haven't come across any that work well. Seems like the area the stylus touches isn't specific enough for any fine detail, or even writing properly.
Related
Since apparently BN is still changing framework.jar, I'm making a thread to allow separate updates/downloads. framework.jar for 1.0.0 is already in market hack/autonooter/autoconfig
1.0.0 - http://www.mediafire.com/?1wb78ollpb1bd78
1.0.1 - http://www.mediafire.com/?37fugab7xo8s3j3
This framework.jar helps you get an Android ID when you first run the Market. You can replace it with the stock version once your market is working if you want, but leaving it shouldn't cause any issues either.
Um, this thread is remarkably empty.
Thank you for your work!
Not having to generate ID's manually is better than awesome ...
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
johnopsec said:
What did you have to change in Framework.jar I know your hacked version works. I'd just like to understand why.
Click to expand...
Click to collapse
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
Thanks. That makes sense now.
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
JeepFreak said:
Can somebody post the stock version of either of the two files from the OP? I'm trying to get this working on the eLocity tab and, since I'm no developer, I need to compare the two files to see what Clockworx change... and therefore, what I should try changing in our framework.
Thanks!
Billy
Click to expand...
Click to collapse
If you want to post your framework.jar, it would probably be faster.
clockworx said:
If you want to post your framework.jar, it would probably be faster.
Click to expand...
Click to collapse
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
JeepFreak said:
Fine by me! I was tying not to be a bother
http://www.slicky.net/android/elocity.a7.framework.jar
Thanks a bunch!
Billy
Click to expand...
Click to collapse
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
This might not be the place or already covered, but is it possible to make the big button in the notification bar not pop up the B&N Soft Buttons? I tend to hit that far too often.
Personally if it was gone, or did nothing, I'd be happy. I can launch the apps from ADW myself, they're all individual apps anyway.
clockworx said:
Here it is if you want to take a shot.
http://www.mediafire.com/download.php?dd9zif5h89ve7mz
I would back up your stock one and ensure you can restore it, just in case.
Click to expand...
Click to collapse
Awesome man! Thanks a bunch!
Billy
clockworx,
can i replace framework.jar from slide_update.zip (BN 1.0.1) with yours
and also what i said in your other thread (supernooter) and then flash the ereader.
I am asking too many questions as i dont want to end up with an over sized 7" ice scraper...
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Skwurlsoft said:
I'm in the same spot as JeepFreak, but mine's a Cruz Reader.
If i upload the framework.jar can you mod it?
P.S. its Eclair-2.0 otherwise i'd try and use an existing copy off the web.
Click to expand...
Click to collapse
We actually ended up getting the eLocity going without using the modified framework.jar.
Billy
clockworx said:
Are you using a custom firmware for it? I could have sworn someone had already done it for the CR over at Slatedroid. If not, feel free to upload and link.
Click to expand...
Click to collapse
nope, stock firmware, I've been trying to re-create the custom firmware that Velocity Micro made for it, but I'm having trouble figuring out exactly what settings they used for the kernel config. I'd like to eventually roll my own firmware image and update the device to either Éclair-2.1 or Froyo-2.2, but that will be awhile.
Until just now I'd never heard of Slatedroid, so i wouldn't know if anyone has succeeded over there or not. I've tried searching using Yahoo, Google and others to no avail, so...
here's the framework.jar, pulled from the most recent firmware update
(version 091257)
'mediafire'/?c76hrb1awmtc4mq
sorry 'bout the link being butchered, I'm a new user and it won't let me post links.
thanks in advance
Edit:I found the post at Slatedroid, but he's using a modded Cruz 102/103 Tablet firmware with Éclair-2.1, and until I get my own rom cooked, I'm going to try and stay as 'stock' as possible. besides, i don't know if the Cruz 103 firmware will work on the reader.
On another note, would it be possible to pre-mod the file in question if you were building from source?
and if so, what modifications would need to be made?
clockworx said:
Google requests a valid phone ID and phone type when assigning an Android ID. Tablets tend to have neither, so Google doesn't assign an ID. It spoofs a valid phone type and ID so that Google is happy and will send you back an ID.
Click to expand...
Click to collapse
I am working with others in another thread to determine why nootering the NC removes the access to B&N instore features.
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought? Can you share what lines in the hacked framework.jar are different that the stock NC framework.jar? Would it be possible to change these lines back to stock after nootering to gain access to the instore features?
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
nikto34 said:
We have been trying changes to the build.prop file but this does not seem to help. My thought is that something is changed in the framework.jar file that when instore B&N checks to see if the device is a NC. Is this a plausible thought?
Click to expand...
Click to collapse
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
nikto34 said:
Also, could changes in framework.jar also expalin why the market on NC does not have access to some apps?
Click to expand...
Click to collapse
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
clockworx said:
Anything is possible since we don't know what they're doing, but it seems unlikely BN would check phone type and phone ID when on a regular nook they probably both return "invalid". Before you go through the trouble of investigating deeper, I suggest taking the engineering approach and change one variable: push back a stock framework.jar and see if the store works. If it does, then it's the framework.jar. If it doesn't, then it's something else.
No, that would be the fingerprint needed in build.prop, which I thought had already been solved and was part of Autonooter.
Click to expand...
Click to collapse
Thanks for the idea! Do you have or know where to find a stock framework.jar?
As for the fingerprint issue, we have tried returning the rooted NC fingerprint back to the stock fingerprint with no success. When replicating the stock build.prop file on a rooted NC, instore features still do not work and some apps are still not available in the market.
Has anyone got swpe to work on the nook color? or is it not even allowed?
I would be willing to work on the port if I am allowed to.
once I get a nook color that is.
If I am allowed to dont expect anything soon, I need a nook, I need more java exp. I am only fluent in c++
Swype is one of the few applications which aren't allowed on xda.
Sounds ok,
Sorry for thread! you can /delete
Sign up for the beta you might get a surprise. I'm not a fan of swype and I see it as an uneeded resource hog.
V.A.T.Juice said:
Sign up for the beta you might get a surprise. I'm not a fan of swype and I see it as an uneeded resource hog.
Click to expand...
Click to collapse
I don't think they have made a compatible beta for the Nook Color.
You can cobble it together for use on NookieFroyo from the info in this thread.
There's a similar kb several others have advocated called SlideIT (in the market) but it has a really annoying autocorrect that changes what you're writing to something from it's limited dictionary.
Several others have loved it so it might be worth a try for you.
I signed up for the beta, but I keep getting the message that downloadable apks aren't supported.
A. Nonymous said:
I signed up for the beta, but I keep getting the message that downloadable apks aren't supported.
Click to expand...
Click to collapse
You need to uncheck and recheck allow downloaded apks in nook color tools. It's checked by default but like the allow compatibility mode button you have to repeatedly click it for it to actually work.
gallahad2000 said:
You need to uncheck and recheck allow downloaded apks in nook color tools. It's checked by default but like the allow compatibility mode button you have to repeatedly click it for it to actually work.
Click to expand...
Click to collapse
Press the button repeatedly to make it happy? So like most women I know? Will definitely try that when I get home. Thumb typing is cool, but Swype is cooler.
There is a hack going around that I have been playing around with that unfortunetly I have not been able to get working. It is an edit for the Build.Prop file in \system. (this does require a root and some sort of root explorer) (I've tried some of the other "hacked" APK's, but I can't deal with crappy video)
Take a quick look at this article on Reddit:
http://www.reddit.com/r/Android/comments/ha5oh/root_how_to_edit_your_buildprop_to_make_netflix/
After looking at that for a while I started tooling around.
Changes I made :
ro.product.model=Nexus S (Replacing MB860)
ro.product.model.internal=Nexus S (Replacing MB860)
ro.product.manufacturer=samsung (Replacing motorola)
So basically, this is supposed to fool the device check by making the application think you are using an accepted device. Like I said I haven't been able to get it to work. If anyone can see any other changes to make, any input would be appreciated. Hopefully we can get this working and share it with the community, until Netflix decided to come to their senses.
I've attached the Official Netflix app if anyone needs it
Already a working app..
Someone already posted a APK that bypasses the check.. there are video issues with colors, but that is the Atrix screen not the App...
also i'm pretty sure root explorer is a paid app, so posting that here violates terms and conditions
raybond25 said:
also i'm pretty sure root explorer is a paid app, so posting that here violates terms and conditions
Click to expand...
Click to collapse
Thanks I wasn't paying attention to what I was doing. I've removed it
sublimejosh2000 said:
Someone already posted a APK that bypasses the check.. there are video issues with colors, but that is the Atrix screen not the App...
Click to expand...
Click to collapse
How is it the screen? (not arguing, I just don't know)
I was hoping that this might just fix that problem
CingZack said:
How is it the screen? (not arguing, I just don't know)
I was hoping that this might just fix that problem
Click to expand...
Click to collapse
It something to do with either hardware acceleration of how the app handles teh qHD screen. the Watch ESPN app does thes same thing.
also this method is not a good idea when compared to using the modified APK, because you are editing your actual system files through this way. and as said before this has been discussed and a different way found already on this forum.
CingZack said:
How is it the screen? (not arguing, I just don't know)
I was hoping that this might just fix that problem
Click to expand...
Click to collapse
The Atrix has a higher resolution screen than every other android phone currently available. An app, especially a graphically intensive video app, has to be designed to scale up to this resolution. Not to say it can't work, just doesn't yet.
Sent from my MB860 using XDA Premium App
what can I use to modify the apk? I have the modified apk already, but I want to take a look
CingZack said:
what can I use to modify the apk? I have the modified apk already, but I want to take a look
Click to expand...
Click to collapse
if you don't already know how to modify APKs, then you're in over your head.
dLo GSR said:
if you don't already know how to modify APKs, then you're in over your head.
Click to expand...
Click to collapse
I am trying to learn, thats why I asked, and why I come to this forum
CingZack said:
I am trying to learn, thats why I asked, and why I come to this forum
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1060199
apk Manager is a start.
jimbush3 said:
http://forum.xda-developers.com/showthread.php?t=1060199
apk Manager is a start.
Click to expand...
Click to collapse
Thanks downloading right now
I had success getting Netflix to work on Viewsonic G-Tablet running CM 7.0.3.
I used the instructions posted by natemckn at reddit. As a noob, I'm not able to post links to the XDA forum (yet), so you'll need to search for the instructions on reddit or google. The post is titled "[ROOT] How to edit your build.prop to make Netflix work on unsupported devices."
Specifically, I modified these two lines in build.prop:
ro.product.model=HTC Vision
ro.product.manufacturer=HTC
Also, I moved NetFlix to my external SD card.
Rebooted, everything works like a champ.
http://forum.xda-developers.com/showthread.php?t=994974
There's already a thread discussing all of this. Please avoid duplicate threads.
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
gspitman said:
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
Click to expand...
Click to collapse
I can cook you up a straight stock rom without it. It's only an apk you can uninstall with tb
Sent from my PG86100 using Tapatalk
aray92 said:
I can cook you up a straight stock rom without it. It's only an apk you can uninstall with tb
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
gspitman said:
I don't know how many chefs read this side of the forum, but I know I'll get my hand slapped for posting this in the development side.
But now that Swype beta is available to pretty much everyone, why are we including the stock version anymore? Everyone seems to do it, and it's difficult to remove to install the beta.
It's obvious that the old version doesn't play nice with Gingerbread's text selection process, and the new version has solved that issue.
Can anyone explain why we're still including an almost useless version?
Click to expand...
Click to collapse
+1 10chars
gspitman said:
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
Click to expand...
Click to collapse
its included because its the only authorized version allowed to be distributed by the manufacturer, if the developer ( the Rom maker ) included it, swype could get pissed and ask for a take down. you need to sign up for an account and be part of the beta to get it.
so in short.. its against Swype's ToS and EULA. in order to avoid complications, rom makers dont include it
Spyderekz said:
its included because its the only authorized version allowed to be distributed by the manufacturer, if the developer ( the Rom maker ) included it, swype could get pissed and ask for a take down. you need to sign up for an account and be part of the beta to get it.
so in short.. its against Swype's ToS and EULA. in order to avoid complications, rom makers dont include it
Click to expand...
Click to collapse
That's just it, I'm not asking to include the new version... just to NOT include the old one.
The old one doesn't really work, and prevents the easy installation of the new one.
So why include broken software?
gspitman said:
Thank you, but that's not really the point. I can remove it from any ROM, just asking why we're bothering to include something that generally doesn't work with our version of the OS.
Click to expand...
Click to collapse
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
http://forum.swype.com/showthread.p...install-Swype-Swype-PreLoad-Production-Device
Edit: Instead of requesting the devs remove, write a quick script that will remove the old. Then you just need run it once whenever you install a new rom.
lyric911 said:
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
http://forum.swype.com/showthread.p...install-Swype-Swype-PreLoad-Production-Device
Edit: Instead of requesting the devs remove, write a quick script that will remove the old. Then you just need run it once whenever you install a new rom.
Click to expand...
Click to collapse
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
gspitman said:
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
Click to expand...
Click to collapse
Am I the only one who's seeing the same trend here that happened in the movie "Anger Management"?
He's only asking "Who you are." LOL
gspitman said:
Again, I know how to remove it, I know that it's possible to remove.
The question that no one is answering is WHY INCLUDE SOFTWARE THAT IS NOT COMPATIBLE WITH GINGERBREAD?
Sorry for yelling, but I'm trying to grasp the value of having the original package.
Click to expand...
Click to collapse
Woops. Meant to quote aray92, not you since he/she said only the apk must be removed.
lyric911 said:
It's not just the APK, there's a file in system/lib that needs to go too. Last paragraph:
ht tp://forum.swype.com/showthread.php?2287-Unable-to-uncheck-uninstall-Swype-Swype-PreLoad-Production-Device
Click to expand...
Click to collapse
Thank you for the link. The Swype beta always crashed for me and now I know why. I removed the files and now Swype works. Thanks!
I agree, I want to be able to install the latest swype. If I recall correctly, couldn't they make it so we could uninstall? I think that's how it was with OG Evo custom roms.
It's been removed from mine from day one.
I thoroughly inspect my ROM for every instance of software that I don't want.
gspitman said:
That's just it, I'm not asking to include the new version... just to NOT include the old one.
The old one doesn't really work, and prevents the easy installation of the new one.
So why include broken software?
Click to expand...
Click to collapse
1) It works just fine.
2) It takes 10 seconds to uninstall with TB.
3) Did you ever consider the possibility that some people may not have another version of swype?
nabbed said:
1) It works just fine.
2) It takes 10 seconds to uninstall with TB.
3) Did you ever consider the possibility that some people may not have another version of swype?
Click to expand...
Click to collapse
1. It doesn't work right.
2. Takes longer than that including removal of the lib files and a half dozen reboots to get the beta installed
3. F%#@ them. Majority wins and its a fantastic idea to remove it, let's get rid of car panel, Twitter, footprints, friendstream, stocks, htcfacebook, fm radio too
its not in my rom either
NewZJ said:
1. It doesn't work right.
2. Takes longer than that including removal of the lib files and a half dozen reboots to get the beta installed
3. F%#@ them. Majority wins and its a fantastic idea to remove it, let's get rid of car panel, Twitter, footprints, friendstream, stocks, htcfacebook, fm radio too
Click to expand...
Click to collapse
Done, agreed, done, may not play right, and maybe!
anyone got the new Swype beta? Haven't tried it out yet
Hi,
The Lenovo Android Tablet is released. It comes with the same n-trig digitizer technology as in the Flyer. It has apps with handwriting recognition such as VisionObjects Notes and maybe DocsToGo ( 5'30": http://androidcommunity.com/lenovo-thinkpad-tablet-hands-on-video-20110719/ ) which are quite handy.
It would be wonderful if our community can extract and port those apps to the Flyer (through ROM or apk). I am not in IT so I hope that the work can be done by someone here.
Cheers.
(I don't know whether the Development Forum is a correct one to post things like this. Mod please move the thread to other forums if necessary.)
We will need a leaked rom first..
nickiberli said:
We will need a leaked rom first..
Click to expand...
Click to collapse
What he said.
Oh, and a Hex-Rays Decompiler, lol.
ikingblack said:
What he said.
Oh, and a Hex-Rays Decompiler, lol.
Click to expand...
Click to collapse
Hex-Rays decompiler?
nickiberli said:
Hex-Rays decompiler?
Click to expand...
Click to collapse
Google it. People are donating so this team called iDroid can get a Hex-Rays Decompiler to put Android on the iPhone.
Maybe this Lenovo Tablet Dump will do it?:
http://forum.xda-developers.com/showthread.php?t=1252957
Edit: I just took the notesmobile_len-oem.apk and notesmobile_len-data-de_DE.apk(for german language) from the dumb.
They installed fine on my GB 2.3.3 Flyer but once I'm starting the app it ays that this version of notes mobile is not compatible with my device.
Could someone simply check if it works on a HC flyer?
Edit2: Just removed the device check... However - it still crashes right after start - anyone who wants to try my version without device check? Maybe it is running on honeycomb.
cool software.hope can get it soon
I hope someone will do it, it seems great.
Well - like I said:
I can share the notesmobile apk to anyone who is running honeycomb on the flyer.
I eventually also removed the device check.
But since I haven't moved to honeycomb yet - I can't try. :-/
Himmig said:
Well - like I said:
I can share the notesmobile apk to anyone who is running honeycomb on the flyer.
I eventually also removed the device check.
But since I haven't moved to honeycomb yet - I can't try. :-/
Click to expand...
Click to collapse
Please, do it! A lot of people have already moved to HC
Try the following:
1. Install Notesmobile_len_oem.apk
2. Install the language pack (eg notesmobile_len-data-en_GB.apk)
3. Put the two lib files in your "system/lib" folder if possible
4. Run the notesmobile application for the first time. --> If you get a "device not supported error" continue with 5.
5. Uninstall notesmobile (keep the language pack and lib files in place)
6. Install notesmobile_len-oem-signed.apk
7. Run the notesmobile app (this version should ignore the device check)
@Himmig, got FC on process com.visionobjects.notesmobile_len
I also got the same force close.
I wanna know can man use it on GB?
Sent from my HTC Flyer P510e using xda premium
Anybody tried WritePad, and another one is PenReader? It seems to be a pretty decent handwriting recognition app. It works like a keyboard, so can be used in any app. I hope it will be even much better on the Flyer with Honeycomb.
Anybody using Flyhigh ROM has been succesful to run this application?
well the problem is the following;
1. The flyer has 2 x touch film layers which work on different voltage readings. However the main touchscreen has the ability to detect both voltges, and hence why it can trigger into notepad mode when the pen nibbles touches the screen.
2. The the application itself is designed to work on a different android framework... This would need to be modified to sense.framework as otherwise they just won't compile well together. You also have to modify the application source code to accept the pen voltages instead of fingers...
Unless you want to use fingers too? If so that is another bastard in itself to set up with the pencils interface.
I've tried with SBM to see if the pen could be modified to write with it etc, and but failed, and hence I believe we need afew development to work on this.
Sent from my HTC Flyer P510e using xda premium
update your flyer to HC and buy writepad : you won't need to port this app anymore
Are people trying to get Notes Mobile to work or the handwriting recognition text input to work? Or both?
For those still getting force closes on Notes Mobile, I monitored logcat and found that you need to push the following into /system/lib/:
libMyScriptEngine.so, libMyScriptHWR.so, and libStylusCore.so
If you're running Himmig's modified apk, then it should be fine. If you're just using the apk straight from the system dump, then build.prop needs to spoof the Lenovo Thinkpad Tablet.
I've been playing with Notes Mobile on my Flyer for a couple of days, and handwriting recognition is quite spiffy. As a note-taking app, I still like HTC Notes better since it syncs with Evernote and it's just integrated better. You could export to HTC Notes from Notes Mobile though.
I actually don't know if the handwriting IME is part of the system dump. Is it there?
Thanks for the input mate... I should have looked at logcat :-/
I'll try if it works and see if the modified apk is able to surpass the device check... however - could you post your build prop modifications?