Hey Guys,
I have installed Vicious's JB GSM port of Jelly Bean on my verizion Galaxy Nexus. Everything works fine except when I am debugging my apps. I can't debug my compiled apps on the phone.
I also selected the device on AVD Manager and still its doesn't work. All developer options are enable on the phone (Unknown sources, USB debugging)
Would appreciate any feedback
[p.s - i am using the stock jelly bean kernel]
I noticed the same problem today too.
Had the same issue..
I had the same issue and trying reloading V3, loading a bunch of different kernels with no luck. I ended up doing the following to get a working Jellybean release as ADB / eclipse still working correctly for development.
t=1738018From this page:
TeamLiquid JellyBean V1- SU zip necessary - Stock Kernel
SuperSU for Jelly Build
vannilia kernal "Stock Flashable JellyBean kernel boot.img format: HIGHLY RECOMMENDED!!!"
Wifi Fix "If you want to stay on the stock kernel there is a WiFi fix here thanks to Mwalt2"
metalideath said:
I had the same issue and trying reloading V3, loading a bunch of different kernels with no luck. I ended up doing the following to get a working Jellybean release as ADB / eclipse still working correctly for development.
t=1738018From this page:
TeamLiquid JellyBean V1- SU zip necessary - Stock Kernel
SuperSU for Jelly Build
vannilia kernal "Stock Flashable JellyBean kernel boot.img format: HIGHLY RECOMMENDED!!!"
Wifi Fix "If you want to stay on the stock kernel there is a WiFi fix here thanks to Mwalt2"
Click to expand...
Click to collapse
What did you end up doing exactly? Flashing the stock kernel?
I'm getting the same errors showing the apk being installed but nothing working and wierd output in logcat.
Alright, I know the camera isn't broken because the camera works on any rom that isn't cyanogen based. I made sure i wiped all data and cache before installing cyanogen and I got the correct gapps too, but every time i try to load any camera app, it errors and shuts down. the integrated camera app says "cannot connect to camera" and then closes right away after opening it. How is this fixable? what am I doing wrong?
Bump, Im having the same issue. Its perplexing to say the least.
What camera are you using? I was on Paranoid Android 2.54 and when I flashed the 4.2 camera, it did not play nice. Taking a picture will freeze the app and then from that point on it never connected to camera. Are you pulling the right Gapps?
ELStiko said:
What camera are you using? I was on Paranoid Android 2.54 and when I flashed the 4.2 camera, it did not play nice. Taking a picture will freeze the app and then from that point on it never connected to camera. Are you pulling the right Gapps?
Click to expand...
Click to collapse
I flashed black bean v7 along with the gapps they posted on their website for bb7. I've been flashing the 4.1 gapps on the 4.1 Roms and 4.2 gapps on the 4.2 Roms. I did a bit more research and a few people have mentioned a bin file that they grab from the stock image and put into /data on the new rom. I'm going to try that in a bit.
Try this,
http://forum.xda-developers.com/showthread.php?t=2102981
T-Mobile SGS III
Hi guys,
I'm running stock 4.1.2 Jelly Bean on my d2tmo Galaxy S3. When I look up kernels and whatnot, they are labelled many different ways. Some have JB in the name, some with AOSP in the name. I'm wondering: what types of kernels can I flash if I'm running a rooted stock ROM? I don't want to flash any custom ROMs because I'm a musichead and I like the stock music player
Thank you!
First of all you can get then stock music player with a custom rom
Second you can only run aosp kernels with an aosp rom. Aosp stands for android open source project. Aosp is not stock.
You can only use kernels labeled stock or touchwiz if you are using stock based rom
Sent from my SGH-T999 using Tapatalk 2
3rd of all, what in the heck do you want? Haha, you say you are running a 4.1.2 rom (only aosp available on TMO) so AOSP... but you want a kernel for stock (4.1.1) touchwiz rom? The stock music apk is great and works on all stock touchwiz based roms, and in my resource guide I have a huge list of what is available and what is what, if the kernel says 4.1.1 TouchWiz then it is for 4.1.1 TouchWiz. if it says 4.2 AOSP it is for 4.2 AOSP, if it says 4.1 AOSP then it is for 4.1 AOSP... Look in my resource bible in my signature, or in the dev sections for [kernel].
See, that's where I get confused. Sorry for the noob questions. I've been looking around but can't find clear, precise answers.
I'm running the stock TouchWiz, out of the box, 4.1.1 Jelly Bean (updated while not rooted to 4.1.2). That stock ROM is not the same as an AOSP ROM or an AOKP ROM, is it? I have another Android device that runs CM10.1 so I know a bit here and a bit there about ROMs and whatnot, but I'm not so confident when it comes to my S3.
Simply put, I want to keep that stock ROM, but get a custom kernel, because the stock kernel SUCKS. I need to know what kernels I can flash, and clninja already said I can only flash kernels labelled stock or TW. Am I correct, so far?
Thank you!
Well here's a Kernel that is supposed to be supported for STOCK rooted : http://forum.xda-developers.com/showthread.php?t=1785466 :highfive: But seriously you should get a custom ROM, the performance improvement is incredible and power management too ! :laugh:
There is a 4.1.2 stock ota ROM?!? I suck lol.
Sent from my SGH-T999 using xda premium
kruse1944 said:
Well here's a Kernel that is supposed to be supported for STOCK rooted : http://forum.xda-developers.com/showthread.php?t=1785466 :highfive: But seriously you should get a custom ROM, the performance improvement is incredible and power management too ! :laugh:
Click to expand...
Click to collapse
That ROM is labelled Jelly Bean in the title but underneath that it says it's only compatible with ICS. Question mark.
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
seokhun said:
That ROM is labelled Jelly Bean in the title but underneath that it says it's only compatible with ICS. Question mark.
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
Click to expand...
Click to collapse
There are a couple of touchwiz kernal's around, Ktoonsez is one that I would recommend, http://forum.xda-developers.com/showthread.php?t=1871946
Usually the general rule of thumb with upgrading custom rom is full wipe and flash, but some users has dirty flashed and had no problems so it depends whether your phone likes you or not.
mt3g said:
There is a 4.1.2 stock ota ROM?!? I suck lol.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I see what you did there. :highfive:
seokhun said:
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
Click to expand...
Click to collapse
Most of the times when you flash a ROM that is built off itself, you can "dirty flash". Example--> That means if you are already on a RootBox Nightly 2/17 with a clean install and RootBox 3/6 comes out, all you have to do is wipe /cache and /dalvik-cache and then flash the new version of the ROM. If any bugs creep up, then if you dirty flashed, chances are that is why.
If you are going to go from a TWiz ROM to an AOSP/AOKP ROM then I suggest a full factory reset and wipe accordingly. That way you have a clean install.
Read the OPs of the ROMs
TieDye21 said:
Usually the general rule of thumb with upgrading custom rom is full wipe and flash, but some users has dirty flashed and had no problems so it depends whether your phone likes you or not.
Click to expand...
Click to collapse
Yup. Thankfully my phone likes me, plus I kind of know what I am doing with regards to diagnosis.
@OP Can you please post exactly what your Build Number says in Settings>About Phone?
seokhun said:
That ROM is labelled Jelly Bean in the title but underneath that it says it's only compatible with ICS. Question mark.
Question: when you're running a custom ROM, if there's an update for it, say from 1.0.0 to 1.0.1, you can just flash the update right over and not worry about problems right? Or do you need to factory reset through recovery and wipe the caches all over again?
Click to expand...
Click to collapse
You could install the update, but seriously I never do updates. I manual flash the whole new ROM. ( and I never had any accidents or bugs)
For the kernel, its was a example kernel chose the one you prefert ( THAT SUPPORT TOUCHWIZ STOCK ROM ) or just flash a new ROM with build-in kernel like the ParanoidKANGdroid 10.2 ROM !
I flashed the FrostyJellybean ROM with Xone kernel and it's been good so far. I'm a religious person when it comes to battery, but so far it's about the same as the normal drainage on the stock ROM, no noticeable improvements.
Another question (whoop): if I run a Nandroid backup, does that backup include the ROM itself? In other words, if I'm running the Frosty ROM, and there's a ROM I want to test, will creating a Nandroid include the Frosty, or will it just backup the system image excluding the ROM itself? I'm asking this because I have wanted to restore my Nandroids but didn't know if that backup may overwrite my existing ROM with the previous ROM.
Thank you guys for taking your time to help me out, I really appreciate it!
Woody said:
@OP Can you please post exactly what your Build Number says in Settings>About Phone?
Click to expand...
Click to collapse
I have flashed a new ROM, so I no longer have the stock Build Number. It now says FrostyJellybean v11.6. I can tell you for a fact that I was previously running 4.1.1 rooted but without any customization or mod whatsoever outside the phone's original settings, so as stock as you can get.
A Nandroid is essentially a snapshot of your ROM at that point in time. You can back it up, try a new ROM and if you don't like it, then restore your Nandroid. A Nandroid should be done before you flash anything. You don't necessarily have to keep them all except your latest, but at least have one for when you try something out.
You can flash and restore just fine from ROM to ROM. Only thing is, you can't restore across platforms. Meaning, if you are on JB 4.1.1, you couldn't restore to ICS 4.0.4. Likewise you can restore a JB 4.1.1 if you are on a JB 4.2.2 ROM because of the file structure. There are ways to do it, but I won't go into that right now. Moral of that story is you can flash and restore laterally as far as builds go, but you cannot restore across different base builds.
*************
I just wanted to see your Settings>About Phone>Build Number because in your OP, you stated that you were running "stock 4.1.2 Jelly Bean". We don't have a stock 4.1.2 ROM, so I was making sure you didn't have another phone. Sure, could be a T999 but there are Canadian versions out there that require different things.
Oh, about the Android version, yes, it's 4.1.1. I wrote 4.1.2 because I thought there was some stuff going on, like wireless and whatnot, and had previously read somewhere that 4.1.2 was rolling out and my phone was doing the "Android is upgrading" thing when it booted up and I didn't check the version before writing that. No worries, it was the stock 4.1.1.
Thank you so much for answering my questions, you guys are awesome!
hi all just tried to update my cer iconia a700 with cyanogenmod cm 10.1 anyways download it to tablet installed clockwork recovery as well as downloading gapps clicke on mod file and it opened clockwork and i clicked install to install mod/update and now just boots to cyanogenmod on load screen and just sits ther for hours like its loading but nothing happening how to i get back to old rom or even carry on with update i was on 4.1 jb tried to update to 4.2 and yes its rooted sry i am a noob to this thanks in advance
Hello smedzz.
Your device only has experimental and nightlies for Cyanogenmod, with no RC or stable ROMs available. The problem you are experiencing sounds a lot like the problem I had with Cyanogenmod 9.0 for my Samsung Galaxy S i9000. It was a release Candidate (RC), and slightly unstable, and hung up on the boot graphic occasionally. The only way to fix it was to flash the phone again (my experience).
If that sounds like a pain, you could look for a different ROM in the Developer section of the forums for the a700. The "iconiaN 2.6" ROM, based on Jelly Bean 4.1.1, sounds good. At least it would get your tablet working again.
http://forum.xda-developers.com/showthread.php?t=1952124
Already solved?
Did you wipe?
factory reset
wipe cach/dalvik
flashed pa and gaps
has no keyboard, got around it now it reads all these errors
googleplaystore stopped
androidaosp stopped
.com.android.phone stopped
is this compatible, fixable? worth it?
forgot to add it has android 4.1.2 3.0.46 cynogenmod kernel and pav 2.5
Which gapps are you using?
Also, is there no updated ROM for you device?