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 !

[Q] Xperia Arc | CM9.0 | FXP106| Can't add any APN's

Hello,
I flashed my Arc with baseband 62 on the latest CM 9.0 FXP106. I'm pretty satisfied so far. The only thing that bugs me is that it seems that I can't add any APN's. That means if I want to add a new APN and I want to save it, it won't let me do it.
I tried backing it up with APNsBU (ROOT) -> didn't work
Hard reset -> didn't work
Fixing permissions in ROM Manager -> didn't work
Thanks for your help!

1.) Have you heard of posting in the relevant thread?
2.) It's a known bug. Read before post and use the search!
Sent from my LT18i using xda premium

Hey,
as I don't have 10 posts yet I can't post in the CM9.0/FreeXperia Thread.
I actually looked through a lot of posts and didn't find any relevant help.
Thanks for your reply though.

dont find it?it is already mention posted so many time..
Sent from my LT18i

this problem is in all xperia 2011, few networks operate

I have the same problem, does anyone know a way around this?

monstercable said:
I have the same problem, does anyone know a way around this?
Click to expand...
Click to collapse
Bin4ary posted a probably way to fix it, check out CM9's thread for more information.
Bin4ry said:
From what i can tell now the problem is that in CM9 we are using the ICS (ofc ) RIL-structure. There are already some oldRil features implemented, but this features are mainly for phones which use standard communications. We are having this weird Qualcomm RIL which acts different. For example we have no Status which tells System that SIM is ready, this status is piggybacked for us in another call.
On the other side we SE implemented some more messages for additional informations. For example: OperatorInfo is not standard one, it has one more entry.
So i need to go through the lines and check we're i can implement the different structure well without breaking other devices. Maybe i am able to trigger all needed parcel reads from RIL, maybe not. The main difference is lying in some other files which was still working in GB RIL structure.
Please wait for next week when i am able to work again on this issue. It's annoying me too
No. I will work on GSM data. Jerpelea will fix this problem ASAP.
Since we are 2 people working on this CM9 for the SE phones we can split the work.
And it is always better to work on 1 problem after another.
You see, 2 people -> 2 Todo lists
Regards
Click to expand...
Click to collapse

Thanks for your help. I didn't get that this was related to the APN issue.

BUG: JB 4.1.2 update - Pressing Home Button to wake brings up task manager sometimes?

I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.

mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...

Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse

My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.

I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse

mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test

You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse

No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?

I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.

mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days

I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you

kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear

Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.

It's not all notes.
Sent from my SGH-T889 using xda premium

kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?

wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry

wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.

kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over

[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.

GOOD NEWS CM 12 on E980 every thing work LTE-phone work

GOOD NEWS CM 12 on E980 every thing work LTE-phone work.
http://forum.xda-developers.com/optimus-g-pro/general/data-voice-heard-phone-t3061313
DangNavyCM12-F240L-Fix fix dial audio after I mod .
PS.. when update the new rom voice not heard,don't forget to update my mod .
By DangNavy
Now I can go spring fishing, 2 days of the testing, happy got my lollipop ,any girls want some.HA HA HA
PS...Don't forget give me some love

Go fishing
Audio call fix

Can you explain what this does exactly? I have needed to install your mod for every CM nightly, and also for Blisspop on my e980 running on tmobile. Just curious what it does, in case your patch file stops working for new version.
Thanks again!!

I think it changes at least these 2 options in /system/build.prop file
1. persist.audio.dualmic.config, from 'endfire' to 'false'
2. persist.audio.handset.mic.type, from 'digital' to 'analog'
You can change these values yourself with the prop.mod editor, but you also have to change these values every time you update or install the ROM. The dangnavy script also changes some other values, but the two I've mentioned are the ones that effect the in-call phone mic volume. I got these solutions from this post: http://forum.xda-developers.com/showthread.php?t=2709781

thank you hawkwind!! Yea I was curious because in roms like CM, Blisspop, or even slimLP there is no mention to needing anything after installing the ROM to make the sound work during calls. However I always have to install this patch to make it work so it leads me to wonder what is different about my e980 that causes me to have issues that no one else seems to bring up lol .

damainman2015 said:
thank you hawkwind!! Yea I was curious because in roms like CM, Blisspop, or even slimLP there is no mention to needing anything after installing the ROM to make the sound work during calls. However I always have to install this patch to make it work so it leads me to wonder what is different about my e980 that causes me to have issues that no one else seems to bring up lol .
Click to expand...
Click to collapse
In the earlier version of the blisspop, the dev had changed the values in the build.prop file so the users would not needed to do so them selves. Since this was such an old issue according to that posting, perhaps dev thought that it was no longer necessary to change those two values.

Hi I'm using stock g4 ux4.0 lollipop g pro v12 final rom and during phone calls I have to use headphones whit mic because there is no sound without them . Will this fix work for me?

It may, though I think with the ROM you're using there is a patch for the sound issue, check the dev's thread first. Otherwise try the solution we've discussed here with prop.mod editor anyway, since it will not harm your device even if, it doesn't fix your problem. Just remember to reboot the phone once you're done with changing the values.

hawkwind212 said:
I think it changes at least these 2 options in /system/build.prop file
1. persist.audio.dualmic.config, from 'endfire' to 'false'
2. persist.audio.handset.mic.type, from 'digital' to 'analog'
You can change these values yourself with the prop.mod editor, but you also have to change these values every time you update or install the ROM. The dangnavy script also changes some other values, but the two I've mentioned are the ones that effect the in-call phone mic volume. I got these solutions from this post: http://forum.xda-developers.com/showthread.php?t=2709781
Click to expand...
Click to collapse
If changing these doesn't affect other variants (E985/6/9 and even F240x), I'd be glad to change them in my device tree.

ShadySquirrel said:
If changing these doesn't affect other variants (E985/6/9 and even F240x), I'd be glad to change them in my device tree.
Click to expand...
Click to collapse
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.

hawkwind212 said:
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
Click to expand...
Click to collapse
Couldn't agree more. Since this is variant specific thing, I won't change anything... I've put an info about that in Slim's thread, but it looks like people really don't like reading.

hawkwind212 said:
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
Click to expand...
Click to collapse
Just wanted to state, this patch is what fixes the no call audio issue for me while utilizing the TMobile network.