I know the viewsonic g tablet has a 1.3mp camera but anyone know the manufacturer of it? Is there a pic that can show some identifiable markings on there? There can't be that many manufacturers of these little guys.
dobah said:
I know the viewsonic g tablet has a 1.3mp camera but anyone know the manufacturer of it? Is there a pic that can show some identifiable markings on there? There can't be that many manufacturers of these little guys.
Click to expand...
Click to collapse
Here's some pics I took of mine awhile back. Hope this helps you on your quest.
https://dl.dropbox.com/u/25883802/camera pics.zip
Thanks for the pics. In the link below, there are some references about the camera. Specifically the manufacturer and the model number with a nice reference page.
http://www.slatedroid.com/topic/29039-rom-13-beta-ics-40x-team-drh-update-070212/page__st__2720
Another link was for linux kernels with a specific line in mind.
m5602 - ov9650: Add CIF mode (commit), add QVGA mode for the ov9650 sensor (commit)
http://kernelnewbies.org/Linux_2_6_29
Another link that came up is the one below and a file named s3c2440camera-r5.tar.gz which I don't know what to do. It has been maybe a decade since I have last compiled a kernel and that was for x86. Coding/compiling isn't my strong point so I'm staring at a file that I don't know what to do. It would be nice if I could insmod a module in and the camera would magically work but that just isn't the case.
http://code.google.com/p/s3c2440camera/
dobah said:
Thanks for the pics. In the link below, there are some references about the camera. Specifically the manufacturer and the model number with a nice reference page.
http://www.slatedroid.com/topic/29039-rom-13-beta-ics-40x-team-drh-update-070212/page__st__2720
Another link was for linux kernels with a specific line in mind.
m5602 - ov9650: Add CIF mode (commit), add QVGA mode for the ov9650 sensor (commit)
http://kernelnewbies.org/Linux_2_6_29
Another link that came up is the one below and a file named s3c2440camera-r5.tar.gz which I don't know what to do. It has been maybe a decade since I have last compiled a kernel and that was for x86. Coding/compiling isn't my strong point so I'm staring at a file that I don't know what to do. It would be nice if I could insmod a module in and the camera would magically work but that just isn't the case.
http://code.google.com/p/s3c2440camera/
Click to expand...
Click to collapse
haha dream on about the insmod. We have the proper drivers for the gtab camera. We are missing the interface between these drivers and the hardware. This is the part that NVIDIA has kept closed source.
Related
Ok I know in the General thread we have a bounty page, that's fine but there needs to be a discussion on exploits and technical issues not hope and rainbows.
If you have any information on what was tried and what seemed to half work we need to put it on here but lets be organized about it.
<format>
<Exploit CVE>
<Date Tried>
<Results>
<Fail, Success, Re-Visit>
I just got my phone Friday and I have no idea on any of the specs, Kernel, ArmVersion ..etc that a Root Dev would need. So until I know what Kernel we are on I couldn't search CVE exploits (Even thought they are know exploits) so neither could a Dev from another forum.
I know its said every time but DONT FEED THE TROLLS it gets annoying to have to parse through 5 pages of *****ing. These Devs do this for little to nothing and they deserve our respect to at least be civilized.
Info Needed
What boot setps does this phone have?
I know ADB is part in the beining and someone mentioned that it is quickly locked. I know that the reason for the ADB at the boot is to check the sdcard for any updates so if flooding a card with mass amount of data to slow down that process could a shell at that point gain temp Root to pause and gain control over the protected memory sections?
Kernel V
What CMD's are even in the damn thing
Like I said I am not an experienced Dev by no means but am willing to jump in and test or try to assist.
Someone that has an IRC server would be nice if we could have rooms setup for Devs and help for the ones that just come in with the phone, I know I had a heart attack when I bootlooped mine after a botched recovery install. I still don't know what the thousand different modes are in the pre-os boot are or do so Help rooms would be great.
Let's work together instead of posting how no one loves us and the chatter is dying down, I am sure that there isn't a Droid made so far that hasn't been rooted and if so no respectful Dev will leave it alone until it is. Its a pride thing that we have an open source device that Corporate Capitalism tries to lock down.
Pardon the rant but got to light a fire..Let get full Root.
SORRY FOR THE FALSE HOPE....OOPPS
Change the title of this thread...
Elite49 said:
Change the title of this thread...
Click to expand...
Click to collapse
+1000000000
Sent from my DROID X2 using xda premium
Nothing wrong with the title. I will be back later with any information I can find
ashclepdia said:
Nothing wrong with the title. I will be back later with any information I can find
Click to expand...
Click to collapse
Title makes it seem like this is a BLoader unlock...
I don't have any answers to the questions in op yet although im not sure if this means anything useful so I figured id post it. I found it in a file from an x2 dump don't know if it means much but here it is. It was right in the middle of a larger file . Probably isn't much help buy ::
###### MAIN ROUTINE ######
bootmodeProp=`getprop ro.bootmode`
case $bootmodeProp in
"factory")
;;
"dev")
;;
*)
# Disallow unless the debug MBM is being used. This is
# critical to the security of the device.
#echo "Permission denied: ro.bootmode=$bootmode";
#exit 1;
;;
What file is it and where is it located in the filesystem?
Sent from My DroidX²
DAG425 said:
What file is it and where is it located in the filesystem?
Sent from My DroidX²
Click to expand...
Click to collapse
It was in system/bin and the file name us qbp-port-mgr
I also noticed that the file is not in my current system when I looked for it.
I also so a file about using permission DIAGNOSTIC or something to that effect which said diagnostic permissions were for manufacturing and carrier only but the way I read it I thought it might be a vulnerability mabye? Will try to find
In system/permission folder file platform.xml it reads this along with a LOT more(and in the first few lines it mentions android open source project ))
<!-- RW permissions to any system resources owned by group 'diag'.
This is for carrier and manufacture diagnostics tools that must be
installable from the framework. Be careful. -->
<permission name="android.permission.DIAGNOSTIC" >
<group gid="input" />
<group gid="diag" />
</permission>
Also says in beginning " <!-- This file is used to define the mappings between lower-level system
user and group IDs and the higher-level permission names managed
by the platform.
Be VERY careful when editing this file! Mistakes made here can open
big security holes"
My apologies if it's all useless info
I have just noticed these files are either nonexistent on my phone right now ir are VERY different in my current system.
The files in the dump I am reading are dated back in may.
No ? is a dumb ?
ashclepdia said:
My apologies if it's all useless info
I have just noticed these files are either nonexistent on my phone right now ir are VERY different in my current system.
The files in the dump I am reading are dated back in may.
Click to expand...
Click to collapse
Don't be sorry to offer what you see as possible information,sometimes a fresh set of eyes is what is needed.
So if you think that your post will be stupid or a bother don't you may never know that could be something that leads to what we are looking for.
Now do search the thread and see if it has been looked at before as to not re# old subjects.
And as for the title I made a syntax error and didn't put [project][no root yet] and it looked like I had the answer.
SwiftLegend said:
Title makes it seem like this is a BLoader unlock...
Click to expand...
Click to collapse
Umm How Do You Figure The Title PROJECT Means A Finished Product?
"Project n. a specific task of investigation"
MikeJ92YJ said:
Umm How Do You Figure The Title PROJECT Means A Finished Product?
"Project n. a specific task of investigation"
Click to expand...
Click to collapse
I didn't have it set that way when I first posted imagine [Title]-[Project no root yet]=Oh **** its done...My Bad
Wondering if anyone has seen this yet and id it could help with anything. Even if it would only help in making our phones run better.
http://sourceforge.net/projects/mb870.motorola/files/Droidx2_VZW/DTN_14.8/
Can anyone explain to me (in pm if it this is way off subject) what would be done with these open source files?
The Kernel that is assigned to my phone is listed as : [email protected]#2, the build thats on site is showing was the 2.2 build but the odd part that im seeing in some of the files is where its referring to a TI OMAP 3 chip which is only in the Droid 3 and Bionic, I'm going to look at some more and see what i can catch.
singlesword said:
The Kernel that is assigned to my phone is listed as : [email protected]#2, the build thats on site is showing was the 2.2 build but the odd part that im seeing in some of the files is where its referring to a TI OMAP 3 chip which is only in the Droid 3 and Bionic, I'm going to look at some more and see what i can catch.
Click to expand...
Click to collapse
if you go up a directory they also have one for 2.3.4 which isnt on the x2 yet which is kind of confusing
This is very true, last night i was talking a friend of mine that works for moto (sale's guy), which he said that there is supposed to be a patch coming out next month for the rebooting and signal issue. The info i get from my friend I take with a pinch of salt tho.
singlesword said:
The Kernel that is assigned to my phone is listed as : [email protected]#2, the build thats on site is showing was the 2.2 build but the odd part that im seeing in some of the files is where its referring to a TI OMAP 3 chip which is only in the Droid 3 and Bionic, I'm going to look at some more and see what i can catch.
Click to expand...
Click to collapse
I believe bionic is omap 4430 tho...
I didn't find much activity after gingerbread was released tho it seems around the date it started being pushed activity stops unless im missing something.
I am gonna search more after im done work and see what I can come up with. Might stop by my sisters so I can look at it on a computer and dive deeper
Hopefully it can point us to something somewhere lol
gnuworldorder said:
if you go up a directory they also have one for 2.3.4 which isnt on the x2 yet which is kind of confusing
Click to expand...
Click to collapse
Hmmm..prerelease maybe? For a dev maybe? I will look farther...
So while digging around the sourceforge site, i found http://sourceforge.net/projects/mb870.motorola/ which allows to download the kernel but for some reasons, I'm having issues with viewing this document, also i was able to find another build listed as 2.3.4 ( http://sourceforge.net/projects/mb870.motorola/files/Droidx2_VZW/DTN_117.15/ ) and from the link before was showing the build of 2.2 which we once had, currently my computer is giving me major issues with viewing these files, maybe because i'm running linux as a VM i dunno yet but im going to try and fix that problem so i can view some of this, but figured that maybe someone on here could look also.
Hi,
I have found a driver for our digitizer, on the Cypress webpage, and I think it is the full 10 finger driver.
There is a .c and a .h file. What are they, and what should we do to make it working?
I upload them in attachments.
hdavid1 said:
Hi,
I have found a driver for our digitizer, on the Cypress webpage, and I think it is the full 10 finger driver.
There is a .c and a .h file. What are they, and what should we do to make it working?
I upload them in attachments.
Click to expand...
Click to collapse
nice find.but you have to wait for more devs to get interested in NEO
Well that is a very nice find but I don't think it's very useful yet, until someone finds a use for it, keep the files handy though just incase they are inaccessible when the time comes to having a use for them
Hello everyone, in trying to find a thread I saw about 2 weeks ago about changing your build.prop to have gameloft games be playable that normaly aren't on the E3D. I don't remember exactly where I had seen it but I've looked for it. Maybe someone remembers the thread and can post me a link for it. Thank u in advance. I know there is one in the games section of Android but its for arm6.
http://forum.xda-developers.com/showthread.php?t=1338181&highlight=gameloft
Thanks ekz13 but that's not the one I'm looking for. The one I remember had changes to the script that where way longer. I remember something about changing the device to LG Optimus.
I thought that was the one to change it to the optimus one. I don't remember seeing another though.. gl finding it, post up a link when you do please
ekz13 said:
I thought that was the one to change it to the optimus one. I don't remember seeing another though.. gl finding it, post up a link when you do please
Click to expand...
Click to collapse
Yea I hope someone else remembers it. I think it was in the EVO3D forums but I looked in there and even went back as 10 pages of posts and still nothing...maybe I'm just missing it. I'll keep looking but I also hope someone finds it too or stumbles upon it, cuz I really wanna play Sacred Odyssey If anyone has gotten it to work on the E3D, how did u do it? Thank you peeps
SilverSuperman said:
Yea I hope someone else remembers it. I think it was in the EVO3D forums but I looked in there and even went back as 10 pages of posts and still nothing...maybe I'm just missing it. I'll keep looking but I also hope someone finds it too or stumbles upon it, cuz I really wanna play Sacred Odyssey If anyone has gotten it to work on the E3D, how did u do it? Thank you peeps
Click to expand...
Click to collapse
From a android market developer's point of view there are really only two ways the market allows the developer to explicitly filter out devices for their application:
1) by specific build model of the device
2) by screen resolution support
the /system/build.prop supplys the information the Market uses. if you have a konwn good device that supports these games, such as the LG Optimus, you would only need a copy of the LG Optimus build.prop file in order to mimic.
if it was me personally, i would suggest changing the fingerprint to make the lg optimus first, wipe market cache, reboot and see if it appears in the market. if it doesn't, then i'd look into screen settings, but i think most filter by device as that is the easier of the two to manually control/adjust in the developer market console.
as a side plug, my app, build prop editor, makes it very simple to edit the file from android mode, along with maintaining backups/restoring and switching between them!
hope that helps take a bit of the mystery away!
Hi all,
I have been using afreechart to get some charts in an app I have been trying to develop (very very slowly). However I noticed that, when I plot a XYLineChart, the lines for each data series do not show up in the legend. See attached image. It seems odd, as it can get the info about the series, such as the name, but it does not display the line. Has anyone bumped into this? Any idea?
Cheers
what is odd is that I installed the exact same app with the exact same code to generate the graphs on a phone running GingerBread and the graphs and legend showed up exactly as expected, while they misbehave on ICS or JellyBean. Oh well it seems like nobody has any experience with this library. I tried to contact the devs of this library and got no response or support, so maybe it is time to consider a different way to display my graphs.
Cheers
Questions should be asked in Q&A forums, not Development forums.
Thread moved.
Archer said:
Questions should be asked in Q&A forums, not Development forums.
Thread moved.
Click to expand...
Click to collapse
I stand corrected. My apologies :good:
I am not sure if this is any use to anyone, but I found the solution and I thought I'd post it here for future reference.
The thing that pointed me in the right direction was the fact that the graphs would behave perfectly on the emulator, independently from what version of Android the emulator was running. That made me think that maybe the hardware acceleration (which if I am not mistaken was introduced with HoneyComb) had something to do with this. A bit of googling showed me that other graphics libraries had similar issues on ICS and JellyBean, so I tried switching off the hardware acceleration for the chart view:
Code:
chartView.setLayerType(View.LAYER_TYPE_SOFTWARE, null);
lo and behold, the graphs and the legends show up just as expected on any device.
Hope this saves some time to someone in the future.
Cheers
maurimauri29 said:
I am not sure if this is any use to anyone, but I found the solution and I thought I'd post it here for future reference.
The thing that pointed me in the right direction was the fact that the graphs would behave perfectly on the emulator, independently from what version of Android the emulator was running. That made me think that maybe the hardware acceleration (which if I am not mistaken was introduced with HoneyComb) had something to do with this. A bit of googling showed me that other graphics libraries had similar issues on ICS and JellyBean, so I tried switching off the hardware acceleration for the chart view:
Code:
chartView.setLayerType(View.LAYER_TYPE_SOFTWARE, null);
lo and behold, the graphs and the legends show up just as expected on any device.
Hope this saves some time to someone in the future.
Cheers
Click to expand...
Click to collapse
thanks a lot man. that line of code was exactly what I was needed.
Hey all, I'm not actually sure where to post this, so I'll give this subforum a shot. I'm a hardware guy. I don't develop, but I need some guidance on my research topic so I'm turning to those of you who know what I don't.
I'm working with a software deveopment board based around the Snapdragon II and I'm performing some tests on it. At the moment I can't divulge the nature of the tests, but I can tell you that I'm working specifically with one of the cameras. During my tests, I am monitoring the board via a serial connection and ADB, and I see errors pop up and the camera application crashes. I've uploaded a screenshot of the ADB output for those of you who are interested, but since I'm new, you can't see it. PM me if you want to see it.
My question is this: How would I go about figuring out where these errors came from? I'd like to know if this is a driver issue, an application issue, a kernel issue, or something else.
Thanks for looking!