Related
--update4 feb 18 below: camera patch + WIFI dropped connection
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
--update1 (new user = no new post to devel board):
Thanks arrrghhh for moving my post here. Yes, the zip can be flashed from SD card from the boot menu.
[ACL], the changes apply to all MACH_TYPE_HTCRHODIUM machines (from mach-types.h), that includes all GSM Rhodium devices I believe. I don't know how to narrow that down to the 100 alone, aside from using a kernel boot parameter.
As for the intended scope for this change: most people reporting camera issues are rhod100 users, but I've seen posts from non-rhod100 users having occasional camera crashes. Because the patch targets the used frame rate it is likely that the camera hardware in most rhod100s - and some non-100's? - just can't handle the original framerate. So if there are non-rhod100 users having occasional camera crashes...
--update2
Changed patch to make it rhod100 specific using machine_variant_type. Thanks muziling. See attached zip and diff (postfixed _1). Non-rhod100 users with crashing camera's -if any- should use the original zip to test.
Please note that this patch does not include brinka123's change for low-light conditions. Didn't that one cause problems when zooming in? I can look into that change, but would like to separate it from this patch.
Next thing I want to do is look into the audio issue when using the cam - audio runs for 1 sec, then drops. I need to go into Android code for that*
I've worked hard this evening to compile OMGB with [ACL]'s device specific files (both github), but failed miserably. Looks like I'm missing the rhodium makefiles, any pointers?
I did manage to get 7.5 GB of sources on my PC, so I guess I'm at least halfway
*: while recording video logcat shows a happily recording cam and then suddenly:
V/Libacoustic-wince( 85): msm72xx_start_acoustic_setting
I/AudioHardwareMSM72XX_wince( 85): disabling volume method=AUDIO
V/Libacoustic-wince( 85): msm72xx_set_acoustic_table 256 0
V/Libacoustic-wince( 85): Use current device 13
-- update3
The attachment OMGB_2.6.27.46-01399-g6a073c7-rhod100camera_1.zip lacked matching kernel modules (no wifi, ...).
Corrected that by uploading attachment OMGB_2.6.27.46-01399-g6a073c7-rhod100camera_1a.zip
Note that this second update does nothing for rhod 2xx,3xx devices.
--update4
Camera:
Some people reported improved all-rhodium camera quality under low-light conditions using brinka123's changes. The change that is present in the attached patch does improve low-light image quality somewhat as it lowers the framerate, increasing the ccd integration time (1 frame + blanking). The remaining changes from brinka123 not included in the patch do not improve low-light image quality. These changes just limit the CCD integration time to one frame incl blanking, preventing hardware enforced framerate drop but delivering a darker picture with more noise. So I think the patch as-is is fine.
Wifi:
To properly debug camera audio issues I wanted a build environment using OMGB git + [ACL]'s device_htc_rhodium git. After a week of total war between me and the Android build system I have a working environment that results in a working phone. Had to create lots of Android makefiles from scratch to do that, and by accident it resulted in a phone that doesn't drop it's WIFI connection every now and then (Wifi icon turned gray 1-2 times a day, toggling wifi off/on reconnects). The difference with [ACL]'s build is not in the code, but somewhere in the makefiles + properties + different firmware files and is difficult to narrow down. If the WiFi issue I had is real and not something limited to my phone/access points I can look into this. Anyone with this problem?
Thanks mate, moved your thread to development.
Interested to hear how this pans out. I'm assuming RHOD100 users on OMGB can just flash that .zip via recovery?
ImTuxy said:
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
Click to expand...
Click to collapse
Hey dood. Lets get some rhod 100 folk to test this bad boy. We also need to make sure it doesnt break the other variants. I'm also going to send this to the kernel team so it can be analyzed for xdandroid as well. If this change is Rhod100 specific, then we need to change it so only rhod100 loads it.
ImTuxy said:
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
Click to expand...
Click to collapse
Great work, Eric. I have tested now cursorily and first observations are:
1. Camera works great including autofocus
2. Camcorder - videorecording works, but there is problem with recording audio. Recording approximately first 1 second and then silence.
I made 4 photos and 2 videos (30 second and 5 second) and this consumed 49% of my battery.
May I send you any logs or another help with testing?
Anyway many, many thanks to you!
Edit: After recording this kernel is sometimes spontaneously turns on the display including four buttons at bottom, in that moment the LED lights up in orange (wake) and immediately off again and the LED turns green (sleep). Display lights approx. 1 second.
[ACL] said:
Hey dood. Lets get some rhod 100 folk to test this bad boy. We also need to make sure it doesnt break the other variants. I'm also going to send this to the kernel team so it can be analyzed for xdandroid as well. If this change is Rhod100 specific, then we need to change it so only rhod100 loads it.
Click to expand...
Click to collapse
I was under the impression that the 'improvements' would actually help all RHOD's. I know when I ran brinka's kernel for testing, the low-light performance did seem better.
So unless it outright breaks all other RHOD's, I'd say it should be applied to all RHOD's.
milda25 said:
Great work, Eric. I have tested now cursorily and first observations are:
1. Camera works great including autofocus
2. Camcorder - videorecording works, but there is problem with recording audio. Recording approximately first 1 second and then silence.
I made 4 photos and 2 videos (30 second and 5 second) and this consumed 49% of my battery.
May I send you any logs or another help with testing?
Anyway many, many thanks to you!
Edit: After recording this kernel is sometimes spontaneously turns on the display including four buttons at bottom, in that moment the LED lights up in orange (wake) and immediately off again and the LED turns green (sleep). Display lights approx. 1 second.
Click to expand...
Click to collapse
This patch does absolutely nothing for recording audio. I would ask how it worked before, but you've probably never been able to test it.
So long as it fixes the cam, we're good. Recording/audio is completely separate from this patch.
arrrghhh said:
I was under the impression that the 'improvements' would actually help all RHOD's. I know when I ran brinka's kernel for testing, the low-light performance did seem better.
So unless it outright breaks all other RHOD's, I'd say it should be applied to all RHOD's.
This patch does absolutely nothing for recording audio. I would ask how it worked before, but you've probably never been able to test it.
Click to expand...
Click to collapse
Sorry, I did not know this. Before the camera really did not work at all. There is tremendous progress. Thanks.
Tested on Rhod100.
milda25 said:
Sorry, I did not know this. Before the camera really did not work at all. There is tremendous progress. Thanks.
Tested on Rhod100.
Click to expand...
Click to collapse
Yes, it is nice to have the cam working at all, and I realize you couldn't test this before.
I just wanted to make that clear, this will only fix the broken cam. Nothing else...
Both RHOD100,210,300 user had crash
Use function get_machine_variant_type to get rhod type, it will return
MACHINE_VARIANT_RHOD_1XX or MACHINE_VARIANT_RHOD_2XX, MACHINE_VARIANT_RHOD_3XX,MACHINE_VARIANT_RHOD_4XX,MACHINE_VARIANT_RHOD_5XX
muziling said:
Both RHOD100,210,300 user had crash
Use function get_machine_variant_type to get rhod type, it will return
MACHINE_VARIANT_RHOD_1XX or MACHINE_VARIANT_RHOD_2XX, MACHINE_VARIANT_RHOD_3XX,MACHINE_VARIANT_RHOD_4XX,MACHINE_VARIANT_RHOD_5XX
Click to expand...
Click to collapse
Exactly !!!
here is some pseudo to brighten everyones day
Code:
current_variant = get_machine_variant_type();
if ((current_variant == MACHINE_VARIANT_RHOD_1XX)) {
do_rhod100_poop();
}
ImTuxy said:
--update2 feb 08 below
Hi,
Sorry to post here, as new user I don't have access to the Android development board.
I have altered [ACL]'s latest kernel (2.6.27-46 git g6a073c7 from 2 feb) to support the Rhodium 100 camera. The update package and the diff are attached.
The change does essentially the same as an earlier change to Andoid SD posted by brinka123, but is implemented differently to prevent upstream rejection as happened to the patch by brinka123. The update package is the 2 feb update that [ACL] posted with the kernel replaced. Can someone can post this to the devel board? I'm looking for testers...
Thanks,
Eric.
--update1 (new user = no new post to devel board):
Thanks arrrghhh for moving my post here. Yes, the zip can be flashed from SD card from the boot menu.
[ACL], the changes apply to all MACH_TYPE_HTCRHODIUM machines (from mach-types.h), that includes all GSM Rhodium devices I believe. I don't know how to narrow that down to the 100 alone, aside from using a kernel boot parameter.
As for the intended scope for this change: most people reporting camera issues are rhod100 users, but I've seen posts from non-rhod100 users having occasional camera crashes. Because the patch targets the used frame rate it is likely that the camera hardware in most rhod100s - and some non-100's? - just can't handle the original framerate. So if there are non-rhod100 users having occasional camera crashes...
--update2
Changed patch to make it rhod100 specific using machine_variant_type. Thanks muziling. See attached zip and diff (postfixed _1). Non-rhod100 users with crashing camera's -if any- should use the original zip to test.
Please note that this patch does not include brinka123's change for low-light conditions. Didn't that one cause problems when zooming in? I can look into that change, but would like to separate it from this patch.
Next thing I want to do is look into the audio issue when using the cam - audio runs for 1 sec, then drops. I need to go into Android code for that*
I've worked hard this evening to compile OMGB with [ACL]'s device specific files (both github), but failed miserably. Looks like I'm missing the rhodium makefiles, any pointers?
I did manage to get 7.5 GB of sources on my PC, so I guess I'm at least halfway
*: while recording video logcat shows a happily recording cam and then suddenly:
V/Libacoustic-wince( 85): msm72xx_start_acoustic_setting
I/AudioHardwareMSM72XX_wince( 85): disabling volume method=AUDIO
V/Libacoustic-wince( 85): msm72xx_set_acoustic_table 256 0
V/Libacoustic-wince( 85): Use current device 13
Click to expand...
Click to collapse
we share acoustic and libaudio with xdandroid. Just compile it there and move the binaries over. Detule is the master of these for now and he has been killing bugs left and right.
Also your second patch looks worthy. So next round of updates i'm going to include it.
We are tracking this issue on the issues list.
http://code.google.com/p/rhodium-nand/issues/detail?id=15
You can update the request if you have more info.
Hello everyone
Just want to ask you if there is any app which let me increase the brightness. I have it to 100 % but i still find it a bit to dark.
Any ideas / advices / are welcome, thanks in advance
nex_t said:
Hello everyone
Just want to ask you if there is any app which let me increase the brightness. I have it to 100 % but i still find it a bit to dark.
Any ideas / advices / are welcome, thanks in advance
Click to expand...
Click to collapse
If you are on a stock rom may be you'll feel that the brightness is bit low. But on custom rom the same is not so.
If you have a matte screen protection you may experience the low brightness but not otherwise.
shrirangvedanti said:
If you are on a stock rom may be you'll feel that the brightness is bit low. But on custom rom the same is not so.
If you have a matte screen protection you may experience the low brightness but not otherwise.
Click to expand...
Click to collapse
I have this phone from my brother, he used it about 1 year. It's my first Android phone.
All i know is, the phone have root / kernel AK 225 SKL /
How do i find if the rom is stock or modified ?
Thank you
LE : i read this, on xda forum :
" The screen seems to be limited in brightness from the factory, as a matter of settings. Using AOKP Rom and increasing the color multipliers makes the screen much, much brighter, but i've read speculation that it could cause the screen to burn-in images much faster, which logically speaking, seems to make sense. Maybe it's limited by Samsung for that reason. This particular panel seems slightly more prone to image retention than the one on my Droid Charge, granted it isn't the same as burn-in, but maybe an indicator of inclination toward it "
Should i try, maybe, AOKP Rom ?
nex_t said:
I have this phone from my brother, he used it about 1 year. It's my first Android phone.
All i know is, the phone have root / kernel AK 225 SKL /
How do i find if the rom is stock or modified ?
Thank you
LE : i read this, on xda forum :
" The screen seems to be limited in brightness from the factory, as a matter of settings. Using AOKP Rom and increasing the color multipliers makes the screen much, much brighter, but i've read speculation that it could cause the screen to burn-in images much faster, which logically speaking, seems to make sense. Maybe it's limited by Samsung for that reason. This particular panel seems slightly more prone to image retention than the one on my Droid Charge, granted it isn't the same as burn-in, but maybe an indicator of inclination toward it "
Should i try, maybe, AOKP Rom ?
Click to expand...
Click to collapse
Yes. but make sure that you know what you are doing. Follow the instructions of rooting, flashing custom recovery, so that you don't get stuck anywhere.
shrirangvedanti said:
Yes. but make sure that you know what you are doing. Follow the instructions of rooting, flashing custom recovery, so that you don't get stuck anywhere.
Click to expand...
Click to collapse
I wont make any step before i'm 100 % sure of what i'm doing
So, do you think that AOKP Rom will increase the brightness, like the guy said ?
What's the difference between Rom and kernel ? How do i find out which Rom i have now ?
nex_t said:
I wont make any step before i'm 100 % sure of what i'm doing
So, do you think that AOKP Rom will increase the brightness, like the guy said ?
What's the difference between Rom and kernel ? How do i find out which Rom i have now ?
Click to expand...
Click to collapse
Turn off the phone:
Press Volume up + Volume down simultaneously. While you hold both press the power button.
The screen will show the details where you may check whether the bootloader is locked or unlocked.
For checking which ROM you are on go to settings>About phone
Hit thanks if I helped.
These are some useful threads. You will have to go through
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
http://forum.xda-developers.com/showthread.php?t=1392310
I went to About Phone, and i have the follows :
Vanir version 4.2.2.1 041913
Status, phone number, etc
Legal information
model number
Galaxy Nexus
Android version 4.2.2
cpu, ram, etc
baseband version i9250XXLJ1
Kernel version
3.0.75+ ~ AK.255.SKL
[email protected] #1
Build number JDQ39
nex_t said:
I went to About Phone, and i have the follows :
Vanir version 4.2.2.1 041913
Status, phone number, etc
Legal information
model number
Galaxy Nexus
Android version 4.2.2
cpu, ram, etc
baseband version i9250XXLJ1
Kernel version
3.0.75+ ~ AK.255.SKL
[email protected] #1
Build number JDQ39
Click to expand...
Click to collapse
Its rooted, with custom ROM Vanir : http://forum.xda-developers.com/showthread.php?t=2162937
Ok.
So, you think it's worth to try AOKP Rom, to increase the brightness ?
nex_t said:
Ok.
So, you think it's worth to try AOKP Rom, to increase the brightness ?
Click to expand...
Click to collapse
nope. Download Trickster Mod from the Play store and play around with the screen colors. I think Anarkia kernel uses the dark, bluish morfic settings by default
The relentless pursuit of the perfect rom
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
CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Broken:
Video recording (Missing symbols for AVC Encoder)
GPS
Bluetooth calls
RenderScript driver (Missing symbols)
Changelog:
http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_samsung_treltexx
Downloads:
Build 1
Builds can be flashed by your favorite recovery.
Please do not post bug reports (or logcats) at this point!
I'm well aware of most of them and will try to fix them as fast as possible.
If you like my work, please consider donating a few bucks, it will help buying new devices and maintaining them (Most probably Exynos ones that no one else likes doing AOSP development on).
XDA:DevDB Information
CyanogenMod, ROM for the Samsung Galaxy Note 4
Contributors
RaymanFX
Source Code: https://github.com/CyanogenMod/android_kernel_samsung_trelte
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2015-11-29
Last Updated 2016-07-15
The second Marshmallow! I am sure that you will solve the issues it has now.
Thank you for your work and support mate.
silentattack said:
The second Marshmallow! I am sure that you will solve the issues it has now.
Thank you for your work and support mate.
Click to expand...
Click to collapse
Video encoding is fixed!
http://review.cyanogenmod.org/#/c/122021/
Next on my list is the RenderScript driver (once it's working it should provide a noticeable performance boost).
It seems to be broken on the cm-12.1 branch as well by the way.
I also fixed a bunch of overlays, the most important one (to me) being proper brightness levels.
Auto brightness works much better now
Also, with Android's Doze feature (to save battery while suspended) I was able to make it through the day with 40% charge left in the morning, and now it's 8pm here. This includes flashing multiple test builds, debugging and so on, with the device being connected via USB for short periods (a few minutes each).
Now we all know that charging on the USB port doesn't really 'charge' the device all that effectively, so I'm super impressed by this uptime.
I wasn't able to get anywhere near this in any of my Lollipop builds, it's just crazy.
Wow great news mate I am happy like a child
RaymanFX said:
Video encoding is fixed!
http://review.cyanogenmod.org/#/c/122021/
Next on my list is the RenderScript driver (once it's working it should provide a noticeable performance boost).
It seems to be broken on the cm-12.1 branch as well by the way.
I also fixed a bunch of overlays, the most important one (to me) being proper brightness levels.
Auto brightness works much better now
Also, with Android's Doze feature (to save battery while suspended) I was able to make it through the day with 40% charge left in the morning, and now it's 8pm here. This includes flashing multiple test builds, debugging and so on, with the device being connected via USB for short periods (a few minutes each).
Now we all know that charging on the USB port doesn't really 'charge' the device all that effectively, so I'm super impressed by this uptime.
I wasn't able to get anywhere near this in any of my Lollipop builds, it's just crazy.
Click to expand...
Click to collapse
Impressive! You are a machine! Thank you for your wonderful work! :good: :good: :good: :good:
OMFG!! Thanks Bro!
Enviado desde mi SM-N920C mediante Tapatalk
I've seen good developers and then there's you. Superb, thank you
Running the build. All seems amazing, apart from your mentioned to-do list (except video encoding-considering you fixed it before I even booted up-; you're a boss). Performance is pretty snappy already!
Any chance for 910 u user or was my $40 just a unknown c financing the beginning of the year?
Eny idea wen is for f compatible ?
Enviado desde mi SM-N920C mediante Tapatalk
BallerMan said:
Running the build. All seems amazing, apart from your mentioned to-do list (except video encoding-considering you fixed it before I even booted up-; you're a boss). Performance is pretty snappy already!
Click to expand...
Click to collapse
Which bootloader and modem are you using? For me it is not passing starting apps screen. I'm on the 5.1.1 bl and modem.
Gesendet von meinem SM-N910C mit Tapatalk
RaymanFX said:
Video encoding is fixed!
http://review.cyanogenmod.org/#/c/122021/
Next on my list is the RenderScript driver (once it's working it should provide a noticeable performance boost).
It seems to be broken on the cm-12.1 branch as well by the way.
I also fixed a bunch of overlays, the most important one (to me) being proper brightness levels.
Auto brightness works much better now
Also, with Android's Doze feature (to save battery while suspended) I was able to make it through the day with 40% charge left in the morning, and now it's 8pm here. This includes flashing multiple test builds, debugging and so on, with the device being connected via USB for short periods (a few minutes each).
Now we all know that charging on the USB port doesn't really 'charge' the device all that effectively, so I'm super impressed by this uptime.
I wasn't able to get anywhere near this in any of my Lollipop builds, it's just crazy.
Click to expand...
Click to collapse
Is there anything you can do with sound quality and level? I know it's hard since Samsung doesn't release all the source codes. I just ask if it's possible or not?
EDIT: BTW you are the top of devs that making our precious baby better.
Congratulations for the work, waiting for the official version, I love u work <3
Danmann said:
Any chance for 910 u user or was my $40 just a unknown c financing the beginning of the year?
Click to expand...
Click to collapse
Give him time he will get it working. He is one hell of a developer.
Small feedback
Dirty flash ended with bootloop (on top of the last 5.1.1 buld)
Clean flash hanging at "Starting apps" (aprox 15mins)
Regards
Edit:
Hm it is possible the ext card to be the reason for this.. Will try without tomorrow.
N910U sim card not recognised (RIL issue?). Remove SDcard for it to boot up or it will just boot-loop when it tries to finish setup.
travis82 said:
Give him time he will get it working. He is one hell of a developer.
Click to expand...
Click to collapse
Well, that's my only choice at the moment. That's the reason i ask. To get a little bit hope for a second choice ?
Danmann said:
Well, that's my only choice at the moment. That's the reason i ask. To get a little bit hope for a second choice
Click to expand...
Click to collapse
I think he hard coded it for the 910c modem when he gets it proper it should work on any 910xx modem. So be patient he is damn good at what he does and I'm sure he will fix it up when he is ready to.
pappschlumpf said:
Which bootloader and modem are you using? For me it is not passing starting apps screen. I'm on the 5.1.1 bl and modem.
Gesendet von meinem SM-N910C mit Tapatalk
Click to expand...
Click to collapse
COJ5 bootloader and COJ5 Modem, but the issue you are having has nothing to do with the bootloader or Modem. Take out your SD card on bootup and it'll boot fine.
@RaymanFX
You deserve a beer, here have one!
Confirmation number: 29234028H1821762C
Howdy!
I hereby offer an alternative build of the latest visi0nary's kernel.
The original thread is located here
Please note that the credits remain with BlueFlame4 (the maker of visi0nary's kernel), as this is the same kernel, just differently built.
Some years ago I spent many months trying to optimize UI smoothness and power consumption for a kernel of a different device, in which I succeeded.
From this time I remember some build flags and kernel config settings that improved (scrolling) smoothness and power consumtion for that device at that time.
So, in an attempt to do the same for the P9000, I re-built the latest visionary's kernel with the following differences:
different/improved build flags
minor changes in kernel defconfig
compiled using a self-compiled sabermod toolchain
With these changes in the build process I try to achieve the following things:
improved smoothness/snappiness of the UI (NOT higher benchmarks - I just want the user experience to be as smooth as possible, benchmarks do not really matter)
improved (lower) power consumption
The built kernel feels improved in smoothness to me, but this might be my own biased opinion.
Anyway, I would appreciate, if some of you good people could use this kernel as a daily driver, in order to see after a few days, if there are really any noticable improvements over the original build of visi0nary's kernel. Please report back in this thread, thank you.
Installation: just flash in recovery - delete cache & dalvik cache afterwards (also in recovery, after kernel flash)
Attention: this build is not for cyanogenmod - it's for Stock P8000 ROM or other Stock-based ROMs like Eragon (I'm using it on the latest Eragon myself).
To verify that you are running the alternative build, you will see a "-gueste" (that's me) appendend to the kernel version number (see attached screenshot).
Thanks mate.
I will flash it to See if something is different/improved
Wish you all the best for this project!
Thanks Allways glad to see effort.
Testing will return with feedback.
Thanks for the kernel. I've just flashed it and so far I see that when you go directly to the battery menu from the notification bar, that menu is much snappier. On the stock and on visionary's kernel you had to wait a little bit to see the details of specific apps draining the battery. That's the feedback which I can say now, I'll try to give information about the power consumption in the future. Thanks for developing!
Thanks in advance at all.
For me so far power consumption seems to be very good (while it is not bad on the original build either). I'm anxious to see, how it will compare to the original build after 2 more days.
Hello! I have just fleshed the phone with this kernel. Seems great for now. Will update you for the power consumption in the near future.
P.S Im so happy that someone has taken over this project, and I hope it will keep you developing it!
boka18 said:
Hello! I have just fleshed the phone with this kernel. Seems great for now. Will update you for the power consumption in the near future.
P.S Im so happy that someone has taken over this project, and I hope it will keep you developing it!
Click to expand...
Click to collapse
Actually it is still BlueFlame4's project, as the changes I performed so far do not qualify for this project to be standalone. For now I only intend to make improved builds for visi0nary's kernel, but not my own kernel.
Making an own kernel out of this would include things like porting stuff to the kernel to enable new features - like SIO scheduler or "Snappy compression" for ZRAM, or even an enhanced kernel tweaking tool that allows the user to set additional kernel settings and tweaks in Android GUI.
But this is not the purpose of this thread/project
Stefan Gündhör said:
Actually it is still BlueFlame4's project, as the changes I performed so far do not qualify for this project to be standalone. For now I only intend to make improved builds for visi0nary's kernel, but not my own kernel.
Making an own kernel out of this would include things like porting stuff to the kernel to enable new features - like SIO scheduler or "Snappy compression" for ZRAM, or even an enhanced kernel tweaking tool that allows the user to set additional kernel settings and tweaks in Android GUI.
But this is not the purpose of this thread/project
Click to expand...
Click to collapse
Feel free - that's the spirit of open source! My P8000 is already on eBay so I'll visit this forum less and less. It's good to see people picking up my work though!
Stefan Gündhör said:
Actually it is still BlueFlame4's project, as the changes I performed so far do not qualify for this project to be standalone. For now I only intend to make improved builds for visi0nary's kernel, but not my own kernel.
Making an own kernel out of this would include things like porting stuff to the kernel to enable new features - like SIO scheduler or "Snappy compression" for ZRAM, or even an enhanced kernel tweaking tool that allows the user to set additional kernel settings and tweaks in Android GUI.
But this is not the purpose of this thread/project
Click to expand...
Click to collapse
I understand completely, but I DO hope that u will be able to continue optimising this great kernel!
What new in this kernel?
What the bug fix?
Okalash said:
What new in this kernel?
What the bug fix?
Click to expand...
Click to collapse
Pro Tip: Read the OP :laugh:
For me so far battery life seems to be very good.
After 2 days and 10 hours of uptime I still got 42% battery.
Now this value is not very informative, as it depends heavily on the usage of the phone.
Compared to the original build of the kernel at least power consumption seems to be better on my phone.
During phone uptime I occasionally played games (not very long though), was connected to bluetooth and wifi many hours, browsed through the web regularly and had only few and short phone calls. Over night for some hours I was in flight mode, while last night I wasn't.
Thank you for continuing the project! I flashed the rebuilt kernel because I had a "feeling" that the battery performance of the original Visi0nary kernel was somewhat lower than the stock kernel. (But maybe I am mistaken.)
So far I have no problems with the rebuild kernel. It is too early to comment on battery performance.
Does it make sense to run Skeleton's Seeder app (part of Eragon ROM) in conjunction with this custom kernel?
Moreover, is there any chance to port the P7000 kernel scripts that enable Android device encryption into this P8000 kernel/Eragon ROM? See http://forum.xda-developers.com/elephone-p8000/general/dev-cwm-elephone-p8000-t3200296/page11 The lack of device encryption is my main gripe with the P8000. Apart from that, I love this phone.
-Tiz- said:
Does it make sense to run Skeleton's Seeder app (part of Eragon ROM) in conjunction with this custom kernel?
Click to expand...
Click to collapse
This rebuild of visionary's kernel is feature-equivalent to the original build. So, yes, you can use the seeder app (I use it myself).
Regarding device encryption you need to understand that it has been left out of the ROM most likely on purpose, because this is a China-phone, and the chinese government is quite restrictive on encryption. And as Eragon (same as other stock-based ROMs) is based on the stock ROM, this feature is missing there as well.
This means, depending on the effort, Elephone made, to remove this feature from Android, it might be possible to reactivate it, it's just a matter of (testing) time.
I haven't tried with other ROMs like Cyanogenmod, but in theory it should work there.
As far as I have seen, the to enable encryption for P8000 stock and stock-based ROMs we would need to modify one or more scripts of the P8000 ramdisk (for example the russian guy you linked added in init.environ.rc:
Code:
export LD_PRELOAD libsigchain.so
And there are also a couple of other differences in the other rc scripts. It's not exactly clear (to me), which changes in the end are required for encryption to be enabled. Also we don't know if after these changes, the encryption option will magically appear in the device settings, or if we need to enhance the menu ourselves.
Furthermore, the russian guy mentions, that we might have to modify and rebuild the sepolicy binary file located in the ramdisk, in order to get selinux (security enhanced linux) to permit our changes (but I don't know if we would need that just for the encryption feature, as init.d already works for P8000 as opposed to P7000 - correct me if I'm wrong).
So to sum up, this sounds like a lot of testing, which I personally don't have the time for But maybe someone else does.
Don't take the Android encryption feature too seriously - at least not, if you are trying to hide from government. However, if you are trying to protect your data from normal people, it surely would be nice to have.
Stefan Gündhör said:
Tin order to get selinux (security enhanced linux) to permit our changes (but I don't know if we would need that just for the encryption feature, as init.d already works for P8000 as opposed to P7000 - correct me if I'm wrong). ...
However, if you are trying to protect your data from normal people, it surely would be nice to have.
Click to expand...
Click to collapse
Thanks. It is also my understanding that init.d already works for Eragon ROM. Therefore, I was hoping that it might be relatively easy to enable encryption. On the P7000, it seems that the menus simply appeared once the scripts were implemented. Wooster even talked about the possibility to make a "blind" patch for the the P8000.
Moreover, I agree that Android device encryption might not be 100% bullet-proof. However, it would allow me and others to sufficiently protect private email passwords and work-related data (e.g. if the phone gets lost or stolen). By contrast, the screen lock is no protection at all. In particular, if a custom recovery is installed ...
It appears that I am not the only P8000 owner who has a vital interest in device encryption:
http://bbs.elephone.hk/thread-6924-1-1.html#.Vow51hBukwE
http://bbs.elephone.hk/thread-9012-1-1.html#.Vow51xBukwE
Tonight I will download and test it
I don't care much about encryption, but God, I would pay for someone who could actually SOLVE the sub-15% sudden battery charge. Any chance you can look into/fix it, Stefan? You look like one of our potential hopes, haha
---------- Post added at 02:42 PM ---------- Previous post was at 02:41 PM ----------
BlueFlame4 said:
Feel free - that's the spirit of open source! My P8000 is already on eBay so I'll visit this forum less and less. It's good to see people picking up my work though!
Click to expand...
Click to collapse
Hi, sorry to ask but why exactly? Got a new/better phone? Got tired of the P8000 bugs/camera? In time, which phone did you get?
Best regards
Rizera said:
Hi, sorry to ask but why exactly? Got a new/better phone? Got tired of the P8000 bugs/camera? In time, which phone did you get?
Best regards
Click to expand...
Click to collapse
No problem, haha. Well, I bought this phone because I want to learn how to port CM or ROMs in general onto other devices and how Android works internally. Unfortunately MediaTek SoCs are quite beginner-unfriendly so I'll go for Qualcomm for now. Just got my Elephone Trunk btw Also there's basically zero "from source" development going on the the P8000 and it's not really fun to do all the things completely alone.
Cheers!
1.
Battery performance of the newly built kernel seems to be good. Heavy WLAN browsing still quickly kills the battery. But I could imagine that this is a hardware issue (power inefficient Mediatek WLAN modem?).
2.
"Also there's basically zero "from source" development going on the the P8000 and it's not really fun to do all the things completely alone. " Sad but true.
Announcing kernel "guestekrnl" (based on the latest version of visi0nary's kernel): http://forum.xda-developers.com/elephone-p8000/orig-development/kernel-guestekrnl-v1-6-2-t3287518