Database Develop

libcamera Eclair - [RLS2 - 19-07-2010]

This is libcamera for Eclair. It won't work under Ion, Donut, Froyo.
RLS2
This release supports froyo kernel with the additional available memory and is also backward compatible with previous kernel.
Tested under Bell's Vogue running Vanilj Eclair RLS6 under both zImage-froyo-15-07-10 (RAMSIZE 0x07300000) & zImage-01-07-10 (RAMSIZE 0x08000000).
Backport dzo libcamera changes from froyo. Now works with both eclair & froyo kernel
Add support for jpeg quality setting
Only reports Auto WB. The other WB settings are not supported by the driver/kernel at the moment
RLS1
Fix FC in Settings with standard Eclair Camera Application
Should now work on Kaiser too
Not working
Video Recording

very nice work bud. Thanks for your contributions

I can confirm it working under Kaiser. Good work.

libcamera RLS1 kaiser test
Hi!
Just4Info: I just want to note that following apps now work on my Kaiser device:
* Standard camera
* Google Goggles (Wohoo )
* Camera 360 (Free)
(Tested by taking 1 picutre with each app)
Only thing i noticed is that the "post"-views... the picture shown after taking a picture is disorted (camera/camera360), but god thanks the saved picture is ok.
Mucho thanko for your work+fix!

Google Goggles does not work on my vogue running Myn's Warm Eclair RLS1 at 320x480 with the nbh from 6/27/10. The standard camera works just fine, and barcode scanner works as well. Any ideas?

hockeymike said:
Google Goggles does not work on my vogue running Myn's Warm Eclair RLS1 at 320x480 with the nbh from 6/27/10. The standard camera works just fine, and barcode scanner works as well. Any ideas?
Click to expand...
Click to collapse
im not sure but i always thought it uses the camcorder API for google goggles to work

thoughtlesskyle said:
im not sure but i always thought it uses the camcorder API for google goggles to work
Click to expand...
Click to collapse
Hmmm... I just can say that i just re-tried Google Goggles with a "Hansaplast" (Ouch... *g*) carton and it worked a second time
1st libcamera version did work for pictures but settings FC'ed and Google Goggles FC'ed.
2nd libcamera version didn't FC, but had broken images (wrong resolution thingy) on Kaiser devices
3rd libcamera (aka current RLS1) has working cam and not FC'ing settings and Google Goggles.
My setup:
Device: KAIS130
Display resolution: 240x320 with 104dpi
SD-card installation (Booting via HaRet)
Myn's Warm Eclair RLS1
Self-odex'ed
Actual git-kernel (selfcompiled) as of yesterday (2010-06-29)
libcamera RLS1 installed via androidupdate.tar
Greetings!
*oink*

Distortion / Noise on preview screen when taking shots
Anyone else noticed that the noise issue with the CAM isn't random?
I am referring to the temporary still image in the preview area following a shot.
On my Vogue running VaniljEclair RLS6, the top part shows the current 'shot' but the bottom part is from the previous shot. It is systematic except for the first shot following a reboot in which case, the bottom part is random noise.

I confirm that on polaris with eclair and with froyo
Sent from my Full Android on polaris using XDA App

I have a Kaiser running latest Myn's Warm Eclair. Very glad to have to camera working! My problem is that all pictures are out of focus. Is autofocus working? How would I configure it? The camera app doesn't seem to have any menu.

focus - never mind
I found out that the focus is manual using the jog dial.

dlepage said:
RLS1
Fix FC in Settings with standard Eclair Camera Application
Should now work on Kaiser too
Not working
Video Recording
Click to expand...
Click to collapse
This may be a stupid question but how do I compile the library once I've done a git pull to get the source? I've only compiled the kernel and also done the full automated Froyo build. I suppose the Froyo building means I now have all the necessary stuff and I somehow should use the ndk to do this.

kallt_kaffe said:
This may be a stupid question but how do I compile the library once I've done a git pull to get the source? I've only compiled the kernel and also done the full automated Froyo build. I suppose the Froyo building means I now have all the necessary stuff and I somehow should use the ndk to do this.
Click to expand...
Click to collapse
Once you've done your Froyo build according to dzo instruction here, libcamera.so should be located under out/target/product/vogue/system/lib/ or something similar. I am not in front of my dev computer at the moment, so I can't check.
libcamera.so should be >200kb. If it is much less than that, it is probably the 'fake Camera' from the default/emulator build. If your build did indeed target our phones, your should also have libhtcgeneric-ril.so in the same directory.
I don't think you need ndk unless you want to develop a new applications that includes native (C,C++,asm, anything else than Java) code. For sure, you don't need to do anything special with ndk to build Android for any platform...

any ideas as to what might need to be fixed for camera in eclair
to work with the new froyo zImage?

dlepage said:
Once you've done your Froyo build according to dzo instruction here, libcamera.so should be located under out/target/product/vogue/system/lib/ or something similar. I am not in front of my dev computer at the moment, so I can't check.
libcamera.so should be >200kb. If it is much less than that, it is probably the 'fake Camera' from the default/emulator build. If your build did indeed target our phones, your should also have libhtcgeneric-ril.so in the same directory.
I don't think you need ndk unless you want to develop a new applications that includes native (C,C++,asm, anything else than Java) code. For sure, you don't need to do anything special with ndk to build Android for any platform..
Click to expand...
Click to collapse
But if I want to build just the lib and for a specific Android version? Like if I'd like to try to apply the 11Mb-extra-memory change to the Eclair version of the libcamera.so? I also may want to try stuff in libgps in the future and I very much like to try building a fake sensor lib that uses the GPS bearing to fake a compass sensor (some GPS apps assumes there is a compass available).

mnjm9b said:
any ideas as to what might need to be fixed for camera in eclair
to work with the new froyo zImage?
Click to expand...
Click to collapse
Propalby just do the same changes as dzo did in the froyo branch and compile it for Eclair. Should be just a matter of copy'n'paste once you know how to compile it.

kallt_kaffe said:
But if I want to build just the lib and for a specific Android version? Like if I'd like to try to apply the 11Mb-extra-memory change to the Eclair version of the libcamera.so? I also may want to try stuff in libgps in the future and I very much like to try building a fake sensor lib that uses the GPS bearing to fake a compass sensor (some GPS apps assumes there is a compass available).
Click to expand...
Click to collapse
After you've build at least once, you can modify some parts, like libcamera and then, make -j xxx again from the AOSP root directory. It will just rebuilt the parts affected by your changes.
As for switching between different Android release, I don't know yet. It looks possible with git (as is with most Revision Control System) to switch between branches/tags/releases/whatever but since Android is build from multiple git repositories, I don't know.
Myself, I just init / sync in a seperate directory using the other release manifest file.

kallt_kaffe said:
Propalby just do the same changes as dzo did in the froyo branch and compile it for Eclair. Should be just a matter of copy'n'paste once you know how to compile it.
Click to expand...
Click to collapse
I am planning to do it. It's just that eastern north america is in a heat wave at the moment and I don't have Air Conditioning at home.
Sorry, but I don't feel like powering the computer and sitting in front of it when the temp. is ~33°C and sweat is pouring down my eyes...
Hopefully by the end of the week, things will be back to normal.

dlepage said:
After you've build at least once, you can modify some parts, like libcamera and then, make -j xxx again from the AOSP root directory. It will just rebuilt the parts affected by your changes.
As for switching between different Android release, I don't know yet. It looks possible with git (as is with most Revision Control System) to switch between branches/tags/releases/whatever but since Android is build from multiple git repositories, I don't know.
Myself, I just init / sync in a seperate directory using the other release manifest file.
Click to expand...
Click to collapse
Thanks, I suppose building for Froyo may be enough since I see no reason not run Froyo now. But maybe you could try dzo:s changes to the Froyo camera libs in Eclair that should make the current Froyo kernels compatible with Eclair and also enable 11Mb extra RAM for Eclair users aswell. Currently that's all I see needs to be done right now but I'd like to have a go at a "fake" compass sensor when/if I get time.
EDIT: Just noticed that you wrote that you planned to do it.

dlepage said:
I am planning to do it. It's just that eastern north america is in a heat wave at the moment and I don't have Air Conditioning at home.
Sorry, but I don't feel like powering the computer and sitting in front of it when the temp. is ~33°C and sweat is pouring down my eyes...
Hopefully by the end of the week, things will be back to normal.
Click to expand...
Click to collapse
Don't be sorry...
it is this kind of stuff that entices novices like me to try and learn how to fix it myself.
although for some reason I cant get the repo to work on my laptop (works on my slow desktop)
Code:
[email protected]:~$ ~/bin/repo init -u git://androidhtc.git.sourceforge.net/gitroot/androidhtc/manifest -b froyo
Traceback (most recent call last):
File "/home/q1/bin/repo", line 595, in <module>
main(sys.argv[1:])
File "/home/q1/bin/repo", line 562, in main
_Init(args)
File "/home/q1/bin/repo", line 181, in _Init
_CheckGitVersion()
File "/home/q1/bin/repo", line 210, in _CheckGitVersion
proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)
File "/usr/lib/python2.6/subprocess.py", line 633, in __init__
errread, errwrite)
File "/usr/lib/python2.6/subprocess.py", line 1139, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

[ROM][JellyBean][4.1.1]Unofficial CyanogenMod 10 (WIP)

Ill organize this and make it look good later...but for now lets get to the point:
This is an Android 4.1.1 Jellybean (JB) ROM, it is an unofficial version of a popular after market firmware known as CyanogenMod. it is essentially AOSP with some cool added features by the CyanogMod team -this has no sense, and it is not based off a sense stock rom
Befor i even begin stating what works and doesnt i would like to thank Synergy, he is the one who got this started, he is the one who got the first version of this to boot...unfortunately he quit due to frustrations with HTC and how hard they have made things, i am just picking up where he left off...
What works:
WiFi
Audio
Calls? **check out not working***
SMS...aka texting
home button -I know it sounds funny, but for a while the home button didnt work on CM10
Not working:
Data
Bluetooth
GPS
MMS...aka picture messaging and othe multimedia messaging (will work as soon as data works)
Camera
Video-likely a driver issue...mx player allows for videos to be played but they are extremely laggy...only tested with mp4's of videos i filmed while on ICS
Calls? i need people to test calls...i believe if you have ATT in call mic wont work...so the other end wont be able to hear you work...i cant verify it...but if you use any other carrier (even if you have an ATT vivid but are unlocked and using a differnt carrier) then i believe in call mic does work...i need people to verify...so make some calls and let me know if they work and if the other line can hear you, and also let me know what carrier you have
Instructions
1) Wipe data/factory reset
2) Wipe cache
3) wipe dalvic cache
4) flash CM10
5) flash GAPPS
S-ON?
just fastboot flash the boot.img located in the zip then follow the instructions above
Download
CM10
http://goo.im/gapps/gapps-jb-20120726-signed.zip
All versions of GAPPS: http://goo.im/gapps/
what are GAPPS? GAPPS are just google applications...like Play store, GMail...ETC, its not necessary...but if you wanna get any apps your gonna need it
Other stuff...
Featuring Synergys Kangbang-rebirth kernel...supports OC up to 2052 MHz...or about 2 GHz (you can change clock speed under settings/performancee
Features a built in file explorer...not included in most cm builds
Thanks/Credits
once again...synergy...cant thank him enough
kevstheblast, he also worked on cm10 for a little bit
TeamCodefireAOSP - most of my device trees are from you...some with slight modifications
DragunKorr - i am using your msm8660-common device tree
...ill add to this list later, but its late and i need to finish my homework and go to bed
-Its time to bring the vivid back to life...CM10 opens the door to numerous AOSP based JB ROM ports...lets get this stabilized!

Screenshots...coming soon

How to build:
1) First you need to sync CM10 source:
A)
Code:
mkdir cm10
-this creates a folder for where the source will be downloaded
B)
Code:
cd cm10
-this navigates you to the folder the source will be downloaded in
C)
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
-this initializes the repo...gets it ready/prepares for the sync
D)
Code:
repo sync
-this downloads the source...depending on the rom can range from 8-15+ GBs!
E)
Code:
./vendor/cm/get-prebuilts
-downloads necessary prebuilts for CM10
2) Now you need to clone my local manifest:
A)
Code:
cd ~/cm10/.repo
-this navigates to where the local manifest will be cloned
B)
Code:
git clone git://github.com/mg2195/local_manifest.git
-this makes a copy of the local manifest in your .repo folder
C)
Code:
repo sync
-downloads the sources that were added by my local manifest
3) Now you can build:
A)
Code:
. build/envsetup.sh
-prepares the system to build
B)
Code:
lunch
-opens the device menu for you to choose your device
c)
Code:
6
***or whatever number the holiday pops up as*** -the item number of the device
D)
Code:
mka bacon
-begins the build...can take a few hours depending on your computers CPU
4) relax, eat some pizza, go for a walk...do something, this can take a while...your finished product will be located in /cm10/out/target/product/holiday
How to build other roms from source:
1) First you need to sync there source:
A)
Code:
mkdir workingdirectory
you can name "workingdirectory" whatever you want...i suggest the name of the rom for organization purposes...so for AOKP i would do "mkdir AOKP"
B)
Code:
cd workingdirectory
C) repo init there manifest...for AOKP:
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b jb
found from here: AOKP...so basically find the roms source, then find there manifest, type "repo init -u gitreadlinkhere -b branchnamehere"
D)
Code:
repo sync
2) Now you need to clone my local manifest: (this gets you all the device specific stuff...device tree, common device tree, kernel...ETC)
A)
Code:
cd ~/workingdirectory/.repo
B)
Code:
git clone git://github.com/mg2195/local_manifest.git
C)
Code:
repo sync
3) Now you can build:
A)
Code:
. build/envsetup.sh
B)
Code:
lunch
c)
Code:
6
***or whatever number the holiday pops up as***
D)
Code:
mka bacon
***please note, this may or may not work for every roms source...some require a little extra work...but this should get you the core files needed...look at how other official devices are set up, try and match them...specifically in the workingfolder/vendor***
4) relax, eat some pizza, go for a walk...do something, this can take a while...your finished product will be located in /cm10/out/target/product/holiday
SOURCE
https://github.com/mg2195
https://github.com/KangBangKreations/KangBanged-Kernel/tree/kb-rebirth

CHANGELOG
10-08-2012
-First real release/started thread...

Post any bugs...and if possible get me some LOGCATS
To save a log to a file:
Code:
adb logcat > logcat.txt
Press
Code:
ctrl+c
once you are done collecting information
Then upload the logcat.txt as an attachment so I can look at it with ease...DO NOT JUST COPY AND PASTE THE LOGCATS HERE! that just hogs space and is a pain for those on mobile devices...if you really want to copy and paste there is this great site called pastebin paste it there, hit submit and post the link here

Absolutely awesome man! I love the persistence . Picking up where others left due to frustration, so x10 thumbs up for the dedication!
Will definitely be testing this out and posting back as much bug info I can get you (I will edit this, not just a thank you post). I can't agree more, hopefully you can bring the Vivid back to life . I have faith!
LOG/BUG UPDATE:
Ok so whooo again, great build! Very smooth and speedy, just love this phone without sense (sense works good, but this JB is so refreshing - 0 lag).
Cant wait for the bugs to be worked out, it will be very worth it. Anyway, onto the my report:
_______________________
First boot, it restarted after the white and green HTC screen, so anyone testing no worries when it reboots.
Everything loaded up pretty quickly, and no FCs or bugs besides the known ones. I did notice I think its new probably because of the work you did to get audio to work (messing with the display), when rotating it sometimes makes the screen go all funky (part of the current image is displayed like 4 times in a horizontal line for about .5 seconds) then its fine. So not a big deal.
Bugs:
I tested the calls using my VM, sound works . Now if I try to change the volume of the headset speaker it changes ringer volume I believe, as I didnt notice a difference in volume when the VM automation was talking to me. It also showed a telephone, not w.e it supposed to be (shows same image as not in a call - like its not realizing its 'in' a call). I tried to record a new greeting message, but mic does not work still (tmo).
Data is still the same [as your test builds], blinks E real quick (.5 seconds) then goes away. Under phone status it shows Mobile network type as EDGE:2. Then DCed for network state (changes to connected for the .5 secs when E pops up). Changing bearer to LTE or unspecified doesnt change anything. Also forcing LTE/GSM/WCDMA or GSM/WCDMA Preferred doesnt change anything either.
Camera I tried but FCs with gallery. So also with a few other apps that wouldnt be linked to gallery (though gallery works), no go. They all FC for some reason.
Now no worries, I got you logcats of everything here. I tried to slim them to just the problem although I dont know exactly where the problems end in these huge scripts lol. So I apologize for the length of some, rather you get more than less and I miss the problem line.
Making Calls while changing Volume: http://pastebin.com/gXmiHrCc
Changing bearer to LTE: http://pastebin.com/9hXBiNmS
Clicking Enable Data: http://pastebin.com/xH3AWUp4
Stock Camera: http://pastebin.com/xRsyUTmj (Sorry for lengthy, couldnt tell if it was looping or just straight erroring out million times x( )
Camera Illusion: http://pastebin.com/NFxf2nxd (Again sorry for lenthy, same ^^)
Camera 360: http://pastebin.com/YmRfXBxJ
Maybe hopefully you can get some matching errors on the camera, narrow the problem on that. And hopefully you can figure out the data, thats really big. Same with mic of course. But, again, very good job first actual alpha build.

Unless you wanna damage your hearing....I don't suggest using DSP manager while wearing headphones...went to change the bass and as soon as I changed it my volume went to like full blast lol...definitely some work needs to be done there
Anyways its bed time for me
Sent from my Holiday using Tapatalk 2

Lied about going to bed...found a work around for video...
Go to settings/developer options
Make sure its on
Then disable hw overlays
-my mp4s now play...but they are really laggy...YouTube app now playa video s flawlessly now... maybe its the resolution/quality?
Now I go to bed...
Sent from my Holiday using Tapatalk 2

Would love to try this now, but as this phone is my only phone, I'll have to wait. But once calls and data are working, I'd be more than happy to test out the rest for you. Thank you for your efforts!
Sent from my De-Sensed HTC Vivid using xda app-developers app

finally some JB love for Vivid. as soon as most of the features work, ill test it out.

Dear Santa.....

Can confirm in-call mic doesn't work with AT&T. Everything else is exactly as you described. Let me know if you need a reliable, thorough, tester on AT&T. Will be following this project very closely. Thanks for picking up the project. Keep it up and good luck sir
This thing is wicked fast, and buttery smooth. If in-call mic worked this could be my daily driver. Don't give a damn about data ATM
Internal/External storage works as well, but they arent auto-mounted you need to go into storage settings and manually mount. no usb mount either. but it does recognize the cord.

MisterSchnapps said:
Can confirm in-call mic doesn't work with AT&T. Everything else is exactly as you described. Let me know if you need a reliable, thorough, tester on AT&T. Will be following this project very closely. Thanks for picking up the project. Keep it up and good luck sir
This thing is wicked fast, and buttery smooth. If in-call mic worked this could be my daily driver. Don't give a damn about data ATM
Internal/External storage works as well, but they arent auto-mounted you need to go into storage settings and manually mount. no usb mount either. but it does recognize the cord.
Click to expand...
Click to collapse
Didn't think to test USB as it was working on previous builds...since it was previously working it shouldn't be to hard to fix
Sent from my Holiday using Tapatalk 2

It may be because data doesn't work lol, but I'm getting great battery life!
Anyways...doing some research...trying to figure out how to fix what's currently broken...
Also, it appears that many different devices have graphics/video problems caused by hw overlays....no real fix has been discovered except the work around I mentioned earlier about disabling hw overlays under developer options in settings
As far as USB...I think I might've deleted a line in accident that "defines" its function...
Once I get this stabilized I'll do a tutorial on how to build from source using my existing device sources and plug them into other source ROMs like aokp...
Sent from my Holiday using Tapatalk 2

:fingers-crossed:

Do both mics not work? Could we maybe use the camera mic instead?

Brand New said:
Do both mics not work? Could we maybe use the camera mic instead?
Click to expand...
Click to collapse
The mic works for everything except calls...ive tested it using the voice search app...i searched pizza lol, but it recognized what i said and BAM...all the local pizzerias
Apparntly ATT payed HTC extra to add some extra "security" features...the result is broken in-call mic for ATT users...still waiting for confirmation but if you are a non ATT user then in-call mic SHOULD work...
i stopped my research for a little bit and got my github set up...if you understand how it works you can track my progress there whenever i upload changes...also i edited the third post with instructions on how to build CM10 using my sources, you must already have a build environment set up though...ill add that part later https://github.com/mg2195 ***ill only push changes to github if something is fixed...or improved, so my sources should always produce a working build of the most stable CM10 available***

mg2195 said:
The mic works for everything except calls...ive tested it using the voice search app...i searched pizza lol, but it recognized what i said and BAM...all the local pizzerias
Apparntly ATT payed HTC extra to add some extra "security" features...the result is broken in-call mic for ATT users...still waiting for confirmation but if you are a non ATT user then in-call mic SHOULD work...
i stopped my research for a little bit and got my github set up...if you understand how it works you can track my progress there whenever i upload changes...also i edited the third post with instructions on how to build CM10 using my sources, you must already have a build environment set up though...ill add that part later https://github.com/mg2195 ***ill only push changes to github if something is fixed...or improved, so my sources should always produce a working build of the most stable CM10 available***
Click to expand...
Click to collapse
Please take a look at my updated post (a few up).
Mic for calls do not work for T-Mobile either. Logcats for all of that in that post, which should help you pinpoint some [hopefully].

theslam08 said:
Please take a look at my updated post (a few up).
Mic for calls do not work for T-Mobile either. Logcats for all of that in that post, which should help you pinpoint some [hopefully].
Click to expand...
Click to collapse
Thanks! I'll take a look later...and you have an Att vivid unlocked for T-Mobile?
Maybe in call mic will work for the velocity/raider...me having Att with a vivid...I don't really know, i just remember when syn was working on this he stated in call mic didn't work on Att...but he said it worked for other carriers...
I was able to use mic for voice search...so the problem isn't with the mic its self...has to be with the way the vivid handles calls...
Sent from my Holiday using Tapatalk 2

What about including as littlemount of HTC framework as possible for phone calls?
Just throwing ideas out hahah

SlimKat 4.4.4 Unified (QualComm)

Code:
[B][I][U][COLOR="Red"]WARNING![/COLOR][/U][/I][/B]
This is an ALPHA build. Everything is being worked up to come up to speed as
quickly as possible to be with its CM brother. Just be patient and all will
come in due time. But hey, at least is boots up into the system ... LOL
This is an UNOFFICIAL build of SlimKat (although built from offical SlimRom source) and by NO means is this my ROM. I am just compiling from SlimRom Source and credits go to elelinux, xda-garwyn, albinoman and all other coders who contributed to CyanogenMod device tree.
Code:
For which devices. The ROM should work with all klte versions that are qualcomm
chipsets.
Included in the build are:
kltexx,kltelra,kltetmo,kltecan,klteatt,kltedv,klteub,klteacg,kltedcm,klte
(UNOFFICIALLY SUPPORTED): kltespr,kltevzw,klteusc
Code:
IMPORTANT
* DO NOT expect daily builds. I'll build when I'm free.
* DO ask for support in this thread.
* DO NOT use this unofficial build and ask for support at the official threads.
* DO NOT be rude.
* RESPECT all users
* If u see a NOOB question and u don't feel like replying, DON'T, just ignore
that post. If u do reply, good for u.....and be nice in your reply.
Code:
[B][U]WORKING[/U][/B]
Audio
WiFi
Google Now
Bluetooth
GPS
Video playback
Audio playback
Code:
[B][U]NOT WORKING[/U][/B]
Service
Data
Calls
MMS
Hard keys
Camera
Internal/External SDcard mounting
Code:
[B][U]INSTALLATION[/U][/B]
Do NOT use superwipes
Wipe data, cache, and dalvik cache
* ((do not report bugs if you didn't full wipe))
Flash ROM
Flash GAPPS
Reboot
Report anything that is an issue
As of right now I have no way of testing NFC or IR Blaster, so I do not know if they are working on this build or not. Also on this build there is the infamous red box that appears when moving from screen to screen or app. I am going to fix that either today or tomorrow and then post the new build. The reason there is no data or cell reception is due to the APN list which will also be fixed in the next build.
I tested this on my T-Mobile G900T, so if others can please report back on their experience with this ROM on other devices that would be greatly appreciated and I will get those issues resolved as soon as possible. Thank you.
Code:
[B][U]DOWNLOADS[/U][/B]
ROM: [URL="http://d-h.st/2e0"]SlimKat 4.4.4 (QComm)(ALPHA 1)[/URL]
GAPPS: [URL="http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4"]Click me to pick your poison[/URL]

Great I'll try it out. I've 900F BTW

Thank you. Just remember what is working and what is not working please.

lunerceli said:
Thank you. Just remember what is working and what is not working please.
Click to expand...
Click to collapse
BTW, what the thing that you want me to report?

Just if it boots and the working list is working on your version please.

lunerceli said:
Just if it boots and the working list is working on your version please.
Click to expand...
Click to collapse
Slim minimal gapps.
1st edit: It's booting.
2nd edit: back key, home button and recent/menu key not working? Get NavBar. I like this!
3rd edit: Setting slow to response
4th edit: Stock camera has stopped. Google camera work but need to insert USB storage.
5th edit: Stock Music player not playing
6th edit: USB storage not mounted so can't test out audio/video but ringtone ringing at audio setting.
That's the issues at the moment besides of known issues. I guess i've to restore my backup now. Waiting for your new build thank you.

Ok. Thank you. I will get all of the issues fixed asap.

I'll try it tomorrow but I am also using a sm-g900t so I won't shed much light on the issues/bugs list cause its most likely to be the same as @lunerceli. Still going to flash thou, lol
Thanks for sharing your build with us.
Sent from my SM-G900T

I read your other post in the SlimRoms thread and I'd like to help a bit if I could. I'm going to flash this in the next hour after backing up my memory cards and then I'll grab you some logcats of crashing apps to save you some looking. I know enough to help, but not enough to debug so you aim me at the logs that help you and I'll get you as much as I can.
I run a SM-G900T as well so we will have similar errors. Thank you for taking the time to do this, I really like all the slim roms.
Working: (Mini Gapps)
- Booted and completed setup (hung on "Welcome..." for a bit, it got through)
- Wi-Fi
- Bluetooth/Stereo Bluetooth
- GPS (Took a minute, but did lock with "Device Only" setting chosen)
- Customization Options working (battery color, statusbar transparency, quick tile settings)
- Statusbar brightness slider
- Volume and power buttons
- Real Dark Slim (hangs for a few seconds, but it succeeds)
- Camera works with third party app (Camera ZoomFX) but crashes when taking photo since it can't save to storage (16MP!)
- Headphones (Music stops when unplugged; nice!)
- Music
- Keyboard
- Navigation Bar/Pie Controls
- Dialer
- Root Permissions (had to enable prompt in settings, but it works)
- Secure Lockscreen (Pin Number)
- Normal Apps (Browser, Calc, clock, Dialer, Hangouts, etc.)
Not Working:
- Hardware buttons (Back, Home, Menu/Recents) Tried to run a logcat here, but Android doesn't even see these other than vibration
- No Signal
- Storage (Internal and external can't be accessed) Startup Media Scan Pastebin
- Auto-brightness (Cannot be enabled) Auto-Brightness Log Pastebin
- Occasional Red Rectangle
-NFC (This, once turned on, cannot be turned off and the logcat feedback is about NFC every 7-10 seconds) NFC Feedback Pastebin
Not going to lie, this isn't far from being not only usable, but a daily driver. I'm going to see if I can pull a log later on for Auto-brightness failing and also for startup and maybe see why storage isn't being recognized and mounted. The file system sees both storage cards, /storage/sdcard0 and sdcard1 are both in the root explorer of android tuner, I just get permission denied when I try to access them.
Edit: Ran fix permissions scripts to see if it would mount the memory for me, and it did not. Also, adjusted media scan to prompt and it still didn't find anything. I'm going to try to pastebin you a log for each of the above failing. Got to work on a school assignment first though

Thank you for your feed back bro. I was on 24 hour duty last night and just spent like an hour to bring everything up and build it. I am going to work on it Friday night when I get off of work and hopefully by the end of the weekend it will be daily driveable and I can move to the next project.

lunerceli said:
Thank you for your feed back bro. I was on 24 hour duty last night and just spent like an hour to bring everything up and build it. I am going to work on it Friday night when I get off of work and hopefully by the end of the weekend it will be daily driveable and I can move to the next project.
Click to expand...
Click to collapse
There is no rush, I just wanted to get you some feedback putting things through its paces. I still intend to get you those log files if you find them helpful.
Get some sleep, this project will being be there tomorrow and thanks for tackling this for everyone in the community.
Edit: I put the logs I could get from my device in the last post next to the items in the list. Some things I couldn't pull, but you may know how. Also, and as I mentioned in the post, watching the Logcat scroll every 7-10 seconds I see the NFC log I pasted for you there. Not sure what is causing it, but NFC is toggling itself on and off.
Like I said, no rush on this I just wanted you to have it when you got around to working on it. Now it's my turn to get some sleep and if you need me to pull a log under a certain condition just quote me here and I'll get whatever you need. I'm looking forward to the next test build

Thank you for all of the info bro. I should have the next build up some time Saturday afternoon and almost everything should be fixed. Its been a while since I have done this so I am a little rusty. It is almost like riding a bike. Lol.

Build two is being compiled right now as we speak. I fixed a few things in the code so hopefully everything will work like it should. HAHAHAHA

Okay, so build two keeps stopping and ending in a segmentation fault for the framework.apk... I think I may have fixed it, but really don´t know .. LOL .. keeping the fingers crossed.

lunerceli said:
Okay, so build two keeps stopping and ending in a segmentation fault for the framework.apk... I think I may have fixed it, but really don´t know .. LOL .. keeping the fingers crossed.
Click to expand...
Click to collapse
Awesome thanks for your work! I would gladly test it when it's finished. I came from the Skyrocket a week and a half ago so I am still getting used to the Galaxy S5, but I helped the OP there for SlimKat by testing and providing logs, so just let me know if there is anything I can help with.

Well, every time I get close to getting another build done something gets in the way. I lost my system and had to set it up again. Now whenever I sync the repo it keeps not finding some of the repo saying it can't connect. Lol

lunerceli said:
Well, every time I get close to getting another build done something gets in the way. I lost my system and had to set it up again. Now whenever I sync the repo it keeps not finding some of the repo saying it can't connect. Lol
Click to expand...
Click to collapse
We appreciate that you keep on keeping on and that you keep us updated with this. Developing isn't easy, if it were we would all be making our own ROMs. Whenever you get this build out there will be testers around waiting to flash it to their devices. Me included

Sorry I haven´t posted anything in a couple of days, but I lost my system again and had to start from scratch. Some times I really have VM´s, but on my laptop I take everywhere It is too much of a pain in the ass to install Linux on the side or even straight up.
Just to update though, I am compiling the 2nd build right now and everything is going smoothly. I had to replace some of the Slim files with those from CM just to get past some build problems. I do believe that I have corrected most if not all of the not working. I am waiting for it to finish compiling and test it out before I release it to you guys. I will put up the download link regardless so that you fine ladies and gentlemen can test what and see what is going on in the development. The reason that I like to do this is so that the community can see active development and to compile the lists of what is and is not working with the ROM. I know it is a different approach to other developers, but this is just how I do it. Without you guys we as developers cannot do our jobs correctly and get a working daily driven ROM. Thank you for your support.

Mods please delete this thread. I am merging with another thread of the same topic. Thank you.

Will this rom work on G900FD as it has a qualcom chipset?

M8 CM Audio Issues

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Now for the more specific stuff. Let me preface this entire thread by saying that I'm very much out on a limb here. I, as well as many others, have noticed that there are some fairly significant audio issues in CM stretching back to early CM11 builds for the M8. The general fix has always been "install v4a, and it'll work just fine". This isn't really a fix imho, it's a band-aid.
As such, I've created two repos: 4.20.x Sprint Stock, and 02/26 CM Unofficial (NOT NIGHTLY). I've uploaded the various parts that I think are going to be relevant in comparing the two code bases in the hopes that this problem can be tracked to its origin and finally fixed. The repos are on github as Stock and CM.
As far as the problems that have been noticed, it's good to remember that not all problems related to audio issues are what we're trying to address here. As an example, this is not a bluetooth thread, so bluetooth connectivity problems aren't going to be addressed even if it relates to phone calls or music playback. This is by no means a complete list and additional items should be listed as noted in posts. Some of the issues I feel that are actually related to audio problems are as such:
Distortion at loud volumes; speakers sound like crap when played loud, but not on stock or gpe
Improper playback channels; speakerphone volume level activating through phone channel rather than media channel
Sound dropouts during calls; caller can be heard but not hear M8 user (common with V4A Lolli installs)
Problem Submission: If you submit a problem to the list in your responses, please tag it as such;
PROBLEM_ITEM: [my problem description here].​This will allow me to easily search the thread and add additional known issues to the list. If you submit a problem but don't see it in the list, check Post #2 for reasoning as to why the problem wasn't initially added to the list.
Inside the Stock repo is a logcat that I took while performing operations during music playback. Specifically, I started the music playback via Poweramp, opened AudioFx from inside Poweramp, changed the EQ Preset various times,returned to Poweramp, and stopped the music. I'm hoping that starting with the logcat will lead somewhere..... as I mentioned, I'm waayyy out on a limb here.
As for my device, I'm running my own builds of CM12, no cherry-picks, SuperSu, CM kernel w/ no tweaks, NO V4A. Repo sync for this build includes Settings: reorganization merge on Feb 26, 2015 7:35 AM. Anything after is not in the current build, and therefore not in the CM repo.
ALL help is greatly appreciated, unconstructive / disrespectful comments are not. Here's to hoping this goes somewhere.

Saved for Info

It's most likely not possible to fix. Boomsound drivers are closed source. Unless HTC decides to make the drivers open source, then we probably won't be able to get sound fixed on cm. [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80]

Yea... that was a statement I made in another thread responding to one of those "Why can't CM fix the audio issues already" posts. I still think that there might be a channel problem, especially with the way that the speakerphone is operating. So far though, I've not found a direct reference to the boomsound drivers in digging through the stock sources.

Rescue9 said:
Yea... that was a statement I made in another thread responding to one of those "Why can't CM fix the audio issues already" posts. I still think that there might be a channel problem, especially with the way that the speakerphone is operating. So far though, I've not found a direct reference to the boomsound drivers in digging through the stock sources.
Click to expand...
Click to collapse
I'm thinking it could be done through the kernel. But that's beyond my skill level.

probably not relevant , but all i got.lol. just found on beanstalk ROM. of course , i wouldnt know what to do with it. lmao.
"all i can really do , is stay out of my own way and let the will of heaven be done"

mrrocketdog said:
just found on beanstalk ROM. of course , i wouldnt know what to do with it.
Click to expand...
Click to collapse
no worries mrrocketdog. can you verify that you do not have audio issues on beanstalk rom? If so, think you can find mixer_paths.xml, audio_effects.xml, and audio_platform_info.xml and post links?
I found up that mixer_paths.xml is indeed used, unlike what some were saying in the other thread. and I'm starting there.

Rescue9 said:
no worries mrrocketdog. can you verify that you do not have audio issues on beanstalk rom? If so, think you can find mixer_paths.xml, audio_effects.xml, and audio_platform_info.xml and post links?
I found up that mixer_paths.xml is indeed used, unlike what some were saying in the other thread. and I'm starting there.
Click to expand...
Click to collapse
no audio issues confirmed. will look for path and report back.
"all i can really do , is stay out of my own way and let the will of heaven be done"

@Rescue9 , all i could find were these under system-lib-hw.
https://www.dropbox.com/sh/3xaqr8nlr19v6mm/AAD2VdLPQf8ijftOxZQiKmeGa?dl=0
if there is some other folder to check just let me know. i think i went thru them all. (maybe just named different?). will also go thru my cm11 nightly and look for above mentioned files. also can confirm no audio distortion on it. ran for about 2 months.
here is cm11.
https://www.dropbox.com/sh/prv441xo5mu25sj/AAAtGuWro9Jz4y3B2E8dtvm9a?dl=0
again , could not find exact files you requested , but uploaded everything with 'audio' in title.
"all i can really do , is stay out of my own way and let the will of heaven be done"

The discussion in this thread is great and definitely development related with an end goal as the rules say. However, since it's unofficial, we decided to move it to Development. Please PM me if you have questions or concerns.
Thanks,
coal686
Forum Moderator

@Rescue9, found maybe something else. beanstalk - system - media - soundimage.
https://www.dropbox.com/sh/whqk8elvgjbd7jh/AACoqdZrxrNH3C1BMn2IHzXha?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"

Some possible Kernel help.
Not sure if this will help or not, but I'm running the CM12 based rom Resurrection Remix by: Brian Koluch
The Kernel he includes seems to fix a lot of the speaker distortion issues I was having with my M8. The Kernel is: B14CKB1RD v3.4.36 (g1069d49)
Here's his Google+ RR Community Post: https://plus.google.com/115522815889154627721/posts/d9BApKK8nbx
Maybe you guys can review that Kernel and see what's different, it has some audio commits in it.

toknitup420 said:
It's most likely not possible to fix. Boomsound drivers are closed source. Unless HTC decides to make the drivers open source, then we probably won't be able to get sound fixed on cm. [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80] [emoji80]
Click to expand...
Click to collapse
nothing is imposible.

What about using v4a or using a volume limiter ??

fcukmayank said:
What about using v4a or using a volume limiter ??
Click to expand...
Click to collapse
Those are band-aid solutions. The goal is to fix the problem once and for all.

CJ-Wylde said:
The Kernel he includes seems to fix a lot of the speaker distortion issues I was having with my M8. The Kernel is: B14CKB1RD v3.4.36 (g1069d49)
Click to expand...
Click to collapse
This is very informative! After playing around extensively with the config files in /etc/ I'm beginning to think that this is indeed a problem wholely related to the kernel. I remember using Quantum on my GS3 simply because the kernel fixed a number of issues.
Part of the problem that I'm facing is the fact that my M8 doesn't sound all that distorted on the high end. I feel as I'm trying to grease a squeaky wheel when I don't even hear the squeak.

I know that with the build I'm on now with the Kernel I mentioned, things are definitely more clean & clear on the speakers. I'm glad I can help a little bit.

Thanks @CJ-Wylde never knew this Brian guy built Roms for the m8. I see the kernel is a from wyldstallyn using blackbirds git.
OP maybe ask Brian on G+ if he can direct you to who built the kernel and ask them what they changed if anything that is maybe fixing the distortion

krazie1 said:
OP maybe ask Brian on G+ if he can direct you to who built the kernel and ask them what they changed if anything that is maybe fixing the distortion
Click to expand...
Click to collapse
That's a good idea @krazie1. Would you take care of that for the team. I'm still working through lines of code looking for a connection.
I did install the blackbird kernel straight over the 02/28 CM12 build I'm running now and the speakers actually sounded worse. Very distorted at half volume. I didn't even want to increase the volume fie fear of damaging them.

Rescue9 said:
That's a good idea @krazie1. Would you take care of that for the team. I'm still working through lines of code looking for a connection.
I did install the blackbird kernel straight over the 02/28 CM12 build I'm running now and the speakers actually sounded worse. Very distorted at half volume. I didn't even want to increase the volume fie fear of damaging them.
Click to expand...
Click to collapse
Here is the wyldstallyn's kernel github https://github.com/wyldstallyns
I will be flash testing the resurrection remix 5.3.7 build later when my phone charges up

SMS sending not working in LineageOS 15.1

Hi,
I'm acually working on LineageOS 15.1 and I'm running into a problem:
In frameworks/base/core/java/android/content/BroadcastReceiver.java (in the method PendingResult beginning with line 86) the resultCode is set to 4!
This is
Code:
RESULT_SMS_UNSUPPORTED
added in API level 19
public static final int RESULT_SMS_UNSUPPORTED
Set by BroadcastReceiver to indicate that the message, while possibly valid, is of a format or encoding that is not supported.
Constant Value: 4 (0x00000004)
My problem is, I can't figure out, where and why this is set!
So, it's not possible to send a message via SMS...
Any help is welcome!

These two main problems are left in LineageOS 15.1:
Camera not working
Sending SMS not working
There are a few minor problems, but they are not important.
If there is no further help, this finally will be the end of developing this ROM! :crying:

thanks for the work
im just want stable rom.
my stock ROM reboot too much everday after rooting.
so now im using 14.1 no reboot here, you already lose lots good options in the LA14 camera like slow motion(high fps rate) and EIS \ OIS
this phone slowly dying
even my old sony(LWW) was develop from android 2.3 upto 7.1 (through CM to lineage) about 7 years (include custom roms)

Superrman said:
thanks for the work
im just want stable rom.
my stock ROM reboot too much everday after rooting.
so now im using 14.1 no reboot here, you already lose lots good options in the LA14 camera like slow motion(high fps rate) and EIS \ OIS
this phone slowly dying
even my old sony(LWW) was develop from android 2.3 upto 7.1 (through CM to lineage) about 7 years (include custom roms)
Click to expand...
Click to collapse
I understand what you are saying but I think the users enjoying Bernie's ROM are practical users who do not care about latest (crap) features like live emoji or animojis or whatever teenage functions they implement. Real innovations are not to be found. Currenty i switch between my iPhone 7 and Z5c every other week. I still think my Z5c rocks!
I would love to try L15 so I sincerely hope Bernie will find support for his development.

Berni-0815 said:
Hi,
My problem is, I can't figure out, where and why this is set!
Click to expand...
Click to collapse
I've been skimming through LOS repos. AFAICT, the only place in which that constant is used is here.
Antonio

antonio.galea said:
I've been skimming through LOS repos. AFAICT, the only place in which that constant is used is here.
Click to expand...
Click to collapse
Yes; I know. But I've set a logging command at this point and the code is never reached.
So, it ("4") must be set somewhere else...
I've set so much logging commands in some suspicious sourcecode-files but I can't figure out, where this could happen.
The logging commands are showing this chronological order:
Code:
packages/apps/Messaging/src/com/android/messaging/util/PhoneUtils.java #getCanonicalByCountry()
- MessagingApp: (bt): Number valid at this point! getCanonicalByCountry(): canonicalNumber: +nnnnnnnnnnn
>>> It must happen [B]after[/B] the above sourcecode-file and [B]before[/B] the next ones: <<<
frameworks/base/core/java/android/app/LoadedApk.java (Don't find anything)
frameworks/base/core/java/android/content/BroadcastReceiver.java #getResultCode() #PendingResult() #getPendingResult() and #setPendingResult()
- BroadcastReceiver: (bt): PendingResult(Line 86): resultCode: 4