Related
The adaption of the newly released VegaComb / honeycomb 3.0 for our tegra2 brothers (advent vega and Adam) and is getting to a state where its usable and the latest alpha4 release for Vega is working quite well on Folio100 as well. with a few modifications of course...
I cannot take full credits for the intensive work done on this honeycomb 3.0 , that is primarily done by NotionInk Adam and Advent Vega developers , which are: MrGuy , newbe5 , corvus , HomerSp I added some kernel changes and image adjustments to support A7.
Download A7Comb 0.2a patch update here
installs like any other "Update.zip", rename the downloaded file to Update.zip
Download A7Comb 0.2 full image update here
installs like any other "Update.zip" (extract the Update.zip from this downloaded zip file) and make sure you "wipe" / factory reset.
Alternate kernel, with original softkeys enabled can be downloaded here
this is also used when you change density setting to 130, so you get the "gingerbread" launcher running instead.
Rename this download to Update.zip and copy directly to sdcard. no unpacking for this is required.
So what is status on a7 port.
- Wifi works, you need to reboot the first you enable it, and it will scan correctly.
- touchscreen seems 100% ok. (did not test multitouch apps)
- Adobe Flashplayer blank (just keep pressing upper left corner like normal to get fullscreen and it works)
- too many apps in the apps list makes them go outside screen.. one solution might be to change density. see build.prop and maybe try 110 instead of the current 120.
You can write whatever status or reported finding, but please check, its not already in the advent/vega issue list, as it share alot with their image.
I will do what is possible to bring it to a better state, but i cannot promise anything and maybe patches from vega/adam might actually work on A7 depending on what they change. (if its a patch)
v0.2a
- Increased 2d/3d performance
- polaris office fixes
- brightness control fix
v0.2 updates
- using newest updates from VegaComb (Gmail and other googleapps now shows correctly)
- Market can now be used for login with an Googleaccount.
reserved for me
I did get bigrushdog to take a look into making us a kernel he is the one who has been working on them for the xoom.
And its online.
Thanks for HC dexter I am testing it now...
Been playing with it for a few hours. touch on the screen is hit or miss at best. Market is a non-starter. Titanium Backup is crashing every other app install. Unable to load Amazon App Store anymore (just stuck in a non-ending registering cycle) But on a good note looks great in landscape, Portrait not so much. Wifi started right up after restart and found my network just fine. Will play a little bit more.
Google Apps working now!!
Ill post the new image later on.. and "Books" now stays (was automatically removed before)
Had to revert back to 1.42, no soft key work. Will wait for new update..
Sent from my A7-040 using Tapatalk
tumpy said:
Had to revert back to 1.42, no soft key work. Will wait for new update..
Click to expand...
Click to collapse
softkeys disabled.. Honeycomb do not use them anymore
Look at the bottom left, thats your control buttons.. thats pretty much what as example "motorola xoom with honeycomb 3.0" looks like now.. so its no error , i disabled those on purpose..
problem is that you got half the screen size of a "certified" tablet, so not much room for pressing buttons and resolutions very low.. so you're missing alot due to the lack of space.. and thats pretty much why A7 is never getting a proper honeycomb when minimum requirements are 1280x800
Soft keys were removed If I had read correctly due to the fact HC has them and dex seen no reason to have two of them. I like the idea of not having them means you don't have to worry about hitting them on accident
http://www.slatedroid.com/topic/179...otloader-froyogingerhc-works-for-notion-roms/
adams kernel was this the basis a source you used to make changes to ours?
rombold said:
http://www.slatedroid.com/topic/179...otloader-froyogingerhc-works-for-notion-roms/
adams kernel was this the basis a source you used to make changes to ours?
Click to expand...
Click to collapse
no, i used StreamTVNetwork's released source from their website..
you cannot use other devices unless you once again try to adapt the drivers to the kernel, which is a big one, since no one did, you can imagine how much work it takes..
you modifiy the existing kernel you got for your device, which the git changes where possible into your existing code, and update where it requiress it.
So we could maybe get the 1.5Ghz update, but im not sure if i can extract and diff it so we can implement into the a7 kernel.
I wasn't meaning did you use that kernel. I guess I could have been a bit clearer. What I meant was seeing how that kernel is adapted to be used with HC could that be off benefit to a dev for our a7. Using it as a guide to some degree
This may be a silly question but...with a dedicated gpu could not the ROM resolution actually be resized to fit the A7? I mean this is not a case of trying to increase resolution (at its native resolution you can't get more than it can reproduce) but down converting it. In other words (This may be a bad example) a standard 720p television that can receive a 1080p signal but down-converts it to 720p.
amwilliams9 said:
This may be a silly question but...with a dedicated gpu could not the ROM resolution actually be resized to fit the A7? I mean this is not a case of trying to increase resolution (at its native resolution .
Click to expand...
Click to collapse
with the next update, im uploading in some hours you can use Market, then download the "Density" app, which can change density (not resoluion) but everything becomes smaller and its harder to hit the soft buttons in lower left side, so you know (as i tried it)
Hi Dexter: Thanks for your work. I m new w A7 and try yet this update but bluetooth not turn on...
wait for you new release. Thanks again.
v0.2 is online
V0.2 is online. Got Googleapps login fixed, so you can use Market and Gmail (Using apps from latest VegaComb)
ming_a said:
Hi Dexter: Thanks for your work. I m new w A7 and try yet this update but bluetooth not turn on...
wait for you new release. thanks again.
Click to expand...
Click to collapse
i can almost say 100% Bluetooth will never work on this rom!
so don't wait for it, then you can start looking for a new tablet with 3.0
Notice the 02 image is much smaller than previous image, about to test this one..I think GB will be out best bet for the A7, I am satisfied with froyo, if HG is out of our reach how about Gingerbread..is it possible Dexter?..
Sent from my A7-040 using Tapatalk
tumpy said:
Notice the 02 image is much smaller than previous image, about to test this one..I think GB will be out best bet for the A7, I am satisfied with froyo, if HG is out of our reach how about Gingerbread..is it possible Dexter?..
Sent from my A7-040 using Tapatalk
Click to expand...
Click to collapse
no, basically a7 is stuck on in 2.2. a 2.3 release still require a formal 2.6.36. kernel which vendors do not adapt drivers for, so if any 2.3 arrive, it will be like this one, using a 2.6.32.9 kernel. maybe with a few patches upto 2.6.32.34 or so, but still using the old drivers vendors delivered..
the guys found out several "libs" of 40MB+ were not needed at all, so i removed them as well..
Weird, Upon first install i recived " Installation aborted" Due to some E:Can't find entry for META-INF/com/google/android/update-binary. Any ideas? Trying install again from fresh download.
Update: No go 2nd time around..... ?
Hi! This is my first mod for Android; a partially working attempt at getting the Samsung camera (from the leaked 4.2.2 ROM; XUFME7) to work on AOSP ROMs. Not a skin, this is the full camera along with most of the features!
Want to see it in action? No screenshot - it looks exactly the same as on TW ROMs - but here's a video. http://www.youtube.com/watch?v=mYX4PSVDiIU Apologies for the terrible quality, but it's hard to film a phone with the Nexus 7's front camera, and I couldn't find a decent screen capture app :<
--
Port for Android 4.3
Beta version NOW AVAILABLE, click here for details + download: http://forum.xda-developers.com/showpost.php?p=46566446&postcount=135
It doesn't work as well as the 4.2.2 version - in particular, video recording is 100% broken, even in the AOSP camera - but you can still try it out if you don't mind this!
--
Port for Android 4.2.2
Working/Non-Working Features List:
What Works:
Front and back cameras
"Wand" Filters
Flash
Auto & Macro focus modes
Tap-to-focus
White Balance options
GPS tagging
Gallery shortcut (uses AOSP Gallery)
Shooting modes:
Single Shot
Best Photo
Face Detection
HDR
Beauty
Smile Shot
Low light
Possibly Working, depending on kernel:
(These features require that the mediaserver process can write to /sdcard (for burst shot/best face) and /data (for panorama). The only way to change this is using a modified kernel with an init.rc which gives it that access. In my experience, with Googy-Max kernel, Panorama works but the other two don't. Your mileage may vary.)
Burst shot
Best Face
Panorama
Not Working, may be fixed later:
Shutter sounds
Automatic mDNIe / screen brightness adjustment
Not Working, unlikely to be fixed:
Camcorder
Share Shot
Voice recognition
Weather/city photo tagging in the media database (what's this used for exactly?)
Untested:
Buddy Photo Share
External SD card
Download:
Download:
This patch is ONLY compatible with AOSP-based 4.2.2 ROMs running on the GT-I9300 and GT-I9300T; the international models of the Galaxy S3 (Exynos chip, no LTE)
CWM zip: http://d-h.st/sg8 (5.26 MB / MD5: f53d603f49de1bb0aba90546b9bbc1ce)
Notes:
This patch has only been tested on RootBox 4.1. Please let me know if you have trouble using it on any other ROM!
Disclaimer:
This is an experimental patch, and you install it at your own risk! I am not responsible for anything that occurs as a result of this. Always make backups.
Installation:
You need a recovery that allows you to install .zip files; most likely CWM or TWRP. But you probably already have one of these if you're running AOSP on this phone
1. Boot into recovery mode: turn the phone off, hold down VolumeUp+Home and then press the power button
2. Make a Nandroid backup (not obligatory, but recommended in case something goes wrong!)
3. Flash the camera mod zip
4. Wipe the Cache and Dalvik Cache - just in case
Hope you enjoy it! Now go out and take some awesome photos
Changelog:
20th July 2013: Released first version. Camera (+ most features) is functional. Camcorder appears but does not record successfully.
22nd July 2013: Released new version which should work on any AOSP ROM, instead of needing a custom built ROM.
17th October 2013: 4.3 beta release is out.
Hm, I'm guessing that the picture quality isn't different from the AOSP camera app and this tho there still is missing sources from Samsung that we'll never get.
Otherwise. Nice mod!
Eleve11 said:
Hm, I'm guessing that the picture quality isn't different from the AOSP camera app and this tho there still is missing sources from Samsung that we'll never get.
Otherwise. Nice mod!
Click to expand...
Click to collapse
Thank you
I've seen people talk about how the camera on AOSP is worse because of missing sources, but I'm not sure what sources these are. The Samsung kernel module is open source, and this mod replaces all the user space code related to the camera - as far as I know, anyway - with the TW versions. (Please correct me if I'm wrong on this )
This is purely anecdotal and rather hard to test accurately, but I never noticed much of a difference in picture quality between AOSP and TW, I just wanted the camera app because of the extra modes and options that are really useful.
I was not Using AOSP based ROMs only for the sake of camera.
But now, i can use any ROM i want..
Thannks man.. This is super cool.. will test this ASAP..
Well, the full version method didn't work for me on todays' CM nightly build. I installed it following the procedures, and then opened the camera app. The screen went black, and then froze. I restarted the phone, and it kept looping on the boot animation
Luckily I don't delete the CM updater temporary files, so I was able to boot into recovery and re-install the 'stock' CM build. Also, despite the fact that I mostly understood the instructions, they were quite confusing!
does hdr work? is it like the tw cam?
Sent from my GT-I9300 using xda app-developers app
kuci06 said:
Okay, so I just flashed the modified Rootbox rom, and the burst shot feature does not work properly. The little counter bar comes up, but doesn't shoot photos at all. Also breaks functionality after that, not even the close button works.
Click to expand...
Click to collapse
Just as I expected I'll have to figure out a fix for this somehow...
Writing to /data does seem to work, so maybe I can patch the Samsung lib to store burst shots there, and move them to the SD card from the camera apk :x
iSasha said:
Well, the full version method didn't work for me on todays' CM nightly build. I installed it following the procedures, and then opened the camera app. The screen went black, and then froze. I restarted the phone, and it kept looping on the boot animation
Luckily I don't delete the CM updater temporary files, so I was able to boot into recovery and re-install the 'stock' CM build. Also, despite the fact that I mostly understood the instructions, they were quite confusing!
Click to expand...
Click to collapse
Apologies for the confusing instructions :< I think I got carried away a bit with the technical details!
You cannot use this mod with an existing build of another ROM (like the CM nightlies) unless it has been compiled with the source code patches I provided. Samsung's camera libs are not compatible with normal AOSP builds, but my patches change the interface in AOSP to fix that.
It's a bit of a lofty goal but I hope that other ROMs will some day include these patches, because it doesn't affect normal camera operation, and it allows you to use the Samsung camera if you flash the appropriate libs...
I would like to provide builds of other ROMs in the future, but this is difficult to do because it takes me 2-3 days to download the source code of each ROM and 8 hours to compile it from scratch - this is why I only have RootBox right now. So it would be extremely helpful if other developers would integrate this.
Notor1ouS- said:
does hdr work? is it like the tw cam?
Click to expand...
Click to collapse
HDR works perfectly Exactly like in the TW 4.2 camera, you get an Options menu with Normal/Strong HDR effect and with the option to save original/HDR photo or just HDR.
Treeki said:
Apologies for the confusing instructions :< I think I got carried away a bit with the technical details!
You cannot use this mod with an existing build of another ROM (like the CM nightlies) unless it has been compiled with the source code patches I provided. Samsung's camera libs are not compatible with normal AOSP builds, but my patches change the interface in AOSP to fix that.
It's a bit of a lofty goal but I hope that other ROMs will some day include these patches, because it doesn't affect normal camera operation, and it allows you to use the Samsung camera if you flash the appropriate libs...
I would like to provide builds of other ROMs in the future, but this is difficult to do because it takes me 2-3 days to download the source code of each ROM and 8 hours to compile it from scratch - this is why I only have RootBox right now. So it would be extremely helpful if other developers would integrate this.
Click to expand...
Click to collapse
Oups... I just copied over the lib and camera files over using a root explorer app. I doubt that I'll have the patience to wait days to build it form source myself, but I'll be looking forward to see these libs integrated in future versions of CM!
"Not Working, unlikely to be fixed:
Camcorder"
is that a typo for "cam recorder" ? or cam recording is working just fine?
AvivEliyahu said:
"Not Working, unlikely to be fixed:
Camcorder"
is that a typo for "cam recorder" ? or cam recording is working just fine?
Click to expand...
Click to collapse
Camcorder is a term for video recorder.
Also op thanks this mod hope it gets implemented in the rom I'm using!
Sent from my GT-I9300 using xda app-developers app
@Treeki would you continue to publish updated Rootbox Nightlies with this camera every time Rootbox is updated?
EDIT: I also think you should move this to Android Development forum instead of apps and games because you are working on a ROM based of Rootbox sources... Not just the app itself..
Sent from my GT-I9300 using Tapatalk 2
sorry for quick quesrion...
if i merge this to rom, will it just replace the original cm camera or cm camera is still there and it make new icon for the sammy camera?
Sent from S3, power By Temasek'Rom and Kernel!
I'm quoting the answer provided on the Original Thread...
Treeki said:
.
It's a bit of a lofty goal but I hope that other ROMs will some day include these patches, because it doesn't affect normal camera operation, and it allows you to use the Samsung camera if you flash the appropriate libs...
.
Click to expand...
Click to collapse
If I'm not wrong it doesn't break CM Camera, it just helps Sammy camera to Partially work...
Sent from my GT-I9300 using Tapatalk 2
thanks~
Sent from S3, power By Temasek'Rom and Kernel!
jimbo77 said:
@Treeki would you continue to publish updated Rootbox Nightlies with this camera every time Rootbox is updated?
Click to expand...
Click to collapse
Hm.. that's something I hadn't thought about yet :x
I will try and publish a new one every few days but I don't have the resources to make daily builds, unfortunately...
Now that I have some more experience with the Android build system and I know exactly what needs to be changed, I'm going to look again at modifying the Samsung binaries to work with any AOSP ROM instead of doing this the other way round. That was my intention when I first started the project, but I changed tactics because I wasn't sure exactly how much I would need to modify.
I don't know if I'll succeed at this but I'll give it a shot ... If I could get it to work, it would be a much better solution because it should work on practically any ROM with just a flashable zip. Can't promise anything yet though :<
Treeki said:
Hm.. that's something I hadn't thought about yet :x
I will try and publish a new one every few days but I don't have the resources to make daily builds, unfortunately...
Click to expand...
Click to collapse
Well, the Rootbox Nightlies doesn't come out every day as well so I think it will be nicely timed with you, btw if you ever want a beta tester of some sort.. Shoot a PM and I'll be more than glad to help...
I'm a Rootbox user since long time so it will not affect me to try your builds...
Sent from my GT-I9300 using Tapatalk 2
Welp.
I was going to post a picture of myself facepalming... taken with the TW camera app, of course... but I figured XDA is just a bit too public for that.
It turned out that one single byte in mediaserver was all I needed to change for my original attempt from several days ago to work. I wish I had known that before I started all this stuff about compiling ROMs... I suppose it was a good learning experience, though. I really didn't expect the fix to be that simple.
So my final mod turns out to be much, much simpler:
- Use Samsung files, with one modified to add a version of Camera::connect that only takes one param
- Modify mediaserver to allocate a CameraService that is 12 bytes bigger than the AOSP version
I feel kinda dumb now. Oh well! Hindsight is 20/20. And... sometimes the simplest solutions turn out to be the right ones
I'll put together a CWM zip that should [hopefully] work on all ROMs and add it to the OP shortly! Now available. Please try it out and let me know how it goes, and what ROM you're using! Off to sleep now, at the very appropriate time of 9am...
It is working correctly on the temasek rom. Thanks a lot.
Treeki said:
Not Working, unlikely to be fixed:
Camcorder
Click to expand...
Click to collapse
first. really cool mod !!!! exactly what im waiting fot
Q
is it possible to change the shortcut to googlecam recorder , when we click on video?
and a shortcut to photosphere from sammys cam "scenes" would be cool
Gesendet von meinem GT-I9300 mit Tapatalk 2
Wow if this could be optimised with AOSP it will be perfect! Flashing it now.
Sent from my GT-I9300 using xda premium
Does the new google 4.4 camera works on 4.4 based roms ?. Hi before several days google pushed new camera app in the play store with its blurry photo filter.
I had installed and used it on my galaxy nexus running 4.4 based ROM (commotio B65...ROM based on vanir sources, toro variant)
It did work. But I have to say I was not impressed with it. Could be due to that it is not intended for use on Galaxy Nexus(and the fact that Gnex camera isn't all that special/good to begin with). But it DID function. And I DID try out the "blurry" function. I just wasn't impressed with it.
Especially it's UI.(seriously? That HUGE area for a shutter button? Looks so tacky and not clean at ALL in my opinion. It just looks to me as if a 10 year old designed it in grade school art class. Ugly)
Do not let my experience deter you though. You may enjoy it more than I did. To each their own! Do not be scared to try it out.
(Also, it shows up in the Play Store for me as an update, I think due to me not using the aosp camera but the Google Camera with photosphere function that came with gapps I used)
Yes, it works perfectly well on 4.4 ROM's. It is pretty good as compared to AOSP camera. And as for the big button, according to what I read, it is used to show the ratio of the photo being actually taken.
Working really well on CM11 Snapshot 5.
I quite like it and I belive it is quicker than the stock/CM one!
Hi,
I am a custom rom fan and use them in most of my devices. But with my Note 8.0 I only use original Samsung based rom.
because I don't want to lose Samsung features like S-Pen etc.
What I wonder is, with a custom rom ;
- is the s-pen supported ?
- is there an alternative to Samsung AllshareCast support ? (in standards this is miracast support. Do the custom roms support miracast ?)
- What would I miss from Samsung features if I use custom rom ?
Thanks.
The s-pen works and is very functional on custom roms however you need to find the right software to go in tandem
S note is only compatible with touchwiz based roms and Imo is the best but actual pens functionality and sensitivity is as sensitive on any custom rom
Sent from my GT-N5110 using Tapatalk
thnaks for the fast reply.
So you mean S-Pen works but S-note (app) does not work. That's good news because I don't use S-note.
But for example, I can use Adobe Photoshop with S-Pen ?
What else I miss with custom rom ?
and what about screen mirroring ? (miracast)
mrmrmrmr said:
thnaks for the fast reply.
So you mean S-Pen works but S-note (app) does not work. That's good news because I don't use S-note.
But for example, I can use Adobe Photoshop with S-Pen ?
What else I miss with custom rom ?
Click to expand...
Click to collapse
You may of misunderstood what he replied. Just to clarify....if the custom rom is based on Touchwiz then SNote will work fine otherwise it in most cases won't.
If the custom rom is based on Touchwiz you should actually gain more functionality and not lose any. AOSP roms will vary on what is working and what is not.
---------- Post added at 08:44 PM ---------- Previous post was at 08:43 PM ----------
mrmrmrmr said:
and what about screen mirroring ? (miracast)
Click to expand...
Click to collapse
If I am not mistaken I believe that is confirmed working on civato's latest rom.
A little clarity:
There are ROMs based on the official Samsung ROMs, and they generally support all of the same features as stock but without bloatware and with additional features. Civato's excellent ROMs are a great example; they perform better, have more features (particularly kernel-based), allow the user to select which bloatware to install, and generally are wonderful. Consider it stock ROM fixed up. I have used them for nearly a year and can recommend them highly. This means you get S-Note, and Allcast I believe at this point. There have also been other apps that have been ported from other Samsung devices to this ROM.
Other ROMs are based on AOSP (Android Open Source Project) and do not include the Samsung-specific software. No TouchWiz, S-Note, or any app that depends on the Samsung APIs in their stock ROM. The Photoshop app that is shipped for Samsung crashes immediately on my OmniROM and I had to uninstall - I guess that it is calling a Samsung API. So now, with Omni-ROM I will be dealing exclusively with the world of generic apps, which is not a problem. The stylus works out of the box. To have an app launch when the stylus is removed it is necessary to add a non-free app from the store. This will also enable other features of the pen. There are stylus-supporting note programs (e.g. Papyrus) which work just fine. Most apps using a stylus should work (e.g. Sketchbook) unless they were written using the Samsung APIs, in which case that should be obvious in the store as they will be Samsung-only apps. Edit: if you like to use the stylus for general text entry then you will need to get an app for that as well; they are available - but the neat way that the Samsung keyboard can switch to stylus input is lost.
I have no knowledge of the Allcast issue, other than noting that there are apps available. DLNA is certainly available through any number of apps for any ROM.
You will find a good source of ROM info on this thread: http://forum.xda-developers.com/showthread.php?t=2630650
mrmrmrmr said:
- is there an alternative to Samsung AllshareCast support ? (in standards this is miracast support. Do the custom roms support miracast ?)
Click to expand...
Click to collapse
Both AllshareCast (Miracast) and Chromecast screen casting work fine on the most recent @civato ROM's (FlexNote 3.0 and FlexBurst 1.0). This app and the official app are required for Chromecast screen casting.
ramjet73
Hi,
I would like to make some clarification to my question. By "custom rom" I meant "non-Touchwiz based" rom. Of course, Samsung/Touchwiz based roms do support everything related to Samsung APIs.
So my question is;
with a non-Samsung based rom, shall I be able to use S-Pen with 3rd party apps ? (like Adobe Photoshop - not the one distributed with Samsung devices but the commercial Store version)
Also does miracast work with them ? (not DLNA , real screen mirroring)
Thanks.
Yes you can use your stylus. Miracast depends on Rom kernel development. Due the fact that this is included in Stock Samsung Kernel Source maybe not working...
That is a problem of all Samsung devices, lack of Source code...
Ok. Allshare Cast is Samsung feature but AOSP based roms do have Miracast support , correct ?
mrmrmrmr said:
Hi,
I would like to make some clarification to my question. By "custom rom" I meant "non-Touchwiz based" rom. Of course, Samsung/Touchwiz based roms do support everything related to Samsung APIs.
Click to expand...
Click to collapse
That's not necessarily true.
Some custom ROM's based on Samsung stock break things that work on the official ROM by using a different kernel, modifying the framework or implementing alternate versions of Samsung components from other devices. You need to check the OP and read through the thread to determine if any stock features are broken or missing.
It is definitely harder to mimic all the features of the stock TouchWiz firmware on ROM's compiled from AOSP source. If you plan to use one of those ROM's you really need to verify that the features you use/need are available and can expect to add several third party apps to get anything close to stock sPen support.
Here's a similar thread from last October and this post should help with fleshing out Spen support for AOSP ROM's even though it was written for the Note 3.
mrmrmrmr said:
Ok. Allshare Cast is Samsung feature but AOSP based roms do have Miracast support , correct ?
Click to expand...
Click to collapse
Allshare Cast is just Samsung's name for Miracast but it is still certified by the WiFi Alliance so it should be compatible. From the Wikipedia article on Miracast:
On 29 October 2012, Google announced that Android version 4.2 (updated version of Jelly Bean) will support the Miracast wireless display standard, and by default will have integrated features for it.[8] As of January 8, 2013, the LG Nexus 4 and Sony's Xperia Z, ZL, T and V officially support the function,[9][10] as does HTC One, Motorola in their Droid Maxx & Ultra flagships, and Samsung in its Galaxy S III and Galaxy Note II under the moniker AllShare Cast. The Galaxy S4 uses Samsung Link for its implementation.[11] In October 2013, BlackBerry released its 10.2.1 update to the existing line of BlackBerry 10 devices, which brings Miracast and Wi-Fi Direct support to the Z30,Z10,Q10 and Q5 models.
Click to expand...
Click to collapse
Chromecast screen casting is different and obviously requires a Chromecast device. I have done both successfully on the stock ROM and the latest versions from @civato but don't expect either to work on AOSP based ROM's at this point. They do work with the M10 snapshot for CM11 on my Nexus 4 but the Note 8.0 is not a Nexus device and I think those functions are highly dependent on the kernel used.
If you want all the features of the Note 8.0 working then you should stay with something close to the stock ROM. It will take a lot of time, effort and some money for apps just to get away from TouchWiz interface.
ramjet73
paying for 3rd party apps is not an issue if there are apps supporting S-pen.
I would stick with Samsung ROM if I believed Samsung will support this device anymore. But I doubt Samsung will release Android L to it.
So , I should turn to non-Touchwiz rom at some point. (I like the idea of 8 inch note device, and Samsung doesn't release a 2014 edition replacement)
2 things important for me on the Note device:
- S-Pen usability with 3rd party apps (I understand that non-Samsung roms support S-Pen)
- Screen mirroring (miracast should work if the rom is based on AOSP)
Any advice for a good non-Touchwiz rom ?
mrmrmrmr said:
- Screen mirroring (miracast should work if the rom is based on AOSP)
Any advice for a good non-Touchwiz rom ?
Click to expand...
Click to collapse
"Should" and "does" are two different things.
Out of curiosity, I loaded the M10 snapshot (the latest) for CM11, just to see if it supports screen casting for Miracast and/or Chromecast. The answer is "no" and it doesn't even appear in the display options for settings even though the M10 release for my Nexus 4 works fine with both.
The moral of the story is don't expect much better support in the future from the AOSP ROM makers. CyanogenMod will probably release an L (CM12) version since the N51xx is an officially supported device but don't expect it to support all the features of the Note 8.0 that the stock ROM does.
For a ROM recommendation, I'm planning to stay with the enhanced stock versions from @civato.
ramjet73
I appreciate your confusion on the stylus support, so let's talk about that. First off, the stylus is not unique to Samsung. Most if not all ROMs will provide the status of the raw stylus data (location, pressure, button, storage slot) to applications. Programs written to access the stylus at this level should work on any device that has the (Wacom?) stylus, Samsung or not. The PS Touch in the store should work fine on AOSP - the one I tested last night was a freebie tied to the Samsung ROM and didn't work on Omni-ROM (no surprise there). The fly in the ointment is that Samsung includes a library of stylus functions in their ROM which makes it easier to develop apps for use with a stylus, and which will lock the apps to Samsung devices (the APIs are Samsung-specific). Any app using those APIs will not work on AOSP ROMs. It is easy to tell the difference in the Store because those apps will be for Samsung-only; if it works on non-Samsung devices it is a good bet it will work with open ROMs.
In addition to the stylus software library, Samsung includes software to do things when the stylus is removed from storage or touches hot-spots, a keyboard option to use the stylus and handwriting recognition to create text input in any program, and stylus-enabled programs like S-note that can also convert your scribblings to text with varying levels of success - YMMV. These functions can all be added back into AOSP ROMs with programs from the store, at a modest price. Of course they will be a little different but the functionality will be there.
My recommendation would be to go with Civato's latest ROM (FlexBurst) for now, assuming you are using your stylus a lot and enjoy the Samsung implementation. Civato has added into the ROM support for aircommand, which is available on other Samsung devices but not stock for the Note 8. Also, there are newer versions of S-note available. Samsung (and thus FlexBurst) is currently at 4.4.2, while Omni-ROM is at 4.4.4; I don't see the small lag as anything important at this stage. Once Samsung stops supporting it there will be time to convert to AOSP. In any event once your Note is rooted and TWRP Recovery installed it is a simple matter to make a Nandroid and Titanium backup before installing a new ROM to try out; if you don't like it then wipe and reinstall - not a big deal. The only downside is that you will break your warranty if you have a KitKat bootloader (required for Civato's latest as well as Samsung's latest).
Hope this helps,
Greg
Hey guys I'm a little sad :/
As many of you would know G3 camera support on AOSP is in a really poor condition.
The driver made by LG isn't present on AOSP, making it an utter disappointment after you get over the thrilling speed compared to LG's own rom.
I know the G2 camera has been ported, I also found a post requesting a port for G3 (last response in october), but that didn't happen.
I don't know in detail how hard the problem is, but I imagine that it should be doable unless of course this is completely proprietary code by LG.
I am imagining that you could simply move the right apk's to the phone and try out if something will work, unless of course it is in the LG kernel itself, but then maybe an LG kernel could be used with AOSP, who knows.
The guy who is working on LG XCam for both the G2 and G3 already said he will focus on LG's own roms, so that a no go as well. I have really been looking, but nothing seems to be up.
So is anyone working on this and does anyone know in detail how hard it is to solve?
Coming from Nexus 5 with SlimKat on it, LG G3 seems like the slowest thing known to man, haha, so AOSP is a must, preferably with a good camera as well.
1 moving some files wil not work start by understanding how a total framework works.
2 ya you can do kernel but do you know how it works with driver and app .
3 if you love the cam so mutch why not build a rom with lg framework ?
Jhinta said:
1 moving some files wil not work start by understanding how a total framework works.
2 ya you can do kernel but do you know how it works with driver and app .
3 if you love the cam so mutch why not build a rom with lg framework ?
Click to expand...
Click to collapse
1. I don't think the whole framework needs to be understood to port the functionality of the camera
2. No I don't, but I think the kernel is actually containing the driver, if I understand how a Linux Kernel works, but I could be wrong, since I don't know for sure on Android. Furthermore I was thinking both (parts of) the kernel and camera app could be applied to AOSP.
3. It's not the camera app or LG framework, it's the fact that the camera does not work properly on AOSP. I don't care about settings, GUI or functionality, but it simply performs like a phone from 5 years ago with 15 fps video and poor colors and constrast in images.