Database Users

Galaxy S 5 touch screen not responding

Hi
I installed the last XAD Carbon Rom 4.4.4 [29.06.14] on a brand new Samsung Galaxy S 5 SM-G900F (French model). I installed XBMC 13.2 Gotham – beta 1 too. Unfortunately the apk is unusable because S 5 touch screen isn't responsive at all, like if it was frozen. I only can increase or decrease the volume.
Thx for your help.
Olivier

ikvat said:
Hi
I installed the last XAD Carbon Rom 4.4.4 [29.06.14] on a brand new Samsung Galaxy S 5 SM-G900F (French model). I installed XBMC 13.2 Gotham – beta 1 too. Unfortunately the apk is unusable because S 5 touch screen isn't responsive at all, like if it was frozen. I only can increase or decrease the volume
Click to expand...
Click to collapse
No idea, I don't use either package. Surely you'd find better support in the ROM support thread though?
Did you wipe the cache partition?
Did you wipe the data partition prior to installing the ROM?
Did you install Gaps?
Did you see if the problem occurs before you install XBMC?
Did you search the Carbon support thread to see if anyone else has similar issues?
.

fffft said:
No idea, I don't use either package. Surely you'd find better support in the ROM support thread though?
Did you wipe the cache partition?
Did you wipe the data partition prior to installing the ROM?
Did you install Gaps?
Did you see if the problem occurs before you install XBMC?
Did you search the Carbon support thread to see if anyone else has similar issues?
.
Click to expand...
Click to collapse
Hello fffft and thx for your help.
As a nob, i can't post on the appropriate forum yet, but yes, i wiped all i was able to wipe. I installed the appropriate gapps too. The problem is specific to xbmx and didn't occur before.
Edit : I reinstalled a Samsung stock rom and xbmc works like a charm. The problem is inherent to that carbon rom.

[Q&A] [ROM][4.4.4][KTU84P] SlimKat - Mako -[Build 8][+ Weeklies]

Q&A for [ROM][4.4.4][KTU84P] SlimKat - Mako -[Build 8][+ Weeklies]
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

SlimKat. Incoming call LED light color.
Im having trouble changing notification light for incoming call (not missed, but the light while phone actually ringing). LightManager and built-in settings do a good job for all lights except this one. It stays white-ish.. I assume some code in systemui needs to be changed? Please, help.

Could someone recommend color settings for faux123's color temperature correction app ? I'd like to find just a genetic setting to help fix the washed out appearance the colors have by default?

I set PIN to unlock screen, but when i lock the screen only slider works, never appear the keypad for insert PIN.
Anyone have PIN to unlock working in weekly 8.9?

@bart.found
No problem here

I'm having troubles using miracast... I don't know why.. But I tryed to connect my mako with a samsung smart tv and with a lg smart tv... Same result! Connection starts, but after a second it disconnect...
Edit: could it be kernel related?

Nexus 4 with slimkat receiving OTA update?
Hello,
I have a Nexus 4 with slimkat 4.4.4 and I just received a notification to download lollipop by google.
Is it normal? If I do the download, what would happen?
Really hope you can help me because I though I wouldn't receive more OTA updates since my custom rom.
Thank you all!

Sekas said:
Hello,
I have a Nexus 4 with slimkat 4.4.4 and I just received a notification to download lollipop by google
Click to expand...
Click to collapse
+1
I was really surprised as well. If you check out which app brings it up, it turns out the entire OTA thingy is managed through Google Play Services app. Seems like updating may temporarily brick your device or return you to stock ROM.
But that also brings another question: when will Slimpop/SlimLP nightlies start to show up for our makos?

Is the current SlimLP based on 5.0.1 already?

(less than 10 posts so I reply here, original post: http://forum.xda-developers.com/showpost.php?p=57585383&postcount=8497 )
@brordavid "Anyone experience problem with Netflix on slimlp? It won't start at all, it just shows the Netflix logo and the loading ring for a while, and after a while it gives me an error that it cannot connect."
Yes, I have exactly the same. Error is: "Sorry, We Cannot Reach the Netflix Service (-9)". I tried all what Netflix help pages suggested (reboots, reinstalls) but no help.
Here is logcat from Netflix app startup to error -9: http://pastebin.com/MEnPasAa

I have a problem in incall ui in slimkat stable 9 (clean flash).. my contact pictures when I call (or being called) someone are bigger than they should be, anyone experiencing the same problem?

Slim-mako-5.1.1.alpha.0.3- and f2fs
Hello
please tell me the current status of f2fs on the Slim-mako-5.1.1.alpha.0.3-UNOFFICIAL-20150521-2151 release mentioned here
Do I need to follow the instructions as described here
and edit the actual ROM, or is f2fs support built in now?
I know that data and cache need to be formatted as f2fs, but is that enough, or do I need to modify the ROM itself
thanks
Daniel

Cant seem to get Franco 217 working. Just get boot loop when flashing it. Any suggestions?
Sent from my Nexus 4 using Tapatalk

Nexus 4 screen problem .

Hi ! if someone can help i have about 1 mm dead zone bottom but when i install chroma os based on 6.0 everything works , i wont to use stock 5.1 is it possible to move navbar with some kind app for that 1mm as in chroma os .
Thanks !

nebojsabarjaktarov said:
Hi ! if someone can help i have about 1 mm dead zone bottom but when i install chroma os based on 6.0 everything works , i wont to use stock 5.1 is it possible to move navbar with some kind app for that 1mm as in chroma os .
Thanks !
Click to expand...
Click to collapse
Your Digitizer is gone.
You can install "Handy Soft Keys" which will give you an alternate navigation panel which can solve your problem.
Else you can get the screen replaced, as its a hardware fault. Most Nexus 4 users have suffered it.

[6.0.1][K920][kingdom_row]CyanogenMod 13.0 for Lenovo Vibe Z2 Pro - Support and Help

Since the development thread is closed by OP request( sad but true ), and personally building a "port" of the ROM, i'm glad to help everybody as i can, with this thread.
It doesn't mean to be a development thread since i only build and implement some changes, but just to share comments, issues( like xposed one ) or just ideas to people who own this device ( CN or ROW ).
As a reminder you can find my builds here: LINK or just use OTA function in ROM.
And a big thanks to @frantisheq and @Electry for the works on CM13, and for the next, CM14.

reserved

Are someone try to flash Vibe Z2 (NON PRO) with this ROM?

don't do it, you will probably brick the phone.
K920/Z2 PRO only

Uploaded new build!
Should have Dec 5 patches, have a nice day

Try to install the latest build together with xposed. There is a boot loop with CM logo...... It seems to me there was such kind of problem......

That should be fixed by cm ? . Will apply the xposed fix in next build.
Thanks to inform me about this!
Tapatalk

updated build, with xposed patch, hoping now works fine

The latest build works fine for me. I installed it with xposed.

Hey @malaga82
I have a strange feeling that the new ROM is worse in performance compared to the previous build. It has way more stutters and sometimes the system UI resets and changes my wallpaper to the stock one. Anyone else facing such issues?

Saamyo said:
Hey @malaga82
I have a strange feeling that the new ROM is worse in performance compared to the previous build. It has way more stutters and sometimes the system UI resets and changes my wallpaper to the stock one. Anyone else facing such issues?
Click to expand...
Click to collapse
Could you please provide more details about this behavior and I try to reproduce it? Now I have not such kind of problem. But I can say that the UI sometimes has strange behavior. For example, the horizontal size of quick settings can be more widely than the size of the screen.

maybe it's something related to CM repo's and they will fix "soon".
give some days to see if they fix anything, i'll provide a new build.

In additional to my previous report I would like to add that the latest build cannot hold loading. At the previous build from 16 Nov I can run at the same time a navigation application and a video registration application. Now I cannot do the same because the device is rebooting due to overheating. I tried to figure out what is going on and found that the high limit of CPU0 temperature is set up to 85 C (it seems to me it is low....) and I cannot change it – try several tuning tools. And it is not only one reboot – there are several reboots….. After its a Bluetooth pairing was lost….. And I can repair a normal work only wipe cache & dalvik through TWRP and pair a Bluetooth once again…..

i'd like to have more feedback if possible.
i'm thinking to try to build with the "old" kernel that have cpu voltage control and other features i included times ago.
atm we are a bit stuck with development.

malaga82 said:
i'd like to have more feedback if possible.
i'm thinking to try to build with the "old" kernel that have cpu voltage control and other features i included times ago.
atm we are a bit stuck with development.
Click to expand...
Click to collapse
What information could I provide to you to help?

i just want to know if someone else have that overheating issue

Could you please prepare a build with "old" kernel? Who does not face the overheating problem can stay on the previous one

Solved games issue.
Hello!
Sorry for my English, I from Russia.
On roms later CM 13 2016.03.07 in file: build.prop, increase the value: dalvik.vm.heapsize= from 512m to 768m. This led to the errors in game Real racing 3 (insufficient free memory, missing textures, game crashes). With value 512m games work fine.
If install Adreno drivers from ROM CM 13 2016.03.07, game Gear.club also work fine. The difference can be noticed immediately after starting the game.
I also sent this message to frantisheq.
Happy new year!

Solved games issue.
Additional information to the previous post.
I was looking the file: default.prop, and the parameter ( dalvik.vm.dex2oat-xmx ) is set to =512m. System parameter ( dalvik.vm.heapsize=768m) overlap kernel parameter. Possible, if rebuild kernel with the value 768m, all be fine? I don't test this.

About Lineage OS and other things

Hey guys, this is my 1st post so if I'm doing anything that I'm not supposed to or posting in the wrong area, please say so.
Ok, so, I used to have Android phones back in the day, since 2.2-2.3, then 4.0-4.4 and still used custom roms to update my mom's Moto G 1st Gen, from 4.4 to 7, but I manly used iPhones ever since 2012 and the easy jailbreak life made me kind of lazy - all of the process of jailbreaking and installing tweaks was very easy.
Now I'm back into the Android world with a Moto G4+ and I've already unlocked the bootloader and installed a few of the available custom roms, but none of them were actually stable enough to use in a daily basis so I got back to the stock rom.
Now I'm downloading LineageOS (that's the rom I also used to upgrade my mom's phone) and I got a few questions about it (since I can't post them on the official thread):
- can I enable the notification LED?? I can't do that in the stock rom but it worked really fine in the cypherOS rom.
- is there any option to disable the soft keys and use the fingerprint sensor as these buttons?? I mean, some kind of gesture, like the VirtualHome tweak in iOS, when a touch equals to home, a double tap to multitask etc. Just saw that the G5 will have some gestures in the FP sensor that will replace the soft keys, so a port of this feature would also be good.
- is this rom already rooted or do I have to install something else??
- is xposed working?? I actually found one article about it in the G4 but it was for MM and then I didn't find anything about it in N.
Sorry for my dumb questions, I swear I was going to read all of the official thread but when I was in the 9th page I saw that there was 294 total pages and then I gave up. :crying:
[EDIT]
imgur . com/9t1zK4M
imgur . com/BvDf0Uh
OK so, answering my own questions (at least a few):
- the LED is enabled by default I'm in heaven;
- THERE IS a default option to use the FP sensor as home button AND another one as to place multitask screen to show up by double pressing the home button. With this two options I am able to use the FP sensor at it's full potential (in my humble opinion) BUT as you can see in the images I am able to hide the softkeys only in a few parts of the system, it still shows up when you pull down notification center and also when you open up the keyboard. It's very annoying. I guess this question is still up.
- I think it's rooted by default thank you very much.

To your xposed question: no, there's no xposed for nougat out yet

cm theme engine
How to get cm theme engine on lineage os
I just saw cm theme engine in a screenshot which is attached in a thread based on unofficial lineage os

kd0321 said:
How to get cm theme engine on lineage os
I just saw cm theme engine in a screenshot which is attached in a thread based on unofficial lineage os
Click to expand...
Click to collapse
It won't come back. If you mean a screenshot where you see "themes", then it is with substratum. Themes appears in settings after installing substratum. It has nothing to do with CMTE.

strongst said:
It won't come back. If you mean a screenshot where you see "themes", then it is with substratum. Themes appears in settings after installing substratum. It has nothing to do with CMTE.
Click to expand...
Click to collapse
Ohhh thanx
I too just found out that