yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] 0lvin:
ok :good: Good news - that it showed logs before reboot, it mean: we have issue with some init script, but can boot.

Have all images showed log before reboot? If yes i create image with backported next my changes.

ok
[HTC Desire S] i23098:
Yes, all 3 images showed some logs before rebooting. Did not took notice if they rebooted at the same point though...
[HTC Desire S] jokergermany:
Can someone help me, i have a bootloop.

I don't know if this was triggered by a update, but i had a bootloop and flashed the 2016-08-26 image.

But it looks like i have still a bootloop =(

S-Off
[HTC Desire S] kylon:
If you have a bootloop an update does not help

You could try to post a log or just do full wipe.
[HTC Desire S] jokergermany:
Which log?

I need to do a titanium backup from the **** whatsapp app...
[HTC Desire S] kylon:
Whatsapp should not be affected.

You can find your chats and data in /sdcard/whatsapp.
[HTC Desire S] jokergermany:
The Problem is, that i need a titanium backup of whatsapp because i don't own this number anymore ;)

But i found a backup which is from end 2015, perhaps this will help...

€dit:

Nope dont work, i have to verify me number.

Which logs would help?
[HTC Desire S] mar-he:
Bluetooth don't work

Bluetooth don't work. The switcher in bletooth setting is gray, i can't switch bluetooth on in CM 13 (in CM 12 it works, but the performance in CM13 is much better). What can i do?
[HTC Desire S] kylon:
Use the android sdk to take a log

[MENTION=7696444]mar-he[/MENTION]

Can you try a previous version?
[HTC Desire S] jokergermany:
Which log is required?
[HTC Desire S] i23098:
I would say logcat. You can upload it at http://logcat.scheffsblend.com/logcat_submit.html
[HTC Desire S] mar-he:
Thank you for your answer! I have try a lot of cm13 version, but the issue is the same, bluetooth don´t work, only on CM 12.1 and CM 11 it work´s.

For a log i must look, if i can do this. I have read the information for you in your answer from today. I hope, i can find the software in SDK to make a log, then i can post it.
[HTC Desire S] kchaisu:
In fact you may use logcat app from play store, i.e. Catlog to get logfile, but some time the file is too big to post just zip it and post though. Enjoy the forum.
[HTC Desire S] mar-he:
Here is my Catlog - see txt.file.
[HTC Desire S] kylon:
Attach kernel logs

Just boot the phone and from a terminal or adb 'echo dmesg > log.txt'

If the icon became grey only when you try to enable the bt, enable it and save the dmesg.
[HTC Desire S] mar-he:
I can´t switch the bt icon realy on. The switcher is grey also i switch it on, it goes back automaticly to off. Sorry for my bad english.

I don´t know, how i can make log.txt with terminal or adb ... do you mean on my smartphone or on windows pc .... ? must i start in bootloader my htc and then in terminal pc "echo dmesg ..."?
[HTC Desire S] jokergermany:
ok my computer wasn't authorized, i will make the log now...

http://logcat.scheffsblend.com/view?id=39539530
[HTC Desire S] i23098:
Tried myself, last part of logcat when trying to turn it on.

Then did a dmesg, take note of time, tried to enable again, and dmesg again... Messages that it got, don't seem very useful :(, are:

[39458.208648] call alarm, type 2, func alarm_triggered+0x0/0xec, 156959049000000 (s 156959049000000)
[39458.988922] [BT]== R OFF ==
[39458.990478] [BT]== R ON ==
[39460.203399] [LED]pm8058_drvx_led_brightness_set: bank 6 brightness 255 +
[39460.203613] [LED]pm8058_drvx_led_brightness_set: bank 6 brightness 255 -
[39461.409698] init: Starting service 'rmt_storage'...
[39461.423736] rmt_storage_ioctl: get shared memory parameters ioctl
[39461.427337] init: Service 'rmt_storage' (pid 4329) exited with status 0
[39461.427520] init: Service 'rmt_storage' (pid 4329) killing any children in process group
[39465.205200] [LED]pm8058_drvx_led_brightness_set: bank 6 brightness 0 +
[39465.205627] [LED]pm8058_drvx_led_brightness_set: bank 6 fade out brightness 0 -
[39465.461944] [LED]pwm_lut_delayed_fade_out
[39466.431945] init: Starting service 'rmt_storage'...
[39466.445404] rmt_storage_ioctl: get shared memory parameters ioctl
[39466.449005] init: Service 'rmt_storage' (pid 4330) exited with status 0
[39466.449188] init: Service 'rmt_storage' (pid 4330) killing any children in process group
[39466.970642] call alarm, type 2, func alarm_triggered+0x0/0xec, 156967811000000 (s 156967811000000)
[39467.817962] [BT]== R OFF ==
[39467.820098] [BT]== R ON ==
[39472.168670] init: Starting service 'rmt_storage'...
[39472.181762] rmt_storage_ioctl: get shared memory parameters ioctl
[39472.185363] init: Service 'rmt_storage' (pid 4357) exited with status 0
[39472.185546] init: Service 'rmt_storage' (pid 4357) killing any children in process group
[HTC Desire S] kylon:
not sure how to fix this

try this
[HTC Desire S] jokergermany:
Which sickness has my phone?
[HTC Desire S] i23098:
did not work :(

Logcat was a bit big, hopefully only correctly removed unrelated stuff :fingers-crossed:
[HTC Desire S] nijawang:
Hi,

How to do to choose my own mp3 for clock alarms?

I could choose my own files before, but in these days the files I put in /sdcard/Alarms folder don't show-up in clock alarms choice list.

So I remove the the files in Alarms folder first, then put them back again.

But now I could not see any own file for alarm, only the default alarms!

How to fix this issue?

Thank you.

ROM: aceopt 20160901

Desk clock: system default
[HTC Desire S] ze7zez:
Did you try to insert the file into the /system/media/audio/alarms ?
[HTC Desire S] kauh:
Hi, first of all big big big thanks for making rom like this! I leave in Moscow (Russian), and in all roms of saga (11, 12.1 and 13) one mistake about timezone of Moscow +4, but actually it +3, so I need to turn off automatic time sync or use another UTC +3. Info about that https://en.m.wikipedia.org/wiki/Moscow_Time
[HTC Desire S] ze7zez:
If you have inserted the SIM card and the phone receives a GSM signal, the automatic time synchronization is performed by the network operator, and not by the android.

Maybe something spoiled location settings google?
[HTC Desire S] mar-he:
Is there anyone who gets bluetooth working on cm13 and htc desire s?
[HTC Desire S] kauh:
No with SIM card and automatic time synchronization I've got +1 to the current time.

My main phone nexus 4, works correct with SIM card and time sync.

So the problem with the old UTC rule for Moscow time zone.
[HTC Desire S] nijawang:
Yes, I ever put the mp3 into /system/media/audio/alarms but it not works.

But I got encryption error afterward and Android asked me to reset system...

I have no choice, so I reset system then the alarms function comes back.:confused:
[HTC Desire S] nijawang:
This morning, I installed cm13 aceopt 20160912 nightlies with Open GAPPS pico 20160912.

But the development mode fails to function now! There is nothing in development mode, just it's not available for this user.

I check with ROOT CHECKER, it pass.

But I tap the version item times, and it always stock at 1 step to query Device ID then show up "Device ID is not available on this build".

I use Device ID checker, the Device ID is MOB30Z

How could I fix this issue?

Thanks!
[HTC Desire S] i23098:
This is Saga (HTC Desire S) thread... Ace is here. Although developers are the same in both threads :p

I'm on 20160911, and it works fine I think... Either got introduced in latest build or it's a Desire HD specific bug...
[HTC Desire S] nijawang:
Sorry for posting here by mistake, will transfer to ace thread.

And thanks for your advice.

Just wonder if factory reset will help?
[HTC Desire S] i23098:
Not sure :rolleyes:

But you should take a logcat while it happens (you can submit it here).
[HTC Desire S] i23098:
Hi, finally got some free time...

First I got an error with the

git clone git@github.com:free-z4u/android_kernel_htc_msm7x30.git

and I replace it with

git clone https://github.com/free-z4u/android_kernel_htc_msm7x30.git

And seems to be doing something :D

But the resulting image did not work :(

It starts, shows the logs, stops a little - took a pic:

some more logs, stops a little - took a pic - and then reboots to recovery :(

---------- Post added at 09:29 PM ---------- Previous post was at 09:06 PM ----------

Doesn't seem to be working :(

Is there anything else we can do to try and help debug it :confused:
[HTC Desire S] 0lvin:
Yep, i write this for my self :( For use gic clone in such way need to configure git.

By first image - phone tried to mount all partitions, so it is fully correct behavior by first look.

It looks like troubles with usb configuration. Do you have any message in case run by "fastboot boot ***.img && adb logcat"? By message looks as no.

Please try to run such:

comment out/drop:

git checkout cm-13.0
git pull

revert last commit:

cd android_kernel_htc_msm7x30
git reset --hard HEAD~1
cd ..

rerun create/boot image

go to revert until boot is not success
[HTC Desire S] i23098:
No :( while the logs are showing, logcat cannot connect...

I assume you mean "until boot is success", as it is not success now :p

Will give it a try when I have some time, hopefully won't be hundreds of reverts before finding the culprit... :fingers-crossed:
[HTC Desire S] i23098:
Did not take long :D After I got

HEAD is now at 7b8de21 update arch/arm/mach-msm/devices_htc.c from cm-12.1-3.6

It boots :good:

I went to settings, it shows kernel version as 3.0.101-ODP-g7b8de21 instead of 3.10 :confused:

And got and error saying

Unfortunately, Ok Google enrollment has stopped.

Did a git pull, changed the arch/arm/kernel/devtree.c to move the return just after the pr_info and it boots. Still got the same error message. Logcat of wrror, I believe it is:

--------- beginning of crash
09-20 19:28:52.300 3619 3647 E AndroidRuntime: FATAL EXCEPTION: IntentService[ModelUpdateService]
09-20 19:28:52.300 3619 3647 E AndroidRuntime: Process: com.android.hotwordenrollment, PID: 3619
09-20 19:28:52.300 3619 3647 E AndroidRuntime: Theme: themes:{}
09-20 19:28:52.300 3619 3647 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke interface method 'android.hardware.soundtrigger.SoundTrigger$KeyphraseSoundModel com.android.internal.app.IVoiceInteractionManagerService.getKeyphraseSoundModel(int, java.lang.String)' on a null object reference
09-20 19:28:52.300 3619 3647 E AndroidRuntime:	at com.android.hotwordenrollment.EnrollmentUtil.getSoundModel(EnrollmentUtil.java:143)
09-20 19:28:52.300 3619 3647 E AndroidRuntime:	at com.android.hotwordenrollment.ModelUpdateService.updateSoundModel(ModelUpdateService.java:58)
09-20 19:28:52.300 3619 3647 E AndroidRuntime:	at com.android.hotwordenrollment.ModelUpdateService.onHandleIntent(ModelUpdateService.java:48)
09-20 19:28:52.300 3619 3647 E AndroidRuntime:	at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:66)
09-20 19:28:52.300 3619 3647 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:102)
09-20 19:28:52.300 3619 3647 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:148)
09-20 19:28:52.300 3619 3647 E AndroidRuntime:	at android.os.HandlerThread.run(HandlerThread.java:61)
09-20 19:28:52.622 2023 2023 W art : Long monitor contention event with owner method=void com.android.server.am.ActivityManagerService$UiHandler.handleMessage(android.os.Message) from ActivityManagerService.java:1465 waiters=0 for 111ms
[HTC Desire S] kchaisu:
I am wondering if there is any problem on upstream porting for DS because HD has 201623 build but DS has none. Thanks.
[HTC Desire S] Mustaavalkosta:
Hmm, I can see 20160923 builds for saga just fine.
[HTC Desire S] i23098:
It was probably some issue with the build machine that only executed the saga build much later than usual. Looking at server times, it's usually between 11 and 12 in the morning. The 23 build only finished the day after at 00:24. But the next builds are fine, so, just some temp issue...
[HTC Desire S] kchaisu:
I am sorry for misposting before the build was out. Thanks.
[HTC Desire S] i23098:
Hi 0lvin (just quoted you to try and grab your attention :o), still working on getting the kernel working :confused: Let me know when you want me to try something else...

Hi Mustaavalkosta (tried to grab your attention too :o) Anything we can do to try and help you to get bluetooth working :confused: Still not working on 20161012, got a logcat. I'm a web developer, don't know about OS development, but I can try and help :cyclops:
[HTC Desire S] Mustaavalkosta:
I've been meaning to try simple lib switch from 12.1 but it has been a bit difficult to sit down and do it. I haven't even got far enough to name the libs that might be switched. :( If you feel adventurous, you can try to figure it out by lib names though and see if anything changes. Or even try to figure out from git Android.mk files which LOCAL_MODULE names there are for BT but that may be a bit cumbersome without source tree to grep on.
[HTC Desire S] JerseyChewi:
I'm not sure what you mean exactly but it's important to note that there was a brief period where Bluetooth did work on 13. I think it was around March.
[HTC Desire S] i23098:
No worries, just wondering if would need some tests on a device to get a logcat or so...

suuuure :eek: Can you write that in baby steps? Like, go to this list of sites, look at this or that in search for changes in whatever, etc... :silly: Pretend I'm really dumb when writting instructions, that way I might understand :fingers-crossed:
[HTC Desire S] 0lvin:
next chance

Hi!

Please try commits from updated cm-13.0 branch. Need fully same actions - if something does not work try revert last. Also when you found last working commit - try to boot with such command "fastboot boot new_boot.img && adb wait-for-device && adb shell dmesg> dmesg.log && adb logcat" I need "dmesg.log" to check which atag parsed last.

About kernel version - we will have 3.15 with your help ;)
[HTC Desire S] bastei:
I ported your sagaopt repo back to saga to build a cm13 saga version. I used the bluetooth firmware and configuration of ivanich's Sensation ROM there (thanks [MENTION=4329165]ivanich[/MENTION]) and it is working fine as Sensation and Desire S share the same bluetooth/wifi chipset. Here you can find the bluetooth commits:

https://github.com/bastei/android_device_htc_saga/commit/de23acb

https://github.com/bastei/android_device_htc_saga/commit/c8fe803

The saga version is working fine but you have to remove some CM apps to get a small enough system image:

https://github.com/bastei/android/blob/cm-13.0/local_manifest.xml
[HTC Desire S] ralfbergs:
I'm not sure I understand what exactly you did...

IIRC the difference between "saga" and "sagaopt" was in the handling of the external uSD card, where sagaopt would treat it as "adopted" storage and use the original /data as /system (because it is larger).

If that is correct, then I don't see what the point of your exercise is...

Can you please spare some minutes and explain?

Thanks!
[HTC Desire S] i23098:
Doesn't even start the boot process :(

Simply reverting last it shows logs and then reboots into recovery. I then edited android_kernel_htc_msm7x30/arch/arm/kernel/devtree.c an in the last function of the file (void __init setup_safe_machine_fdt(char *dt_phys)), I added a return after the pr_info call. (half revert - only the devtree.c file - of 1629a1e)

...
pr_info("Safe machine: %s, model: %s\n", mdesc_best->name, model);
return;
/* Retrieve various information from the /chosen node */
...

Then, it does boot :D

You can find logcat attached. dmesg was 0 bytes initially, but rebooted again and you can find it attached...

Nice :highfive: Not that I have any idea what features the new kernel will have for our phone :o but using newer versions is always nice :victory:

Edit: Forgot to say, but it seems the SIM card could not connect correctly to the network as there was no signal...

Edit: Got the same error popup as before
[HTC Desire S] bastei:
Sorry if this was a bit misleading. Basically you are right regarding the difference of the both variants.

What I did is nothing special: OpenDesireProject has a saga repo where development for cm13 stopped early in favor of sagaopt. But I wanted to use the original partitions, so I merged the more up-to-date sagaopt repo back to it to built "my own" cm13 saga version.

The "special" thing is working bluetooth. And as saga and sagaopt indeed only differ in the usage of the partitions my changes concerning bluetooth should work on both variants.
[HTC Desire S] ralfbergs:
Sounds like a great accomplishment then, thank for your contribution.

Hopefully someone can merge your changes into sagaopt....
[HTC Desire S] Mustaavalkosta:
Thanks for the commit links! Looks something that might be easy enough to replicate to opt variants too. I need to get my Arch Linux booting to prepare test builds after installing Win10 wiped my MBR and killed my dual-boot setup. :p
[HTC Desire S] i23098:
Great news :victory:

Btw, the latest build in https://dl.opendesireproject.org/cm-13-0-unofficial-sagaopt/nightlies/ is 20161013.
[HTC Desire S] 0lvin:
Could you try to put return as first line of early_init_dt_scan_chosen and delete return before

of_scan_flat_dt(early_init_dt_scan_chosen, boot_command_line);

?
[HTC Desire S] i23098:
I've git pull to the last commit, and changed that file with return 1

ralmeida@amd64:~/Downloads/android/kernel/android_kernel_htc_msm7x30$ git diff
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index 6b8c13c1..f8e10f8 100644
--- a/drivers/of/fdt.c
+++ b/drivers/of/fdt.c
@@ -747,7 +747,7 @@ int __init early_init_dt_scan_chosen(unsigned long node, const char *uname,
{
unsigned long l;
char *p;
-
+return 1;
pr_debug("search \"chosen\", depth: %d, uname: %s\n", depth, uname);

if (depth != 1 || !data ||

The phone shows HTC logo, black screen (no logs) and reboots after a few seconds :( I tried just return; and the result is the same..

Btw, I'm using your old saga-atags.e136fab7.log.img as base image

./create_saga_ubuntu.sh saga-atags.e136fab7.log.img

Is that ok?
[HTC Desire S] kylon:
Thanks!

Your changes have been added to odp repos

Hope the next build will not break :)

Ps. MBR is a pita if you want to dual-boot win + other. You can "convert" your bios pc to efi with Clover bootloader.
[HTC Desire S] kchaisu:
There is another way around to solve the problem on AOSP Keyboard FC by [MENTION=4329165]ivanich[/MENTION] on Open GApps forum which makes AOSP Keyboard FC gone by removing Keyboard Gesture Support (system/lib/libjni_latinimegoogle.so). This way the same keyboard could be used to setup accounts. Thanks.
[HTC Desire S] kchaisu:
I was sometime facing problems on browser crashing and slow wifi sign showing up. In addition on 20151212 build widget apps page included searching strip on top of the page. Thanks Kylon and Mustaavalkosta for your kind contribution to DS community. Currently, I am using the nighly as my daily ROM. However, I don]t know how to get the contact from my account so I imported them from my vcf file. Thanks.
[HTC Desire S] ralfbergs:
I noticed that FileManager doesn't even seem to declare "SuperUser" as one of its desired permissions, which may be why the menu option to operate in "Root Mode" is not present.

Has anyone else noticed this?

I do have dev mode enabled and allowed root for Apps (and cmd line).

--

Sent from a mobile device.

Please excuse my brevity.

---------- Post added at 07:40 ---------- Previous post was at 07:03 ----------

Is it just me, or is anyone else also having the problem that Bluetooth isn't working properly?

When I try to pair a device some process seems to be crashing...

Please let me know if I should collect some logs and send them...

--

Sent from a mobile device.

Please excuse my brevity.
[HTC Desire S] kylon:
The bluethoot should work in tomorrow build.

Yes, there are a few problems with su on M, they will enable it again when ready
[HTC Desire S] kchaisu:
There is another way to solve Setup Wizard FC by [MENTION=7111288]Mustah[/MENTION]F on Open GApps by the use of clean install Open GApps 6.0. And I got every information on account setup sync including contacts. 1) Flash ROM and wipe data partition without rebooting, 2) Flash Open GApps 6.0 3) Delete or rename system/lib/libjni_latinmegoogle.so (otherwise AOSP keyboard will FC and unusable) before rebooting, and 4) Reboot the device and following the setup.

This way could provide the same information as CM-12.1 on the account setting. Thanks and enjoy the CM-13.0 20151215 sagaopt build.
[HTC Desire S] kchaisu:
To confirm that clean flashing GApps solves google play services and google account setting problems, I have tested both clean flash ROM and reboot setup and flashed Open GApps and clean flashed ROM and clean flashed Open GApps and rebooted. I found that clean flashed Open GApps has made my Saga Google Play Services FC free and getting all my contact from google account. And the device is very stable and fast. Thanks to Kylon, Mustaavalkosta, Paul_nb and the team for their kind contribution to CM-13.0 sagaopt nightly and MustahF for elaboration of clean flashing of GApps to solve Setup Wizard FC
[HTC Desire S] youngboy:
I flashed 20151215 nightly. I was interested in Android 6 new features.

A met a problem. When the phone was connected to PC by USB in case of choice charge only phone was in windows explorer but storage was not shown. Changing the connection to MTP or PTP phone was removed from win explorer.
[HTC Desire S] Mustaavalkosta:
Workaround from a sibling device primou: http://xdaforums.com/showpost.php?p=64364837&postcount=13

No clue if it works for saga but worth a shot if you are eager to use MTP.
[HTC Desire S] joolli:
Tried what I thought was clean flash of latest cm13 and gapps-mini and still got keyboard FC. What do you mean by clean flash? What I did was wipe data (not /data/media/), dalvik, cache, system.
[HTC Desire S] kchaisu:
Please read post#25 of this thread, just a few posts back which explained how to setup to avoid setup wizard FC and Aosp keyboard FC. However, factory reset is for clean ROM installation, wipe data after flashing ROM before boot is GApps clean installation. Clean installation GApps is for avoiding Setup Wizard FC. But for the AOSP keyboard FC, just delete or rename system/lib/libjni_latinmegoogle.so before booting up to avoid Keyboard FC. Thanks.
[HTC Desire S] jokergermany:
Hi,

whats my mistake?

I flashed this twrp:

http://downloads.codefi.re/jrior001/TWRP-recovery-sagaopt-2.8.7.0.img

I assume that this should change my sage in a sagaopt device?

My HTC Desire S is still a saga, twrp will not flash this, because it is not a sagaopt device =(
[HTC Desire S] Mustaavalkosta:
Huh? There's no assert check in TWRP when flashing images. You are doing something seriously wrong if you get complaint about device name when flashing that. You can even flash recovery for ace into saga, it's just it's not a recommended thing to do because ROMs have assert check for device name which then prevents you from using anything else than ace ROMs.
[HTC Desire S] jokergermany:
The problem is, that i don't know what i am doing wrong...^^
[HTC Desire S] i23098:
I assume you are on CM12.1 normal saga version...The recovery by itself won't convert your saga to sagaopt, so the rom you have installed is saga, thus the error.

You must loose all your data first (so back it up to a pc or so and restore it latter). You must format your sdcard to ext4, wipe all partitions, copy the sagaopt.zip file and then flash it.
[HTC Desire S] jokergermany:
which sageopt.zip file do you mean?

I have done everything what you said...