yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] blahmartinblah:
Booted this 3 times, with SD card available after each!

Boot1 with 16gb Sandisk Ultra SD card mounted after boot up: http://pastebin.com/71UQx6JZ

Boot2 with 16gb Sandisk Ultra SD card mounted after boot up: http://pastebin.com/Rn373JpE

Boot3 with 16gb Sandisk Ultra SD card mounted after boot up: http://pastebin.com/ThCTJY6r

And also 4 successful reboots with my 32Gb Sandisk Ultra Class 10 card!

Boot1: http://pastebin.com/rNGc0PUX

Boot2: http://pastebin.com/ab0gDQc2

Boot3: http://pastebin.com/zi4Yi32A

Boot4, full dmesg output: http://pastebin.com/WaMgM3Kx

I think [MENTION=7319300]ottmi[/MENTION] is a hero :)
[Miscellaneous Android Development] siljaer:
Better, he is a real genius, that is 1% inspiration, 99% transpiration (famous quote by uncertain author).
[Miscellaneous Android Development] ottmi:
Great, I'm glad its working now. Thanks a lot to [MENTION=722204]blahmartinblah[/MENTION] and [MENTION=7529884]siljaer[/MENTION] for all the testing! I will see whether I can find a cleaner solution than this ugly hack.. Maybe it's just a matter of increasing the timeout..
[Miscellaneous Android Development] vickdu31:
Sorry to answer late ^^ yeah i just used the Ark kernel because it was the newest at the time.

But i dont recommend my rom anymore because its a bit outdated but if you think its mire stable you can use it. My trunk is dead so i cannot do anything anymore :/

I recommend ottmi version because he is a true dev not like me who just mess around stuff, thanks to ottmi for the time you dedicated to the device. Your work is perfect
[Miscellaneous Android Development] ottmi:
No that's odd.. I just realised when I went over the code again, that I introduced the additional retries to the MMC code not the sdcard code. I don't really understand why it still improved the situation with sdcard initialization. Maybe the additional debug output added enough delays to make it work ?!?

Anyway, I have re-compiled yet another kernel that adds the retries in the right place and also gets rid of most of the debug messages. [MENTION=722204]blahmartinblah[/MENTION] could you please try this one and post the usual dmesg here?

https://drive.google.com/open?id=0BwV0Nb8HTEBwSjZiNFpHbkM0T2c
[Miscellaneous Android Development] blahmartinblah:
First boot, no SD card :( http://pastebin.com/Qb2N6xPg

Second boot, working! http://pastebin.com/cdeen0NR

Third boot, working! http://pastebin.com/1ZYZBj41

Fourth boot, working! http://pastebin.com/Wg7gEAed

Fifth boot, working!

Sixth boot, working!

Seventh boot, working!

Eighth boot, working!

Ninth boot, working!

Tenth boot, working!

So, not sure what happened first time!
[Miscellaneous Android Development] siljaer:
I've found a video showing the inner working of the driver :) https://www.youtube.com/watch?v=aGooEP4FMjY
[Miscellaneous Android Development] ottmi:
Right, now I recall.. I will try with a different sdcard and see what's happening. Once I find this spare sdcard :o
[Miscellaneous Android Development] ottmi:
There's a new ROM available under downloads. Only noteworthy change: haptic feedback on the soft buttons should now work.
[Miscellaneous Android Development] Sampierdarena:
[MENTION=7319300]ottmi[/MENTION]

Thanks to the new version.

The virtual keys now vibrate regularly. :good:

The ROM is wonderful, no LAG, excellent fluidity. Battery OK.

The only question I want to ask: the management of charging, I believe that the absorbed amps are a bit 'too much. (1.5 ampere)

You can adjust?
[Miscellaneous Android Development] ottmi:
Why would you want to change this? If your power supply can provide the 1.5A it will charge faster. If it can't, the phone will draw less anyway..
[Miscellaneous Android Development] :
I think he was mainly concerned that the battery will wear off faster with those values...

edit (my measured values):

Offline charging: ~ 950mA, device on (display off) ~ 1.05A. Kernel from build 20160611.

Then I used a cable without the data pins connected: 1.46A. Guess we found the "fast charge option". ;)

(with the regular cable it also dropped off nicely at the end as expected and was around 300mA)
[Miscellaneous Android Development] marcachas:
Thank you very much for your work, the ROM is being perfect, is fully usable, it is worth mentioning that I'm using in my day to day, everything works fine, the only problem is with the SD memory, which does not recognize, I have to restart about 5 times to recognize it, but when you restart the device again fail to recognize the SD, what it should ?, continues well and if I can support or donate gladly I will, a hug from Mexico. :)
[Miscellaneous Android Development] :
Manufacturer / model of the SD card?

I hope you just have a faulty SD card, otherwise it's your device and that would be 'not so good'.

(When SD card is formatted as internal storage: System reports an error, claims the card is corrupted. Formatted as regular external SD, it works fine.)
[Miscellaneous Android Development] ottmi:
Hmmm, I don't think this in line with the USB standard :o

But good to know since I wanted to fit an QI receiver to my Trunk and wire it internally. I was already thinking about how to signal fast-charging without interfering with the USB port. Obviously, I only have to wire V and GND - that makes it much easier :)

I wouldn't worry too much about battery wear off - anything up to 1C should be fine..
[Miscellaneous Android Development] ottmi:
I don't think this is a software problem. Try a different sdcard or check the pins on the connector.
[Miscellaneous Android Development] siljaer:
echo during calls

Hi ottmi, thank you for your work. I've had my trunk only for a few days, and I flashed your rom (20160606) as soon as it arrived. It worked flawslessly, but people kept telling me that they heard their own voices' echo while speaking to me.

So I tried calling myself, and I must admit that I can hear the echo while speaking to the Trunk via another phone. So I flashed 20160611, but the problem remains. I've looked for such a problem in the forum, and I found that you were aware of it ( http://xdaforums.com/showpost.php?p=66476171&postcount=437 ). It looks like some people are affected, some others aren't. Decreasing call volume does not help. Well, just to let you know that someone is still experiencing the echo. Apart from that, I think your rom is perfect. Thank you again!
[Miscellaneous Android Development] marcachas:
I have a lot Of problems

Thanks, i wil check the sd, but the new compilación got a lot Of problems, a fc for example, the sistema sound crash and collaps, i will return to 20160606, why have this problems? Oh yeah, thanks for the vibrate feedback. sorry for my bad english. :crying:
[Miscellaneous Android Development] :
I noticed it more since the last 2 or 3 builds, so I made those changes to the build.prop:

from (old)

ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=false

to (new)

ro.qc.sdk.audio.fluencetype=fluence
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true

and had multiple phone calls, 2 people with landline, 2 with mobile and and they reported back: it's clear / no echo.

Then I made one call to a person with landline (IP based, lives in a small village = s#itty connection ^^) and he said it sounds good while I heard a small echo of my own voice, meh. :silly:

If you guys wanna try it for yourself and report back, that would be nice. :good:

I refrained from uploading flashable build.prop ZIPs for now, if someone doesn't want to edit manually, let me know.

---

The 20160611 build is "rock stable" imho, no crashes, no random reboots, nothing. Did you wipe caches after flashing the new 'compilación'?

Any special system intrusive apps added? Xposed modules?
[Miscellaneous Android Development] siljaer:
Hi, thanks for your intererest. I have modified build.prop as you suggested and since I'm not an expert, I am going to explain what I did in detail: I edited with CM file manager the file /system/build.prop, then I rebooted (was that right?).

Unfortunately, people keep hearing echo; i tried calling my trunk from landline and I still heard it. I have to say, however, that now and before it isn't so annoying as people tell me, but maybe my annoyance threshold is higher...

Maybe there are different revisions of the hardware....
[Miscellaneous Android Development] :
It's definitely not the ultimate solution for this issue but it's a decent improvement until the real cause is known.

CM file manager keeps the permissions of the file I guess (I use solid explorer) so you had no trouble rebooting. If the file kept the changes: job well done. ;)

Don't know about the hardware, but since Elephone is one half of an OEM platform, I hope they keep their batches exactly the same...
[Miscellaneous Android Development] marcachas:
Greetings and thank you very much for answering, responding to your comment, I have not installed absolutely nothing, no changes or anything, just whatsapp and Clash of Clans, again download the ROM and google apps to see if it was an error with the download, check files, again install from scratch, even delete the system folder, but still the problems, why is it ?, by the way, the SD memory still gives me problems, not detect my device, I returned to the ROM factory and detects no problems, is on the right path ROM only this latest version is giving me problems.
[Miscellaneous Android Development] todoss:
I have same problem with sd card mounting. I must reboot meny times to mount sd card correctly. Same problem is with 3.x recoveries. Only recovery 2.8.7.0 working prefect for me.
[Miscellaneous Android Development] 21prods:
Could it be related with the speed of the SD card? I have not had any problem except the fact that I cannot use it as internal memory.

Enviado desde mi Nexus 5 mediante Tapatalk
[Miscellaneous Android Development] siljaer:
Yes, it has kept the changes. This problem is somehow funny. It reminds me that someone was studying a kind of anti riot weapon/device based on the fact that most of people shut up if they hear their own voices back with a small delay. In fact, people calling me tend to talk much less. This bug could become an interesting feature to shorten unwanted conversations :)
[Miscellaneous Android Development] ottmi:
Interesting catch. The Wileyfox Swift also uses these settings (apart from the speaker setting which is set to false). So I will include in my next build, I guess it shouldn't hurt..
[Miscellaneous Android Development] ottmi:
I think there might be some more settings in the mixer_paths.xml file that could help. But documentation is really scarce and since I have no problems with echoes I can't really do anything about it..
[Miscellaneous Android Development] 21prods:
[emoji1] [emoji1] [emoji1]
[Miscellaneous Android Development] ottmi:
Very strange.. The problem was this:

[ 0.901085] mmc1: Signal voltage switch failed, power cycling card

Not sure why it happened, though.. Let's keep an eye on it, hopefully it was just a one time hickup..
[Miscellaneous Android Development] blahmartinblah:
Interesting - no idea there!

What are your plans next ottmi? Release a build with this, or should I flash the kernel as is and use it for a while?

Martin
[Miscellaneous Android Development] ottmi:
I've just uploader a new ROM:

http://xdaforums.com/devdb/project/dl/?id=20162

It includes the patched kernel that hopefully fixes the sdcard problems as well the fix for the previous ROM that corrects the thermal-engine and audio effects. Apart from that, I've now switched to the Wileyfox blobs for everything but the camera and tweaked the auto-brightness a bit more. I think it's much better now (at least for me ;)). Also, I've setup my own server for OTA updates - so from now on you can conveniently update from your phone.
[Miscellaneous Android Development] 21prods:
Wow!!! Simply incredible!

Enviado desde mi Nexus 5 mediante Tapatalk
[Miscellaneous Android Development] cool400:
That's really awesome!

Can I make a dirty flash over my existing installation, so that I don't have to re-install every single app again?

Or do I have to wipe everything in advance?
[Miscellaneous Android Development] ottmi:
Sure, you can just do a dirty flash..
[Miscellaneous Android Development] fcc123:
Kernel changes solved the SDCard issue!!

Can confirm / my 64GB Samsung card works now!

Thanks for all the efforts!!
[Miscellaneous Android Development] Sampierdarena:
Good morning [MENTION=7319300]ottmi[/MENTION]

I report a problem I have with the latest version: the camera does not work correctly, in time to capture the image, crashes

I also tried with "Camera FV-5" it happens anyway.

P.S.

I can not find the OTA menu
[Miscellaneous Android Development] fcc123:
Here same Issue with camera
[Miscellaneous Android Development] blahmartinblah:
I downloaded the ROM and applied the available OTA update to 0902. SD is working great. The camera is not working - I use the A Better Camera app. It just freezes after pushing the shutter button.
[Miscellaneous Android Development] Bizen-Ya:
Hi !

i'm still on the thermal-engine stuff, which isn't working at 100% right now.

The CPU mitigation isn't working on cyanogen, while it's ok on the stock rom.

The only diff in the logs between stock and cyan is :

09-03 22:31:01.149 20329 20329 E ThermalEngine: devices_manager_reg_clnt: Invalid dev cpu.

09-03 22:31:01.149 20329 20329 E ThermalEngine: pid_algo_init: Device clnt create fail cpu

09-03 22:31:01.149 20329 20329 I ThermalEngine: pid_algo_init: No PID's to be configured.

09-03 22:31:01.150 20329 20329 E ThermalEngine: devices_manager_reg_clnt: Invalid dev cpu.

09-03 22:31:01.150 20329 20329 E ThermalEngine: ss_algo_init: Device clnt create fail cpu

09-03 22:31:01.150 20329 20329 E ThermalEngine: devices_manager_reg_clnt: Invalid dev cpu.

09-03 22:31:01.150 20329 20329 E ThermalEngine: ss_algo_init: Device clnt create fail cpu

09-03 22:31:01.150 20329 20329 E ThermalEngine: devices_manager_reg_clnt: Invalid dev cpu.

09-03 22:31:01.150 20329 20329 E ThermalEngine: ss_algo_init: Device clnt create fail cpu

09-03 22:31:01.150 20329 20329 I ThermalEngine: ss_algo_init: No SS's configured.

any idea ?
[Miscellaneous Android Development] ottmi:
My bad, I made a mistake with the binary blobs. I've just compiled a new ROM that should fix this. It should be available via OTA or via this direct download link:

https://it-chefs.com/~ottmi/CyanogenModOTA/builds/full/cm-13.0-20160904-UNOFFICIAL-trunk.zip
[Miscellaneous Android Development] ottmi:
So apart from the error messages, what exactly isn't working and how should it work?
[Miscellaneous Android Development] siljaer:
Camera working again, thanks!
[Miscellaneous Android Development] Sampierdarena:
Thanks [MENTION=7319300]ottmi[/MENTION],

the camera works perfectly.

I received the OTA update, excellent system. Compliments!

:good:
[Miscellaneous Android Development] Bizen-Ya:
Hi, the engine dont slow down the CPU freq when the temp is close to the max.

So I'm trying to setup a build env to do some test, but I can't manage the cyanogenmod_trunk-64_defconfig file.
[Miscellaneous Android Development] ottmi:
You don't need to setup a build environment to play with the thermal engine, just edit /etc/thermal-engine.conf. You could also just remove this file from your phone in which case the daemon would start with default parameters - that's what the stock ROM does..
[Miscellaneous Android Development] Bizen-Ya:
i think there is something wrong with something, maybe selinux ..

without config file, i don't have the same behavior with the stock rom.
[Miscellaneous Android Development] ottmi:
I don't think it's related to selinux. You might want to check Qualcomm's Thermal Debugging guide:

https://developer.qualcomm.com/qfile/28825/lm80-p0436-8_thermal_debugging_guide.pdf

Also, enabling debug output by uncommenting the "#debug" line in the config file might help. And maybe start with a simpler config file, like the one from the Moto G3: https://github.com/CyanogenMod/andr...mmon/blob/cm-13.0/configs/thermal-engine.conf

I don't recall where I got the current config file from, but it seems overly complex and particularly the LCD_MONITOR is quite annoying as it interferes with the autobrightness controller..
[Miscellaneous Android Development] blahmartinblah:
I enabled daily checks for OTA updates. Despite already downloading and installing 0904, I have had notifications there is a new update available. Has anyone else noticed this?
[Miscellaneous Android Development] cool400:
No update here, I'm also on 0904.

Gesendet von meinem Elephone Trunk mit Tapatalk
[Miscellaneous Android Development] ottmi:
Same here. What happens if you check manually? Does it show the 0904 as installed?
[Miscellaneous Android Development] todoss:
No updates for me when manualy check, but there is some message "Available upfates" and sometime I have same notification!
[Miscellaneous Android Development] blahmartinblah:
Thanks for the screen captures [MENTION=5312743]todoss[/MENTION], I was planning to do the same but I already cleared the notification.

It's not a massive issue, and easy to just clear the notification - but I am experiencing the same symptoms as you. It was just a little bit of a let down the first time after I got excited [MENTION=7319300]ottmi[/MENTION] had made some awesome new update :)

Martin
[Miscellaneous Android Development] saboy1976:
my trunk shut down when it heat

i used my trunk today in my car with "TomTom Navigation GPS Traffic"app , after 15 minuts , it shutdown, so i wait 5 minutes to restart the phone almost 15 minuts later it shut down again. the thermal-engine is maybe in fault. Must i flash the last rom with this http://xdaforums.com/devd...t/dl/?id=19877 or the cm13 2016 09 04 rom is already modified?

SD card is working for me , thanks.
[Miscellaneous Android Development] blahmartinblah:
What ROM version do you have? Ottmi's change log on page 1 of this thread mentions the thermal fixes were introduced at version 0902.

I had shutdown issues when using Google maps navigation before 0902, but I now have 0904 and used navigation successfully yesterday for a period of about 20 minutes.
[Miscellaneous Android Development] saboy1976:
I use the last rom from 0904, That's why i'm surprised :(
[Miscellaneous Android Development] ottmi:
The 20160904 build didn't fix the thermal-engine properly. It probably improved things a little as it would throttle the GPU and dim the display, but didn't throttle the CPUs. I'm just now compiling a new ROM that has a modified thermal-engine.conf that should hopefully work better.

It should soon appear in the OTA menu, or if you want to flash manually will be available here:

https://it-chefs.com/~ottmi/CyanogenModOTA/builds/full/cm-13.0-20160909-UNOFFICIAL-trunk.zip

This build will also include the September Android security fixes..
[Miscellaneous Android Development] saboy1976:
thank you very much Ottmi for everythings you do for our Trunk
[Miscellaneous Android Development] ottmi:
It's up now. As always with the builds early in the month, some stuff might be broken due to the upstream changes at Android..
[Miscellaneous Android Development] Sampierdarena:
I rise to thank [MENTION=7319300]ottmi[/MENTION]

I received OTA with the latest version, all right, no problem! :good:
[Miscellaneous Android Development] blahmartinblah:
Everything seems to be working OK for me too - I'll try the GPS navigation tomorrow and see how it handles the thermal loading.

Thanks Ottmi!
[Miscellaneous Android Development] blahmartinblah:
So I used the navigation today for 2 trips, each about 35 minutes in duration. No shutdown/reboot problems at all, which is a definitely improvement over the performance a few weeks ago. Things are looking good!
[Miscellaneous Android Development] ottmi:
I also did 2 trips yesterday, both about 1 hour. No problems here. But then again, I use an airvent mount for my mobile phone and AC was running. So maybe that helped ;)

Regarding the update notifications: I've also received a few of them by now although no new update was available. I'll have look at it.. Or maybe just switch to daily builds ;)
[Miscellaneous Android Development] cool400:
Just wanted to do an OTA-update from 0409 to 0909 and ended up in TWRP asking me if I want to leave the system-partition read only or allow to modify it.

I swiped the slider to the right to allow it and landed in TWRP doing nothing than waiting for my input.

I then searched any firmware-file through the 'install'-button but found nothing.

BTW, I have mounted my SD-card as additional internal memory if this is important.

This happened after I finished downloading the 0909-update and clicked on the install-symbol.

Is it not possible to do an OTA-update with TWRP installed instead of the stock-recovery?

Or what was my mistake?

Best regards

Mischa

Gesendet von meinem Elephone Trunk mit Tapatalk
[Miscellaneous Android Development] blahmartinblah:
I have TWRP 3.0.2-0 and updated to 0909 using the OTA update - it all happened automatically - no need to select the update file in TWRP.

Have you tried downloading and installing the OTA update again?
[Miscellaneous Android Development] ottmi:
It should work without any interaction with twrp. In fact, I'm pretty sure it wouldn't work with stock recovery due to missing signatures..

The update files go to the internal storage in folder /cmupdater if you want to try it again manually.
[Miscellaneous Android Development] ottmi:
I think I've fixed the problem with the OTA notification for already installed updates - this was a server-side fix, there's nothing to be done on your side.

In other news, there's a new build available via OTA now. Nothing new there besides the CM13 upstream changes. URL for manual downloads:

https://it-chefs.com/cm/builds/full/cm-13.0-20160915-UNOFFICIAL-trunk.zip
[Miscellaneous Android Development] marcachas:
I can't dowload this version, un ota and link dont dowload. ):
[Miscellaneous Android Development] cool400:
Same here, download is aborting

Gesendet von meinem Elephone Trunk mit Tapatalk
[Miscellaneous Android Development] todoss:
I 've had the same problem yesterday, but today I successfully update over the OTA!
[Miscellaneous Android Development] Dininthedrider:
From 9.02 release 2d performance became really slow for me. Webpage scrolling, and 2d game interactions are lagging. Is there a workaround?
[Miscellaneous Android Development] marcachas:
Mee too, but reboot and work perfect. Good Rom, i detected bug in bright, up this alone to full birght. ):
[Miscellaneous Android Development] josoft86:
After installing the 09-15 version are no longer able to see if there are updates for this error, "The update check failled. Please check your internet connection and try again later", even if the internet connection works perfectly. Thanks for the great work you are doing
[Miscellaneous Android Development] ottmi:
I think I messed up the OTA server configuration right before I left for vacation. I think I've fixed it now, but will in anycase have a closer look once I'm back home. There won't be any updates anyway while I'm out of town ;)

I didn't notice any issues with 2D performance after the update, but as always it is possible that some changes upstream in CM or Android broke things..
[Miscellaneous Android Development] siljaer:
It's working now. Have fun! :)
[Miscellaneous Android Development] blahmartinblah:
My phone is working great now too :) Ottmi deserves a holiday!
[Miscellaneous Android Development] josoft86:
Ok all enjoy the holidays :laugh::laugh::laugh::laugh:
[Miscellaneous Android Development] Dininthedrider:
Thank you for the ROM!!

Now that CM13 is stable and bug free, is there any change for Resurrection remix 5.7.4 (like for Ark benefit: http://4pda.ru/forum/index.php?showtopic=692103&st=4260#entry53190996) :fingers-crossed:
[Miscellaneous Android Development] marcachas:
I see cm14 in this page, ¿work in trunk?

Really, the ROM by ottmi is perfect.