I have multiple windows network shared folders that I would like to mount. The main point in doing this would be so that I can play videos on my epic without having to do the convert&stream/copytoSD shuffle.
I would like to get either CIFSManager to work, or Mount Manager. I've tried multiple kernel/rom combinations with no luck. Has anybody been able to get this to work on their Epic?
As far as I know, there isn't a cifs.ko compiled for the Epic 4G, which may be causing the problem. I tried using a cifs.ko that was compiled for other Galaxy S devices, but that didn't seem to work.
If anybody has any info on how to get this working, it would be greatly appreciated. I am currently on stock DI18, but I have no problem flashing to something else if that will help my situation.
Hi all.
I have looked and found nothing regarding the Xperia S
I have been trying a bit of porting lately, not with much luck unfortunately. My main concern is that when trying to run logcat through ADB, before entering the system, (eg while phone is booting) adb does not pick up the phone.
Is it possible to get logs from when the XS is booting? If so, how is it done?
Thanks in advance
How is porting normally done?
Can someone with experience of this please enlighten me:good:
I'm trying to install pdroid but I can't get the patch installed! I made a patch on my PC and install it but when I reboot my phone it locks just before it shows the little blue Guy skateboarding on cyanongenmod. I'm running HTC 4g 2.3.7 cyanogenmod 7.2.0. On my old 4g evo I remember I was able to use pdroid with the custom patch that was available at the time, but now it don't work at all. I thought maybe it was the rom so I tried several but the same thing happens. It locks to a black screen! Can somebody please help me out and tell me what I'm doing wrong? I emailed developer but didn't get a response. Any help at all would be greatly appreciated!!! Thank you
I have built and slightly tweeked CM 10.1 but to be honest, it does drain that battery quite a bit and sometimes it freezes in landscape mode.
So I sync'ed up the source for the AOSP and then I realized that I needed binaries and I don't have the stock ROM to extract them from.
Are these "Galaxy Nexus (Sprint) binaries for Android master (20130603)" the right binaries for SPH-l710 ?
Under the Toroplus section at the very bottom of this page https://developers.google.com/android/nexus/drivers
Basically I just want try moding from stock because of the battery thing, I need to add Arduino support and maybe tweek USB or write an app, so that my phone can hook up over usb to an Arduino board and chit chat. I want the Arduino to control motors while Android gathers sensor data and decides where to go, Arduido will just follow orders. Anyways, battery consumption is huge in this project.
EDIT-1: Also, what version of Android are the 20130603 binaries for?
These are the binaries
https://github.com/themuppets/proprietary_vendor_samsung
d2spr folder.
That's not all you need to build for our device though.
I suggest just building an existing rom rather than syncing AOSP....you're gonna need to make a TON of edits to even get it to build, much less boot. I know because I'm very much involved with a new AOSP rom called omnirom and bring ups for that rom. It's not easy. We're still making edits to the source to even get it to build for non-nexus devices
CNexus said:
These are the binaries
https://github.com/themuppets/proprietary_vendor_samsung
d2spr folder.
That's not all you need to build for our device though.
I suggest just building an existing rom rather than syncing AOSP....you're gonna need to make a TON of edits to even get it to build, much less boot. I know because I'm very much involved with a new AOSP rom called omnirom and bring ups for that rom. It's not easy. We're still making edits to the source to even get it to build for non-nexus devices
Click to expand...
Click to collapse
hmm
I thought it would be a lot easier than it has been to build a stock rom, but I guess not, I am not trying to build kit-kat though, I want to build for 4.1.2 as I think thats where their updates left off but maybe I am way outta the loop.
What about the factory images? Are those flashable with the "flash-all.sh" over fastboot? Idk either way I haven't been able to get fastboot working, I don't think I have even been able to boot into fastboot, when I "adb reboot bootloader" I go to what looks like Odin's download mode, and when I do the volume up+down+power I just boot into "safe mode" and get to the launcher like normal but its in safe mode. I rooted it on Windows about a half a year ago or so using Odin and some dude's tuts on YouTube "High on Android" or something. I haven't really studied rooting so I guess thats my bad not knowing really what I was doing, but I haven't looked back and wouldn't be here now if it wasn't for it.
I'll take your word for it but I am going to keep trying to figure it out, Figureing out all this proprietary stuff is tuff, maybe I should get a device or board targeted to developers lol, didn't know Id ever say that, I thought I was going to major in Chemistry.
Edge-Case said:
hmm
I thought it would be a lot easier than it has been to build a stock rom, but I guess not, I am not trying to build kit-kat though, I want to build for 4.1.2 as I think thats where their updates left off but maybe I am way outta the loop.
What about the factory images? Are those flashable with the "flash-all.sh" over fastboot? Idk either way I haven't been able to get fastboot working, I don't think I have even been able to boot into fastboot, when I "adb reboot bootloader" I go to what looks like Odin's download mode, and when I do the volume up+down+power I just boot into "safe mode" and get to the launcher like normal but its in safe mode. I rooted it on Windows about a half a year ago or so using Odin and some dude's tuts on YouTube "High on Android" or something. I haven't really studied rooting so I guess thats my bad not knowing really what I was doing, but I haven't looked back and wouldn't be here now if it wasn't for it.
I'll take your word for it but I am going to keep trying to figure it out, Figureing out all this proprietary stuff is tuff, maybe I should get a device or board targeted to developers lol, didn't know Id ever say that, I thought I was going to major in Chemistry.
Click to expand...
Click to collapse
All of the downloads on the Google site are for and will only work with nexus devices
Those proprietary files are the bare minimum to "inject" our device's characteristics into a rom. That's how I ported Sense actually
CNexus said:
All of the downloads on the Google site are for and will only work with nexus devices
Those proprietary files are the bare minimum to "inject" our device's characteristics into a rom. That's how I ported Sense actually
Click to expand...
Click to collapse
Makes Sense.
So if I am learning anything... I would need binaries ("blobs"), I am sure Sprint, Google, and Samsung proprietary apps, and the nessiccary make (Android.mk) files, maybe some kernel patches and/or kernel object files, and hopeful to all hell I don't have to do too much XML modification I need to go find a trust-worth factory zip for the sph-l710 and rip everything I need out of that, and the bootloader I need to get it all back to stock eventually in case kit-kat does get updated by the Samsung (I am guessing thats whose hands it is in, I think they have a counter), who knows maybe the open source community will get there first.
Thanks for your help, saved me a ton of hassle.
Hello all,
First I want to express my appreciation for those who take the time to make ROMs for our TF201/300T tablets. Doing just this little task took 3 days of experimenting, I couldn't imagine debugging an entire ROM!
As some of you may know, people with broken touchscreens are getting replacements on eBay that are the wrong version, and are having reverse x-axis issues. The only way this was solved previously was to install Hairybean 2.31 which had the corrected driver and init script to activate it on the install. Unfortunately that meant that we with the wrong screens were stuck on Android 4.2, and what fun is that?
I have figured out and created a new driver for the atmel_maxtouch which will allow you to turn on the reverse axis by echoing 1 to /sys/module/atmel_maxtouch/parameters/reverse_axis. For those without the reverse axis issue, you should be fine, as the reverse axis is only called by the command above.
There's a lot of great ROMs out there, and now those with the different screens can enjoy them too, and all you need is this driver and an init.d script.
Please let me know if you have any questions or need something debugged (though I am not a programmer, so how much I may be able to help will be limited ). The new atmel_maxtouch.c is attached in the zip.
I've added it to KatKernel #19 that will be in the next KatKiss V18
Hi. I have an Asus TF300T with touchscreen issue. It doesn't working even if I replaced it. Maybe the replaced part was the wrong one... Can I do anything? I have JB 4.2.1 with the latest bootloader, root, bootloader unlocked. I flash via fastboot the TWRP recovery but I can't flash or use it because it is only touch usable...so I can't flash Katkiss rom... What can I do?
ADB is active...