Re: [CM10.1|4.2.2] JellyBeer-v3.57.2 [DPI Groups] [Feb. 17]
I have but im a noob at this stuff.. are there alternatives then using usb.. like will airdroid work?
Wifi File Explorer works, and the UI/performance differences are OP.
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
---------- Post added at 12:51 AM ---------- Previous post was at 12:49 AM ----------
So taking pictures work but recording a video doesnt. I'm assuming there's going to be a fix for this. Are there any alternatives or no.
Update: i did a reboot and now recording actually works.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I haven't had any issue whatsoever with recording...I think you may he gotten unlucky with a wonky flash. Backup, wipe, reflash.
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
---------- Post added at 01:18 AM ---------- Previous post was at 12:51 AM ----------
you can't cross flash - it's a huge architectural difference and it'll break things.
from what i'm seeing, yes bluetooth (for hid things) is completely broken and works with neither jellybeer 3.57.2 nor cm10.1 (as of 2/19 which is the last build i tested). bluetooth hid devices pair but don't connect after. bluetooth for a2dp seems to be working properly for me though as i was able to successfully pair with and transmit to several bluetooth speaker systems so i'm not sure exactly what's going on, but BT HID devices just plain don't work with current i717 4.2.2 builds from what i'm seeing. if someone here has a method of fixing this, or noticing that it works in more recent builds, or would like to captain this, figure out wtf is wrong, and fix it, I and many others would be greatly appreciative.
HID as in PS3 and Wii Remotes? Or are you working with a different peripheral set? Let's see what we can figure out.
To all:
Please keep in mind that the 4.2x ROMs are previews, built from a CM base. You're not gonna find a fix if a fix doesn't exist. Manuel is great, and if its reasonable and possible, he'll fix it. There are currently no incentive to exclude fixes, for any developer for our device. But there also exists no incentive to duplicate work and create fixes that'll be reworked, or won't be committed to the project. Being a trendsetter on a midnight-showing of a preview-before-the -preview before the release of the preview-for-the-release-of-a-preview will net you a lot of work , and little, to no gain when you see the fix pushed out the next day.
These are unofficial previews which are dang stable, dang fast, and flawless from a feature standpoint. If your needs are niche in nature, you'll likely have better luck in time once we get past the preview stage, or right now with something that isn't a preview.
Car mode (actually my first time even hearing about a car mode for our note....is it a docking profile? An app? Hardware? Send me a PM please!), HID, will probably be pretty low on the Priority-Fix-Totem-Pole, so don't expect a miracle.
With that being said....there's an app for anything. A specific method might not work with your car, but I bet there's an app alternative. There's an app for everything
HID, however, is another story sadly. I wouldnt expect an app to work its way around an entire protocol
But people need to be reasonable with their expectations....their expectations of what's essentially an alpha, or pre alpha, and their expectations for a fix...especially one that goes above and beyond what the CM project currently does. Do you guys remember the CM9 previews? We've gone a looooooooong way since then.
This isn't a case of "the fix is out there, grr why isn't this working" because the issue is widespread...but we should clicky-the-thanky button (beyond informing people of their objective-yet-reproducable issues and then moving on) and look to the awesome tweaks and fixes that are exclusive to Manuel and his work, like the flicker workaround.
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app