ADWLauncher Running on Adam - Adam General

Here's a video with ADWLauncher installed incase people didnt like the Notion Ink UI. It worked very well. I'm not too familiar with the settings in ADWLauncher, so bear with me for a bit.
I really hope the XDA community can help me getting the natural google experience back on this device. the hardware with PQ is really nice, Adam's Specific Programs run well, but UI is a bit beta still with some FC.
------------------------------------
update with two more videos
------------------------------------
another view demonstrating the gps error, google maps, and the gyroscope
and Notion Ink Adam's ability to handle online adobe flash applications (www.sumopaint.com)
-------------------------------------
I dont take credit for this, but the people at notioninkhacks.com and xda-developers have finally rooted Adam and installed the Android Market!

How is the touchscreen in terms of sensitivity? Also is there any give to the display when you press on it?

The screen seems very responsive. seems comparesble to the nexus one minus the screen issue
Sent from notion ink adam

Thanks for the walk though.
BTW, Appbrain uses official Android Market for access, so since it isn't on the Adam, it can't work.
Care to try applnet and or the other "alternate" markets?
-CC

How is the Pixel Qi in terms of brightness/evenness? Are the colors washed out enough to make you consider the LCD model? Thanks again for the walk-through!

Video looks good, it's the only video of the Adam that I've watched without wanting to throw up.
How're you liking the non-backlit Pixel Qi? Decent for everyday use? Or only in situations where LCD has problems (sunlight) or battery saving?

bemymonkey said:
Video looks good, it's the only video of the Adam that I've watched without wanting to throw up.
How're you liking the non-backlit Pixel Qi? Decent for everyday use? Or only in situations where LCD has problems (sunlight) or battery saving?
Click to expand...
Click to collapse
the non-backlit PQ is interesting. i dont know whether it's a good thing or bad thing long term, but for battery wise, it's a good thing. but i've been using it in color mode mostly. but with the PQ mode, the view angel are much better. I say it'll take a bit getting use to seeing things in b/w lol~~. It's like kindle but more responsive in a nutshell

What about in portrait mode? Saw some apps that you used in portrait, but what about like homescreen, facebook, twitter, etc. Was a bit saddened how the stock launcher seemed to be fixed to landscape.

I am impressed.......!!!!!!!!wow ..

is there any website in particular you used to download the .apk files
Sent from my Nexus One using XDA App

benyameen said:
What about in portrait mode? Saw some apps that you used in portrait, but what about like homescreen, facebook, twitter, etc. Was a bit saddened how the stock launcher seemed to be fixed to landscape.
Click to expand...
Click to collapse
ADWLauncher is not locked in landscape mode. the home screen can rotate. it resizes the icons and widgets and it's not too bad. facebook can rotate too, but it's rotates according to the app as you see it on your smartphone

posted some new videos for you guys

inspiron41 said:
ADWLauncher is not locked in landscape mode. the home screen can rotate. it resizes the icons and widgets and it's not too bad. facebook can rotate too, but it's rotates according to the app as you see it on your smartphone
Click to expand...
Click to collapse
Thanks for the reply and video.
The biggest worry I had about the Adam was that it would only be usable in landscape mode - this is clearly not the case =]
Just can't wait for the next round of open orders... Definitely buying...

inspiron41 : can you confirm that Adam comes pre rooted ..?
Are you able to install Super User ? Can you try VISIONary and post results here for Temp root..? or may be Perm Root..??

zabaknilesh said:
inspiron41 : can you confirm that Adam comes pre rooted ..?
Are you able to install Super User ? Can you try VISIONary and post results here for Temp root..? or may be Perm Root..??
Click to expand...
Click to collapse
i never rooted anything, but i'm following the development section carefully trying to learn as i go. i dont want to do anything to brick my device lol. i'll let you know when i figure things out

zabaknilesh said:
inspiron41 : can you confirm that Adam comes pre rooted ..?
Are you able to install Super User ? Can you try VISIONary and post results here for Temp root..? or may be Perm Root..??
Click to expand...
Click to collapse
It is not pre-rooted but rooting is work in progress:
http://notioninkhacks.com/forums/viewtopic.php?f=29&t=345
Also NI had to release a complete recovery procedure due to an issue with the first update. This procedure includes a bootloader and recovery image which should recover any bricked device.
http://notioninkhacks.com/forums/viewtopic.php?f=29&t=364

two new videos

2-finger Rotation on Google Maps
I noticed on one of your videos that the two finger rotation on Google Maps is not working. There is a file called /system/etc/permissions/handheld_core_hardware.xml that tells Android about the hardware. I don't have my Adam (yet -- 1/29 shipping -- I hope), so I can't check. However you might check if the the following permissions are included:
<feature name="android.hardware.touchscreen" />
<feature name="android.hardware.touchscreen.multitouch" />
<feature name="android.hardware.touchscreen.multitouch.distinct" />
These are needed for "independently-trackable multiple-finger multitouch," or so it says in the associated xml file (that you could alternately include if it exists in the same directory):
<feature name = "android.hardware.touchscreen.multitouch.distinct.xml"/>
Good luck.

ptok said:
I noticed on one of your videos that the two finger rotation on Google Maps is not working. There is a file called /etc/permissions/handheld_core_hardware.xml that tells Android about the hardware. I don't have my Adam (yet -- 1/29 shipping -- I hope), so I can't check. However you might check if the the following permissions are included:
<feature name="android.hardware.touchscreen" />
<feature name="android.hardware.touchscreen.multitouch" />
<feature name="android.hardware.touchscreen.multitouch.distinct" />
These are needed for "independently-trackable multiple-finger multitouch," or so it says in the associated xml file (that you could alternately include if it exists in the same directory):
<feature name = "android.hardware.touchscreen.multitouch.distinct.xml"/>
Good luck.
Click to expand...
Click to collapse
/etc/permissions/handheld_core_hardware.xml
where do i start looking for that file? on root drive?

Oops sorry, its /system/etc/permissions

Related

[FIX] Tnt mod based orientation fix for games

Weeds2000 fixed the orientation on our Folio100 to work with games like Asphalt5 and now its possible to play, although graphics are still kinda messed up. but other games like the 3d tilt works nearly perfect now too.
you might find it useful, and VEGAn mod might be able to include this as my FolioTntMod is based of the TNT framework...
Find the download patch i made for our folio in this thread.
it also include a full 360 rotation fix, if you need it
As we all share the same Tegra2 platform and can nearly swap experience here, im posting this to share the fixes weeds2000 made for us...
Hope you find it useful..
Note:
The patch i made might actually work fine as update.zip on your tablet as well, or might need minor adjust to install, but let g tablet modders fix this if needed.
at least now you know its available.
Thank you! One question - do you know what file(s) were altered for the 360 rotation fix? Was it a lib file, for example?
EDIT: Also, to any other modders looking at this, the system.img is a ext2 filesystem image, NOT a yaffs2 image.
roebeet said:
Thank you! One question - do you know what file(s) were altered for the 360 rotation fix? Was it a lib file, for example?
EDIT: Also, to any other modders looking at this, the system.img is a ext2 filesystem image, NOT a yaffs2 image.
Click to expand...
Click to collapse
Roeby wan Kanobi, is this something that could work and be added to TnT Lite? My Clockwork back up just completed
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
Click to expand...
Click to collapse
This could be another watershed update Also- with the accelerometer corrected, folks will be getting exercise by holding up the G while playing games
added:
Perhaps the one extra update that would be nice is a DSP manager so dB level or gain increases can be made. Modders released a DSP manager on the Incredible that allows increases to 3.5mm and speaker output. Hardware based EQ too.
Perhaps being too picky, but louder speakers would be nice.
Did you see.. they provided the SOURCE!!!!! This is what we need!
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Getting my dev unit ready with TnT Lite 3.1.2. There's also a new music player apk I need to test out.
Click to expand...
Click to collapse
What does the patch change? Would is break things when the application developer fixes the orientation code in their game.
We saw this problem fixed in the application in the Gallery 3D application by google, not in framework. http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html
roebeet said:
Yes, I can package it as a supplement - I just need to know what to package.
Click to expand...
Click to collapse
okay here are some details.
the framework.jar modified comes from this file: update-smb_a1002-3338-user.zip
the library should be generic, but is required for the gsensor/rotation/orientation fix as part of the new framework.jar changes.
the 2 primary folders in the framework.jar changed are /android/hardware /android/view
you should be able to easily spot the differences in filesizes..
do note: there is another change android\os\Environment.smali as i modified it to work with /mnt/sdcard and /mnt/sdcard/sdcard-disk0 and /mnt/usbdisk-disk0 for compatibility with folio mount functionality.
here is the "vold" also different but works fine with the tap'n'tap framework.
remember that /etc/vold.fstab needs changed to support the more new mount devices if you wish to use that one too.
360 rotation fix is in android\view\WindowOrientationListener$SensorEventListenerImpl.smali
orientation fix is
android\hardware\SensorManager*.smali
but again, the framework.jar is Tap'n'Tap based, so works directly on top of r3338 edition.. and i made a patch in my section with just framework + lib files included.
rothnic said:
We saw this problem fixed in the application in the Gallery 3D application by google, not in framework. http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html
Click to expand...
Click to collapse
No, as far as i understand, weeds2000 only made the hardware swap sensor reading, so now it acts like a portrait mobile phone, where our Tegra2 has the chip rotated once 90degree.
Dexter_nlb said:
No, as far as i understand, weeds2000 only made the hardware swap sensor reading, so now it acts like a portrait mobile phone, where our Tegra2 has the chip rotated once 90degree.
Click to expand...
Click to collapse
Hmm, so it does a 90 degree rotation. And the device is still a default landscape device. We definitely need to make sure there are no negative effects on games that utilize the acceleromether and worked fine before.
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Thanks for the explanation - this is something I suspected would fix it, but it's good to see that someone had pushed the idea all the way through to an actual fix.
So, I suspect that when the device boots up, it should be in portrait mode initially (until the sensor kicks in).
roebeet said:
So, I suspect that when the device boots up, it should be in portrait mode initially (until the sensor kicks in).
Click to expand...
Click to collapse
That makes more sense to me if that is true.
I read through the code ... Prior to the code change they were performing the rotation either for Acceleration minus Gy on the y-axis
or Acceleration minus Gz on the z-axis and NOT Acceleration minus Gx on the x-axis. Now the axis swap is always occurring... under all 3 conditions irregardless of sensor.
Dont know why there was an exclusion in the first place for Acceleration minus Gx on the x-axis...
When I get back I will look through the code some more...
rothnic said:
Hmm, so it does a 90 degree rotation. And the device is still a default landscape device. We definitely need to make sure there are no negative effects on games that utilize the acceleromether and worked fine before.
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Click to expand...
Click to collapse
rothnic said:
I would assume that the android developers would recommend making this change to framework, instead of handling it in applications if there weren't implications.
Click to expand...
Click to collapse
if Google didn't "invent" the different way of reading sensors, there would only be one way of doing it, so developers would not be able to see it, so an update to like 2.2 or higher is now an requirement, right? but if older games do not check, it would work with them, so this fix solves it as i see it.
putting back androidos orientation handling to its original state, as many developers should be reading it.
I have ported the fix for both TnT stock and lite. As well as Vegan beta 4.
http://forum.xda-developers.com/showthread.php?t=892345
gojimi said:
I have ported the fix for both TnT stock and lite. As well as Vegan beta 4.
http://forum.xda-developers.com/showthread.php?t=892345
Click to expand...
Click to collapse
remember its all done by weeds2000 , i cannot/will not take credits for his effort here, i am just sharing the good work done on this fix.
I have released a new version of the fix, this should clean up all the remaining issues with the accelerometer/compass. Code is also much cleaner now. Some weird hacks you may have seen were caused by the legacy API which was used by my test game.
Only known issue up to now is that the mouse coordinates are also rotated.
The source can be found in the zip file attached to the original post, I hope that all changes are prefixed with // XXX:
The source files are based on the nvidia-froyo tree.
Link:
http://forum.xda-developers.com/showpost.php?p=10209624&postcount=38
Doodle jump doesn't work. Game loads upside-down with home buttons on top. If you tilt left you go right...Any fix for this?
Does this work for the VegaN Ginger Edition, or is that fix built into the ROM, I think I am having issues with some games on that ROM.
bmw4aaron said:
Doodle jump doesn't work. Game loads upside-down with home buttons on top. If you tilt left you go right...Any fix for this?
Click to expand...
Click to collapse
I think you can write the developer and tell , that the games is not working normally.. all other games work fine, so why would one game stand out, only reason, bad programming, or misunderstanding of androidOS and orientation. maybe developer thought he should fix the "orientation" in his game on tablet, and forgot other trying to make it reverse.. so: bad programming and choice of developer..he should follow guidelines and not his ideas.

[Widget]blue neon clock done, batt. meter help needed - public dev

PUBLIC DEV
============
dont call me a windows fanboy, but I really wanted this windows widget on my phone. I have the same clock on my wall. Something to work with any clock app... I like alarmclock Xtreme.
EDIT: original .pngs attached
EDIT 2 : V1 of neon clock posted (thanks to Kaik541)
EDIT 3 : V2 attached "alarmclock xtreme with modded clock" and "deskclockgoogle" versions (below) post 11 for details
EDIT 4 : V3 (final??) attached. stand alone 1x1 clock. MicroNeonClockWidget (below) post 12 for details.
**TO DO: *****HELP NEEDED
- find artist/programmer to change neon "ring" into battery meter...
- add second hand.
View attachment 533210
EDIT: added original .png images. shouldnt be hard from here..
Unfortunately, the source images are pretty tiny (130 px by 130 px) and upscaling them creates an obnoxiously blurry image so I have included here a widget that will work (though looks a bit tiny). Push the apk to /system/app (it may work in /data/app, didn't test though) and add the widget like any other
note: the above image was created with a DPI setting of 200 instead of the standard DPI of 240, may look a bit different on your screen. also, the widget in this apk does not use a seconds hand, that's why there isn't one shown.
thanks man actually that will work perfect see screenshot of where i put it...
but i think you forgot to attach the file, thank you again
Trusselo said:
thanks man actually that will work perfect see screenshot of where i put it...
but i think you forgot to attach the file, thank you again
Click to expand...
Click to collapse
then this may not actually be all that helpful to you. I plugged it into the deskclockgoogle.apk which makes it take a 2x2 square even if the actual image isn't that big and I'm unsure of how to change it
either way, thank you.
Trusselo said:
either way, thank you.
Click to expand...
Click to collapse
no problem, just hit me that you could, of course, be using a launcher that supports resizing widgets dynamically (launcherpro plus/adw) and it wouldn't matter, so good luck with it, hope it fits your needs.
actually using launcherpro plus i was able to re-size the widget and it didnt scale the image, so i have 1x1 perfect.
EDIT: gotta love timing...
is there any way to Untie it to alarm? so i can use it with alarmclockextreme?
Trusselo said:
actually using launcherpro plus i was able to re-size the widget and it didnt scale the image, so i have 1x1 perfect.
EDIT: gotta love timing...
is there any way to Untie it to alarm? so i can use it with alarmclockextreme?
Click to expand...
Click to collapse
hmm, to be honest I have no experience with modifying market apps. I know that standard taking apart and putting back together doesn't work because it breaks the key signing. there are probably some guides on how to resign the application properly, but for now it is beyond my grasp, sorry =/
Kaik541 said:
hmm, to be honest I have no experience with modifying market apps. I know that standard taking apart and putting back together doesn't work because it breaks the key signing. there are probably some guides on how to resign the application properly, but for now it is beyond my grasp, sorry =/
Click to expand...
Click to collapse
we're all learning, thats what we're here for.
thanks again
here is a version of the free alarm clock xtreme available on the market with the above neon clock as the analog clock. remove any version installed from the market before attempting to install this and then install like any normal apk.
ok, I think I finally have something that could suit anyone's needs. Here is a widget that is permanently 1x1 (which can be scaled up with a launcher that resizes, but it looks best at this size given the resolution of the PNG's anyway, so it'd be kind of pointless). This is a modded version of this app:
http://www.appbrain.com/app/micro-clock-widget-1x1/factory.widgets.Micro available for free on the market. I have changed the name so they can be installed side by side in case you wanted multiple clocks. Unfortunately, clicking it doesn't open anything, so it's just a standalone 1x1 widget analog clock. Install like any other standard apk.
edit: wow I spent too much time on this, but now I know how to edit market apps yay learning experiences.
a few hours in a single night is fast for learning, it would have taken me at least 2 or 3 days to get there. i dont even have the sdk installed.
your work is really appreciated.
just thought of a great final feature, but it is out of the scope for me and Kaik541,
need to find an artist/programmer to convert the neon ring into a battery meter.
bump... due to |OP| update...

			
				
Wow...very nice Kaik. Great work.
sent using a phone.
very nice Kaik. a keeper.

Nook ghosting in FastMode

Hello, i installed http://forum.xda-developers.com/showthread.php?t=1906507 kernel, adn i wanted to test FastMode.
And i noticed than is useless, because i have horrible ghosting effects - it's hard to read anything in browser.
It's normal?
Shissu said:
Hello, i installed http://forum.xda-developers.com/showthread.php?t=1906507 kernel, adn i wanted to test FastMode.
And i noticed than is useless, because i have horrible ghosting effects - it's hard to read anything in browser.
It's normal?
Click to expand...
Click to collapse
The initial ghosting occurs (at least in fastmode2.apk) because the apk does not perform 1 full screen refresh after the start (yet).
Try to lock and than unlock the device after starting fastmode2.apk.
The other reason may be that you have 'NoRefresh' installed and it autostarts on boot.
Never use both NoRefresh and FastMode at the same time.Kill one or another using TaskXP (or similar apk).
Edit:
Yeah. I have checked it. Applying 1 full refresh helps a lot. (you can also try do display a white full screen image to get the same result).
If you have time you can edit the source of fastmode2.apk. I won't do this during this week for sure.
osowiecki said:
Applying 1 full refresh DOES NOT helped me.
Click to expand...
Click to collapse
I do not mean any offence but FastMode2 does the trick but with terrible ghosting. Nevertheless thanx to osowiecki
Mnurlan said:
I do not mean any offence but FastMode2 does the trick but with terrible ghosting. Nevertheless thanx to osowiecki
Click to expand...
Click to collapse
What I meant by performing a 1 full refresh :
1. you can see extensive ghosting
2. I push the lock button, the screen blinks (full refresh)
3. After unlocking there is no (a little) ghosting effect.
It would be nice to force fullscreen refresh after fast mode gets activated.
Alas, That is not an acceptable solution for me (still poorly readable), I think the only way to get the NST working with normal resolution is to rollback to factory settings and install the FW with which this mode is working.
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Mnurlan said:
Alas, That is not an acceptable solution for me (still poorly readable), I think the only way to get the NST working with normal resolution is to rollback to factory settings and install the FW with which this mode is working.
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Click to expand...
Click to collapse
"lurk moar"
stock image 1.1 for CWM
https://code.google.com/p/nst-recovery/downloads/detail?name=nook_1_1_update_cwm.zip&can=2&q=
Also..why not use NoRefresh then?
Both modes work on kernel v166.
Mnurlan said:
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Click to expand...
Click to collapse
1.1.2 FW straight from B&N
Also..why not use NoRefresh then?
Click to expand...
Click to collapse
Yes, agree, I am a "lurk more" and thank you for the link - I would never be able to find it myself. We, Russian speaking people, used to say "to make someone's nose pointed in the right direction" . The only thing is I am not sure now that downgrading the FW is the right thing to do as they say that the performance was improved in 1.2.1.
I've tried every NoRefresh I could find, even some NoRefreshToggle-debug2.apk, they seem to be having no effect whatsoever so far.
2 straygecko - link seems to be incorrect. Thank you nevertheless.
Mnurlan said:
Yes, agree, I am a "lurk more" and thank you for the link - I would never be able to find it myself. We, Russian speaking people, used to say "to make someone's nose pointed in the right direction" . The only thing is I am not sure now that downgrading the FW is the right thing to do as they say that the performance was improved in 1.2.1.
I've tried every NoRefresh I could find, even some NoRefreshToggle-debug2.apk, they seem to be having no effect whatsoever so far.
2 straygecko - link seems to be incorrect. Thank you nevertheless.
Click to expand...
Click to collapse
What do you mean by "no effect"?
You should run NoRefresh once (it starts it's deamon), then you run in the second time to get results.
By default the contrast options are set to "auto". Go to "NoRefresh Settings"->"Contrast Settings" and select "appear always".
Add shortcut to NoRefresh to 'quicknav' bar or any other place that you can always reach on the screen.
NoRefresh works only within the application that it was started with. When you change the focus to another apk, it stops.
If you are on stock kernel and 'NoRefreshToggle-debug2.apk' does not work, that means you don't have FW 1.2.1 installed.
Seems like I've now got a bricked device, neither Noogie, nor CWM can help - my PC doesn't "see" my NST anymore and I can't replace the uImage, the NST itself is working now, but this means I will not be able even to restore it to a saved image:crying:
A day later I've found out that for some reason my desktop PC ("floortop") refuses to "recognize" my NST (although "sees" it alright without Noogie or CWM), then I have managed to replace uImage on my NST using my son's laptop, yet FastMode is not working, same as NoRefresh, FW 1.2.1 (I'm positive), FastMode2 works fine but resulting view renders it useless.
Update: 26.04.2013 - NoRefresh is working, but the resulting resolution renders it also almost unusable. Just delivering my SitRep, not whining. Installed kernel 166 with CWM.
dots
I have same problem in addition dots. I tried different software versions(1.1.0-1.2.1), different root methods(nook manager, touchnooter, minimal touch) and also different kernels with all variations. But no change. Screen resolution is awful because of dots and ghosting. What the wrong?
View attachment 2413476
View attachment 2413477
View attachment 2413478
eraycr said:
I have same problem in addition dots. I tried different software versions(1.1.0-1.2.1), different root methods(nook manager, touchnooter, minimal touch) and also different kernels with all variations. But no change. Screen resolution is awful because of dots and ghosting. What the wrong?
View attachment 2413476
View attachment 2413477
View attachment 2413478
Click to expand...
Click to collapse
Same here, try many kernels.
I thought it was normal operation of this modification. Oo
Well, I'm late to the party, having generated an apparently useless post here. But I agree with you all who are underwhelmed with the screen appearance using either of these two mods. I like the sprightly Android performance of the NST in FastMode, but there really is a lot of visual "noise" on the screen. NoRefresh is even worse on my Nook. I can hardly get an image at the beginning, the screen is almost an all white overlay so the contrast buttons don't do me any good because I can't see much through the white film (sort of like a bad cataract!). Scrolling a bit gradually brings in a fractured image and by the time the app has closed.
I've tried disabling the NoRefresh app entirely to see if FastMode would work better. No deal. Same poor image quality. Nothing like some of the YouTube videos I've seen.
FW 1.21, kernal 166.
But who knows? At least multi-touch is nice.

[Q] Used the wrong method

I just bought a new nook simple touch and had assumed it would come with version 1.2.1 so I followed the instructions from this article on MakeUseOf.
As it turns out my Nook was on 1.1.0. Rooting seemed to go fine but I don't seem to have multi-touch. I haven't tried the 174 or 176 kernel instead taking the recommendation and using the one that jptiger put together in this thread.
So my question is: did I screw this up by not upgrading to 1.2.1 first? If I go to settings it still shows the software version as 1.1.0 even though I've rooted. How can I ensure I've got the latest/greatest kernel?
EDIT: Ok, I upgraded to 1.2.1 and then rooted again. Multi-touch still doesn't seem to work for me. Did I miss something?
Do you have the right kernel? (I've lost track of them.)
Did you modify /system/etc/permissions/required_hardware.xml:
Code:
<feature name="android.hardware.touchscreen" />
[b]<feature name="android.hardware.touchscreen.multitouch" />[/b]
Renate NST said:
Do you have the right kernel? (I've lost track of them.)
Did you modify /system/etc/permissions/required_hardware.xml:
Code:
<feature name="android.hardware.touchscreen" />
[b]<feature name="android.hardware.touchscreen.multitouch" />[/b]
Click to expand...
Click to collapse
I do have both those lines in my required_hardware.xml file. As for the kernel, I read on another forum that this was the latest/greatest.. if there's another recommendation I would love to have it!
Thank you!
Hmm.. I wonder if it actually works but it's not supported in the default browser app or Opera Mobile. Possible?
Yes, that's possible.
Load UsbMode.apk from the signature.
Among the things it does, it shows you touches.
Just touch anywhere that isn't buttons.
(On my cell phone, it will show that it tracks 5).
I installed your app and when I touch the screen two places I see that it's captured and two sets of coordinates show up.
But when I use an app like reddit is fun I can't zoom in on images or anything although this works with the same app on the my Nexus 4.
It's obviously not critical but it's confusing me as to why it registers in your app and yet I can't seem to use the functionality. Bad choice of kernel?
UsbMode is just showing what should be available to any app.
Are you certain that the exact same apk is running on both devices?
I don't know that application at all.
Renate NST said:
UsbMode is just showing what should be available to any app.
Are you certain that the exact same apk is running on both devices?
I don't know that application at all.
Click to expand...
Click to collapse
Most likely different versions of the same app. Also it turns out I had Opera Mini installed instead of Opera Classic. The latter supports multi-touch zooming just fine so it's definitely an app level issue. Mystery solved - thanks for the guidance!

New Ultra headed my way!

Should have it by the 17th. Really looking forward to it.
There looks to be a lot more info here on Remix in general ...looks good! ?
One thing is I am hoping for is a way to safely increase the ram. Seems I read that the Ultra is already rooted, so hopefully there is an easy way to do this!
OH... The Ultra is on sale at Amazon for $199 ...says it includes keyboard! Sweet!
?
It's not rooted. But its easy to flash a custom recovery and install the su binary.
BamaPanda said:
Should have it by the 17th. Really looking forward to it.
There looks to be a lot more info here on Remix in general ...looks good!
One thing is I am hoping for is a way to safely increase the ram. Seems I read that the Ultra is already rooted, so hopefully there is an easy way to do thd
OH... The Ultra is on sale at Amazon for $199 ...says it includes keyboard! Sweet!
Click to expand...
Click to collapse
If you can find the Cyanogen Mod recovery then you can download the supersu from the market. Boot into recovery and then apply the supersu as an update. Once done you cannot get OTA updates, but supersu lets you unroot and then you can repeate the process of replacing the recovery and rooting. Very easy to do and much easier than using other root tools out there.
Got it early. Ordered Friday... delivered Monday.
Already updated to 2.0, which changed the settings app. Then the mouse stopped working on the keyboard, so I may be looking to reset the tab and start over... not that big of a deal.
Unless someone chimes in here with an idea to get the trackpad working again.
Neat tab. Made a video I may post later.
Thanks for any helpful input.
Reset the tablet, all is well for the trackpad.
So this is supposed to be a multi-tasker, but for the life of me I cannot find the feature that was on version 1.5 ....the ability to have phone sized windows.
Where did that feature go? Anyone know?
Thanks.
BamaPanda said:
Reset the tablet, all is well for the trackpad.
So this is supposed to be a multi-tasker, but for the life of me I cannot find the feature that was on version 1.5 ....the ability to have phone sized windows.
Where did that feature go? Anyone know?
Thanks.
Click to expand...
Click to collapse
Try under settings / applications and see if open in full screen mode is checked.
tomlogan1 said:
Try under settings / applications and see if open in full screen mode is checked.
Click to expand...
Click to collapse
Thank you. I found it and it is un-checked.
I have since found a few apps, like calculator and another I installed ...Ccleaner, do open in smaller or larger windows, and can be moved about on the screen.
Still none of my larger apps, that I use for business ...like Polaris, seem to have any options to change.
I am thinking I am going to have to carefully check my apps and look for those which may work and fit with the Remix multi windows setup. So far there are not many.
Not quite what I expected, but I will keep working with it.
Thanks again!
I mentioned this in another post here. It applies to version 2.0.
The way to determine if the app being used can be brought down to a phone sized/smaller window is to swipe down with your finger from the top. To the right will be the option to expand or contract the app. Works on some apps, not on others, but at least now I know where the option is.
Hope this helps.
App Freezing
Anyone having problems with apps freezing, mouse still working, but cant scroll or select on apps.
Giving me trouble in facebook messenger and google drive
oh yeah. i have to hard-reboot mine at least once a day. video is usually the culprit, specifically youtube.
support didn't have any advice so i've just gotten used to it.
Its an ongoing problem. Video is the first notification of it you'll notice, but I've seen it in games too, specifically Alto's Adventure and The Room 3.
According to the errors I've captured with logcat its an issue caused by the nvidia drivers.
yes, i have noticed that in logcat too. is it that NVIDIA is not meant to work with android? surely there are other android devices on their chips... it is so frustrating.

Categories

Resources