Related
This is a flashable (via Clockwork) zip of the stock Sense kernel for the Vision. It will work on any of the Vision-based phones (G2, DesireZ, etc) but you must be running Sense UI.
Details
Stock kernel binary, nothing touched: 2.6.32.21-gd2764ed
Ramdisk modified with the following:
Property changes: ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Support for /system/etc/init.d scripts.
Conservative and powersave governor modules (loaded automatically on startup). These are not active unless selected, which is why they are loaded.
Overclocking module included, not loaded automatically.
Kineto kernel module included (needed for wifi calling).
CIFS module included.
User Impact (i.e. What does this do for me?)
When using "adb shell", you'll immediately be given a root prompt as opposed to having to "su" first.
"adb remount" works and will remount /system "rw".
You can "adb push" or "adb pull" from any location on the system, once you've remounted.
adb runs during boot up, to help diagnose any issues after applying a change (new kernel, mod, etc).
Mock locations are enabled.
Ability to select 2 additional power governors in SetCPU.
Support for CIFS mounts using supported apps (i.e. Astro).
Support for WiFi calling, assuming other support libs/apps are present.
Disclaimer
As with any modification (ROM, patch, etc), you run the risk of damaging your device. While unlikely, it is important to consider this possibility before proceeding. I take no responsibility for any such damage, data loss or otherwise.
Download Kernel
Fifth haha lol. Dude awesome job on the sense port thanks.
Sent from my T-Mobile G2 using XDA App
mcp2009 said:
Seriously? mad I said first? Don't think your post mattered. I posted to say thnx. What did you post for?
Click to expand...
Click to collapse
Yes. I'm upset you said first because this is supposed to be a serious forum. I posted to point that out. Apparently no one else agrees with me but whatever.
To the OP, thank you for the kernel that I'm sure a number of people are looking for. Sorry for jacking your thread.
not a rom its a kernel, thx OP
Thanks dev I appreciate your work towards Sense UI. Does anyone mind telling me what this kernel will be good for? It says stock Sense, so does that mean, its like the stock kernel but on sense? or that its the desire z kernel?
Phawkes said:
Thanks dev I appreciate your work towards Sense UI. Does anyone mind telling me what this kernel will be good for? It says stock Sense, so does that mean, its like the stock kernel but on sense? or that its the desire z kernel?
Click to expand...
Click to collapse
I presume it's a modified version of the DZ kernel, because the G2 doesn't come with Sense.
Ok, so what exactly do the modifications offer to the end user?
What does this do?
I think by isntalling this kernel it will give you perma root in the rom on a g2.
meaning that root wont get wiped out after reboot.
Even though the emmc is set to s-off the kernel might not have been aware of that.
If i get a bit of time i will give it a shot.
been running the desire rom for a day since i like sense but i noticed i didnt have root even though i could flash stuff (recovery) and hboot was still the eng.
I could be wrong but does the OP refer to setting ro.secure=0 to disable the wp on /system?
so far even though we are perm rooted with an s-off bootloader /system is still set to ro, at least it is for me.
Can someone confirm or deny and explain.
Sent from my HTC Vision using XDA App
what is this? is this desire z with root?
Went back to stock with cyanogen baconbits....it drained too much battery too quick for me
Sent from my T-Mobile G2 using XDA App
Phawkes said:
Ok, so what exactly do the modifications offer to the end user?
Click to expand...
Click to collapse
Here's a rundown of visible changes:
When using "adb shell", you'll immediately be given a root prompt as opposed to having to "su" first.
"adb remount" will remount system "rw".
You can "adb push" or "adb pull" from any location on the system, once you've remounted.
adb runs during boot up, to help diagnose any issues after applying a change (new kernel, mod, etc).
Mock locations are enabled.
You can drop shell scripts into /system/etc/init.d, which are executed at the end of the boot process automatically.
I'll update the OP with this list.
Updated to include several more kernel modules, still the original binary. Check the original post for details.
so.... how do I load the OC-module? Thanks for the kernel
Do you have a public repo I can get the source from? I'd love to compile it with the interactive governor as well, and perhaps BFS.
Novek said:
so.... how do I load the OC-module? Thanks for the kernel
Click to expand...
Click to collapse
yeah i second this. i'm kind of scratching my head here...
To oc you have to:
Insmod /system/lib/modules/z_oc.ko
To get the conservative and powersave scalings you must do an insmod for cpufreq_conservative.ko and cpufreq_powersave.ko in the same folder...
It only oc to 1ghz though
Sent from my HTC Vision using XDA App
Novek said:
To get the conservative and powersave scalings you must do an insmod for cpufreq_conservative.ko and cpufreq_powersave.ko in the same folder...
Click to expand...
Click to collapse
Those are actually loaded for you automatically via initscript in /system/etc/init.d and custom ramdisk which is included with this kernel.
See this thread for more info on the OC module:
http://forum.xda-developers.com/showthread.php?t=813681
Only difference you need to consider from the directions in that thread is the OC module is located in /system/lib/modules rather than /data/local. It will clock all the way up to 1.42ghz if you dare (I don't).
Oki... I just saw that those two weren't in setcpu, and got them loaded by insmod. Thanks
Sent from my HTC Vision using XDA App
cifs Can not be used
cifs Can not be used，File size is also problematic
3200KB?
When using "insmod /sysytem/lib/modules/cifs.ko"
init_module'insmod /sysytem/lib/modules/cifs.ko' failed(On such file or directory)
Why?
I have used many different roms with my metro-flashed evo, and gotten the mms scripts to work. however, i'm trying to use this rom:
http://forum.xda-developers.com/showthread.php?t=1586396
based on SOS/sense 1.0 (i believe..) and I can't figure out why mms isnt working.
i've swapped apns (with the metropcs 3128..) and flashed the 4.67 script, but nothing. any help would be awesome. thanks.
(I would have posted this in Bloody's thread, but I'm a noob/not enough posts)
johnny.dalvik-cache said:
I have used many different roms with my metro-flashed evo, and gotten the mms scripts to work. however, i'm trying to use this rom:
http://forum.xda-developers.com/showthread.php?t=1586396
based on SOS/sense 1.0 (i believe..) and I can't figure out why mms isnt working.
i've swapped apns (with the metropcs 3128..) and flashed the 4.67 script, but nothing. any help would be awesome. thanks.
(I would have posted this in Bloody's thread, but I'm a noob/not enough posts)
Click to expand...
Click to collapse
I couldn't get the script to execute on SOS fo some reason....this, however, did the trick for me:
In root explorer look to see if the script file (metropcs.sh)is in the right place in the internal memory...if not place it there then execute.
Can u guide me to that file from root? Sorry, i have no idea where to go. And how do I execute it? Do i just long press and select "execute" ? I had this same issue with SOS and I don't think I ever got it working on a sense 1.∅ rom
atljatl said:
Can u guide me to that file from root? Sorry, i have no idea where to go. And how do I execute it? Do i just long press and select "execute" ? I had this same issue with SOS and I don't think I ever got it working on a sense 1.∅ rom
Click to expand...
Click to collapse
Sadly, I cannot. Which is why I asked bloodyk. where it was in his rom thread....thinking it disappeared. I cannot locate it in my root or sd.
I know I pulled it from the zip and placed it in root and then executed it within.
To execute, d/l script manager freê from store. Open script manager, locate sh file, ensure su is selected in top row, and touch run (also top row). That should do it.
Thanks Mex. Saw your post just now on bk's thread. If you find anything please let me know. I'm running aosp cuz I really need mms for work. Would love to try the new sos
atljatl....
Did you try doing what JD did to get it going? I am going to give it a try...
JD2589 said:
...And for those of you having trouble getting MMS working on a 4.67 sense rom, Just flashed Bloodys 4.67 MMS script through Amon RA Recovery, For some reason its not flashing in ClockWork Recovery. Here is a link to that specific script only for sense 4.67 roms (successfully tested on Swagstr latest SOS X rom):
http://www.mediafire.com/download.php?5gs5wtgn2jgauj7
JD
Click to expand...
Click to collapse
As for executing/finding bloody's script:
Bloodykiller86 said:
well in my latest scripts its called mpcs.sh and also its not in the root of the phone but in the zip. unzip it and youll see its not inside the folders
Click to expand...
Click to collapse
mexigga said:
atljatl....
Did you try doing what JD did to get it going?...
Click to expand...
Click to collapse
Don't know how I missed that. I'll give it a go... ugh.... Ive been running decks 1.3d for 3 days straight (sort of an eternity....) have everything like i want it! Smh...have u confirmed this fix works?
atljatl said:
Don't know how I missed that. I'll give it a go... ugh.... Ive been running decks 1.3d for 3 days straight (sort of an eternity....) have everything like i want it! Smh...have u confirmed this fix works?
Click to expand...
Click to collapse
JD has...I will try later.
(see you hit JD up also...great)
EDIT: confirmed working.
Hey everyone I am getting a new phone and would like to use my Inc as a mp3 player. I'm looking for a Wifi only ROM not script. If any roms have a wifi only mode that you can choose when you first pick a Tom that would be great. Thanks for any suggestions
Sent from my ADR6300 using XDA
Bump
Sent from my ADR6300 using XDA
bmx5494 said:
Hey everyone I am getting a new phone and would like to use my Inc as a mp3 player. I'm looking for a Wifi only ROM not script. If any roms have a wifi only mode that you can choose when you first pick a Tom that would be great. Thanks for any suggestions
Click to expand...
Click to collapse
Is there a reason why you don't want the script? The beauty of the script is that you can use any ROM you want and use the script to make it wifi-only. Most people pick a ROM that they like and get good battery life with, and then just apply the script.
Aside from the couple of seconds it takes to flash the script, I cant envision any real benefit of having a ROM designed to be wifi-only vs. a ROM made to become wifi-only.
I'm also not sure what picking a "Tom" means... but it's probably not as important as my first question.
Really I did not know that. So when I flash the script what will change on the Rom? And do I need to wipe everything before I flash the script? Oh and spell correct changed Rom to tom and I didn't catch it...........
Sent from my ADR6300 using XDA
bmx5494 said:
Really I did not know that. So when I flash the script what will change on the Rom? And do I need to wipe everything before I flash the script? Oh and spell correct changed Rom to tom and I didn't catch it...........
Sent from my ADR6300 using XDA
Click to expand...
Click to collapse
As far as I know, it doesn't "change" anything... it just disables the radios (except wifi). Think of it like putting your phone in Airplane mode, but the wifi still works. As for wiping, I'm not sure. I've never used the script before.
demarcmj said:
As far as I know, it doesn't "change" anything... it just disables the radios (except wifi). Think of it like putting your phone in Airplane mode, but the wifi still works. As for wiping, I'm not sure. I've never used the script before.
Click to expand...
Click to collapse
Actually wifi works with airplane mode on you just have to turn wifi back on. However with sense you have to do that every boot, not on aosp though. Because of this and to avoid draining battery, the script sounds better for the op.
Sent from my Galaxy Nexus using Tapatalk 2
demarcmj said:
As far as I know, it doesn't "change" anything... it just disables the radios (except wifi). Think of it like putting your phone in Airplane mode, but the wifi still works. As for wiping, I'm not sure. I've never used the script before.
Click to expand...
Click to collapse
All the script does is install a startup script that runs another system script called "radio_options" in /system/bin with an option of 1, dissabling the radio. No wiping is required, and can be removed at any time.
Thanks this helped a lot!
Sent from my ADR6300 using XDA
does anyone have a link to such a script? I remember seeing one a while back but I can't find it anymore. I have turned my D2G into an mp3 player device so I was hoping for the same outcome. Plus it's cleaner to not have a radio attempting to connect all the time.
EDIT: Nevermind, I was under the impression it was a script one would flash, not something you could do yourself with script manager.
nschiwy said:
does anyone have a link to such a script? I remember seeing one a while back but I can't find it anymore. I have turned my D2G into an mp3 player device so I was hoping for the same outcome. Plus it's cleaner to not have a radio attempting to connect all the time.
EDIT: Nevermind, I was under the impression it was a script one would flash, not something you could do yourself with script manager.
Click to expand...
Click to collapse
You just make a file with no extension and then put this in it
Code:
#!/system/bin/sh
radiooptions 1
Then pop the file in your init.d folder if your rom/kernel supports it, or use an app like script manager or autostart root to run the file at boot. Note if using an app to run at startup, you must set the app to run it with root permission.
cmlusco said:
You just make a file with no extension and then put this in it
Code:
#!/system/bin/sh
radiooptions 1
Then pop the file in your init.d folder if your rom/kernel supports it, or use an app like script manager or autostart root to run the file at boot. Note if using an app to run at startup, you must set the app to run it with root permission.
Click to expand...
Click to collapse
I wrote this script using script manager and gave it root permissions and startup permissions and then ran it (also tried rebooting) and it didn't seem to do anything. Are there any visible changes that would take place when you do it?
nschiwy said:
I wrote this script using script manager and gave it root permissions and startup permissions and then ran it (also tried rebooting) and it didn't seem to do anything. Are there any visible changes that would take place when you do it?
Click to expand...
Click to collapse
Yes, the signal bars will grey out and have a white X over them.
Try using a terminal emulator app and type in
Code:
su - Hit Enter
radiooptions 1 - Hit Enter
You should see the signal bars X'd out.
cmlusco said:
Yes, the signal bars will grey out and have a white X over them.
Try using a terminal emulator app and type in
Code:
su - Hit Enter
radiooptions 1 - Hit Enter
You should see the signal bars X'd out.
Click to expand...
Click to collapse
this is what i got when I tried to do that, it didn't seem to change anything.
it's the same image that shows that it doesn't have any signal because there is no number attached to it anymore.
It looks like it worked, the bars are greyed out and has an X. Even if there is no telephone number associated with the phone, it will still show the signal bars as it will still communicate with verizon just not have service.
cmlusco said:
It looks like it worked, the bars are greyed out and has an X. Even if there is no telephone number associated with the phone, it will still show the signal bars as it will still communicate with verizon just not have service.
Click to expand...
Click to collapse
haha well in that case there might be something wrong with the phone because it has been like that since I flashed the ROM but it doesnt really matter since I don't need it.
Hello folks! As the title says I have quite a strange issue with some kernels (Franco,LeanKernel and STOCK!!). I flash the kernels after flashing a rom ,doing it clean(all the wipes) and the phone is working fine for couple hours or a day,after that it just going verry sluggish even in appdrawer or when switching desktop screens. I looked at the CPU frequencies and they change as they shouldn't,I can tell that somethig isn't right with the cpu...I have this issue only with those kernels. I tried stock roms,4.2.x roms,flashed even google images to be sure it's stock,tried them with AOKP 4.2 and 4.1 ,CNA and the list could go on...
Is someone else having the same issue??
Any fix for this? I really want to try franco's kernel!!!
1. Hmmm, are you running a live wallpaper?
2. Do you face the same issue while using Trinity Kernel?
3. Are you sure you do not have any app such as SetCPU which is controlling the speed of CPU?
4. If you set the CPU speed back to normal, does this fix the issue?
5. How much space is mostly left on your sdcard?
I hope the answers of these questions will help to identify your problem much bettER
I don't have the same issue with faux's and trinity kernels . I don't have any program,i don't use a live wallpaper, how I can speed back to normal the cpu?
calinoii said:
I looked at the CPU frequencies and they change as they shouldn't
Click to expand...
Click to collapse
I thought you have checked the CPU speed/frequency using an app like "AnTuTu CPU Master".
calinoii said:
how I can speed back to normal the cpu?
Click to expand...
Click to collapse
Using AnTuTu CPU Master, check the speed set for the CPU when the phone is sluggish and if it something other than the normal 1200 MHz then modify it back to normal. This is what I meant
The frequencies changes verry verry fast,that's when the phone becomes sluggish,i have mini freezes,lots of them
calinoii said:
The frequencies changes verry verry fast,that's when the phone becomes sluggish,i have mini freezes,lots of them
Click to expand...
Click to collapse
I think some background processes are causing this so the CPU is trying to respond to them.
I suggest that you do a full wipe, install a ROM and use Franco's kernel, but do not install any other application on your phone, only default ones installed already with the ROM, maybe Gapps as well just to have a usable phone for some time, then check after a day whether it is again sluggish although there are no applications at all or it is still running fine. At least we would be able to know that maybe one of your application is not compatible well with these kernels and causing this mess.
You may want to avoid wiping so try to force stop the applications running in the background (and cached processes as well) to see if one of them is causing this problem.
Good Luck
I did wipe the data and didn't install any application and I have the same issue :-s
calinoii said:
I did wipe the data and didn't install any application and I have the same issue :-s
Click to expand...
Click to collapse
Do you use any widgets?
Nope
I am not sure I have helpful suggestions anymore except to be sure that you are using the correct Franco kernel whether you are running a 4.1 ROM or 4.2 one.
I hope other members can solve this problem for you. Maybe you will get a bettER help if you discuss this with the Franco kernel users on the Franco kernel thread.
Thanks anyway,i'll post this issue on franco's kernel thread and hope for a fix...and be sure i flashed the correct version of kernel )
Anyone? Please?
calinoii said:
I have some others with the same problem,but thisis the latest,no one could help me this far.I already did what you suggested me...I`m sure I did the clean wipes,just installed gapps and nothing else...when it was getting little hot the freezes were starting too,I think i did all I could,many people in this forums adviced me and still nothing,maybe franco's the only one who can help me with this...
Click to expand...
Click to collapse
Carrying on from here where we were in franco's thread. If you're flashing gapps then clearly you aren't using stock ROM like I told you to try. So, my suggestion to you for troubleshooting remains the same:
osm0sis said:
Well that's really peculiar. I'd try flashing stock again using fastboot. I'd fastboot oem lock, then fastboot oem unlock to wipe, then flash the entire image set as in efrant's thread just to make sure it all gets wiped. But unfortunately, like I said, if stock kernel doesn't work over a fresh fastboot flash of Google's factory image on your device there's still something very wrong, and it's likely wrong with the device itself.
Click to expand...
Click to collapse
osm0sis said:
Use the latest Google Factory Image for your device like I suggested, then you can see if you get the OTA immediately or you can flash it yourself. Do all this before you put any apps on, and don't let it put any apps on and see if you still have the issue with a completely stock setup.
Click to expand...
Click to collapse
Please report back only when you've followed that to the letter.
Tried both,the ones from the images,and the gapps on a stock flashed rom via recovery...I'm trying to resolve this for over 2 weeks now...
L.E : Ok,I will pm you when I manage to have some time for doing this again,thanks for your kindnes
I don't care how many times you think you've done it correctly before, I want you to try it AGAIN. And make sure you've completely wiped by using fastboot oem lock and unlock, then follow efrant's thread to the letter for flashing the entire image set. Factory Images ONLY, no stock-ish kitchen garbage.
I'm happy to help you but you've got to follow my instructions, since this is what I would be doing if I had this issue on my device.
Ok,I will,is there anyguide for locking and unlockingthe bootloader ? or simply "fastboot oem lock" and after "fastboot oem unlock" ?
calinoii said:
Ok,I will,is there anyguide for locking and unlockingthe bootloader ? or simply "fastboot oem lock" and after "fastboot oem unlock" ?
Click to expand...
Click to collapse
Yeah those are the commands. That's it. :good:
I think it's mentioned in efrant's post too, but no special guide necessary. Use the adb and fastboot that he attached too if you're new to fastboot.
I'm used to fastboot,I don't even need the guide to see the commands now,I think I used them like 100 times last 2 weeks )
Fair enough. Please follow the guide anyway though, and be sure to also flash userdata.img and recovery.img to be completely stock. You can fastboot boot cwm.img if you need it to flash your OTA afterwards. We just need you at 100% stock so we can try to figure this thing out. Also maybe hold off on adding your Google account so it doesn't start forcing apps onto your device. It could very well still be a rogue app issue so we need to try and keep your device as empty as possible to see if we can rule out hardware defect. :good:
Should I install any apps?
I did everything you said,now i'm waiting for it to boot up
I did the unbrick method to restore my download mode a few days ago and have since gone ahead and installed the latest roms/kernels(currently on latest TBSGS3 and an AGAT FI16 kernel I believe, also tried with Jellyverse ROM and stock kernel). Now when I try to run my apps with Eclipse or even doing them manually they appear to go through successfully but the app does not end up on my phone. I tried a few samples from google as well as a basic "Hello World" app and it's no good.
Eclipse will report:
[2013-01-08 13:06:06 - BasicGLSurfaceView] Uploading BasicGLSurfaceView.apk onto device '464119fa1e8c1eb'
[2013-01-08 13:06:06 - BasicGLSurfaceView] Installing BasicGLSurfaceView.apk...
[2013-01-08 13:06:11 - BasicGLSurfaceView] Success!
[2013-01-08 13:06:11 - BasicGLSurfaceView] Starting activity com.example.android.basicglsurfaceview.BasicGLSurfaceViewActivity on device 464119fa1e8c1eb
But there is no activity on my phone and no app in the launcher and no further activity in Eclipse's console.
Then when I try to manually do it with ADB I get:
c:\Android\sdk\platform-tools>adb install BasicGLSurfaceView.apk
240 KB/s (11599 bytes in 0.047s)
c:\Android\sdk\platform-tools>
I've done the uninstalling/reinstalling of kies/drivers and the offline install method and all of that. The phone is installed properly for storage mode and download mode and is seen with the "adb devices" command. The lack of errors is baffling to me. Any guesses here?
Please confirm that you're running a jb repack as a dd. The repacks aren't meant for daily use. Application issues are part of the known problems currently.
If you are running the repack, change to stock. At least rule out the kernel.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
MoHoGalore said:
Please confirm that you're running a jb repack as a dd. The repacks aren't meant for daily use. Application issues are part of the known problems currently.
If you are running the repack, change to stock. At least rule out the kernel.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Beat me to it. HAHA!
If you are stock, I found this in stackoverflow for a possible answer.
Make sure when you setup the emulator in the Hardware properties you add GPU emulation and set the value to yes.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Yes I'm using what I wrote in the original post. Without sounding snarky, your answer from stackoverflow clearly says emulator and something about graphics acceleration, and I'm on an ET4G with some sort of USB/permission/kernel issue...
I've been running non-stock everything since I got the phone about a year ago and never ran into this issue. I will try to revert to complete stock but I'm a bit hesitant to try that because two different roms and kernels(one stock) both have this same odd problem, no difference at all. I can't seem to find any similar cases online, the search terms "cant adb install no error"and every other way I've searched has brought up only problems with errors. I'll revert to complete stock and return with results.
If anyone knows a fix, or even something reasonable to try so I can use my favorite latest roms/kernels and retain development ability I will give it a try.
timhimosc said:
Yes I'm using what I wrote in the original post. Without sounding snarky, your answer from stackoverflow clearly says emulator and something about graphics acceleration, and I'm on an ET4G with some sort of USB/permission/kernel issue...
I've been running non-stock everything since I got the phone about a year ago and never ran into this issue. I will try to revert to complete stock but I'm a bit hesitant to try that because two different roms and kernels(one stock) both have this same odd problem, no difference at all. I can't seem to find any similar cases online, the search terms "cant adb install no error"and every other way I've searched has brought up only problems with errors. I'll revert to complete stock and return with results.
If anyone knows a fix, or even something reasonable to try so I can use my favorite latest roms/kernels and retain development ability I will give it a try.
Click to expand...
Click to collapse
You weren't being snarky. I didn't take it that way.
I was taking into account that you were having an install issue from console to device, which that's what I could only find it relating to.
What you've pasted didn't have any returns pointing to permissions and it seems stackoverflow is the only location with any real answers,. And what I said in post two, we know that there are application issues with the repack. That's why I suggested going back to stock to rule out the kernel.
The repack that you're using isn't that old so you have a confirmed setup that you had working prior, why not go back to that setup and confirming?
:edit: -For the Lurkers - Had someone ask me what Eclipse is. AdamOutler did this last year. It's the only reason I know what it is.
MoHoGalore said:
You weren't being snarky. I didn't take it that way.
I was taking into account that you were having an install issue from console to device, which that's what I could only find it relating to.
What you've pasted didn't have any returns pointing to permissions and it seems stackoverflow is the only location with any real answers,. And what I said in post two, we know that there are application issues with the repack. That's why I suggested going back to stock to rule out the kernel.
The repack that you're using isn't that old so you have a confirmed setup that you had working prior, why not go back to that setup and confirming?
:edit: -For the Lurkers - Had someone ask me what Eclipse is. AdamOutler did this last year. It's the only reason I know what it is.
Click to expand...
Click to collapse
Instead of doing something as atrocious as going back to stock I tried an ICS rom/kernel(Blu Kubans) and everything is working smoothly and quickly. I only have a small sample pool of 2 JB roms and 2 JB kernels but I'm going to go ahead and assume it's a JB problem until someone with OS/hardware programming knowledge tells me otherwise(I only do apps). Can anyone confirm this by trying to run an adb install command on a JB kernel/rom? Being on a huge developer site I assumed SOMEONE would have run into this same issue, but maybe they were more content than I am about going backwards in Android versions and not bringing it up.
Again, problem technically solved but only by switching device rom/kernel completely to ICS. The whole developing on JB is a big deal to me just for the sake of being on the latest version so I'd like to keep research going. Thanks.