[ROM] CyanogenMod 10 (qwerty)

[cukierkas]

That is quite a lot of features in that app
I'll try to play with the settings, but really not sure it will help. Lets hope anyway
Regards.

Sent from my GT-I9003

 

[loSconosciuto]

I finally built my own CM10 with the 3.0 kernel. Actually, I've already done it long ago, but my CM10 builds with my 2.6.35 kernel simply outperformed it, until recently.

The ROM is not perfectly stable though. Here the list of the issues I encountered

• Backlight issues for some users (I actually don't have this problem, but I know the bug is there)
• USB transferred files are oftern corrupted (tried UMS, MTP and adb, no luck)
• MTP transferred files are saved in the internal SD, even if you copy them in the external SD (this is really weird)
• WiFi p2p is not implemented (I had to disable it to make WiFi work)
• Audio/video sync issues while recording videos @ 720p, along with frames and fps drops. Things are not that bad @ 480p, but not perfect.
• If you close the camera app while in video mode, the next time you'll open it, it will FC (I must have done something wrong while backporting it from CM-10.1. It also happens in my other CM10 builds)
• If you set as max freq 600MHz, because of the way I implemented power HAL, the max frequency will be set to 1GHz. No problems for the other frequencies. Delete /system/lib/hw/power.latona.so if this bothers you.
• Random hot reboots (that's the main problem for me now)
• You can't change the sensitivity of the touchscreen or the touchscreen. It's not implemented yet.

EDIT: power HAL is included, it's for ondemand and unlike my previous builds the CPU is boosted not so often. It's also used to limit the CPU frequency at 600MHz when the screen is off. DeviceParts was not correctly updated, it will let you select as boosting frequency 1.2GHz, which is not available.

This is just a test.
I can't say anything about battery life.
The ROM feels pretty good, it's as smooth as my other builds, but more responsive.
I didn't test Bluetooth.
I tested audio and video playback only to see if they work (they didn't), but not intensively.
The kernel is mostly like dhiru's, I just did some changes here and there (see my repos)
OC is not availble. I tried it, just for the sake of it, but I could get a stable device only at 1.1GHz. I didn't include the changes for it and I don't want to do it, at least for now.

I flashed the ROM directly on top of my cm-10-20130812-UNOFFICIAL-galaxysl.zip with no data wipes. You should be able to go back to that build with no wipes as well, but it's better if you take a backup, you know, just in case.

You can download the ROM from here: cm-10-20130814-UNOFFICIAL-galaxysl.zip


Why not CM10.1/2?
The answer is simple. I like CM10, it's faster, no jerky scrolling and it does all I need. Plus, there are other threads for CM10.1 and there will be other threads for CM10.2, while there are no threads for CM10.


UPDATE:
Got a SOD, or at least it looked like a SOD. I left the device charging tonight and this morning I couldn't wake it up. I forced a reboot keeping the power buttong pressed to get /proc/last_kmsg and it turned out that the device was awake, but nothing was shown on the screen nor the LEDs were turned on.
I'm not sure of this, but I probably forgot to disable the L3 OPP1 (see this), I was testing it. According to that commits it breaks DVFS, however I didn't notice any error in my logs.
I also noticed too many failed suspensions (PM: Device omap-sdp failed to suspend: error -1)

 

[cukierkas]

hello, thanks for update.
but for mean time I'll stick to flyongb. Just for bt. That app you told me last time didnt made any improvement. I played for two days, but didn't found any setting to improve bt sound quality.
I like your releases, it was my daily driver, but tired of bt problems and battery life. On gb I do have 6hrs of screen time, while on pre-last cm10 build was max 3,5
I'll sertainly wait for stable release, I do like your work. Thanks.

 

[klau7]

Can I flash this one over cm10.1 after wipe (data & system)?

Sent from my GT-I9003 using xda app-developers app

 

[loSconosciuto]

I'm having some issues with WiFi, the device get disconnected from Google services after some time spent with the screen off, even if it remains connected to the AP.
I rolled back to an older WiFi firmware version (R5.SP3.06) and the problem seems to be solved, but I'm not sure yet. The problem I'm having is probably due to my router.

If you are also having problems, try to flash TI-wl12xx-firmware-R5.SP3.06.zip. Even if it didn't solve the problem, I think I'll keep using this version.

hello, thanks for update.
but for mean time I'll stick to flyongb. Just for bt. That app you told me last time didnt made any improvement. I played for two days, but didn't found any setting to improve bt sound quality.
I like your releases, it was my daily driver, but tired of bt problems and battery life. On gb I do have 6hrs of screen time, while on pre-last cm10 build was max 3,5
I'll sertainly wait for stable release, I do like your work. Thanks.

No problem, use what better suits your needs.
I have a question though. It's been a long time since I used a stock ROM and now that you tried both my CM10 and recently moved to a stock ROM, I'd like to know how's the battery with CyanogenMod. I won't flash a stock ROM anytime soon to do a comparison on my own.
Without looking at the stats, at the end of the day, how different is the remaining battery between a stock ROM and CyanogenMod with the same usage?

Can I flash this one over cm10.1 after wipe (data & system)?

Yes. There's no need flash N different stock ROMs, format SD cards etc.
Reboot to recovery, flash the zip, do a data wipe (I doubt downgrades are expected) and then flash gapps.


I don't know if I'm the only one having troubles transferring big files with the USB cable, but make sure that the file you are going to flash is not corrupted. Usually when it happens CWM can't read the zip at all and it fails almost immediately.

EDIT
I know some of you had issues with the SD card which was not automatically mounted. If you had this problem and moved to my CM10 build, could you please tell me if the problem is solved? (this maybe fixed the problem, it's already included in my build)

 

[cukierkas]

Its really hard to say, everything depends on usage
With bt, 3g always on, about 20min to 1hrs of talking time per day, exchange email with push
, wifi at home. Sync about 20min per day. No texts. Skype texts max 20 mins. Autobrightness. That is average my daily routine.
With gb rom at night I still got about 50-40%, with cm10 less than 20
Battery is 2 months old.

If bt sound quality would be better and ram usage as on gb, I would stay on cm10, don't mind to charge every night, but on flyongb rom ram is always about 150-80 MB free and do fluid, as cm10 never was. Maybe ext4 formatting works so well? Or ram management scripts?
Losco, take a look to them, maybe than can be useful? Gb is fast and battery friendly, but cm10 rocks on eye candy stuff and user friendly handling

Flyongb scripts
http://speedyshare.com/M2q7A/external-sd.zip
Thanks to @LoLaTiOn

One more edit :
Losconosciuto, can you compose me a script, witch would keep app in memory if that is possible? Gb one. If that possible and would take only some minutes I'm total noob in Linux stuff. Local.prop doesn't work on gb, guessing that this rom lacks of compiled feature to implement app locking
I still need browser to be locked, but thanks to gb memory management, it killed not so often
Sent from my GT-I9003

 

[cukierkas]

Speaking more about battery. At this screen time, cm10 would have about 15-20% left. And if battery fells below 10%, it runs flat really fast. Gb holds it really better, even below 10%..
Just true observations, nothing personal.

Sent from my GT-I9003

 

[loSconosciuto]

I got another "SOD". I verified that it's not an actual SOD, "only" the screen and the touchscreen don't work. LEDs can be turned on, I can play sound through adb etc. I'm suspecting there are some issues while exiting from the off mode. I will investigate further.

Anyway, I made a new build: cm-10-20130816-UNOFFICIAL-galaxysl.zip. I did some changes to the both kernel and the ROM.
I ported some changes that Samsung did to the mmc driver in our 2.6.35 kernel. Part of them seem to be a power optimization (not sure of the effect), another part is probably to deal with some defective chips.
I also fixed power HAL, it wasn't doing anything in my other release except changing the max frequency when the screen was turned off. Also, you can now set as max frequency 600MHz.
If you don't want to boost the CPU, set from DeviceParts as boosting freq 300MHz. It will practically disable it.
I also re-included the scripts to fix the preview orientation in Skype and to lock apps in memory and as I wrote in my last post, I switched to the old WiFi firmware which seems to work better.

Last thing. I've noticed that there are not audio/video sync issues at 480p. Most likely the problem was caused by the hardware audio encoders which I had to disable to fix audio playback.

On GDrive you can find the patches I used.

If bt sound quality would be better and ram usage as on gb, I would stay on cm10, don't mind to charge every night, but on flyongb rom ram is always about 150-80 MB free and do fluid, as cm10 never was. Maybe ext4 formatting works so well? Or ram management scripts?
Losco, take a look to them, maybe than can be useful? Gb is fast and battery friendly, but cm10 rocks on eye candy stuff and user friendly handling

Flyongb scripts
http://speedyshare.com/M2q7A/external-sd.zip
Thanks to @LoLaTiOn

Thanks for the scripts, but I don't want to use them.
The difference between JB and GB is that GB is a 5 years old OS, less resource hungry than a year old OS.
Things are better with the 3.0 kernel, the ROM became more responsive and it doesn't slow down as much as with the old kernel after some hours of use.

Losconosciuto, can you compose me a script, witch would keep app in memory if that is possible? Gb one. If that possible and would take only some minutes I'm total noob in Linux stuff. Local.prop doesn't work on gb, guessing that this rom lacks of compiled feature to implement app locking
I still need browser to be locked, but thanks to gb memory management, it killed not so often

Not possible without framework changes.

Anyway, I don't know how reliable are the battery stats, that's I asked for the consumption without looking at them.

 

[cukierkas]

I can make a betterbatterystats statistic file if you wish to.

http://speedy.sh/pk4jX/BetterBatteryStats-2013-08-16-220547649.txt

Sent from my GT-I9003

 

[ageback]

loSconosciuto, thank you for your great work! But I encountered some problems when flashing cm-10-20130816-UNOFFICIAL-galaxysl.zip.
I was on CM10.1 alpha8. I wiped factory/data then flash your CM10.After reboot pass the start screen, I got screen malfunction. Then I took out the battery and did clean flash from DDLF2 FULL to cm-10-20130816-UNOFFICIAL-galaxysl.zip. But then I got boot stuck.
I really want to test your CM10 with kernal 3.0. Can you please help me?

 

[loSconosciuto]

I can make a betterbatterystats statistic file if you wish to.

http://speedy.sh/pk4jX/BetterBatteryStats-2013-08-16-220547649.txt

Thanks.

loSconosciuto, thank you for your great work! But I encountered some problems when flashing cm-10-20130816-UNOFFICIAL-galaxysl.zip.
I was on CM10.1 alpha8. I wiped factory/data then flash your CM10.After reboot pass the start screen, I got screen malfunction. Then I took out the battery and did clean flash from DDLF2 FULL to cm-10-20130816-UNOFFICIAL-galaxysl.zip. But then I got boot stuck.
I really want to test your CM10 with kernal 3.0. Can you please help me?

What kind of screen malfunction?

Stuck where? Splashscreen or bootanimation? Does the splashscreen ever disappear? Does the bootanimation ever start?

The kernel is mostly the same of the one included in dhiru's Alpha8. The only things that could have caused issues are the lower voltages I used, but those are the same voltages I used in my 2.6.35 kernels, or maybe that I re-enabled the L3 OPP1. I also changed the path of the internal SD while in recovery without doing some proper tests, but I don't think that's the problem, I simply replace few strings.

I'm sorry, but with no logs I can't help you that much, so the only suggestion I have is to retry to flash the ROM. In case it doesn't work, try to flash my ROM with the old kernel and then the one with the 3.0 kernel over that. You can do a data wipe later if you want.
If you can get any log, please give them to me (dmesg and logcat).


On a different note, I read here and there that sometimes the device loses the phone signal and a reboot is necessary to get it again. I think it happened to me yesterday and it looked like a kernel crash. Unfortuntely after the main crash happened, the WiFi driver kept throwing a warning filling the dmesg with the same message repeated over and over.

 

[ageback]

It's blurred screen, happened after the splashscreen. After taking out battery and reboot it stuck at splashscreen. Clean flashes also stuck at splashscreen.



Sent from my GT-I9003 using xda premium

 

[Siddhant Shankpal]

On a different note, I read here and there that sometimes the device loses the phone signal and a reboot is necessary to get it again. I think it happened to me yesterday and it looked like a kernel crash. Unfortuntely after the main crash happened, the WiFi driver kept throwing a warning filling the dmesg with the same message repeated over and over.

Yea, it does loose the phone signal sometimes & to get over that issue i switch on & then switch off Airplane mode. Signals come back to normal then.
And sometimes 2G data (EDGE) doesn't switch on, this issue need a reboot most of the time.
BTW I'm on Dhiru's 10.1 CM built.
Thanks!

Sent from my GT-I9003

 

[loSconosciuto]

cm-10-20130817-UNOFFICIAL-galaxysl.zip

I was informed that Bluetooth is not working. I'm sure I tried to turn it on at least once, probably it was one of my private builds. Anyway, I fixed it now. I also fixed the camera app, it won't force close anymore and I changed the number of the audio channels from 2 to 1 while recording videos. In this way you'll hear the recorded audio trakc from both the right and left channel, unlike before.

Sadly though, I had to revert this, omap-dsp was frequently failing to suspend because of that. Now ondemand is 10 times slower and because of that I made power HAL a bit more aggressive to minimize the lags. I think it's working quite decently.

It's blurred screen, happened after the splashscreen. After taking out battery and reboot it stuck at splashscreen. Clean flashes also stuck at splashscreen.

The blurred screen is weird, I can't even imagine how it looked like.
If the splashscreen doesn't disappear, it means that the framebuffer is not inizialized. That could indicate that the kernel crashes almost immediately, but usually when this happens the splash screen fades away and the device is rebooted.
I'm just guessing, but it could be the same thing that happened to spacebar2011 and erickkhhk, they couldn't flash my kernels from recovery, only Odin could do it. I don't know why.
If you want, here there's an Odin flashable kernel to test. You should be able to at least boot to recovery using the three keys combo.

Yea, it does loose the phone signal sometimes & to get over that issue i switch on & then switch off Airplane mode. Signals come back to normal then.
And sometimes 2G data (EDGE) doesn't switch on, this issue need a reboot most of the time.
BTW I'm on Dhiru's 10.1 CM built.
Thanks!

I guess mine was a different thing then, I couldn't switch to airplane mode, I tried it.
I don't know about 2G, I never use it, but it shouldn't be that different from 3G, which I keep constantly on.

 

[p1p3r]

....
I guess mine was a different thing then, I couldn't switch to airplane mode, I tried it.
I don't know about 2G, I never use it, but it shouldn't be that different from 3G, which I keep constantly on.

I got same issue many times on dhiru rom alpha8: no signal and airplane mode not switching. May be is not a kernel issue: other roms based on alpha8 never happened this.

 

[ageback]

I tried 0817 version(kernal 3.0). It still stuck at spashscreen, no matter base on CM10-0812(kernal 2) or DDLF2 clean. Sorry, I don't know how to catch log.
Now I stay on 0812-kernal 2.

 

[hjs89]

No problem, use what better suits your needs.
I have a question though. It's been a long time since I used a stock ROM and now that you tried both my CM10 and recently moved to a stock ROM, I'd like to know how's the battery with CyanogenMod. I won't flash a stock ROM anytime soon to do a comparison on my own.
Without looking at the stats, at the end of the day, how different is the remaining battery between a stock ROM and CyanogenMod with the same usage?

Hi loSco,

I'm always switching roms, actually my daily rom is x-gamerz, based on your qwerty work. Battery life using Android 4.x kernel 2 is about 20-30 % shorter than GB, but enough for a full day. With dhiru's kernel 3 is about 50% shorter, I don't use it as daily because I have to charge the phone two times per day.

I make few calls (maybe 1 each 2-3 days) but I use a lot whatsapp and web browsing. Usually I get 2-3 hours of screen time on, in GB usually one more.

 

[loSconosciuto]

The weird SODs keep happening. They happened only in the morning for now, after the device was left charging all night long. I'm sure they are not SODs though, even alarms are fired, something goes wrong with the screen and the touchscreen.
I decided to blame the off mode for this, so I tried to disable it when the device is charging and things seem to be better now. I don't mind about using a bit more power while charging if this can prevent issues. I'm not sure this workaround fixed the problem, I still have to try the kernel a bit more.
If you also had issues with the screen and the touchscreen, post about it.
EDIT: This is what I did.

I also decided to re-enable the automatic voltages calibrations as TI suggests (CONFIG_OMAP_SR_CLASS1P5_RECALIBRATION_DELAY=86400000) and I made ondemand fast again and power HAL less aggressive without causing failed suspensions.
I'm still not sure about what sampling rate it's better to use for ondemand, I'm currently trying 90us and it seems quite balanced, not too fast, not too slow. I didn't notice huge differences with lower values.

In addition, I stumbled upon this patch which allows to show the statusbar in fullscreen apps with a swipe gesture, I adapted it and included it in build. You have to enable it from the system settings.

The build including these changes is cm-10-20130818-UNOFFICIAL-galaxysl.zip


PS: I tried to overclock the CPU once again. I found that with SmartReflex disabled I can use the device at 1.2GHz. Honestly, I care more about SmartReflex, so, if I'll ever add the fifth OPP, it will probably be limited to 1.1GHz. Not that I feel the need to overclock the CPU. If you are interested in the changes:

• latona: add config entry to enable OPP5 (1100MHz)
• SmartReflex: Fix SR on OPP5 by computing the missing nValue

I tried 0817 version(kernal 3.0). It still stuck at spashscreen, no matter base on CM10-0812(kernal 2) or DDLF2 clean. Sorry, I don't know how to catch log.
Now I stay on 0812-kernal 2.

At least I know that the few changes I did to the updater are not the problem.

I got same issue many times on dhiru rom alpha8: no signal and airplane mode not switching. May be is not a kernel issue: other roms based on alpha8 never happened this.

It happened only once to me and that time I couldn't see what happened, but it looked like a kernel crash, even if I'm not sure.

Hi loSco,

I'm always switching roms, actually my daily rom is x-gamerz, based on your qwerty work. Battery life using Android 4.x kernel 2 is about 20-30 % shorter than GB, but enough for a full day. With dhiru's kernel 3 is about 50% shorter, I don't use it as daily because I have to charge the phone two times per day.

I make few calls (maybe 1 each 2-3 days) but I use a lot whatsapp and web browsing. Usually I get 2-3 hours of screen time on, in GB usually one more.

I still don't know how good the battery is with the 3.0 kernel, I started to use it as daily driver only recently and I haven't use the device that recently. However I didn't have a bad impression, it could be that my battery is so old that whatever I use I get a terrible battery life.

 

[cukierkas]

Losco, so what screen time you've got with kernel 3 on your device? My hands are niesing to try your miracle, but battery life, sods and bt holds me

Sent from my GT-I9003

 

[loSconosciuto]

Kernel update: kernel-cm-10-20130820-galaxysl-signed.zip

The battery is now charged up to 95% of its capacity (you'll see 100% though) and once that percentage is reached, the device will stop charging and it will wait for 90 minutes before re-starting (unless you bump charge). That means it's normal to see the battery discharging when plugged in.
The previous kernel were fully charging the battery. Note that we were already altering the percentages so that anything greater than 95% was shown as 100%, making 100% last a lot. The reason why we are doing that is that this should prolong the life of the battery.

I also got rid of the off-mode workaround I introduced in my last update, I want to see if the problem persists.

In addition, I fixed the suspension while in charge mode and I replaced the images with the original ones, maybe they were a bigger than those I used.

Losco, so what screen time you've got with kernel 3 on your device? My hands are niesing to try your miracle, but battery life, sods and bt holds me

Sent from my GT-I9003

I didn't have a single SOD, except for that weird thing which I don't consider as SOD and which is similar to your issue with the alarm not showing up. I got few hot reboots the first day I flashed the ROM, maybe the first couple of days, but it's no more happening.

Bluetooth related stuff has gone through a lot of changes, I can't say if it's better or worse.

Regarding the battery, I can't do a direct comparison with my kernel 2.6.35 because I didn't use the device so much lately and more importantly, I'm using WiFi a lot now. I had several issues with my old kernel and used to enable it only for browsing. Now I keep it enabled almost all the time saving a lot of battery. WiFi is one of the main reasons I switched to the new kernel.

That said, that's a screenshot from yesterday. 2 hours (and 5 minutes) of screen on time. That's not bad at all for me, I used to get less than this, WiFi saved a lot of battery and normally my battery lasts 12 hours or less, 10 hours sometimes.
The standby power consumption is really good as you can see, even with everything syncing in background.
3G browsing kills the battery as it always did and sadly it's one of the few things I do with this device. I think that the radio management is not as good as in stock ROMs, we don't even support fast dormancy. You can loose a lot of battery within a few minutes. The weird thing is that if you leave the device with the screen off after that, you won't lose anything for a while. You can see that in my screenshot, the last part of the plot.

I also think that apps have a greater impact on battery life now, and I'd say that's because of the better kernel drivers which use wakelocks in a better way (for example the total time of max17040-battery, which corresponds to the old samsung-battery, after more than 10 hours, is 3 seconds). If kernel wakelocks are no more keeping the device awake for hours, partial wakelocks will do that.