[Q] CIFS/SMB kernel recommendations for Synergy (Or other Sense ROM) - EVO 4G Q&A, Help & Troubleshooting

Wow, XDA found my original thread back in the day (it does a search when you create a title):
http://forum.xda-developers.com/showthread.php?t=984254
I've come a little ways since that thread, but I'm still in "clear as mud" territory.
I am running Synergy (just flashed a few days ago):
http://forum.xda-developers.com/showthread.php?t=1144447&page=1544
and would like to add CIFS support. This is a networking component, not a scheduling component (I'm getting pointed to CFS/BFS kernels is why I point that out).
I have downloaded CIFS manager and it seems that CIFS is not built into the Synergy kernel (I get an error: Mounting the share has failed with an error. Mount: no such device) so I would like to add it. Problem is, I'm having a hard time finding a sense kernel that adds CIFS.
I found this guide:
http://forum.xda-developers.com/showthread.php?t=894880
and this one
http://forum.savaged-zen.com/showthread.php?6-HTC-Evo-(Supersonic)-Megathread&daysprune=-1
while researching kernels and how to load them. I think I have the process down, I just need to find one.
*edit* I found this one: http://forum.xda-developers.com/showthread.php?t=1192796 Golden Monkey. He says it's still in development though. I'd prefer a release version if I could get one.
In case I wound up looking at the wrong ROM/kernel, I would like recommendation(s) for ROM/kernels with the following criteria:
Must-have's
sense 2.x or 3.x based
gingerbread based
working 4g (I do have 4g in my area)
working HDMI (I would like to start using webtop)
Really want's:
CIFS kernal (a must have, but if I can flash a kernel onto a ROM I'm good)
Would really like:
bluetooth profiles like keyboard, mouse
USB host support
Not interested in:
overclocking/underclocking
adjusting voltage
changing scheduling (CFS/BFS)
god mode (not at the moment anyways, maybe later)

Well I tried Synergy-Kingdom 7/23 and it was kinda slow, so I dropped back to Synergy and flashed the Golden Monkey kernel So far, it seems I have everything I want, although I haven't tested 4G and HDMI yet today.

Related

[Q] Best ROM for app development?

I'm hoping for some advice on picking a ROM. I've tried a few different ROMs based on EC05 and EH06, including SRF 1.2, but for various reasons they've all had problems working with the ADK and eclipse. Using SRF, I get the error "ActvityManager: /sbin/sh: am: not found" when I try to load code onto the phone, and other ROMs have given me even more drastic errors- though I don't remember what they were right now....
Anyway, are any of you developing apps using a custom ROM? I'd love a fairly streamlined one since the app I'm writing will be pretty heavy. It also needs to have access to pretty much all the sensors- accelerometer, magnetometer, GPS, proximity, and light- though those last two aren't as important. It also needs bluetooth and WiFi to be functional.
Thanks!
Does nobody develop apps using a custom ROM? I'd love to hear of any successful pairings of eclipse, the ADK and a ROM....
Sounds like a kernel issue...try just a different kernel

[REQ] Get rid of car mode from my favorite kernel

You've heard of that car mode epidemic happening to evo users all across america right? well, it finally happened to me. i didn't think it would because i dont even use my usb port unless its for transferring files.
Now, ive looked all across the web and it seems to be just a hardware issue. I dont have warranty nor do i have insuarance.
Finally I found this thread: http://forum.xda-developers.com/showthread.php?t=1212260
and this guy in there wrote:
sbradymobile said:
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect config_usb_accessory_detect and config_dock_accessory_detect support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
http://forum.xda-developers.com/attachment.php?attachmentid=687912&d=1313280355
Click to expand...
Click to collapse
I've tried devving but i suck at it. So could someone be nice and kind and stuff and do that for the cfs havs savaged zen kernel?
I dont even know if its a difficult task or if its easy peasy, i just wanna get rid of this god damned car home virus.
Here are some links for ya:
the kernel thread it self: http://forum.xda-developers.com/showthread.php?t=917755
the post i quoted mentioned the need for source, so: https://github.com/Savaged-Zen/Savaged-Zen
PLEASE HELP ME! and thank you

Attempting development for Gingerbread. (Long post/discussion)

Hello everyone...I'm planning on trying to develop a gingerbread kernel for AOSP because we don't really have support anymore and everyone has moved onto developing for ICS (not that this is a bad thing). I figure in my spare time I might as well try to learn and develop for our phone. Let me start by saying I was never really into phones/smartphones/rooting, or software development, but I've always been fascinated by Linux in general. I've played around using a number of Linux distros, but I've never really done anything intensive with them (modified their kernels, etc.) but I am vaguely familiar with terminal usage.
Anyways that was just my introduction. I've been running an ICS kernel on my AOSP GB system (specs/stuff in my signature) and while most advised against it, I find it to run pretty well. I'm not sure why it seems to run so well on my phone, but it's basically solved most of my problems (or at least it appears to have done that), but I know the kernel isn't "optimized" for my phone. Some major things people have said are that the ramdisking operations/system is totally different when comparing ICS and GB. This kernel that I'm using is running pretty well, even knowing this fact. What I was wondering is if I could basically get the ICS kernel, then "merge it" with a GB kernel's parameters that pertain to the ramdisk/other major options of GB. That would probably make it better. Also, people stated that multitouch issues for the DINC2 occured on Aeroevan's 0.8 kernel, but not on the 0.7 kernel. This was the changelog stated by aeroevan:
v0.8: Upstream CyanogenMod changes + small touchscreen driver update from HTC. Only tested on my CM7.2 Kang build.
Click to expand...
Click to collapse
So maybe this "small touchscreen driver update" is the thing that caused it, but I'm assuming many other kernels applied this update too? Maybe there is a way to roll back to whatever was in 0.7 in this sense to get rid of the multitouch bug that plagues some people.
I have a pretty powerful laptop, so development shouldn't be too bad. I plan on running Ubuntu 11.10 (or whatever people find suitable these days) in a Virtual Machine and I plan on compiling stuff from there. I am not claiming I know everything or that these things are correct....I am simply just throwing out some brainstorming to get some ideas out there. I know GB is "old", but I (and some others as well) enjoy it's stability and that it generally functions perfectly. Maybe this thread will get a look from popular devs, or maybe it'll get a look from people who just know this stuff. Thanks for reading, and sorry for the length of the post.
Looking forward to your progress on this.
Sent from my ADR6350 using xda premium
It would be nice to have another kernal for AOSP other than aero.
Your help in developing AOSP kernels would be fantastic.
Thanks given. Because I am hard of hearing I cannot use any of the kernels (even Evan's) and have to stick to Sense

[CM9] Kang's from Fuzz (Defy Porting)

Figured I'd make a new thread so Fuzz\Skankwitch ports and problems with them aren't mixed up in Quarx's CM9 thread. Helps keep relevant info and fixes for their respected rom easily available and findable. And to put Defy Porting in a centralized place (hopefully) All the relevant Defy Porting, especially CM9, is extremely scattered around here. I know, I wrote most of em. I'll post better porting guide eventually.
The latest build (0616) looks like its gonna be pretty awesome since it merges in even more of Linaro build environment. If you don't know, in a nutshell, Linaro is a new toolchain to compile CM9 with fixes and optimizations to the build environment that allows the compiler to use exotic flags, which in turn makes software run faster.
I'm off today and tomorrow, so I plan on starting that Aroma installed Kang in the next few hours. If you've never build a rock wall, they're a pita and will wear you out, especially when you're alone and the rocks are 200+ft away and you push them in about 260-300 pound loads (slightly) up hill to the wall -- damn I missed having the truck that day. Each rock weighs between 60-180 lbs, and I weigh 180 btw. For you metric guys, multiply by 2.2 to get the kilo version, provided my weed math is correct (~2.2 kilos a pound).
Once the initial framework is done, weekly updates won't be that hard to do since it will only be replacing the core rom and updating a few mods that affect system files (volume step, pdroid if it'll patch).
(reserved for later)
Updated:
here's a port I just made: http://www.sendspace.com/file/hh74un (June 28 FuZZ)
Looking forward to the port with the aroma installer. Hopefully linaro is gonna make our devices more smooth. Thanks skeevy!
corvx said:
Looking forward to the port with the aroma installer. Hopefully linaro is gonna make our devices more smooth. Thanks skeevy!
Click to expand...
Click to collapse
Not sure if its Linaro or the build.prop tweaks I did, but the roms feeling really smooth and hardly any lag -- even when opening the app drawer. Base rom and tweaks are done. Currently going over the scripting and changing it as needed, and it needs quite a few since it started as GB Miui, adapted and extended for V4, and now being used for CM9
Almost done with the scripting. I plan on doing a test install later this evening.
Also working on a deal to get a $40 Defy + shipping -- has a cracked screen, but my Bravo's cracked screen is worse Hopefully the deal is able to go through -- seller is in Australia and my online currency is Pre-Paid Visa.
Any Australian Bravoers able to help me out and pay for it for me and I'll hook ya up with an American Pre-Paid Visa #, with it comes full access to the American Market...It's only $40+ shipping. Seller doesn't know much about pre-paid cards, so I sent more info on them, hopefully I'm over worrying about it and the pre-paid card will work.
I plan on getting a Defy or Defy+ as the "upgrade" to my Bravo. Yes, I know that they're the same phones, but I want a damn torch flashlight, 720p recording, and a Gingerbread kernel with 4 Vsel's.
If this doesn't work out, I'll just get one off ebay in a few weeks.
What sucks is doing a GiS for Defy on shopping leads to a few scam sites selling them (Defy) for $120 -- you're lucky to find them on ebay for that price.
skeevy420 said:
Almost done with the scripting. I plan on doing a test install later this evening.
Also working on a deal to get a $40 Defy + shipping -- has a cracked screen, but my Bravo's cracked screen is worse Hopefully the deal is able to go through -- seller is in Australia and my online currency is Pre-Paid Visa.
Any Australian Bravoers able to help me out and pay for it for me and I'll hook ya up with an American Pre-Paid Visa #, with it comes full access to the American Market...It's only $40+ shipping. Seller doesn't know much about pre-paid cards, so I sent more info on them, hopefully I'm over worrying about it and the pre-paid card will work.
I plan on getting a Defy or Defy+ as the "upgrade" to my Bravo. Yes, I know that they're the same phones, but I want a damn torch flashlight, 720p recording, and a Gingerbread kernel with 4 Vsel's.
If this doesn't work out, I'll just get one off ebay in a few weeks.
What sucks is doing a GiS for Defy on shopping leads to a few scam sites selling them (Defy) for $120 -- you're lucky to find them on ebay for that price.
Click to expand...
Click to collapse
Glad to hear that you are upgrading, please dont stop developing for the Bravo. Looking forward to your realease. I tried syllogyking's release, and battery life is amazing, even wifi tethering is working. With all the scriptings you are adding and modifying I can only expect it to be smoother and better. Thanks.
On a side note: I'm not australian, but I use a local pre-paid visa, to buy online on the US, I use paypal though (ex. transfer from the visa to my paypal account).
corvx said:
Glad to hear that you are upgrading, please dont stop developing for the Bravo. Looking forward to your realease. I tried syllogyking's release, and battery life is amazing, even wifi tethering is working. With all the scriptings you are adding and modifying I can only expect it to be smoother and better. Thanks.
On a side note: I'm not australian, but I use a local pre-paid visa, to buy online on the US, I use paypal though (ex. transfer from the visa to my paypal account).
Click to expand...
Click to collapse
I'm not gonna stop, that's the whole reason I want to "upgrade" to a Defy.
I'll try and make it a point to finish the rom by tomorrow evening -- I have things to do tonight.
I did have an idea hit me yesterday -- an aroma installer that contains only the bootloader, our baseband, a few mods, and does basic Defy Rom Porting. It would be a Bravo repair, mod, and porting tool to make it easy for noobs to use Defy roms w\o the hassle of having to port it yourself and be able to tweak whatever rom you're installing. The hardest part would be the build.prop, but I could include generic props for cm7, cm9, miui 2.4.20. Anyone interested in something like that?
After going to the Defy forums, I find it kind of funny that a lot of the posters giving help are Bravo usres....but it makes since since we need to know a bit more about the phones because we have to do a lot more digging around in order to get the roms working.
very good idea to use Aroma with Defy Roms.
I'd like to test it when it will be done.
Also I'm interested will KANG team accept Bravo for rom develompent ?
Unfortunelly CM, MIUI currently stopped
PsyClip-R said:
very good idea to use Aroma with Defy Roms.
I'd like to test it when it will be done.
Also I'm interested will KANG team accept Bravo for rom develompent ?
Unfortunelly CM, MIUI currently stopped
Click to expand...
Click to collapse
I put doing the actual rom on the backburner for the moment -- I only have time to for the one project now since I have things going on everyday IRL now.
I decided to do the recovery tool since, other than volume step mod, everything else in the aroma rom was universal and a port tool means users can update, have mods and tweaks, and not have to either rewrite or remod the rom for updates -- which occur every few days with Defy Skank roms.
The recovery tool is about 1\4 - 1\3 done.
Planned features include
Defy CM9, CM7, MIUI (GB) Porting
Bravo Greenbread Mod (for MS2)
Reinstall the kernel\devtree\bootloader
Mods for ICS and GB roms
Basic Rom Backup and Restore in Aroma
/data/app backup\restore (for keeping apps in between flashes)
andriod secure backup\restore
system\data\andriod secure\cache\dalvik\sdext wiping (all separate)
Bootmenu Fixes for all roms
Apps only available on XDA or other forums (or banned by google; only legal apps, nothing pirate)
Add init.d support to stock roms
Multiple touch recovery options ??? (a new cwm touch is being worked on, need to use and test it first)
build.prop tweaks
Multiple gps, wifi drivers and settings
init scripts for performance
custom overclocks
add multiboot support to roms
Maybe more??? Will take requests
Still have much to do, as I only have the basic aroma layout done. I still need to finalize the aroma layout, add in a few of the mods, write the updater-script, write the language file, test, test, and test again....
A few of the features I have planned have never been done or attempted with Aroma as far as I know, and may not be in the release (full system backup and restore); but they technically should work. I'm going to try and make the backups CWM compatible, but don't quote me on that, as the md5 scripting may be a pita to do for first release and proof of concept.
I quite surprised Quarx hasn't released an updated 9 yet, with all the updates his git-hub page has had over the past few weeks. I was hoping that he'd stay with the every 2 weeks-ish that he was doing up until now -- not a big deal since we're Defy porting again. I suppose he's just more interested in the Novo7 tablet than the Defy\Bravo roms for the moment. I'd like to hear his review of it, since a dev's review holds more stock with me than a random website catered to end users.
Not sure if the Kang team will accept the Bravo, never asked or even heard it brought up until now. If someone here has a Linux Build Environment setup, go ahead and ask them if they'll help get it setup to start building Bravo Kangs. You'd get better results offering to build it yourself versus asking one of them to do it for you. I might ask when this is done, but might not since I'd be able to run the roms w\o even having to edit the zip once this is finished -- just flash Defy Kang, run Aroma Recovery, port and mod the rom, reboot and enjoy...easy enough I think.
Can we have MIUIV4?
glucky said:
Can we have MIUIV4?
Click to expand...
Click to collapse
Easier said than done....the Defy Miui v4's that we port from are based on Quarx CM9 from March 08. The newer CM9's don't like to be the base rom for v4 porting. Miui v4 is based on pure AOSP roms, not CM9; where GB Miui was based on CM7 and more compatible with CM7 porting.
Since it only takes 30-40 minutes to port and see if it works, I'll attempt porting v4 with the latest skank rom I ported last night. Maybe it'll work, maybe not.
In the meantime, I'm about to upload the yesterday's skank slightly tweaked with 30 step volume mod, Motoinspired CM9 Theme, HWA Selector --- I also have the srs mod installed with it, but frankly, the srs mod has washy treble that I don't like so I'm going to remove it first. I should begin that upload in 40 minutes, with it finishing 40 minutes after that. BTW, the lastest Skank (0628) is really stable and battery efficient (I fell asleep lisnening to music, woke up 8 hours later with 65% battery -- 45% loss with wifi on, radio on, 2 hours web surfing on wifi, 8 hours of music, 6 reboots, full brightness, and installing 20 apps from google sync is very acceptable to me -- means I can listen to music while driving for 12 hour, have about 4-8 talk hours, and have that last for at least 2 days on a single charge.
EDIT: Call of Duty being played in the other room, need to wait for the bandwidth to be freed up before I can upload.
As far as the Port Project is concerned, I have the Aroma layout almost finished (just need to add in an install rom feature), its completely translated for English and ready for multilingual. The rest of the Aroma part will only take 5 minutes or so to complete, then its on to the edify scripting and shell scripting; followed by actual testing of the tool. If I had to guess, 50%+ of what I'm trying to do has never been done in Aroma as far as I know; and if they work as expected, you'll soon start seeing Aroma Roms that install from Nandroid Backups as that's a feature I know Walter79 and espaciosalter20 both want. Expect something in the next 4-5 days as all I really have left is a ton of edify scripting and shell scripts (around 20-30 shell scripts I assume).
Skankport 0628 (NOW UP)
Port to Bravo of Skank CM9 0628
Does anyone here still need install instructions???
--If so, feel free to look in any other damn CM thread, they're all the same
Gapps not included, so flash it as well.
30 step volume mod
Motoinspired 1.4 Theme
HWA Selector 1.5 Beta
Bravia Engine
Vibhinna 1.01 Beta (Multiboot Manager Reloaded)
Defy Apps Removed (Torch, Rom Updater)
DOWNLOAD HERE
I don't think that Bravia Engine is working with ICS roms due to there being no Bravia being mentioned at all in logcat output; you can see it loading on GB Roms; also my first time trying Bravia on ICS. Everything else, however, is working perfectly*. Before enabling it in HWA, Chrome actually loaded and let me enter an address, but only showed a grey screen instead of fark.com which did load....Chrome's almost there.
*Except for camera....
camera isn't connecting for me...when I tried making my own skank port based on your instructions, it didn't connect either. any advice?
also, sio wasn't present (only noop and cfq) according to no frills, so I flashed the droidx zip to get it
syllogyking said:
camera isn't connecting for me...when I tried making my own skank port based on your instructions, it didn't connect either. any advice?
Click to expand...
Click to collapse
Not as of yet....I do know the problem -- its not loading the kernel module correctly. I've already tried the Defy modules, replacing camera.kobe.so with a renamed camera.jordan.so, using the Kobe CM9 camera app, swapping init scripts with Quarx CM9...I'm kind of stumped for the moment, but I've only been at it for about 10 minutes now. I never actually tested the camera, just ported over like usual, which usually works.
I'm just hoping that there isn't a new step in camera porting....
For sio, I didn't fully tweak the overclock.sh like I normally do as a test to see if the scripting would work like its supposed to. Apparently it doesn't....You can remove the 2 governors from the DX zip and also remove the 2 insmod lines for the Governors in the init script to save a bit of ram....and the boosted governor works as well as boostedass anyways. I'm not sure what Epsylon did, but he did do something to it.
Perhaps a better option would be to ask Fuzz for some help in starting up a Bravo build environment. I've built my own CM7's in the past. I'd already be doing the same for CM9, but I've been getting sync errors every time I try to sync with Quarx's Bravo repo since he's been releasing CM9 (usually due to MotoMagic, then I fixed that and couldn't sync with Quarx's personal repo).
The building and compiling isn't hard at all, its just a matter of syncing the repo (which I can't do) and knowing how to use git (which I don't). I'll send Fuzz a pm shortly and we'll see what happens from there.
EDIT: PM Sent; Hopefully he'll help me out in setting up a Kang build environment.
Yeah, I'm fearing there might be some further tinkering that now needs to be done to get the camera to work again. Since Fuzz basically adds cherry picks to epsylon's commits (he pushes mostly tpruvot commits in git), I'm thinking all of this is going to quickly change. The reason being because epsylon has already stated that jelly bean is going to be ported to defy in a few weeks, and that I can believe. But because the camera app is further "improved" in jb, it might still require some more steps to keep us on pace with the "bleeding edge".
anyways, I wish I had the time to read up on Android dev and get started on git, but unfortunately real life is taking priority atm
thanks for the pm initiative. hopefully, fuzz imparts some insight.
Oh the fun fun world of porting never ends when you own a Bravo.
From what I've understood, Jellybean isn't that big of an update so I'm not surprised that they're doin it (and doin it and doin it well). I actually expect them to keep coding until the platform just can't handle the new software any longer without updating the kernel...
I figured out my github sync problems -- the manifest.xml linked to the bravo repo was out dated, so I switched it to Quarx's manifest.xml on his github and have now fully synced it with no problems.
I was thinking that if I was going to ask for help, I might as well try to build it from the repo first (or at least have it all on hand).
If all goes well it should compile in while I'm sleeping.:fingers-crossed:
I'm referring to CM9 & not a Skank Kang, btw.
EDIT: NOW COMPILING, time to smoke a bowl and go to bed.
EDIT2: Didn't compile correctly...
EDIT3: Think I found that problem as well, been compiling for 3+ hours now. Problem was I followed the Bravo ICS instructions to the letter & and they're now wrong. Using Quarx's Defy+ Instructions, modified for the Bravo, are working.
EDIT4: Successfully compiled CM9, going to test it in the next hour or so -- took over 5 hours to build.
My First CM9 Compile
Here ya'll go -- my first compiled CM9 rom. This is basically Quarx 0526 with an updated CM app base. Haven't tested it much, but camera works, it synced with Google and installed all my apps, and it hasn't FC yet. It doesn't have the new hwui.allow feature yet, as I'm still learning git and want to do this all in the proper manner.
Once I learn how to properly sync the Defy repo to the Bravo repo and not screw up the camera is when I'll start to be able to make Bravo Kangs.
DOWNLOAD HERE
Install as usual, gapps not included.
While I don't want to start doing too much too fast, I'd like to add in Pdroid support, use Motoinspired as the default theme (I really like it), add in what ever the Skank roms do, and maybe add in Paranoidandriod to the mix.
I've actually wanted to do this since CM9 was released but I got caught up with v4 porting that went nowhere, v4 Patchrom that's being a pita but getting somewhere albeit slowly, found some work, and finally got COD Elite. I'd post my gamertag, but I'm currently using my Dad's since my PS3 is out of commission for the moment (it fell out of my truck door).
/Dammit, all this has done is set my other project back a few days, but I think we'd rather have Kangs from Bravo source rather than a tool to port them from the Defy.....Anyone disagree with that?
Great works skeevy420 ...congratulation..

[Q] Current ROM with OC compatibility

Hi all,
I've scoured the forum for quite some time now and have tried a number of newish ROMs (those posted in May) but have not found any that are compatible with Ktoonsez's latest kernel. A lot of people have advised against overclocking but my GS3 certainly performs better with OC enabled. I flashed one of Jamison's nightlies months ago and it has been the most stable/reliable out of any ROM I've tested since. I either got lucky and found the perfect ROM for my phone or I just haven't found a solid new ROM that supports OC'ing. I've had random reboots, force closes, etc. with all the new ROMs I've tried so I was hoping someone could give me some ideas on a ROM/kernel combination that might work for me. The only reason I even want to change my current ROM is because many of my Google apps report that an update is available, but when I go to update, my "device doesn't support this version." It's quite frustrating and a pretty sad reason to switch ROMs when literally EVERYTHING else works flawlessly, but it is a problem for me and I'd like to be able to stay up to date. Sorry for the long post, but anyone with advice would be wonderful. Thanks!
You need a kernel that support OC, its not ROM specific.. You do however, need to check kernel's description to which base it works with.. Sometimes they will have one for just touchwiz or touchwiz and aosp, thats pretty much the main thing to look for and just try different ones.. It should also say if its OC able or not
Sent from my SGH-T999 using Tapatalk 4 Beta

Categories

Resources