Related
EDIT:
Magister2k7 said:
Please update first post of a thread, as Mer should run X with a latest kernel from git.
You just need to disable FB_MSM_DOUBLE_BUFFER ("Enable MSM Framebuffer double buffering") and enable framebuffer refresh thread.
Click to expand...
Click to collapse
Yeah, I kinda doomed myself from the start with how I structured this post. I'll restructure it later to be more able to show you good information.
Old start:
Mer is a more community-led version of the Maemo phone and internet tablet operating system. See http://wiki.maemo.org/Mer/ .
I was in contact with a member of that project (Stskeeps on freenode#mer), who gave me some information about porting this to phones such as the kaiser. He and I thought it would be a great way to benefit both communities (we get a good, not google-owned linux-based os for our phones, they get developers helping them make mer better). We also agreed that it would take a bit of effort.
First of all, Mer is completely designed for landscape-only, 800x480 phones at this point. It has been run well at 640x480, but that's still 4 times our native resolution, and 2 times what we can fake without crashes. The resolution problem is easily fixed by skilled theme-makers. The landscape/portrait problem should be fixed soon, given that the upcoming n900 will be a portrait/landscape phone. He said wait for the maemo conference for more on that.
The other problems we might hit basically are just the standard problems of molding the userspace around the kernel (get a phone app working, get the modem to work, etc.).
If you are serious about helping, please come to #mer and/or #htc-linux on freenode. At this point, the mer folks are probably more help to what we need to do.
INSTRUCTIONS:
At this point, quite literally nothing works, but it all almost works. Here's what I did to get that far:
1. Partition your sd card into two partitions, and make the second one ext2.
2. Unpack (with the -p option of tar) the rootfs (http://wiki.maemo.org/Mer/Releases/0.16testing , pick the q5 rootfs) to the ext2 partition. Make sure that it's not in any subfolders, but as the root of the drive.
3. Grab a zImage (or build your own) using the instructions we had in place from android. Put it on the fat side.
4. Set up HaRET on the fat side - Use a default.txt from android, get rid of the initrd, get rid of your ppp stuff (for now), and add "root=/dev/mmcblk0p2 rootwait" to the kernel cmdline.
5. mknod /dev/fb0 c 29 0 (this was my number, check using the terminal in android, cat /proc/devices for the major, and /proc/fb for the minor). Also make sure that it's within the root, not on your disk .
That should boot, giving you a ton of messages about an "incorrect resolution png" or something - that's the splash screen unable to load. Simply rename /lib/init/splash-* (two files) to something else. Once you get a terminal later, there's an actual package to remove, but this lets it go a bit further.
You also need to keep X from starting at this point - all it does is hang. I have not yet done this myself, but it should be an initscript that you just un-link.
EDIT: It wasn't X that caused the issues. It was the combination of failed splashes and consolefont. Comment out the lines with "splash" in them in /etc/init.d/check{fs,root}.sh, and re-run.
I do not know if X actually fails - doing that test now.
EDIT: hitting framebuffer issues... no X yet.
So, if you're adventurous, and preferably a dev at this point (this is completely useless to users), please try this out and make it better!
Okay, just a note: the password is "rootme".
First reply!
this is relevant to my interests. I'll take a look. I remember seeing that Maemo was made on top of Gnome. Do you know if there's a chance to get Debian apps on here? That's the big thing for me to get me working on it-- some type of desktop compatibility. Having an X-server is perfect. Looks like you're saying the resolution issue is purely theme based? How open are the devs for it for suggestions and feedback?
2nd reply
This does sound cool
already made some read about this in the new nokia n900..
its cool.. it free.. but i dont like the ui :\
lets see where this goes.. but.. for now.. for me... android (L)
Ok, just saw it's Jaunty based which is what I've been looking for in a phone.
Is there a list of features/bugs/issues and what's been developed so far? Seems like if the kernel brought to us in part by dzo will work maybe it won't be so hard to get wifi and other features working. A list is good.
I'll admit I haven't put much effort into it, but at this point X won't work, for one thing - probably have to change the resolution in a config somewhere.
Indeed, most of the hardware should be fine - I imagine, for example, once we are able to load the firmware, wifi should be good. Some code will have to change (a few things are built android-specific in the kernel), and some of the RIL stuff especially (phone, data, etc.) will have to be ported by someone who has that code and some time.
Indeed, Mer is Ubuntu-based, and so, according to their site, 95% of ubuntu apps should work perfectly. This is really nice for getting software on (aren't just limited to any applications in an app store or market.).
At this point, all we need to do is everything .
I'm going to try now to disable X and see if I can't get a few more things working.
EDIT: in response to your question about how open the mer-folk are to suggestions? The idea that I got from talking to them was that they are more than happy to get this extra help, and since they are trying to bring this to more devices, they are willing to put up with our requirements, to make this more readily available in general.
Alright, as I edited, I got some more success.
By removing the splash calls and the X starting, I can get a terminal. I edited the /etc/shadow file to have a password that I knew for root. Now, I can log in as root on the console (/dev/tty1).
I tried to start X, and I'm getting some strange framebuffer errors.
I'll keep you posted.
Wow, if we could get this working, it'd be sick! Thanks for posting, formatting now.
with all the hard work already done for the Android port, seeing devs being interested in Mer is REALLY PROMISING! Waiting for Google to open up Android even more, is frustrating...
Porting Mer and thus having a REAL linux (kernel+software stack) is what we need to leverage the dev capacity of the great XDA community. At least, this is what I feel like .
Owning both a Kaiser and 2 N800s, I'll probably try out the stuff posted here... I was keeping an eye on Mer for my N800s anyway, but using it on the Kaiser is more triggering
so devs, have courage and good luck!
Frame Buffer and X server
Unfortunately I've been quite busy lately and haven't been following the Android development as closely as I would like. (I don't think I've updated my git repo for months)
If I remember correctly, the frame buffer code in the kernel wasn't finished. That would prevent X from running. Can anyone say whether that was completed? I just wanted to mention this in order to avoid people wasting their time if it is in fact the problem.
It would be great to *eventually* see X running with hardware acceleration, can anyone point me to info about how DZO got that working? Was it reverse engineered, or did he figure out how to make some binary blob happy?
It will be nice to have some choice of Linux based distros the Kaiser and Vogue. Keep up the good work everybody, I appreciate it!
-Mysteryvortex
I've been looking at the n900 for quite some time just waiting for its release to the US next month. I know nothing about developing but I am very excited about this one, and I hope that there is a quick start to the apps that are put out for it. I was curious myself as well at how this would port to the kaiser so I could get a good hands on before I went and bought one. I would be more than happy to be a tester. I bought an iphone cause cause the little green guy is really starting to piss me off and my tilt's about to give up the ghost. I quickly gave it to my wife as the signal strength and battery life just sucks so I hope this maemo can give me what I want
mysteryvortex, Android does not use an X server at all. This was my disappointment when issues arose trying to run Ubuntu in a chroot. This is different though. We should be looking at troubleshooting the X server as top priority I think. The rest should flow. Bear in mind the kernel for Android, like I said, has nothing to do with X compatibility since Android uses its own display so the kernel should need some serious work.
poly, is the build you linked to hardware specific? Looks like a generic one. If so, then the only outstanding difference should be the kernel and if that's the case we should be able to use this on any phone we happen to have a kernel for right?
enatefox said:
mysteryvortex, Android does not use an X server at all. This was my disappointment when issues arose trying to run Ubuntu in a chroot. This is different though. We should be looking at troubleshooting the X server as top priority I think. The rest should flow. Bear in mind the kernel for Android, like I said, has nothing to do with X compatibility since Android uses its own display so the kernel should need some serious work.
poly, is the build you linked to hardware specific? Looks like a generic one. If so, then the only outstanding difference should be the kernel and if that's the case we should be able to use this on any phone we happen to have a kernel for right?
Click to expand...
Click to collapse
The build has a kernel and stuff, but don't use it. Use the regular stuff from android (or build yourself from htc-vogue).
mdrobnak from irc got mer up on his raph - thanks to the vga screen, with a quick kernel patch and some xorg.conf modification, he got X working great.
Within the next few days, I'll do some tests of the data connection and such.
enatefox said:
mysteryvortex, Android does not use an X server at all. This was my disappointment when issues arose trying to run Ubuntu in a chroot. This is different though. We should be looking at troubleshooting the X server as top priority I think. The rest should flow. Bear in mind the kernel for Android, like I said, has nothing to do with X compatibility since Android uses its own display so the kernel should need some serious work.
Click to expand...
Click to collapse
Yes, that's correct. Android doesn't use X. Many, many months ago, it was mentioned that the framebuffer in the Vouge/Kaiser kernel (which X will use) was broken. Nobody was planning to fix it since Android doesn't need it. I was just trying to point people who have time to work on supporting our phones in the right direction.
poly_poly-man: Looks like the Raphael kernel is being developed on another branch, but it sounds like the FB patch helps us?
-Mysteryvortex
poly_poly-man,
I have setup my second partition of sdcard to 512MB and extracted there Mer preserving permissions.
What I did also is to modify the x config and change resolution and also resize the Mer-logo.jpg so it fits.
After I tried to boot I went successfully through all steps (at least I think so) and a blank screen appeared to me.
Can you tell me what was the parameter to output the Haret boot sequence to a file, so I can check what passes and what fails?
Another question: The following "mknod /dev/fb0 c 29" have to be performed on root of second permission, right? If so I think the command should be ""mknod ./dev/fb0 c 29", am I correct?
Regards,
Borkata
Borkata81 said:
Another question: The following "mknod /dev/fb0 c 29" have to be performed on root of second permission, right? If so I think the command should be ""mknod ./dev/fb0 c 29", am I correct?
Click to expand...
Click to collapse
'./dev/fb0 c 29' does only work if you are in "/" (root of the filesystem) otherwise (and in all other cases) 'mknod /dev/fb0 c 29' is correct.
bye...
Borkata81 said:
poly_poly-man,
I have setup my second partition of sdcard to 512MB and extracted there Mer preserving permissions.
What I did also is to modify the x config and change resolution and also resize the Mer-logo.jpg so it fits.
After I tried to boot I went successfully through all steps (at least I think so) and a blank screen appeared to me.
Can you tell me what was the parameter to output the Haret boot sequence to a file, so I can check what passes and what fails?
Another question: The following "mknod /dev/fb0 c 29" have to be performed on root of second permission, right? If so I think the command should be ""mknod ./dev/fb0 c 29", am I correct?
Regards,
Borkata
Click to expand...
Click to collapse
It seems that even set to the right resolution, our fb does not work with X. Needs more patching than just the patches I got from the other branch. We may need to move up to the other branch, I'm not sure.
the /dev/fb0 should be replaced with /path/to/sdcard/root/dev/fb0, of course. And it's better to just get rid of all the splash references - that way, you don't get the blank screen issue.
toasty_ said:
'./dev/fb0 c 29' does only work if you are in "/" (root of the filesystem) otherwise (and in all other cases) 'mknod /dev/fb0 c 29' is correct.
bye...
Click to expand...
Click to collapse
Yes, but poly has written that user have to be in root so that was what I have asked
Question: our fb driver is msm_fb?
poly can you share which patches you tried from raph branch?
Borkata81 said:
Yes, but poly has written that user have to be in root so that was what I have asked
Question: our fb driver is msm_fb?
poly can you share which patches you tried from raph branch?
Click to expand...
Click to collapse
Oh yes, you're right. I should first read the full post before answering questions that havn't been asked
Borkata81 said:
Yes, but poly has written that user have to be in root so that was what I have asked
Question: our fb driver is msm_fb?
poly can you share which patches you tried from raph branch?
Click to expand...
Click to collapse
http://people.openezx.org/tmzt/
the msmts and vres patch. Didn't work, because there are more problems in our older kernel.
I'm interested in finding out why we aren't on 2.6.27 already...
A couple of weeks ago, I picked up a used G1 from craigslist, and I really like it. However, I was disappointed to find out that it won't work with my university's WiFi system. I did some searching and came up with issue 1597 on the android google code page (apparently I can't post a link yet). Post 45 on that thread explains the fix, and since it seems fairly easy to apply to the Android source and google won't release it for who knows how long, I decided to do it myself. However, getting it onto the device has been a real problem. These two threads (which I can't link to either):
t=476563 and t=629551
lead me to believe that I can essentially compile the android source, push the new framework.jar to the device, and the fix will be in place.
I eventually got it to compile, but when I try to install it, It just hangs on the G1 screen. I've tried building it on Ubuntu 9.10 and OS X Snow Leopard using the sources from 2.1 and 1.6 and installing it on King Eclair and BlueMagic Donut (the stock firmware lasted maybe 6 seconds after I got it), and I'm getting the same results, even if I just build the source unmodified. I've probably tweaked and recompiled it 20 times now, and am about ready to lose my mind. I think every time I've gotten at least one error from certain jni libraries not compiling properly, but I've assumed that since they appear to be just for the device, not the system I'm building on, and all I need is the jar file, which should be relatively independent, that isn't important. I'm willing to try a stock rom on my device if that's what I need to do, but I'd like to believe that Android isn't so fragile that I can't use an essentially stock framework with a tweaked rom. Maybe that's not the case, though.
The logcat from my most recent attempt (Currently running BlueMagic) is attached. Everything after the second "AndroidRuntime START" will repeat forever until the phone is rebooted. I've also attached my patched SslCertificate.java and the latest framework.jar I've built from the 1.6 source, if it's any help. I realize the changes I've made to SslCertificate.java might not solve the problem (IMHO the patch description wasn't as clear as it could have been), but if I could actually get something that I've compiled to just run on my device, I think debugging it would be relatively trivial.
I'm not an idiot, I understand most of what's going on here and I've spent a lot of time reading, searching and trying to do this myself, and have attempted to demonstrate that in this post. I am relatively new to Android, but I have been trying to learn as much as I can about it. I don't think this should be so difficult, and I'm really stuck at this point. I assume I'm missing something obvious. If anyone with experience compiling and tweaking Android can spare the time, any advice would be appreciated.
EDIT 2 (6/09/2010):
Success at last!!!
Now confirmed working on numerous devices
Check http://psfreedom.com/wiki/index.php?title=Device_compatibility_list for compatibility.
Check http://www.github.com/psfreedom for source
DESIRE INSTALLATION INSTRUCTIONS
http://psfreedom.com/wiki/index.php?title=OpenDesire4.0.4
N1 INSTALLATION INSTRUCTIONS
http://psfreedom.com/wiki/index.php?title=Nexus_One
HTC DREAM/G1/Magic INSTALLATION INSTRUCTIONS
http://psfreedom.com/wiki/index.php?title=G1
HTC SAPPHIRE INSTALLATION INSTRUCTIONS
http://psfreedom.com/wiki/index.php?title=Magic32A
HTC EVO INSTALLATION INSTRUCTIONS
http://github.com/kakaroto/PSFreedom (NO BINARY AVAILABLE YET BUT THIS DOES WORK)
HTC WILDFIRE INSTALLATION INSTRUCTIONS
http://www.ps3underground.net/esclusiva-port-del-psfreedom-su-htc-wildfire/
HTC HD2 (ANDROID PORT) INSTALLATION INSTRUCTIONS
http://bit.ly/bPZf0C
Other MSM72K devices among numerous others are still being worked on. If you can in any way help please join #psfreedom on IRC.FREENODE.NET (By help I mean if you are a kernel developer or think you can offer some form of useful assistance, asking for status updates may get you kicked off the channel).
HSUSB Devices (Check the compatibility list) have not yet begun development. We are searching for a HSUSB developer to assist in the project, please join #psfreedom on irc.freenode.net if you are.
FAQ
Q: What is all this about hacking the PS3?
A: A few weeks ago, someone released a USB tool that allows you to switch any PS3 into "dev" or "debug" mode. The long and short of this means that the PS3 has finally been hacked and homebrew is a real possibility. After a lot of clever reverse engineering, the hack was documented and distributed under the name "PS3Groove". Some clever people ported that code so that other USB devices could be used for this purpose. It just so happens that your smartphone is also a USB device and this was a project to port THAT code so that your Android smartphone could be used to hack your PS3.
Q: Cool! Where do I start?
A: Slow down there, cowboy. This is pretty technical stuff, if you've come here from another forum, or are unfamilliar with terms like "recovery", "flashing", "rooting" and such, take a deep breath and look around the forums for more information, as any mistakes could brick your phone.
First, you'll need to know if your device is compatible. There is a list of android devices maintained here: http://psfreedom.com/wiki/index.php?...atibility_list
This will tell you if your device is supported, as well as point you to where to go if it is.
Q: Ok, so I have a supported device, now what?
A: Just owning the device isn't enough. You'll need to root it to enable you to install custom ROMs. Once you're confident about installing custom ROMs, you're ready to rock and roll! Now, this IS the Desire dev forum, so from here on I'll assume you have a HTC desire, rooted and ready to go. If you have a different device, refer to the link above, or look on your device's own forum.
Q: What ROMs are compatible with this?
A: If you thought that you might need a specific ROM - you'd be right! The whole hack revolves around the kernel that's loaded into the ROM. Essentially, this means that not all ROMs will be able to do this. Right now, if you're looking for an easy solution, install OpenDesire. CyanogenMOD may well work, too, as well as ROMs based off either of those, but no guarantees or promises are made.
Q: What about Sense ROMs?
A: Unfortunately, this isn't feasible. HTC Have yet to release the source code for Sense 2.2, which means we can't port this into it. So if you have a ROM that you like running sense, you'll have to make a choice - Sense, or PS3 hacking? There's no middle ground with this. Alternatively, you can just nandroid between the two ROMs, however you'll soon see how tedious this can get =P
Q: Ok I've got Open Desire installed, now what?
A: Opendesire by itself is just a damn good ROM, not a lean, mean, PS3-hacking machine, so you'll need to add something else. The details are kept here, but essentially there are two update zip files. One will "enable" the PS3 hack and one will "disable" it. You flash those files directly over the ROM itself, using your favourite recovery.
Q: BDMV or Homebrew?
A: In order to keep PSgroove away from Sony's legal team, they released it without the ability to play backup PS3 games, only PS3 homebrew (to which there is currently very little, but stay tuned!), they did this by disabling BDMV. So there are TWO "enable" files. One is "Homebrew", which is a direct port of the PSGroove code and will not play backup games and the other is "BDMV", which will play both PS3 homebrew AND backups.
Q: Did you say BACKUPS?!
A: Yer darn tootin' I did! Legal backups, of course. One of the few pieces of homebrew available is the Backup Manager. This is a simple application that will let you backup a GAME THAT YOU OWN onto an internal or external USB hard drive, then play it without the disk. You'll still need a disk in the drive, but any PS3 game will work.
Q: Where do I get Backup Manager?
A: Backup manager is built with the PS3 SDK, which means it's technically illegal software, so you wont find it on this site, but it really isn't hard to find with a bit of googling. Whatever you do, don't ask for it here!
Q: Hey guess what, I found a copy of backup manager, how do I use it?
A: Ok, so before you start, do yourself a checklist:
You'll need -
Rooted phone,
running a ROM with the PS3groove code loaded onto it (e.g. open desire with klutsh's enable zip flashed on top of it),
USB cable plugged into your PS3 going to the phone.
Phone switched on and on the home screen.
A PS3 running Firmware 3.41 (support for earlier Firmwares will come later, but don't ask when).
Make sure there's no disk in the drive.
Step 1: POWER OFF your PS3 COMPLETELY. This means flipping the switch off at the back of it (if it's a PHAT PS3) or UNPLUGGING it if it's a SLIM PS3.
Step 2: Switch it back on and IMMEDIATELY press the "disk eject button". When I say immediately, I mean it - you've got 0.2s to press it!
you'll notice your PS3 takes longer to boot, a few extra seconds. Once it has booted, you'll notice under GAME, you'll have a couple of extra options.
Step 3: Plug in your USB drive with manager.pkg on it, then select "* Install Package File". Select manager.pkg and it'll install, giving you a new Icon.
Step 4: Backup manager is now installed. Run it and put a disk in the drive. You'll see it appear in the list and it'll give you an option to back it up. It'll first ask if you want the external drive, then it'll ask if you want to install it to the Internal drive. More on that later.
Now, go make yourself a cup of tea. In fact, make several, Blu-ray disks are frickin' huge and take time to backup.
...................
Ok, so the game is backed up. Go ahead and put it back in it's box, where it'll be safe from harm. Now, get yourself ANOTHER PS3 game, any game at all and put it in the PS3. In backup manager, you'll see both your disk game and the backed up game. Select the backup game and press "X".
You'll now be kicked back to the XMB. But look at the disk icon. It should be showing you the game you backed up, NOT the game in your drive. You'll need a legit PS3 game in your drive for this to work, you'll also need to make sure you're running BDMV enable, or it wont work (it'll still show you the game in the drive).
Q: Sounds great! But what's the catch?
A: Actually, there are several. For one, the external hard drive must be FAT32, or it wont be detected by the PS3.
Because of this, any games that have files greater than 4Gb wont work (for example, God of War III), you'll need to install it onto the INTERNAL drive.
Even then, some games may not work at all. Luckily, there are a few lists showing which games work, which don't and which only work on the internal drive.
Oh and some games require you to delete all of their savegame data before they'll load. Sorry.
Furthermore, things like DLC, patches, etc. tend to not work, but this is very early days at the moment, so sit tight!
Q: What's this I hear about "stealth" backups?
A: Quite simply, everyone is expecting Sony to want to protect their precious PS3, which will likely come in the form of a banwave for anyone doing this. Make no mistake, do not assume for a second that you wont get banned for doing this. Still, some people believe that they might be safer if they use a "stealth" Backup Manager. This is simply a version of Backup Manager that tries to make it look like you're playing a different game, like MW2. So far, despite rumours to the contrary, Sony hasn't banned anyone yet, so nobody knows just how detectable it all is.
I'm hoping something comes of this, but I wouldn't get TOO excited, the developer of this is only 15 and while I'm sure he's quite talented, he's still quite young so it could take him a while, assuming it's possible at all.
Still, I like the guy, he makes no promises, doesn't pretend to be anything he isn't and makes it quite clear what he is and isn't capable of. He's essentially said "I'll give it a shot!" and that's good enough for me.
Sorry for the double post, but there's an update on this:
http://netzke.blogspot.com/
This guy is working on an Android port and, from what he's posted, he's not far off.
I sent the kid a donation, looks liek he already has the PSGroove part of the app working.
@ neoKushan, what does age have to do with anything? i know a few kids who are 15-18 who are smarter then half the people i have met on XDA, Including my self.
there is a version compiled for the n900. i have it and it works,would be good if someone could compile for desire? it is open source
abc27 said:
eavpsp is already working on this and we should offer him all the help that XDA has to offer.
Click to expand...
Click to collapse
He's been exposed as a fake, unfortunately. There's a story on the front page of ps3hax about it.
I'd donate to Netzke if I had some good hard evidence that he's genuine but so far I haven't seen anything.
Relikk said:
He's been exposed as a fake, unfortunately. There's a story on the front page of ps3hax about it.
I'd donate to Netzke if I had some good hard evidence that he's genuine but so far I haven't seen anything.
Click to expand...
Click to collapse
I'm aware. At the time I posted many people believed he had something genuine in store.
To be honest, porting over the N900 version mightn't be all that difficult.
Juggalo_X said:
I sent the kid a donation, looks liek he already has the PSGroove part of the app working.
@ neoKushan, what does age have to do with anything? i know a few kids who are 15-18 who are smarter then half the people i have met on XDA, Including my self.
Click to expand...
Click to collapse
I'm merely trying to point out that at 15, even if he's extremely talented, he's still quite inexperienced. From reading his twitter, he doesn't pretend otherwise. I completely support the guy and wish him well and by no means want to make it sound like he's a n00b or anything, I'm simply saying that he's young is all.
what does bring a jailbroken android to us?
cCeT said:
what does bring a jailbroken android to us?
Click to expand...
Click to collapse
It's not the android phone that's being jailbroken, it's the Playstation 3 being jailbroken through the use of an Android phone.
cCeT said:
what does bring a jailbroken android to us?
Click to expand...
Click to collapse
I believe this is actually a software clone of the PSjailbreak exploit which has been re-engineered to be run off of our Android devices. I.E., Put your Android phone in "PSjailbreak Mode" and then connect to PS3, it would then perform the same functionality that having the actual USB device/dongle would provide.
A marvell idea and one that I would love to try out once the tool reaches a stable version. I'm sure over the next week or so we'll see who can actually port it and who is just 'fronting'.
I'll be subscribing to this thread for sure!
**EDIT** Seems neo beat me to the answer!
I've uploaded the binary files used on the N900 so we can get to work on the Android port.
It comprises of a kernel module and two shell scripts.
If what the other guy who's doing the android port says is true, you don't need a special kernel or anything to do this, just root access. Who knows how true that is, though.
Would be nice to see some collaboration from some devs here who know what they're doing lol
if this happens then its gonna be awesome!!
Finally region free BR!!
Netzke is obviously a scammer looking for a quick buck... he mentions in every post that 15$ will get beta access.
Yes, it looks like scam at mee too.
Anyway, looking forward to get the N900 version ported to Android (someone on PSX Scene said we just need to compile the source for the kernel of our phone)
It does appear to be all that's needed. It's a portable kernel module according to the dev. He's releasing the source later today so we wait in earnest.
Make that source release tomorrow, depending on time zone.
Was pushed on line just before he went to bed.
As for netkaz, he's scamming, first claim was donations for a server.
I offered up a full server for free for the life of the project, no response, now he's going to start on a iPhone port after he can afford a iPhone.
eavpsp, well his own private chat room was leaked, he was getting other dev's to do all the work then planned to put his name to it.
The dev that is showing most promise at the minute is qberty1337
But as already said, once the n900 kernel module source is out it should not take too long.
The PSP porting effort is a farce to be honest. We just need that N900 source code and we can get going.
Klutsh said:
Make that source release tomorrow, depending on time zone.
Was pushed on line just before he went to bed.
As for netkaz, he's scamming, first claim was donations for a server.
I offered up a full server for free for the life of the project, no response, now he's going to start on a iPhone port after he can afford a iPhone.
eavpsp, well his own private chat room was leaked, he was getting other dev's to do all the work then planned to put his name to it.
The dev that is showing most promise at the minute is qberty1337
But as already said, once the n900 kernel module source is out it should not take too long.
Click to expand...
Click to collapse
thats good to hear
I hope someone is able to create a BR region free app for PS3 now!!
i am currently trying to create an app for android 1.6 and i am new to creating applications so be gentle lol. a major problem for those on 1.6 still like people with a G1 have very limited space available for apps, i see that apps to sd in 2.1 could be very useful if it were an app in its self as opossed to being a part of the os. cyanogen and their team of wizards have created a custom rom but what if you are new to this and flashing is either to hard or to risky for someone to perform? as i said i am new to this and could use a bit of help. i want to remove appstosd portion of a custom rom and use it as an app in itself. is that possible? someone please contact me about this if your interested in helping me develop something like this. we can share ideas via email and possibly work together to make those with outdated phones a bit happier with there less fortunate hardware.
Not exactly sure this is what you're looking for, but I came across this tut about enabling move to SD using the android SDK by editing the manifest xml file.
Sadly, I cannot post links, so you have to google "mobile.tutsplus move sd".
First result should be it.
ok it says that is supports all android versions from 1.5 to 2.2 but it only mentions 2.2 and says it must be 2.2 which is pointless cause 2.2 already has this feature standard. any other ideas my friend? i may have read it wrong, as i said i am new to this and dont fully understand everything yet. i appreciate your responce on this matter.
Hi, I recently bought fantastic tablet Point of View Protab 2 IPS 9.7. Basically it is Allwinner A10 device. I tried to install new CyanogenMod 10 on it. Everything works flawessly, except one thing. I don't have any touchcontrols, probably because, I don't know what compatibility pack should I install. Could someone please give me advice, what drivers should I install to get working touchscreen on jelly beans 4.1(CM10)?
Same Here
frees11 said:
Hi, I recently bought fantastic tablet Point of View Protab 2 IPS 9.7. Basically it is Allwinner A10 device. I tried to install new CyanogenMod 10 on it. Everything works flawessly, except one thing. I don't have any touchcontrols, probably because, I don't know what compatibility pack should I install. Could someone please give me advice, what drivers should I install to get working touchscreen on jelly beans 4.1(CM10)?
Click to expand...
Click to collapse
I have been trying to get it running myself so far I have tried just about every compatibilty pack.
All I know so far is this device has an upsidedown screen, and other users have had to make thier own comp packs with the "sun4i" which I think is the touch control.
Please let me know if you have any luck.
times iiescre
Hm, that's too bad. I hope, that someone will have drivers. Anyway, I will try to lsmod loaded drivers and built my own pack. Wish me luck.
Since I recently bought one of this, I would like to know if you had any effort on making it compatible to CM10. I really would like to use it. If I could help you with anything, let me know
I managed to extract the kernel module wich is called pixcir_touch.ko
Unfortunately it is not usable with the latest CM-Version due to a different Kernel Version.
When I try to load the module in CM10 with insmod, it returns an Exec format error.
dmesg then gives me an error indicating that this module is not appliable to the current kernel version (I can hand the detailed message, if you will).
I have no idea how to continue. Here is a link to the .ko module:
share-online.biz /dl/5BTVE4GMTX
Maybe this is a source code for the necessary driver to compile it, but I'm not sure and also my skills aren't good enough to compile it myself:
(google for auo-pixcir-ts.c)
Maybe someone could help me get this running.
palmino said:
I managed to extract the kernel module wich is called pixcir_touch.ko
Unfortunately it is not usable with the latest CM-Version due to a different Kernel Version.
When I try to load the module in CM10 with insmod, it returns an Exec format error.
dmesg then gives me an error indicating that this module is not appliable to the current kernel version (I can hand the detailed message, if you will).
I have no idea how to continue. Here is a link to the .ko module:
share-online.biz /dl/5BTVE4GMTX
Maybe this is a source code for the necessary driver to compile it, but I'm not sure and also my skills aren't good enough to compile it myself:
(google for auo-pixcir-ts.c)
Maybe someone could help me get this running.
Click to expand...
Click to collapse
has anyone found or compiled the module yet?
I looked through most of the compatibility files and could not find it.
Would be awesome to have a good 4.1 on this tablet!
---------- Post added at 12:21 PM ---------- Previous post was at 12:00 PM ----------
palmino said:
I managed to extract the kernel module wich is called pixcir_touch.ko
Unfortunately it is not usable with the latest CM-Version due to a different Kernel Version.
When I try to load the module in CM10 with insmod, it returns an Exec format error.
dmesg then gives me an error indicating that this module is not appliable to the current kernel version (I can hand the detailed message, if you will).
I have no idea how to continue. Here is a link to the .ko module:
share-online.biz /dl/5BTVE4GMTX
Maybe this is a source code for the necessary driver to compile it, but I'm not sure and also my skills aren't good enough to compile it myself:
(google for auo-pixcir-ts.c)
Maybe someone could help me get this running.
Click to expand...
Click to collapse
perhaps this helps:
http://downloads.pointofview-online...ab-ips 8GB TAB-PROTAB2-IPS9 Firmware Upgrade/
I have send a mail to their support people to request the kernel source.
Let's hope they comply to the GPL.
Another approach would be to donwload a kernel tree from CM 10 and try to compile the source code you linked to.
Are you sure it is the proper driver?
Would be awesome if this pulls off
No i'm not sure. This is the only pixcir driver file I could find on the Internet
Hopefully they reply to your mail. The current Rom is very slow compared to the cm10.
Unfortunately my device was in a bootloop and i had to return it for repair.
Let me know when you receive an answer
palmino said:
No i'm not sure. This is the only pixcir driver file I could find on the Internet
Hopefully they reply to your mail. The current Rom is very slow compared to the cm10.
Unfortunately my device was in a bootloop and i had to return it for repair.
Let me know when you receive an answer
Click to expand...
Click to collapse
Well, I did receive an answer, which in short said they cannot provide the source code.
I pointed to the GPL license and requested them to contact the lawyer department if they have one.
If they refuse, I am not sure what options there are to enforce it.
Some usefull info I found here:
https://android.googlesource.com/ke...885aa51f1abf3c40/drivers/hid/hid-multitouch.c
I read somewhere that support for this display is added by Stephane Chatty of ENAC.
Maybe someone can work with that source?
Mr. Chatty helped me before with a touch driver, if you do you some proper work and get stuck, I am sure you can contact him for help.
Personally I would love to dive in, but I can't find the time now.
Perhaps this helps some devs?
Can't imagine those drivers can't be made. Probably some dev setup on Linux for the proper 4.1 kernel version.
There is a ton of information on that.
this link is also interesting:
https://build.pub.meego.com/package...Project:KDE:Mer_Extras:Adaptation:Archos-gen9
It suggests they are in the Archos gen 9 and also that some kind of calibration is being developed.
Perhaps the ko can be pulled from an Archos gen9 rom ?
I saw your posting over in the Archos G9 Forums. Hopefully there is a chance to reuse this. I posted the same question in a large german Android-Forum. Maybe we can get it from there if noone replys here.
Furthermore the Archos seems to use two different touchscreen-devices: bit.ly / VUo71L
If you're correct, this might be the uncompiled driver: bit.ly / UIJ2Bq
But still I neither have an idea how to compile this, nor is my device back from repair.
palmino said:
I saw your posting over in the Archos G9 Forums. Hopefully there is a chance to reuse this. I posted the same question in a large german Android-Forum. Maybe we can get it from there if noone replys here.
Furthermore the Archos seems to use two different touchscreen-devices: bit.ly / VUo71L
If you're correct, this might be the uncompiled driver: bit.ly / UIJ2Bq
But still I neither have an idea how to compile this, nor is my device back from repair.
Click to expand...
Click to collapse
can you please use full links instead of those very irritating-twitter-like short-urls ?
I would like to know where it is pointing to (and it did not work on my android).
I think there is a good chance it might work.
Last time I compiled kernel modules, i noticed it is importent al versioning stuff is matched properly.
POV is not really cooperating in terms of open source obligations.
They are not the first.....
I really would like to post normal links but I cant since I'm not meeting the conditions for posting links here in the Forums (I need at least 10 posts hiere in the forums). I'm close to this.
Removing the whitespace before and after the slash should do it. Sorry for the inconvenience!
palmino said:
I really would like to post normal links but I cant since I'm not meeting the conditions for posting links here in the Forums (I need at least 10 posts hiere in the forums). I'm close to this.
Removing the whitespace before and after the slash should do it. Sorry for the inconvenience!
Click to expand...
Click to collapse
ok, np. sorry did not know that. I think we have gathered quite some resources for devs.
Perhaps someone can create a forum item for our device?
Sorry, personally I cannot find time at the moment.
I do have time to test any dev builds by the way...
another tip.
The main reason I wanted to update, because the browser was performing like thick **** rolling up a mountain against the wind.
And it hanged too sometimes.
When checking processes I noticed the nandd process being on top often.
After googling that process, I found somebody else also had a slow browser issue caused by this process.
He fixed it with a factory reset.
I did that too, and now the problem is solved.
I can also recommend installing setcpu. You can overclock till about 1200 (mine 1152 now) which makes it a bit snappier.
Mine is rooted by default, it just works, not sure if this is always the case.
And please mail POV for the kernel source .
OpenMinded said:
another tip.
The main reason I wanted to update, because the browser was performing like thick **** rolling up a mountain against the wind.
And it hanged too sometimes.
When checking processes I noticed the nandd process being on top often.
After googling that process, I found somebody else also had a slow browser issue caused by this process.
He fixed it with a factory reset.
I did that too, and now the problem is solved.
I can also recommend installing setcpu. You can overclock till about 1200 (mine 1152 now) which makes it a bit snappier.
Mine is rooted by default, it just works, not sure if this is always the case.
And please mail POV for the kernel source .
Click to expand...
Click to collapse
Yeah, The overclcok makes a huge difference also changing governer to performance and io sceduler to noop.
Before my 8 year old used my tablet as a frisbee, I was trying to tweak it futher with pimp my rom from the market, it has some great tweaks for this tab.
I never got any increase in the benchmarks but resposiveness was up with my tegra phone.
Also opera is a fantstic browser for this tab, once ya figure out how to use it you will be hooked.
williamsjp said:
Yeah, The overclcok makes a huge difference also changing governer to performance and io sceduler to noop.
Before my 8 year old used my tablet as a frisbee, I was trying to tweak it futher with pimp my rom from the market, it has some great tweaks for this tab.
I never got any increase in the benchmarks but resposiveness was up with my tegra phone.
Also opera is a fantstic browser for this tab, once ya figure out how to use it you will be hooked.
Click to expand...
Click to collapse
Nice tips! How to swt io scheduler?
Fantasy schedular seems to work better than on demand on this.
OpenMinded said:
Nice tips! How to swt io scheduler?
Fantasy schedular seems to work better than on demand on this.
Click to expand...
Click to collapse
You can change the sceduler in SetCPU
Also i found if i had performance governer enabled i couldnt over clock past 1100 or it would reboot its self
Bought myself this tablet as well. is all nice and good but the 3G is giving me a headache. with the stock rom it works excatly as long as you don't turn on wifi. after that even if you turn wifi off again it wont connect to 3G anymore.
Firmware side isn't helping much either. V4.008 is without 3G (in the settings there is now only a list of supported dongles. and the 3Gfix image has same issue, you see 3G only once until you turn on wifi)
So i was hoping for a better rom but looks like the CM9/CM10 department can't help either. So i was hopin if you guys have had any progress.
E: i have been in contact with POV support over the last week and the only useful intel i ahve gotten out of them is that as far as they are aware there are no clones for this tablet. Also it appears that there is a android 4.1 based firmware for the tablet in the testing. They are not sure if they release it tough.
anybody tried to fix a touch driver for this device?
I had to send my tab back for repair since my headphone jack wasn't working anymore.
Unfortunately they were out of stock so that they couldn't send me a new one and refunded me.
I will not buy a new protab2 9,7 because it's so laggy. I hope you all can figure out a solution for the touch-issue. I'll leave you here, guys. Thanks for your help anyways
Nothing yet?
I see there are a compability zip for the protab2xxl at http://forum.xda-developers.com/showthread.php?t=1760929, annyone knows if that is helpful for the protab 2 IPS 9?