Develop Bugs

Light sensor level mod - no dev?

Hello guys, I've made the question, but the Q&A section is not very visited so...
http://forum.xda-developers.com/showthread.php?t=776871
Is there a DEV that can make the light sensor become adjustable in the SENSE UI roms? like on AOSP (i think open desire has it or cyanogen)
http://twitpic.com/2k4qjz

+1 really love to have one

casca said:
Is there a DEV that can make the light sensor become adjustable in the SENSE UI roms? like on AOSP (i think open desire has it or cyanogen)
http://twitpic.com/2k4qjz
Click to expand...
Click to collapse
Which one exactly? I'm willing to take a look at it as the issue annoys me too, if someone points me to the source (but no guarantees that I might have the time or be able to do anything about it).
EDIT: Found the CM source for it.

+1 I would love to see this as well.

martino2k6 said:
Which one exactly? I'm willing to take a look at it as the issue annoys me too, if someone points me to the source (but no guarantees that I might have the time or be able to do anything about it).
EDIT: Found the CM source for it.
Click to expand...
Click to collapse
you were faster than me searching, i was out lunching and haven't saw the topic reply e-mail
if you need assistance on testing, just PM me or let me know at the topic.
It would be nice to have this working, it's so annoying...
Why the f*ck do they include a light sensor if it doesn't work properly?!even after releasing fixes!?lol
Although I think I might know the answer...
"OK, so we gave them the hardware with buggy software to keep them busy...let them(users) figure out a fix, and this way we have time to develop some even nicer phones..."

The main problem here is that since we don't have HTC Sense sources, as they are proprietary, we can't modify system settings with an application which doesn't run as part of the system.
My understanding therefore is that this can be done in two ways:
1) Writing a kernel module which sets the appropriate/specified values on boot (I don't have enough experience to do that) or modifying the default kernel values.
2) Modify values in /sys (wherever they may be hiding) which will be reset any time you reboot, and also may get overwritten by the system at will.
That's my limited understanding anyway. If anyone would like to shed more light on this then please feel free to, or any other ways how this could be achieved...

Moved to Q&A. Please don't post question threads in Development.

fair enough
could we simply start an "official light sensor level developement for sense UI" thread or something like that ?

+1 guys we really neeeed that **** ;p
tks for your work !

Accelerometer/Gyro kernel programming

I am posting here because I am not allowed to post in the developer forums (although this belongs there).
I am trying to figure out how the accelerometer or gyroscope readings make it out of the kernel to the rest of the Android system. I am using and compiling the kitkat kernel (msm-flo-3.4-jb-mr2) for the Nexus 7 2013 wifi version. I have used printk() in the drivers/input/misc/mpu3050.c and drivers/input/misc/lis3dh_acc.c files to see if the read routines are being called when I move the tablet around or when I use an app to read the sensors but I don't see any reads at the kernel level. The file proc/kmsg shows only the lis3dh_acc driver is loaded but I never see any of the code other than the init being called.
Anyone have any insight as to how the accelerometer and gyro are read? I could not find any other kernel code being built that had to do with those sensors.
Thanks.

stu54 said:
I am posting here because I am not allowed to post in the developer forums (although this belongs there).
I am trying to figure out how the accelerometer or gyroscope readings make it out of the kernel to the rest of the Android system. I am using and compiling the kitkat kernel (msm-flo-3.4-jb-mr2) for the Nexus 7 2013 wifi version. I have used printk() in the drivers/input/misc/mpu3050.c and drivers/input/misc/lis3dh_acc.c files to see if the read routines are being called when I move the tablet around or when I use an app to read the sensors but I don't see any reads at the kernel level. The file proc/kmsg shows only the lis3dh_acc driver is loaded but I never see any of the code other than the init being called.
Anyone have any insight as to how the accelerometer and gyro are read? I could not find any other kernel code being built that had to do with those sensors.
Thanks.
Click to expand...
Click to collapse
I am thinking that maybe the kernel is not called at all for sensor readings. Maybe the AOSP code is calling the proprietary libraries in vendor/qcom/flo/proprietary. If so, I would have to run code at the system level, not the kernel level.

stu54 said:
I am posting here because I am not allowed to post in the developer forums (although this belongs there).
Click to expand...
Click to collapse
I don't have an answer for you, but you posted this in the right place. Questions go in Q&A, ROMs/kernels go in development and the rest goes in general. For the most part anyways.

[Q&A] [ROM][D855][20A][Lollipop] --|||..:: ChupaChups Rom::..|||--

Q&A for [ROM][D855][20A][Lollipop] --|||..:: ChupaChups Rom::..|||--
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][D855][20A][Lollipop] --|||..:: ChupaChups Rom::..|||--. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

is miniview in progress?
thxv

hi, somehow I don't see why not finish CyanogenMod first before you start other projects based on stock rom, which many people don't expect
sorry for my bad english

ermm... why not the 80° mod?
just curious, lol...
and no need to wipe or anything?

19h to chupachups
hi guys.
Sorry, new here, quick question, how would one get from 19h to this version?
getting allot of lag and i think its due to upgrading to 19h instead of installing fresh.
Sorry of the question is basic and if its answered somewhere. i had a hint around without luck.
Thanks

can you port this rom to d850?

Google Services Battery Drain
One would think with all the development in both lollipop and kitkat that this problem would have been fixed and implemented into all the new rom releases. Google Services battery drain depletes the battery preventing the phone from deep sleep and accounts for quite allot of drainage. A fix would be nice from the developers, Thanks.

@Skin1980
there are no notifications, but why my led keeps blinking?

Brave Frontier anyone?
anybody here play brave frontier? i wanted to try this rom but i'm hesitant to make the switch because in the stock kitkat rom, the game would constantly crash (even with all effects off).. Currently on AOSP it works well, but I miss the sleek look of the LG UI

new kernel
lagfree governor
http://imgur.com/hhklRZd
http://imgur.com/j6A3DcI

How did you manage to get those stats?
tehosiris said:
lagfree governor
http://imgur.com/hhklRZd
http://imgur.com/j6A3DcI
Click to expand...
Click to collapse
What kernel are you speaking of? What settings are you running (brightness, tweaks etc)? A little context would help many folks smile a little. The pictures are all fine and well, but how did you achieve that?

astrokreep said:
What kernel are you speaking of? What settings are you running (brightness, tweaks etc)? A little context would help many folks smile a little. The pictures are all fine and well, but how did you achieve that?
Click to expand...
Click to collapse
it's the new kernel, since that has the new options, decided to try lagfree first, worked well i guess
auto brigthness, wifi and location enabled all day

I see...
tehosiris said:
it's the new kernel, since that has the new options, decided to try lagfree first, worked well i guess
auto brigthness, wifi and location enabled all day
Click to expand...
Click to collapse
Sorry for all the questions, just trying to clarify for everyone else. You mean this one?
http://forum.xda-developers.com/lg-g3/orig-development/kernel-chupachups-kernel-t2943339
And how are you finding this kernel?

astrokreep said:
Sorry for all the questions, just trying to clarify for everyone else. You mean this one?
http://forum.xda-developers.com/lg-g3/orig-development/kernel-chupachups-kernel-t2943339
And how are you finding this kernel?
Click to expand...
Click to collapse
yes thats the one,
it's just as good as the one before to be honest, haven't really noticed anything spectacular
although i never had issues before, so i can't tell if it fixes anything or not hehe

Hi,
First of all, thank you for your hard work.
Could you please advise, if it's possible to customize this ROM somehow? I would love to:
1) Remove all lg software
2) Remove stock browser
3) Replace stock dialer with something else
4) Replace messaging app with let's say Textra or something similar
5) Have only Core Google Apps (something like PA-Gaps Nano)
Sorry for noob questions.
Thank you very much,
Yuriy

I dirty flashed this and ever since music from Google Play and Soundcloud just refuses to play. I can play music locally in other apps but even local music won't play in Googe Play Music. Has anyone else had this problem?

Banker Z Concern or False Positive?
Avast alerted me as well. Seems like it was able to remove it and everything was working before it was detected and still is after it was removed. Could be a false positive since a lot of people are reporting it now but better to be safe for now and let Avast and them go to work.

Thank you very much @Skin1980 for the great work! I'm having a little bug about notification LED. I'm having blinking white LED like Whatsapp default LED notification even if I haven't got any new message. I flashed the new kernel and using the Lollipop Theme of Kickoff.

Knock code is buggy
I don't know if someone else is having problem with the knock code feature as well. I found that some times the knock code feature doesn't work properly. While the screen is off and after knocking the proper code the screen won't wake up, not even after double tapping on it. Even the LED that turns on when you introduce a wrong code is not turning on, it is like it was disable. I have to press the power button, wake up the screen and then introduce the code.
I have a quick circle case and a smartwatch connected as a trusted device to use the new Smart lock feature that comes with Lollipop. I'm not looking for a solution, just pointing out the bug, I'll flash the LG stock image as soon as it's realeased in my country.
By the way, none of the quick circle apps work. Only the ones that comes with the phone by stock. You might want to check that up.
Thanks for all your work, it is awesome to have a developer community like this one. =)

Anyone having issues on Feedly after moving to this rom or any other Lollipop rom ? When scrolling the sources list everything gets blank, then reappears, like it's some rendering problem.

[Q&A] [ROM][4.4.4][SM-T700] Bliss Stalk by Team Bliss

Q&A for [ROM][4.4.4][SM-T700] Bliss Stalk by Team Bliss
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][SM-T700] Bliss Stalk by Team Bliss. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

jewnersey said:
not sure why that's happening..but a new build should be up in the next day, hopefully, with some of the kinks ironed out. Probably best to just wait until then.
Click to expand...
Click to collapse
@ jewnersey: It could be the greatest rom :angel:, if you can embedded camera features in the next update. Not forcing you to do that immediately, just requesting you since you are engaged with your job. Thanks.

cant believe how great this rom is..i agree..so so many options...one of the best custom roms ever had..it flashed perfect for me..ive read how some people are haveing problems with wifi not working,i flashed the rom,then kernal,then gapps,and wifi worked out of the box..if it diddnt i was gonna flash a diff recovery like philz and try again..normally that works for me...only issue ive had is when pressing language and input it crashes.i was gonna install a themed google keyboard and activate it as main keyboard but cant get into the settings to even see what keyboard is installed..but still love the rom and understand its a work in progress...thanks bliss team for this rom and port,much better then what i had before this!!!
update..now see witch keyboard is installed threw settings/apps....it is android keyboard..could request that android keyboard come with diff themed options i really like the shafta google keyboards,but cant install if google keyboard allready exsists,and i dont wanna mess with freezeing/uninstalling system apps

any lovin for the t705??
we uad some advancements but got stuck at the lte implementation.
could be due to the 4g/3g intel chip samdung used for its exynos chip.....
i feel so cheated out of my snapdragon 801.....

Am uploading a newer build that should be much cleaner and ironed out.
As far as other devices... I am not a developer, so bug fixing etc is currently beyond me... However, if there is a CM port for the device, I can probably port Bliss for that device, but all the shortcomings of the CM rom will exist in Bliss as well.. Either way, I will see what I can do after I make sure T700 is running smoothly.

New build is up.

Hey
It would be nicer if you have some specific screenshots. BTW, hope you guys can ported this rom to T805 lots of Asian users are waiting for you

stkpxl said:
Tried the new build. Tried to create a second user (which is a must for me). When trying to use the new user, the launcher crashes and basically wont let me do anything. With the new CM11 build, I don't have that issue. Which is weird, since I understand thats what your build is using.
Click to expand...
Click to collapse
will look into this.
vo.tran.thanh.luong said:
It would be nicer if you have some specific screenshots. BTW, hope you guys can ported this rom to T805 lots of Asian users are waiting for you
Click to expand...
Click to collapse
screenshots added.....
I am basically relying on the real developers, so once CM or an equivalent arrives for 805, ill fire up a Bliss derivation.

Thank you for your hard work providing this rom! just couldn't stand the stutter of touchwiz.
one thing I desperately miss is the color calibration though.
I can't find the option in settings. could somebody please point it out to me?
another thing I noticed is that the tablet runs smoother when plugged in. when I pull the plug I have a tiny bit of stutter. Do you have any suggestions how to fix this?

Screen Locks automatically and frequently
Hi Jewnersy,
I appreciate your efforts in creating the Bliss Rom for Samsung Tab S (T700). I have been using the rom from the last two releases. I love the settings and customizations provided in the Rom . I observed one small issue in the latest build. I am using a Flipcover cover for my Tab. When I close the cover, screen goes off which is fine. But When I open the cover am able to the see the lock screen, but not able to unlock the screen by swiping the lock icon to right side. After swiping it to right side, screen suddenly locks again. After giving trails for 10 - 15 times, am able to unlock the device. While watching movies also screen locking unexpectedly. Please help me in getting a solution for the issue. Thanks again for your response & support in advance.

schmandchen said:
Thank you for your hard work providing this rom! just couldn't stand the stutter of touchwiz.
one thing I desperately miss is the color calibration though.
I can't find the option in settings. could somebody please point it out to me?
another thing I noticed is that the tablet runs smoother when plugged in. when I pull the plug I have a tiny bit of stutter. Do you have any suggestions how to fix this?
Click to expand...
Click to collapse
Don't think there are any color options built in to the rom unfortunately. Regarding stuttering.. I'm not sure I'm having that issue. The latest rom had been smooth as butter for me... Interactive governor, cfq, Westwood.
Dynamic status bar will cause constant stutter. Use the xposed mod discussed in thread as an alternative
raghavamsc said:
Hi Jewnersy,
I appreciate your efforts in creating the Bliss Rom for Samsung Tab S (T700). I have been using the rom from the last two releases. I love the settings and customizations provided in the Rom . I observed one small issue in the latest build. I am using a Flipcover cover for my Tab. When I close the cover, screen goes off which is fine. But When I open the cover am able to the see the lock screen, but not able to unlock the screen by swiping the lock icon to right side. After swiping it to right side, screen suddenly locks again. After giving trails for 10 - 15 times, am able to unlock the device. While watching movies also screen locking unexpectedly. Please help me in getting a solution for the issue. Thanks again for your response & support in advance.
Click to expand...
Click to collapse
I noticed a flip cover quirk as well. Will investigate tomorrow and grab some other fixes from other folks.

WiFi is not turning on with the latest (12/15) build of the Bliss Stalk ROM for the SM-T800.
For some truly asinine reason XDA is forcing this reply into a separate Q&A thread (where it will undoubtedly go unnoticed by the developer of this ROM) just because I have fewer than 10 posts.
This post is INTENDED to be a reply to this post:
http://forum.xda-developers.com/showpost.php?p=57506489&postcount=89
Again, I apologize for this reply not appearing in the correct location - blame XDA or whomever thought it would be a good idea to force all replies by new users into a totally separate thread.
---------- Post added at 03:32 AM ---------- Previous post was at 03:27 AM ----------
Zimus said:
WiFi is not turning on with the latest (12/15) build of the Bliss Stalk ROM for the SM-T800.
For some truly asinine reason XDA is forcing this reply into a separate Q&A thread (where it will undoubtedly go unnoticed by the developer of this ROM) just because I have fewer than 10 posts.
This post is INTENDED to be a reply to this post:
http://forum.xda-developers.com/showpost.php?p=57506489&postcount=89
Again, I apologize for this reply not appearing in the correct location - blame XDA or whomever thought it would be a good idea to force all replies by new users into a totally separate thread.
Click to expand...
Click to collapse
Feel free to ignore this particular post, I'm going to post a bunch of B.S. until I can get my total post count over the 10 post threshold so that I can actually post bug reports in the proper thread.

Zimus said:
WiFi is not turning on with the latest (12/15) build of the Bliss Stalk ROM for the SM-T800.
For some truly asinine reason XDA is forcing this reply into a separate Q&A thread (where it will undoubtedly go unnoticed by the developer of this ROM) just because I have fewer than 10 posts.
This post is INTENDED to be a reply to this post:
http://forum.xda-developers.com/showpost.php?p=57506489&postcount=89
Again, I apologize for this reply not appearing in the correct location - blame XDA or whomever thought it would be a good idea to force all replies by new users into a totally separate thread.
---------- Post added at 03:32 AM ---------- Previous post was at 03:27 AM ----------
Feel free to ignore this particular post, I'm going to post a bunch of B.S. until I can get my total post count over the 10 post threshold so that I can actually post bug reports in the proper thread.
Click to expand...
Click to collapse
Wow I tested too! I posted in the rom thread. If your reporting bugs then it's OK to post in the rom thread. q and a stuff goes here about the thread. It's just to remind you to ask questions here. I'm surprised Ui lag is gone! Once you make more than 100 posts then there's no limit on posts.

DUHAsianSKILLZ said:
Wow I tested too! I posted in the rom thread. If your reporting bugs then it's OK to post in the rom thread. q and a stuff goes here about the thread. It's just to remind you to ask questions here. I'm surprised Ui lag is gone! Once you make more than 100 posts then there's no limit on posts.
Click to expand...
Click to collapse
I TRIED to post in the ROM thread by clicking the "reply" button on post #89, but received an error message stating the developer has decided that all posts from users with less than 10 posts should be moved to a separate Q&A thread. Such a decision makes it impossible to actually submit bugs...

Zimus said:
I TRIED to post in the ROM thread by clicking the "reply" button on post #89, but received an error message stating the developer has decided that all posts from users with less than 10 posts should be moved to a separate Q&A thread. Such a decision makes it impossible to actually submit bugs...
Click to expand...
Click to collapse
Lol. After a few posts you can post there. Did you try the camera and see if it works? I forgot to check that.

Zimus said:
I TRIED to post in the ROM thread by clicking the "reply" button on post #89, but received an error message stating the developer has decided that all posts from users with less than 10 posts should be moved to a separate Q&A thread. Such a decision makes it impossible to actually submit bugs...
Click to expand...
Click to collapse
not my decision, but rather the forums.
ANYWAYS, did you try without the kernel or with the kernel?

DUHAsianSKILLZ said:
Lol. After a few posts you can post there. Did you try the camera and see if it works? I forgot to check that.
Click to expand...
Click to collapse
I switched back to the 11/27 build due to wifi not working on the 12/15 build. The camera doesn't work on 11/27, but the developer is already aware of that issue. Give me a few min and I'll re-flash the 12/15 build and check the camera.

Zimus said:
I switched back to the 11/27 build due to wifi not working on the 12/15 build. The camera doesn't work on 11/27, but the developer is already aware of that issue. Give me a few min and I'll re-flash the 12/15 build and check the camera.
Click to expand...
Click to collapse
let me know if you are using the 'skyhigh' kernel or not...
basically need to know if wifi is broken with and without kernel
as well as camera under both conditions,

jewnersey said:
not my decision, but rather the forums.
ANYWAYS, did you try without the kernel or with the kernel?
Click to expand...
Click to collapse
I tried just the ROM w/o flashing the SkyHigh kernel - wifi still wouldn't turn on. My apologies on my rant concerning the 10 post minimum, the "error" message made it sound like it was your decision -- sorry!

Zimus said:
I tried just the ROM w/o flashing the SkyHigh kernel - wifi still wouldn't turn on. My apologies on my rant concerning the 10 post minimum, the "error" message made it sound like it was your decision -- sorry!
Click to expand...
Click to collapse
not a problem.
Let me have a look at the source and see if i can figure whats going wrong. probably something super easy. hopefully can post a new build in a few hours. did you try camera?

[N910C/H][DEV] AOSP sources

*omg, thread updating needed*
Hey guys, as some of you might know, I was donated a Galaxy Note 4 (N910C) and am now working on AOSP for it.
The sources required to build a ROM are hosted at GitHub currently:
device: https://github.com/teameos/device_samsung_treltexx/
kernel: https://github.com/raymanfx/kernel_samsung_trelte/
vendor: https://github.com/raymanfx/vendor_samsung_treltexx/
If you want to give this a shot, you should be familiar with git and repo and be able to sync the TeamEos source yourself.
If anybody feels brave enough, give it a try yourself, all the required bits are posted above
TODO/BROKEN:
Bluetooth headset calls (RX works, TX is broken)
Open source AVC (H.264) Encoder is broken (Videos recorded in portrait are rotated by 90° counter clockwise, and there's artifacts all over the place)
Everything else should be pretty much working.

hopefully watching all your work. congratulations.

hey! any progress on this? I'm really excited!
Sent from my SM-N910C using XDA Free mobile app

+1

Congratulations

First success:
The phone is booting and the adb server is starting.
I'm still missing some sensor blobs from stock which causes the sensor layer not to start and thus prevent various other init tasks (such as display, EGL) to crash.
I'm going to work on getting at least display up this weekend.
No promises though.

This is great news. Thanks for this hard work. Thank you for making our donation future experience CM12.

someone was trying to port CM11 to galaxy alpha.. i guess its a similar kernel..
http://forum.xda-developers.com/note-4/development/exynos-543x-android-development-t2949478
dats d link.. jus posting, if it helps u in anyways..

Good luck!

Superb!!!

Awesome work looking forward to seeing it on my N910U... hopefully

Great :good:

Awesome!

More progress today:
The device partially boots now, boot animation shows but that's where it loops.
Sensors are fully working and storage handling (internal storage, external sdcard and usbdisk) have been fixed.
I'm still missing some camera blobs which I believe keep the device from booting up (because it crashes other init services).
I'll look into that tomorrow probably.
All the latest fixes have been pushed to my github repos, so if anyone in here feels like experimenting a bit, let me know how it goes

RaymanFX said:
More progress today:
The device partially boots now, boot animation shows but that's where it loops.
Sensors are fully working and storage handling (internal storage, external sdcard and usbdisk) have been fixed.
I'm still missing some camera blobs which I believe keep the device from booting up (because it crashes other init services).
I'll look into that tomorrow probably.
All the latest fixes have been pushed to my github repos, so if anyone in here feels like experimenting a bit, let me know how it goes
Click to expand...
Click to collapse
These words cause many joys.

@RaymanFX , great work, update the first post with every progres, and for the other guys this a dev thread, dont spam with greets otherwise im sure a mod is gonna close the thread, keep it dev related or someone can open a thread in the general options for this project

Go go go

Progress?

+1

Well, as stated on the first post, it'd probably make more sense to watch my github for progress instead of asking in this thread.. Just saying.
Big progress has been made in terms of audio, as I finally got around to configuring proper mixer paths for audio devices here: https://github.com/RaymanFX/device_samsung_trelte/commit/c5954750b5c13ce9bf27992f145a18a837099e12.
I had to do lots of research because there is little to no documentation on these mixer_paths.xml configs, so I ended up creating it from scratch based on Samsung's UCM config.
The device still doesn't boot further than the bootanimation, but I still have some interesting lines in the logs to solve, for example it still reports invalid input/output devices in audioflinger, which clearly is an issue.
At least the issues preventing us from booting are no actual display issues, but init services crashing.
Also, it looks like the RIL is starting up after adding Samsung's cbd daemon to early init execution (ramdisk), but I don't expect telephony/mobile data to work just yet.