Develop Bugs

[ Troubleshooting ] The dialer and CM based ROM, i need help

Hello
I have a problem with the phone dialer and the rom based on CM ie CM10, AOKP or AOSP.
Let me explain: When a call is received, the display is on, normal, when the approach of the ear, the screen goes to sleep, ok on stock rom and stock based custom rom
However I could not get out of sleepping the screen on the CM based rom during a call :crying: even if i press home button or power button !
I always flash the included kernel, so i don't know where is my mistake. Am I alone with this failing ?
In advance, thanks for any help.
Regards

Any suggestion

Some CM (or was it just CM10?) based ROMs have issues with proximity sensor. A bug in the ROM.

Someguyfromhell said:
Some CM (or was it just CM10?) based ROMs have issues with proximity sensor. A bug in the ROM.
Click to expand...
Click to collapse
This is what seemed to me : the proximity sensor :crying:
But do you think if I get hw_config.sh from the stock ROM and I paste into a CM based ROM, it will fix the problem ?
Thx

elshur said:
Hello
I have a problem with the phone dialer and the rom based on CM ie CM10, AOKP or AOSP.
Let me explain: When a call is received, the display is on, normal, when the approach of the ear, the screen goes to sleep, ok on stock rom and stock based custom rom
However I could not get out of sleepping the screen on the CM based rom during a call :crying: even if i press home button or power button !
I always flash the included kernel, so i don't know where is my mistake. Am I alone with this failing ?
In advance, thanks for any help.
Regards
Click to expand...
Click to collapse
Hello friend!
It would be the same case?
http://forum.xda-developers.com/showthread.php?t=2070438
http://forum.xda-developers.com/showpost.php?p=31452830&postcount=1

JSS³ said:
Hello friend!
It would be the same case?
http://forum.xda-developers.com/showthread.php?t=2070438
http://forum.xda-developers.com/showpost.php?p=31452830&postcount=1
Click to expand...
Click to collapse
Actually I had not yet tried this kind of response because I was looking for confirmation that it was a problem with the proximity sensor.
Thank you for the suggestion, i'll take a look and keep you informed

[Q] AOSPA black screen issue on find 7 QHD

I just installed the 4.4.2 of AOSP which in theory supports find 7 QHD. There is a bug like in cyanogen mod (i just read that there is), that after unlocking the phone, the screen stays black after turned on. Everything operates in the background, as i hear the unlock and feel vibration if pressing a button.
Is there a solution for that?

I have same issue with CyanogenMod in all versions include M8
some discussion about this problem is here http://forum.xda-developers.com/find-7/find7-development/tutorial-how-to-install-cyanogenmod-t2801982 but I still can't find solution

All the CM11 based ROM has the black screen issue. Only Gummy ROM doesn't at the moment. I'm not discouraging anyone to use CM11, but for now, use Gummy ROM if you really don't want to use ColorOS and also don't want the black screen issue.

Same Issue on PA 4.4.2
hey guys im having the same black screen issue on PA ROM, where can i download that GUMMY ROM?

... it would help if someone could give me a last_kmesg and logcat

ayysir said:
... it would help if someone could give me a last_kmesg and logcat
Click to expand...
Click to collapse
Under the assumption it's not killing ADB, dmesg is what would be needed, not last_kmesg

Gummy rom does not have this issue.

Sebring5 said:
Gummy rom does not have this issue.
Click to expand...
Click to collapse
thats swell

Entropy512 said:
Under the assumption it's not killing ADB, dmesg is what would be needed, not last_kmesg
Click to expand...
Click to collapse
my mistake

dmesg: http://pastebin.com/XVEszqrJ
logcat: http://pastebin.com/SDH7FXQv
I think it has something to do with thermal throttle and screen dim.
This logs are from CM.

rroohh93 said:
hey guys im having the same black screen issue on PA ROM, where can i download that GUMMY ROM?
Click to expand...
Click to collapse
http://www.oppoforums.com/threads/rom-aosp-find7a-find7-team-gummy-rom.15593/

Problem Fixed!
mestermagyar said:
I just installed the 4.4.2 of AOSP which in theory supports find 7 QHD. There is a bug like in cyanogen mod (i just read that there is), that after unlocking the phone, the screen stays black after turned on. Everything operates in the background, as i hear the unlock and feel vibration if pressing a button.
Is there a solution for that?
Click to expand...
Click to collapse
So CM pushed some fixes to address this black screen issue, a friend of mine already compiled them into a kernel, this kernel is compatible with any CM based ROM like PA or Cyanogen.
Just flash it and goodbye to black screen issue.
http: // aospal.hostingsharedbox. com/ayysir/find7/ kernel/ParanoidAndroid-find7-kernel-signed. zip

[ROM] [24/12/15] [Unofficial] CM 10 for HTC Desire 300 [Public Beta]

Unofficial CM 10 for HTC Desire 300 (g3u)
device_htc_g3u v0.8b (24/12/15)
Traded stagefright bug for a new kernel
(no more stagefright and a freshly compiled kernel)
device_htc_g3u v0.77b3 (04/10/14)
Battery comsumption (hot)fix
(rls should no longer drain your device)
device_htc_g3u v0.77b2 (01/10/14)
Wifi is working
(wifi0 is forced into compliance)
device_htc_g3u v0.77b (25/9/14)
jellybean
(nom nom nom)
Full Disclosure
This is my first android project, so go easy on me.
Project Status
It's usable as a phone
So any willing beta testers are welcome to join the 'fun' and report further bugs.
Project !Status
mobiledata works but will drain your battery
(if you need to use it, reboot after switching it off)
libaudio is not fully functional
(stock has no mic unless in a call and custom has no speaker)
USB only works in mtp mode
(mass_storage mode appears to be incompatible with rmt_storage)
FM Radio not available
(required apps are currently not compiling)
Camera (front) appears unstable
(didn't bother to check what might be the cause)
TODO
[high priority]
fix libaudio (recording in stock or speaker in custom)
[medium priority]
fix libril -> mobile data drains the battery
[low priority]
enable apps2sd -> 2GB internal should suffice for the time being
check if cm supports proximity & light sensors -> they do work fine
fix mass_storage -> mtp is working
fix video recording -> it's a phone not a camcorder
fix video playback -> at least they are running
fix camera -> it's a phone dammit
find a better fix for wifi -> it works for now
fix graphical glitches
Disclaimer
Use at you own risk. This is a public beta and not meant for daily use. Please keep that in mind.
I can not be held accountable for any damage you might cause to your device if you decide to flash this file.
Requirements
HTC Desire 300 with unlocked Bootloader and custom recovery
(S-ON or S-OFF does not matter)
Download
Click me if you want the initial wifi free version (9d0a8fcca957d09dbaf306a1986d14dd)
Click me if you want to drain your battery (688c2779b4864ed9b568260477708049)
Click me if you like the stock kernel (1ba8a225bc7772f34f1e56bff51bfe27)
Click me if you dare (78bbcf5bf0eb26520efff6d49adac106)
Warning!!! If you are not a certified beta tester the zip file might explode upon extraction!!! You have been warned!
Installation
Enter recovery and begin by backing up your current system.
Next choose Wipe Data / Factory Reset from the main menu and Wipe Dalvic from the advanced submenu.
Last but not least use the mount submenu to format system.
Now use sideload or zip install to start beta testing this tasty jellybean.
Special Thanks
go out to anyone who has ever contributed something to a msm8225, ath6kl or htc related android project
device_htc_g3u
kernel_htc_g3u
Branch: Android 4.1.2
Version: 3.4.0-g12f638f
Config: g3u_defconfig
Toolchain: arm-eabi-4.6
Click to expand...
Click to collapse
compiled by 4m8
(My mind is a swirling miasma of scintillating thoughts and turgid ideas.)​

What are the requirements ? I guess I should use the only recovery available for the device ? and also, since we don't have s-off working for this device I think we have to flash the boot.img right ?

I'd recommend using the recovery from this build for the job. It won't crash unlike the philz version.
And no, you don't need to flash boot seperately. The only requirement is an unlocked bootloader.
S-ON only protects hboot and radio from flashing so you can safely install this release from the recovery.
Don't forget to backup your current system.

I'm downloading the files now, will test and report ASAP

Can i promote this in 2 german Forums? ist German translation available?
when do you think you will fix wifi?
HUGE THANKS IN FORWARD FOR COMPILING CM!

After the experiment:
the Rom stable and fast, but Wi-Fi does not work and do not contain FM radio
Front camera not working
I wish you success in your work and I hope you update the version of Android to be higher than 4.1.2
Thank you very much ..

4m8 said:
I'd recommend using the recovery from this build for the job. It won't crash unlike the philz version.
And no, you don't need to flash boot seperately. The only requirement is an unlocked bootloader.
S-ON only protects hboot and radio from flashing so you can safely install this release from the recovery.
Don't forget to backup your current system.
Click to expand...
Click to collapse
In which way will PhilZ CWM crash? will it still install the rom or not? will it brick my phone?

bassam_tayyan said:
After the experiment:
the Rom stable and fast, but Wi-Fi does not work and do not contain FM radio
Front camera not working
I wish you success in your work and I hope you update the version of Android to be higher than 4.1.2
Thank you very much ..
Click to expand...
Click to collapse
Ah yes FM. It's included in the custom libaudio that can't connect to the speaker.
Which I currently simply replace with the stock lib to make it work as a phone so it can be used to test battery consuption etc.
Sadly the cm apps used for fm won't compile for me. So even if I get libaudio working FM would still be untestable without non cm apps.
I'll add it to the todo once the libaudio trouble is resolved.
The wifi is an annoying issue. I manged to get it to load the drivers so the p2p0 socket gets created.
But it tries to restart it as STA which if my google fu is correct it shouldn't do, since this firmware does not need restarting.
The front camera is a curious bug. It works absoluetly fine for me until I point it towards my face.
So it's either a problem with the proximity sensor or the nasty htc camera tries some facial recognition crap and dies.
If I ever decide to logcat the camera I can tell you more.
Now for a higher version, don't get your hopes up. At least not from my side.
First I'll try my best to fix this up. Then I'll wait for htc to release the kernel so I can get a closer look at the configuration
for this device and maybe adjust it to make this rom even better. Then again the last kernel I compiled was 10 years ago for a gentoo install.

LukeHorizon said:
In which way will PhilZ CWM crash? will it still install the rom or not? will it brick my phone?
Click to expand...
Click to collapse
If you are quick it will install fine. So if you prefer to live dangereously, don't let me stop you
I don't know if it is only an error that is presented on my device. Or maybe it was updated since then.
But for me philz recovery by SPSPawn does boot into a dead state. If you reboot it will crash until a panic reset is triggered.
Actually it is allready crashed while you are in recovery. Therefore you are on a timer until the device resets or you decide to
take out the battery.
I had the same problem on my build and it was caused by cwm always ignoring the ueventd.rc I had prepared because I didn't know
I had to copy it to root and not to recovery.
I've never bothered to figure out which missing element of this script was responsible because I had to substitute it in any case.
But honestly, tell me. Why do you prefer philz? I'm allready (so far unsuccessfully) trying to port twrp. If you have a few good arguments
I might be willing to try compiling a fixed version of philz aswell.

Well i didnt want to use a pc right now ... A TWRP port would be amazing
Is mobile data working?
Can you make your recovery flashable via cwm?

LukeHorizon said:
Well i didnt want to use a pc right now ... A TWRP port would be amazing
Is mobile data working?
Can you make your recovery flashable via cwm?
Click to expand...
Click to collapse
It always tried to download the google language pack for my region until I aborted it. So, yes mobile data should be available.
You mean put the recovery into an update zip thingy, right. Well I could, but you will have used a pc before I'll find the time to upload it.
I'll keep it in consideration for the next update.

Well, atleast internet
When do you think you'll fix wifi?

Regarding to wifi, it will be fixed once it's fixed. Or if you prefer the usual response: When it's done.
This will happen either after or before libaudio is fixed. And that's about as specific as I can get.

Well, it was worth a try still thanks for your effort!

Okay, here goes.
First I tried installing the ROM with the PhilZ recovery because I already had it on my phone, didn't work. Gave me some kind of error (not sure about the error code anymore). Flashed your recovery, worked flawlessly. Now for the ROM.
It's pretty stable, I've had only one strange crash and that was in the first 2 minutes of using it so I don't even know if it counts. The additional CM settings panel works fine, quick toggles are ok, I haven't tried overclocking yet - I'll leave that to someone else. But I have found some bugs:
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
-signal indicator seems to be stuck at 2 out of 4 bars and doesn't move
Overall very nice, keep up the good work!

luxb said:
Okay, here goes.
First I tried installing the ROM with the PhilZ recovery because I already had it on my phone, didn't work. Gave me some kind of error (not sure about the error code anymore). Flashed your recovery, worked flawlessly. Now for the ROM.
It's pretty stable, I've had only one strange crash and that was in the first 2 minutes of using it so I don't even know if it counts. The additional CM settings panel works fine, quick toggles are ok, I haven't tried overclocking yet - I'll leave that to someone else. But I have found some bugs:
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
Overall very nice, keep up the good work!
Click to expand...
Click to collapse
I guess wifi isnt working for you right?

It's not working, but I didn't put it on the list since he already knows it's bugged.

Well, i'll try today
Lets see what happens

Anyway, forgot to unpack the file ... GApps come with it?
SOOO, booting went fine, working like a charm... quicksettings page not available, quicksettings bar is working properly
Mobile Data works flawless, and i guess the rest is just fine
German language worked instantly
it feels way faster then Sense, a HUGE Thanks for you, makes me actually like that phone again ...
I'd like to promote it in German forums if i WiFi is fixed in near future
regards!

LukeHorizon said:
[...]
GApps come with it?
[...]
German language worked instantly
it feels way faster then Sense, a HUGE Thanks for you, makes me actually like that phone again ...
[...]
Click to expand...
Click to collapse
No, you have to get gapps on your own. Since there are multiple options you can choose for yourself. But if you did not format system,
as I've mentioned in the install instructions, chances are high that google apps did get picked up by the install script.
I am not sure if it can take them from the stock rom but it can and will take them from a cm rom and keep them on reinstall.
(I am really not very pleased by this behavior!)
I also should have mentioned that the primary language is decided by the simcard. (Which is annoying since I prefer english in any case)
Randnotiz:
Es freut mich das ich Dir den Spass am Gerät zurückgeben konnte.
Natürlich darfst Du es in deutschen Foren weiterverbreiten sobald die gröbsten Fehler behoben sind.
Einzige Vorraussetzung ist, daß Du es nicht als Deine Arbeit ausgibst.
luxb said:
[...]
-proximity sensor not working (screen doesn't go black when you place it up to your ear)
-ambient light sensor not working (auto brightness doesn't work)
-video recording doesn't work
-the camera app glitched up the first time I tried to zoom (was fine afterwards)
-sometimes when going from portrait to landscape I got 1 second of weird graphical glitches
-signal indicator seems to be stuck at 2 out of 4 bars and doesn't move
[...]
Click to expand...
Click to collapse
Wow. That's much more broken than I expected it to be. Kudos.
Regarding the sensors. I currently am using the stock lib. And logcat let's me assume that they are working as they should.
(i.e they don't crash or drift into madness afaik)
Maybe the stock lib doesn't play well with cm, or you are expecting features from cm that are not implemented.
I will definetly try to compile a working sensor lib in the future, so I guess we'll see....
Camera is also just the stock lib for now. So it's no surprise that somethings might be acting up.
I need a lot of research into that subject before I can specify the requirements for the camera in my boardconfig.
The graphical glitches are rather minor and can be ignored for now. I am aware they exist.
But for now I'd rather focus on the more prominent broken features.
Like wireless for those of us that can't or won't use mobile data. (I belong to the 2nd group)
I noticed the signal indicator aswell. but that should be a problem of the radio compatibility.
We can't flash radio and I'm using the stock libril as the radio interface which should give maximum compatibility in theory.
Of course it doesn't irl... typical -_- (I hate you, Murphy!)
Sidenote:
Why did you remove your avatar? I really wanted to make some "stop trying to kill spoderman" remark...
@all:
Does anyone have any clue how to use the mock locations for gps? They are enabled, but so far I couldn't find any way to set them to a specific location.

[Q&A] [KERNEL][F2FS/EXT4][GEE/STOCK] jolla-kernel v11.1 20141007 (Stock Based ROM Su

[Q&A] [KERNEL][F2FS/EXT4][GEE/STOCK] jolla-kernel v11.1 20141007 (Stock Based ROM Su
Q&A for [KERNEL][F2FS/EXT4][GEE/STOCK] jolla-kernel v11.1 20141007 (Stock Based ROM Support!)
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 [KERNEL][F2FS/EXT4][GEE/STOCK] jolla-kernel v11.1 20141007 (Stock Based ROM Support!). 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!

Jolla Kernel 12 GEEB L
WiFi is not working on GEEB (Android L)

The donwload links do not work
Where can i donwload it?

Rebound_ said:
WiFi is not working on GEEB (Android L)
Click to expand...
Click to collapse
L kernel is test only now. I'll make it later soon...
Sent from my LG-F180L using XDA Free mobile app

A little problem
Hey, i just flashed the kernel on my e975 with liquid rom. the installation runs smooth and everything seems to be alright but whenever i lock the phone (with the button on the side of the phone) it won't get up anymore. Everything is running but the screen remains black and there is no way to turn it on. I tried to flash the kernel various times and also tried to disable the Slide2Wake or Tap2Wake(or something like this) features but with no result. can anyone help me out with this? this also happens on the other rom i have tried (Gee3). thanks in advance!

Thank you for the fantastic kernel, it is nice to have smartmax back on my OG again!
One thing is puzzling me. My GPU seems to be stuck on max all of the time when on simple and ondemand governors. I've tried altering the simple parameters in trickstermod but this doesn't seem to help.
Sent from my LG Optimus G using Tapatalk

DoubleTap2sleep
Hello,
How can i change double tap to sleep or screen off?

v0xE kernel still getting ghost touch on lockscreen.
Im using Optimus G (e977) original stock rom.

how to uninstall Jolla Kernel
I have any questions:
1) I don't will uninstall Jolla Kernel now, but I need know how can I back to stock kernel?
2) How can I change DoubleTap2Wake's options?
3) How can I change CPU Governer?
Sorry for newbie questions...

can i use this kernel on fiui rom beta 2.3.0 ?

hi, can i use this kernel on fiui beta 2.3.0 rom ?

Nobility350 said:
I have any questions:
1) I don't will uninstall Jolla Kernel now, but I need know how can I back to stock kernel?
Click to expand...
Click to collapse
Just reflash your ROM, no need to wipe data or anything.
Nobility350 said:
2 ) How can I change DoubleTap2Wake's options?
3) How can I change CPU Governer?
Click to expand...
Click to collapse
Use trickster mod from Play Store to do both.
Nobility350 said:
Sorry for newbie questions...
Click to expand...
Click to collapse
No problem, that's what the Q&A threads are for!
Sent from my LG Optimus G using Tapatalk

Throttling
How can I disable throttling? I can't play WOT on 20fps. Disabling it in trickster doesn't help

Problem with Artmod 5.5
Hi, i have a problem with this kernel which I also encountered with other ROMS. I am operating on ARTMOD 5.5 and the installation of this kernel goes smooth and everything seems to work properly. But as soon as I lock the screen, or it lock automatically after some seconds I just cannot unlock it. It stays off but everything works in the background, the notification led works, I can receive notification but the screen won't turn on.
Anybody had this problem? Is there a solution? I flashed it through philz touch 6.23.
Thanks in advance!

karolekpro said:
Hi, i have a problem with this kernel which I also encountered with other ROMS. I am operating on ARTMOD 5.5 and the installation of this kernel goes smooth and everything seems to work properly. But as soon as I lock the screen, or it lock automatically after some seconds I just cannot unlock it. It stays off but everything works in the background, the notification led works, I can receive notification but the screen won't turn on.
Anybody had this problem? Is there a solution? I flashed it through philz touch 6.23.
Thanks in advance!
Click to expand...
Click to collapse
This can happen when the clock speed is too low when the screen is off. Try increasing the minimum clock speed a level and see if it helps.
Sent from my LG Optimus G using Tapatalk

Leavard said:
This can happen when the clock speed is too low when the screen is off. Try increasing the minimum clock speed a level and see if it helps.
Sent from my LG Optimus G using Tapatalk
Click to expand...
Click to collapse
Hi,
Just checked if this could be the problem but the minimum clock speed seems to be ok, 384 Mhz. I tried to set it up to 810 but the problem still persist. I don't have this kind of problem with other kernels. Wondering what could be the reason. Anyway thank you for your answer

NO rear camera...
Hello, I installed it as said,
I use artmod the latest 5.5 and installed Jolla 3.4.105 and...
There is no rear camera or way to activate flash.
If I open camera app and click change camera button, it changes settings and everything but still shows me picture from front camera.
Tried reinstall with dalvik and chache(sorry don't know how to write it) wipe, but still no rear camera or flash.
One more thing to point out Play Services and Facebook Messenger are FC-ing all the time.
Hope for response.

fixed
kevinrumm said:
Hello, I installed it as said,
I use artmod the latest 5.5 and installed Jolla 3.4.105 and...
There is no rear camera or way to activate flash.
If I open camera app and click change camera button, it changes settings and everything but still shows me picture from front camera.
Tried reinstall with dalvik and chache(sorry don't know how to write it) wipe, but still no rear camera or flash.
One more thing to point out Play Services and Facebook Messenger are FC-ing all the time.
Hope for response.
Click to expand...
Click to collapse
I managed to find out what's wrong by myself.
I accidentaly dowbloaded e970 ver, but in installsion screen i chose the other e975 . i tought it was allright.
But downloading the right e975 ver fixed the problem for me, now using GEE3 and jolla.
Sometimes i get some random wakeups when screen is off...

I'm on cm12-0117build. Everything turns to be good,but It shutdown once I set the CPU clock to 1890MHz. It seems a kernel issue occur. My cpu PVS is faster, so I think it won't be a problem of hardware. How can I do it? Any suggestions?

It does have a good performance. [email protected]

[Q&A] [ROM] [n7100] Dirty Unicorns v8.1 [Unofficial]

Q&A for [ROM] [n7100] Dirty Unicorns v8.1 [Unofficial]
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] [n7100] Dirty Unicorns v8.1 [Unofficial]. 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!

I’m trying also this rom. That appear really interesting.
1)Not so important ,I found that the clock don’t show the AM-PM symbols (nor after reboot and cache cleaned)
2)Maybe a little more important . The contacts.apk or the app designed to do that , cant import contacts from extSDcard. The pop-up search just in internal SD.
I tried to use the cyanogenmodX contacts.apk where this work but of curse contacts stop working at all.

About the clock...there is an option to do it, works fine here.
The contacs app dont have the feature you ask for...so you have to put your contacts backup in the internal sd for a bit....and then copy again to the external, its not that hard.
Im no longer working in dirty unicorn cuz the real devs are working on Lollipop and wont release any updates for kitkat...

Cocolopes said:
About the clock...there is an option to do it, works fine here.
The contacs app dont have the feature you ask for...so you have to put your contacts backup in the internal sd for a bit....and then copy again to the external, its not that hard.
Im no longer working in dirty unicorn cuz the real devs are working on Lollipop and wont release any updates for kitkat...
Click to expand...
Click to collapse
Tnx ,
I have done exactly like you have said for the contacts in first instance.
The option for PM-AM was selected but nothing happen (rebooted and cleaned cache). Strange, i have flashed the rom 2 times after full wipe. Is not a real problem...was just for report it.
Thanks for the support.

giostark said:
Tnx ,
I have done exactly like you have said for the contacts in first instance.
The option for PM-AM was selected but nothing happen (rebooted and cleaned cache). Strange, i have flashed the rom 2 times after full wipe. Is not a real problem...was just for report it.
Thanks for the support.
Click to expand...
Click to collapse
Mmmmmm did you use xposed framework and modules? maybe thats the problem..

Cocolopes said:
Mmmmmm did you use xposed framework and modules? maybe thats the problem..
Click to expand...
Click to collapse
Nope, clean rom. Nothing is installed over total-commander for menage the files as i like.
I learned that before i must test the rom for what it is and then put over it all the apps that i need and check all work fine before add more apps. In the past i have done the mistake to put a mess of apps that makes me crazy for found the reason of the FCs.
So , there is just the rom.
Or i select "small character", or i select "normal character" nothing change close to the clock. Also after reboot and cleaned cache.
I try just for to be sure the 3rd flash and was the same.
Have you maybe some suggestion on how to change the clock style? I mean in 24h format. also AM Pm is good but didnt work.
Is not so relevant but im trying to refine the installation for found a more definitive rom for daily use.

changing icon size feature?
thank you so much for this awesome rom.
I hv been using MoKee & nw permanently shifted to DU...
anyways.... i ws looking for changing the size of icons.cuz i m using 'L' theme whose icons r too big.
MoKee had option "USE SMALL ICONS"... do we hv something like that in DU?

kernel installation
(sorry for my english)
Hi, i just installed this Rom , have i to install a Kernel zip from recovery or it's not necessary?
Thanks!

dido78it said:
(sorry for my english)
Hi, i just installed this Rom , have i to install a Kernel zip from recovery or it's not necessary?
Thanks!
Click to expand...
Click to collapse
thats is up tu you....I dont use any custom kernel...the only thing you need it rom zip and gapps....if you want play store...nothing more

Galaxy Note 2 Proximity Sensor Showing Dim Red Light
Those are not questions. Like before, just an advisory.
1) Settings>>>Dirty Tweaks >>> Lockscreen >>> Misc. Tweaks>>> lockscreen notifications>>> WAKE ON NOTIFICATION. This cause a dim red light remain active in proximity sensors during lockscreen.
This is absolutely reproducible and persistent. In clean rom and in modified rom.
This make me almost crazy. I thought was because the devil kernel. Someone speak about infrared , someone in stock rom about smart-stay and so on. But in this case the reason is totally different.
After have back-upped all the system i tried to put the clean rom just without and with devil kernel and nothing occur . So i supposed was a setting or apps matter. And I find it out.
2) Enabling the above WAKE ON NOTIFICATION make disabled also if selected the Setting>>> Display>>> "Notification light" . I had experienced that if you turn off and on , the notification light start work again. (with persisting of the ted light in lockscreen)

giostark said:
Those are not questions. Like before, just an advisory.
1) Settings>>>Dirty Tweaks >>> Lockscreen >>> Misc. Tweaks>>> lockscreen notifications>>> WAKE ON NOTIFICATION. This cause a dim red light remain active in proximity sensors during lockscreen.
This is absolutely reproducible and persistent. In clean rom and in modified rom.
This make me almost crazy. I thought was because the devil kernel. Someone speak about infrared , someone in stock rom about smart-stay and so on. But in this case the reason is totally different.
After have back-upped all the system i tried to put the clean rom just without and with devil kernel and nothing occur . So i supposed was a setting or apps matter. And I find it out.
2) Enabling the above WAKE ON NOTIFICATION make disabled also if selected the Setting>>> Display>>> "Notification light" . I had experienced that if you turn off and on , the notification light start work again. (with persisting of the ted light in lockscreen)
Click to expand...
Click to collapse
thats normal...any rom or app that use the proximity sensors to wake the device turn on the red ligth.

Cocolopes said:
thats normal...any rom or app that use the proximity sensors to wake the device turn on the red ligth.
Click to expand...
Click to collapse
Yep, i suppose that. But in that case the sensor is not active. If I pass the finger on it nothing happen.
Is not , in this case, the wake-up of the phone related just to the incoming notification? Always In this case what is need for the proximity sensor?
If I miss some basic knowledge , sorry.

Ok, im using this rom from lots of time. I re-flash it many and many time. (after proper wipe of all the necessary). I can reproduce that the led for notification missed call didnt work properly. It reproduce every time on missed call a very fast double blink of the led (white as default) and hide definitively the light of the notification. The sms notification work fine.
I tried also the only one kernel that work with this version of rom. The Devil kernel. And this occur again (i tried to change some light parameter).
Damn more or less work all fine but not this simple feature.

giostark said:
Ok, im using this rom from lots of time. I re-flash it many and many time. (after proper wipe of all the necessary). I can reproduce that the led for notification missed call didnt work properly. It reproduce every time on missed call a very fast double blink of the led (white as default) and hide definitively the light of the notification. The sms notification work fine.
I tried also the only one kernel that work with this version of rom. The Devil kernel. And this occur again (i tried to change some light parameter).
Damn more or less work all fine but not this simple feature.
Click to expand...
Click to collapse
Someone experienced something similar in CM11:
http://forum.xda-developers.com/showpost.php?p=57344858&postcount=393
Should be interesting to know the code's procedure that make this occur.

giostark said:
Someone experienced something similar in CM11:
http://forum.xda-developers.com/showpost.php?p=57344858&postcount=393
Should be interesting to know the code's procedure that make this occur.
Click to expand...
Click to collapse
Ok , I tried the CM11 , last nightly and i can confirm this .

Sorry people...I have a lot in my life...so I cant make new builds for this rom...there is a new v8.2 but I cant work on that (dont have the time) and I cant make a L version of DU for the same reason. But this is AOSP so if anyone want to do it...go on!
Cheers

This ROM sounds promising, however every other AOSP ROM gives error with Bluetooth phone calls. Can anybody confirm this works okay in this ROM please?

Gapps
Gapps link has a problem.

Couldn't get it to work properly
Tried everything to get it to work, kept on giving me two errors -Process com.android.systemui has stopped and - Unfortunately, Android keyboard (AOSP) has stopped on Android. Tried the 4 different gapps, cleared the cache and dalvik, did factory reset, nothing got me past the error messages.