yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Spriz:
Riciao!!... volevo chiederti una cosa:

l'ultimo aggiornamento ( la versione del 01/11 ) mi causa problemi, ho già avuto 3 riavii ( uno proprio ora ) e a volte ho un lag quando riattivo il cell dallo stand-by.

volevo provare a reinstallare tutto da zero, formattando anche la memoria interna.

io sono sicuro che con la versione del 17/08 l'app della messaggistica non soffriva dell'overlapping e volevo sapere se è l'app stessa dei messaggi

a dire alla casella di risposta dove mettersi oppure bisogna cambiare qualcosa nel framework ecc???

perchè altrimenti provavo a cambiare nell'ultima relese l'app dei messaggi con quella del 17/08 per vedere se lo fa ancora...

ps. per quanto riguarda lo smartwatch ho provato a cambiare app per la gestione ( essendo cinese non ha un app fatta "dedicata" dal costruttore, te ne consigliano una, ma nel market ne trovi altre che possono farlo funzionare lo stesso) e ho notato che usandone un'altra ho più "funzioni che funzionano", quindi a questo punto sia un fattore di compatibilità delle app con la CM.

comuqnue appena risetto il tel vedo di mandarti il log.

intanto grazie e ottimo lavoro!!

Hello !! ... I wanted to ask you something:

the latest update (version 1.11) causes me problems, I already had 3 reboots (one right now), and sometimes I have a lag when the cell reactivated from standby mode.

I wanted to try to reinstall everything from scratch, even by formatting the internal memory.

I am sure that with the version of 17/08 app messaging dell'overlapping not suffering and I wanted to know if it's the same app messages

to say the answer box where you have to get or change something in the framework etc ???

because otherwise I would try to change the last relese app messages with that of 17/08 to see if he does it again ...

ps. regarding the smartwatch I tried to change the app to manage (since China has not made an app "dedicated" by the manufacturer, do you recommend one, but in the market there are others that can make it work the same) and I noticed that usandone I have another "functions that work", so at this point is a factor of the compatibility of the app with the CM.

comuqnue just risetto the phone I see us send log.

Meanwhile, thanks and good job !!
[Galaxy S 4 i9505 Original Android Development] FPSUsername:
I use it as it brings some good modules such as:

Disableflagsecure (I can screenshot in any app now)

Lockscreen mods (I can quick open my fav apps)

Native Clipboard (Yes, it can be used without xposed, but it doesn't work correctly then, at least, didin't for me)

Screenshot delay remover (So good when you have you capture and action)

Statusbar scroll to top (didn't find a use for yet, but can be useful)

WiFi Password (I can see my saved networks passwords)

XInstaller (I can install any app, no issues with installing "same versions")

Youtube AdAway and Background playback (I could use OGYouTube, but it isn't updated rapidly and v1.0 (current release) has background playback issues)

This rom is amazing, but misses a lot of cool features that roms like RR and AICP have (like statusbar task manager, boot animation changer app in settings). I can not let go of this rom because I have the idea that alucard's kernel is good, apart from the sound issues.
[Galaxy S 4 i9505 Original Android Development] MScantamburlo:
As you type with the keyboard AOSP not be written by sign, I tried deleting the data and cache, any solution?

Durante la digitazione con la tastiera AOSP non va la scrittura tramite segno, ho già provato cancellando i dati e cache, qualche soluzione?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] mattross:
Touschscreen crash

This may be the same crash others have mentioned on this thread. I am running the November 1 ROM, all partitions are F2FS, I do not have Xposed installed, and I use Nova Launcher.

About once a day my screen goes black, except for the statusbar. I can drag down the bar and see my notifications but touching anything brings back the black screen. Usually I just reboot at this point, but today I plugged into my PC and started fiddling with adb.

Firstly the phone thought it was locked (and it wasn't before it crashed). I was able to use adb to send my PIN unlock code followed by the enter key. That worked and the black screen disappeared so I could see my phone's desktop. However the touchscreen at this stage is not responding to my touch. The two soft buttons work, and I can still send keypresses via adb.

Is there a way I can try to restart the touchscreen driver without rebooting? On the plus side I have been able to run 'logcat -d -f /storage/sdcard0/logcat.log' if this is any use to the devs.
[Galaxy S 4 i9505 Original Android Development] LimitsX:
I will do that :) . I tried another CM 12.1 based rom, rev 24 and no wifi disconnects. However, i experienced the black screen freeze for several minutes and then after that phone became responsive. That issue isn't resolved in that rom.
[Galaxy S 4 i9505 Original Android Development] -Deco-:
Personally, i use Xposed for the little "hickup" fixes that it can achieve. Things like the screen going into sleep mode during a call, due to the proximity sensor. I would never use anything that is a resource-hog, things like GravityBox are a no-no for me, although, even with a few modules active it seems to raise the CPU main core temperature by quite a bit, (can be seen by chrome-related browsers flashing in the red box on high CPU activity). Due to this, I have disabled Xposed for now.
[Galaxy S 4 i9505 Original Android Development] dorian2kx:
+1
[Galaxy S 4 i9505 Original Android Development] Indha Lezzio:
Just flashed the last build after being stuck in Dan's GPE for 3 months. I do not use BT in my day per day, I still have not listened to music (neither installed Viper), and I still have to check the camera because i remember two issues: a, camera not connecting and having to reboot and b, heavy battery drain if i closed camera with home button and not back button.

But after 24h of use i'm impressed of smoothness and the battery behaviour in sleep time. A huge growth of the ROM in this 3 months. Congratulations to all the team, the ROM looks like very serious and hard-worked.

Just 2 conclusions:

- really looking forward MM AOSP from the team. I'm so impressed of the behaviour of my Nexus 7 (2012) with MM in terms of battery life and smoothness that makes me feel that LP was not finished. (MM for grouper is not official from Google and does not work at 100%: autorotation, sound and GPS issues, and some people are fighting to bring 3.4 kernel to grouper). It's really the same feeling i had while updating to Win 7 after the disaster of the previous Win. (I do not really want to mention the name, i was so angry because of lack of drivers and more things...).

To sum up: Our phone will FLY when having MM.

- 5.1 GPE deserves a GOOD kernel

[OT]

I love bilingual posts. A funny way to learn words and sentences in other languages.

Me encantan los posts bilingües. Una forma divertida para aprender palabras y frases en otras lenguas.

[/OT]

Cheers!!!!
[Galaxy S 4 i9505 Original Android Development] FernBch:
The reason why the developers will not give support when you use it is because it alters how some parts of the system works. When that happens it can make ROM support a nightmare.

Beyond that, some like it and some don't. If you like it and want to use it you can. Just remember, if you experience issues the best way to receive support would be to uninstall it and see if you still have or can recreate the issue. If you can also capture logs and post a description and a link to the logs here.

Antaresone posted a couple pages back a detailed request on how to report this issue including which app to use to collect logs. Doing that is the best way to help us help you.

---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------

See this post for details:

http://xdaforums.com/showthread.php?p=63625597
[Galaxy S 4 i9505 Original Android Development] mattross:
I've already posted a proper SysLog to AntaresOne for a USB DAC problem so I know how to do it. The problem is that without a touch screen to interact with it's difficult to simulate all the screen touches required to make the SysLog app do its thing. As I had adb shell access, running logcat was the only sensible option. I've had to reboot the phone now anyway as I needed to use it. If someone can tell me how to start SysLog from an adb shell I'll try it the next time it fails.
[Galaxy S 4 i9505 Original Android Development] paolo2331:
Are the first 2 kernels in the picture compatible with this ROM?

If yes which one is better?

Thanks
[Galaxy S 4 i9505 Original Android Development] franzyroy:
One of the ROM!:cool:
[Galaxy S 4 i9505 Original Android Development] Chibbo:
oh franzy u alive, I thought u died ;)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
No not yet!:laugh:
[Galaxy S 4 i9505 Original Android Development] paolo2331:
V1.3b is the one shipped with the ROM? Because I looked in phone info and the name is different.
[Galaxy S 4 i9505 Original Android Development] mafsi:
I asked a few pages ago the same question. Is not, that thread is no longer updated.

<sent with a mockingbird>
[Galaxy S 4 i9505 Original Android Development] FernBch:
My apologies. This may be useful to you:

While Touchscreen working, enable ADB. When issue reappears, adb logcat > logcat.txt (for a few min), and adb shell dmesg > dmesg.txt (takes almost no time) and upload those 2 files please

About Kernels.

If you must there are probably "other" kernels that would work with this ROM and you can try one BUT remember:

While it may fix one issue it could create others.

If it is an older version from alucard or from this ROM it could also do the same as above.

It could cause you to lose features the current one provides.

You will lose support of the developers. You have flashed a different kernel and altered system files. If you do post logs of an error they will reveal that difference, too.
[Galaxy S 4 i9505 Original Android Development] Striker2k:
cant boot recovery anymore

Hi,

first thx a lot for this great rom.

I flashed the latest build of Nov 1st and after that I couldn't boot TWRP recovery 2.8.6.0 f2fs.

Flashed TWRP 2.8.7.1 f2fs odin version with Odin which fixed it.

I just want to understand, why the old version didn't worked anymore.

Maybe someone can answer this.

Regards
[Galaxy S 4 i9505 Original Android Development] bunu:
Is tethering working for anyone else? I tried wireless tethering and my laptop refused to connect. I then tried wired tethering and same issue. It was working flawlessly on the August build. I'm running the Oct 22 build. I did a clean wipe and installed. BTW, I barely got bluetooth crashes since the August build. I might get a crash once in a blue moon but I just clear data and reboot and it works great after that.
[Galaxy S 4 i9505 Original Android Development] paolo2331:
My bluetooth and WiFi tethering are working fine. I am on 1 November build
[Galaxy S 4 i9505 Original Android Development] CE42:
I have used Xposed on 3 different phones, 6 or so different ROMs, and never had any issues. However, I don't like being reliant on it - lack of Xposed stopped me upgrading to Lollipop for a long while and I'm always worried that the next upgrade, when combined with Xposed, will stop my phone from doing something important.

There are only three features I really make use of:

- removal of the "#" sign in the status bar to indicate root access

- the 'transparrent' lock screen mod to view my to-do list widgets without unlocking my phone

- the ability to increase the number of increments in the volume slider from the default 15 to 30

The first two are nice to have and I really could live without them (there are alternative solutions out there), but the last is a showstopper for me. Android phones make useless MP3 players with only 15 steps in the volume slider - tracks are often too quiet on one setting and too loud on the next. If I could find another way I would give up Xposed in a heartbeat.
[Galaxy S 4 i9505 Original Android Development] pankeca:
When I lock my device the menu and back button vibrate when I touch it, can I disable it?

Enviado do meu GT-I9505 através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] pandorra:
something similar happened to me:

after the update the phone was booting into the installed TWRP 2.8.7.0 multirom at every start, but TWRP was stuck in a bootloop (waited up to ~8min). had to flash twrp-2.8.6.0-jfltexx then to start up the phone. after the update google play services FCs all the time and several apps are just gone, like never been installed and supersu was missing, too . reflashed the latest tk-apps and supersu and rebooted... one last gapps FC and now it seems to be ok. hopefully.

oh, btw: though ive flashed the 1101 build via OTA without errors during the update it yet wants to update the very same update via OTA again. the app itself show the correct version, 1101. strange stuff.
[Galaxy S 4 i9505 Original Android Development] RowanDDR:
Check your cable. To get USB tethering to work I sometimes have to pull the cable out by about 1mm. Official Samsung cable...

Edit: oh, wireless tether? Will try tonight.
[Galaxy S 4 i9505 Original Android Development] -Deco-:
Anyone else had issues with the recent OTA update? The phone seems to freeze up during boot if a USB is attached for charging or for MTP file transfer

Issue was fixed, due to a bootloop caused by TWRP v2.8.7.0.
[Galaxy S 4 i9505 Original Android Development] stegalli:
Can someone upload the best stweaks profile for a real energy savings extreme ? Thanks

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] Stucko:
Hi,

thank you very much for your time and effort.

I have a lot of bugs and problems to report:

1. With TWRP 2.8.7.1 you offer I am not able to mount my encrypted data partition anymore. I encrypted normally in the settings and with 2.8.7.0 by AntaresOne I could use my pattern and TWRP could mount the partition. This makes it impossible for me to flash the new ROM which I need because of the bootloop-bug. In the log of TWRP it says the following:

E:Unable to mount '/data

E:Unable to recreate /data/media folder.

Updating partition details...

E:Unable to mount '/data

...done

E:Unable to mount storage

E:Unable to recreate /data/media during GUI startup.

Full SELinux support is present.

Running boot script...

Finished running boot script.

E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file,

E:Unable to mount '/data

With the old TWRP I remember it always said something like "Unable to mount /data, running boot script" and then I could enter my pattern.

2. Is encryption working? In the last versions of this ROM encryption could be activated but the device took only 1 minute to encrypt, after that I always need to enter my pattern to boot, for TWRP and for the lockscreen. But is it really encrypted? I thought it took at least half an hour to an hour? For me it looks like it worked only superficial but the data is still unencrypted.

3. I can not find the option to deactivate the google search bar in the "opened tasks window", perhaps this is fixed in the new version.

4. The old version 2.8.7.0 of TWRP asked for my pattern but I could only choose a 3x3 pattern, if I used a 5x5 pattern for example I could not decrypt my device in TWRP because it does not give me the option to choose the specific pattern design. This forces the user to use the weak 3x3 pattern.

Thank you very much!

Stucko
[Galaxy S 4 i9505 Original Android Development] dorian2kx:
U can make a pattern for TWRP? Does that means no one can factory reset ur phone if it's lost?
[Galaxy S 4 i9505 Original Android Development] r00t_user:
So far with the Nov.1 Build battery life SOT is so far 2Hrs 45 Minutes which is pretty bad but Bluetooth is perfect no more problems when I disconnect my earphones. Thanks Antares. Only issue is snapchats front facing camera fails to record and sometimes cameras cannot connect so i gotta reboot.
[Galaxy S 4 i9505 Original Android Development] -Deco-:
Check here for a good balanced profile, otherwise you could go hardcore and limit all the CPU core clock speeds to minimum, although not recommended. You could attempt to change the values manually to suit your preference.
[Galaxy S 4 i9505 Original Android Development] NZgeek:
All it means is that nobody can get at your data. You can still boot into recovery and format the partitions.

Not that it matters much - someone could just use Odin and flash a stock ROM, effectively nuking whatever was on the phone.
[Galaxy S 4 i9505 Original Android Development] tzyn:
[MENTION=3695291]wpyh[/MENTION] [MENTION=5464206]AntaresOne[/MENTION]

About the Bluetooth wakelock I try to figure out why this problem appears and what causes it. Last night my phone drops from 100% to 50% in 9 hours. When bluetooth is completly disabled the battery life is very good and my phone sleeps very well. If I have it enabled, then sometimes it works good without wakelocks but most of the time it's not.

So I looked into /proc/kmsg for some days now. And everytime when my battery drains it shows the messages below (flooding without break, with NO device connected!). Is there a way to debug bluetooth and why it seems to send data without a connected device and while it should idle? Or can I provide more logs (from SysLog) for you to figure it out?

Tx data during last period [BT]
hostwake line change [BT]
bluesleep_outgoing_data [BT]

And I'm getting also some other rmnet_ioctl error messages (not related to the bluetooth wakelocks). That seems to disappear if I disable and re-enable wifi+bluetooth. I attached some screenshots that shows the rmnet and bluetooth messages.

Infos of my device:

i9505 (jfltexx) with "Stock" optimized November release. No Xposed, no changes in Stweaks and no other modifications - just the vendor btlib from Imperium Rom because of the Bluetooth Share bug which I have also on newest November release. Before the update to November release I did a clean install of October release and updated my bootloader and modem to HOH2.
[Galaxy S 4 i9505 Original Android Development] MScantamburlo:
+1!

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] audianer:
Hey,

can somebody explain me z-ram? Its something like the virtual RAM from Windows, who is outsourceing it to the hdd? At android to the internal storage?
[Galaxy S 4 i9505 Original Android Development] pitelasssss:
From imperium 11 to this ROM

Clean install
[Galaxy S 4 i9505 Original Android Development] johnny88:
I guess the issue is on the modem driver that use usb bus and keep the phone active more than is necessary... As far as I read it is kernel related...

Inviato dal mio GT-N8000 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] jstath1972:
Z-ram is not ram. It is a virtual memory, also known as swap space, which lives in the ram. Virtual memory is the part where the system stores memory fragments which are not accessed, making more room for apps to store information in the ram. Most Pcs work with virtual memory on disk, but Linux has a z-ram feature, aka CompCache, which can hold unused pages in a compressed manner in memory, thus makes more ram available by compressing unaccessed pages.

ALSO...

What does zRAM means?

AND...

wikipedia
[Galaxy S 4 i9505 Original Android Development] franzyroy:
No, 1.3b is the oldest, there are more features in the one of the rom, rom kernel is more adapted to this rom.
[Galaxy S 4 i9505 Original Android Development] wpyh:
OK, this is something beyond my capacity.

So there seems to be an infinite loop of retries. Since the source-built vendor lib and the precompiled vendor lib display the same behaviour, I think this must be coming from somewhere else... I myself don't encounter this battery drain bug frequently.

[MENTION=5464206]AntaresOne[/MENTION] , can you please make a workaround for this bug? Maybe some kind of watchdog, or counter, when the number of Bluetooth send retries are too many, wait a few seconds and then restart the Bluetooth stack.

For me, the biggest annoyance for now, is the missing voice problem. When I make a call, sometimes there is no sound from the other side, and the other side can't hear anything. Only a restart seems to fix the problem. Does anyone else have this bug?
[Galaxy S 4 i9505 Original Android Development] arki82:
Setting is High Accurracy and Europe. Did a full wipe and another clean installation. Compass is still acting strange... Google Maps always points in the wrong direction (does not move), sometimes it thinks that I'm driving backwards. Fix takes really long (sometimes it does not fix at all).

GPS Status APP: sometimes the compass is active, sometimes not (top of the phone is north, compass does not move). Had no fix today in 20 Minutes... Phone seems to forget where it is...

Chrashes happen using Blitzer.de, Google Maps navigation and spotify (sync with SEAT Leon). Screen freezes... nothings happens. Long pressing Power reboots the phone.

:rolleyes:

ROM is still 20151022
[Galaxy S 4 i9505 Original Android Development] Zeitraffer:
Amazing rom.

No problems at all.

Thank you so much.

Really happy about it, and I'm looking forward to CM13 :)
[Galaxy S 4 i9505 Original Android Development] pankeca:
What the best kernel for this rom ?

This is the most updated kernel for this rom ? Kernel-Alucard-V1.3ba

My battery life is so bad about 9hours without using too much...
[Galaxy S 4 i9505 Original Android Development] side:
A new updated recovery for JFLTE just arrived !

Changelog is:

- Fixed missing crypto (encrypted devices supported again)

- Fixed faux nandroid backup/restore experienced sometimes

Remember, the minor subversion number (in this case .2) is device-specific and not related with official TWRP

Brought to you by

[MENTION=5464206]AntaresOne[/MENTION]
[Galaxy S 4 i9505 Original Android Development] Infidel01:
First off, fantastic work thank you very much.

i337m

I have clean installed latest version (1101).

Installed this version of TWRP.

Tried to encrypt device and it seems to silently fail. Shows the wire frame Android for less then a second and goes directly to the DevConnection Load screen skipping the initial boot screen (Samsung GS4).

I have tried this process when connected to wall charger and laptop.

I have also tried in safemode with the same results.

tried on previous version of TWRP to encrypt through adb and it also failed.

Are these the symptoms of the problem identified in this part of the changelog?

"Fixed missing crypto (encrypted devices supported again)"

If so am i missing something? if not can you point me in the right direction?
[Galaxy S 4 i9505 Original Android Development] ralfbergs:
New JDCTeam boot animation

Hi guys,

I really like the new boot animation, just one question: Why do the gears not engage with each other? Looks a bit strange...

Some people here in the forum have an animated GIF in their sigs, and here the gears do properly engage...

Thanks,

Ralf
[Galaxy S 4 i9505 Original Android Development] OathYvne:
Bug with phone call audio its like this weird echoy sound that gets louder and louder really strange sound, impossible to hear people. Also theirs a bug where the screen will be black like its off but the backlight is still on.
[Galaxy S 4 i9505 Original Android Development] vagkar:
Hi all,

the latest Rom has ANT+ enabled but there seems to be still a problem. Cannot connect any device and "Ant Tester" app states "Built-in firmware: Requires ARS" even though I have already installed ANT Radio Service (version 4.14.0).

Is there a way to build some other "libantradio.so"? .... though I'm not sure if that is causing the issues

thank you!