[ROM] CyanogenMod 10 (qwerty)

Search This thread

cukierkas

Senior Member
May 26, 2010
2,158
683
Final Question... there is no way to lock more than one app in memory by some hack or codes..? Just asking because i want it badly.. :(

Sent from my GT-I9003 using xda premium

Try to read last two pages one more time.

Speaking about alarm clock, after update it didn't worked properly, but setting side buttons to dismiss and not using increasing volume- after reboot worked. Now is all fine. Log cat don't shows anything wrong. Except wpa warnings :)
http://speedy.sh/5Naj8/alogcat.2013-07-23-23-19-11-0300.txt

Sent from my GT-I9003
 

loSconosciuto

Senior Member
Nov 21, 2011
765
2,817
cm-10-20130725-UNOFFICIAL-galaxysl.zip

  • Dalvik updates from cm-10.1
  • Various camera HAL changes
    ◦ Faster color conversion for the preview (thanks to nadlabak. This allowed me to increase the preview framerate while recording @ 720p)
    ◦ FFC preview cropped and rotated also in third party apps (still don't know what's wrong with Skype)
    ◦ Fixed crash with apps trying to set lower resolutions for the FFC
    ◦ General optimizations and code cleanup
  • No lags in DeskClock while scrolling lists of disabled alarms (I noticed the performance hit when I disabled a bunch of alarms)
  • Fixed DeskClock layout alignment
  • Use early_suspend to control the state of the modem [1]
  • Possibility to lock two apps in memory [2]

[1] I disabled this month ago because I had the impression that mobile data is less stable with it when you are in areas where there's not always signal, but I'm not sure of this and I want to try this again. If you have issues, please report.
[2] ATTENTION: if you previously locked an app, re-lock it following these instructions. I had to change the name of the prop. To lock two apps, you have to manually set the second prop using "setprop" from terminal emulator (setprop NAME_PROP VALUE). The props are "persist.sys.keep_app_1" and "persist.sys.keep_app_2".
I'm sorry, I did a sync without saving the changes. You have to lock the app manually with and you are allowed to lock only one app:
Code:
su
setprop persist.sys.keep_app com.example.name
The script doesn't work because it sets the wrong prop.

I still have to update my repos/patches, it's such a mess that I can't do it now.

@cukierkas
The navbar issue is known, I posted about it when I did this modification and wrote more or less why it happens. If you enable it using the prop or decompiling framework-res.apk, it will work perfectly. It's a limitation of my simple implementation, less annoying than having to reboot every time.

The fixed DeskLock was only intended to fix the layout alignment and with modifications I meant system modifications, such as freezing apps etc. My DeskClock is built from scratch with no errors, I fixed the code to make it compatible with my ROM. I didn't take the apk from CM-10.1 and included it in my zip. So technically it should work as good as in CM-10.1.
Anyway, there are no errors in your log. Those wpa_supplicant lines appear whenever Android wants to know the current signal intensity. Samsung like debug lines and unfortunately I'm using a prebuilt wpa_supplicant taken from a stock ROM.

@sgatechwork
Happy now? If you want more learn how to build, I won't do it.
 
Last edited:

shaktishekhar

Senior Member
Apr 10, 2012
664
695
Mumbai
sgatechwork.blogspot.in
yes am soo happy now am dancing :D but how to lock 2nd app :(

---------- Post added at 04:44 PM ---------- Previous post was at 04:35 PM ----------

cm-10-20130725-UNOFFICIAL-galaxysl.zip

  • Dalvik updates from cm-10.1
  • Various camera HAL changes
    ◦ Faster color conversion for the preview (thanks to nadlabak. This allowed me to increase the preview framerate while recording @ 720p)
    ◦ FFC preview cropped and rotated also in third party apps (still don't know what's wrong with Skype)
    ◦ Fixed crash with apps trying to set lower resolutions for the FFC
    ◦ General optimizations and code cleanup
  • No lags in DeskClock while scrolling lists of disabled alarms (I noticed the performance hit when I disabled a bunch of alarms)
  • Fixed DeskClock layout alignment
  • Use early_suspend to control the state of the modem [1]
  • Possibility to lock two apps in memory [2]

[1] I disabled this month ago because I had the impression that mobile data is less stable with it when you are in areas where there's not always signal, but I'm not sure of this and I want to try this again. If you have issues, please report.
[2] ATTENTION: if you previously locked an app, re-lock it following these instructions. I had to change the name of the prop. To lock two apps, you have to manually set the second prop using "setprop" from terminal emulator (setprop NAME_PROP VALUE). The props are "persist.sys.keep_app_1" and "persist.sys.keep_app_2".
I'm sorry, I did a sync without saving the changes. You have to lock the app manually with and you are allowed to lock only one app:
Code:
su
setprop persist.sys.keep_app com.example.name
The script doesn't work because it sets the wrong prop.

I still have to update my repos/patches, it's such a mess that I can't do it now.

@cukierkas
The navbar issue is known, I posted about it when I did this modification and wrote more or less why it happens. If you enable it using the prop or decompiling framework-res.apk, it will work perfectly. It's a limitation of my simple implementation, less annoying than having to reboot every time.

The fixed DeskLock was only intended to fix the layout alignment and with modifications I meant system modifications, such as freezing apps etc. My DeskClock is built from scratch with no errors, I fixed the code to make it compatible with my ROM. I didn't take the apk from CM-10.1 and included it in my zip. So technically it should work as good as in CM-10.1.
Anyway, there are no errors in your log. Those wpa_supplicant lines appear whenever Android wants to know the current signal intensity. Samsung like debug lines and unfortunately I'm using a prebuilt wpa_supplicant taken from a stock ROM.

@sgatechwork
Happy now? If you want more learn how to build, I won't do it.

:( again am sad only 1 app :(((
 

cukierkas

Senior Member
May 26, 2010
2,158
683
thanks, losco, I'm happy you finding time for such outdated phone :)
about camera-external-location zip. I need to install everytime I'm updating the rom. Can you hook those settings to stock one? thanks.
any news to bluetooth sound quality? maybe GB value pack's bt libraries can be used? At gb everything was super fine. Not rushing, just wondering.
one more thanks, you are fine dev ;)
 

Sine.

Senior Member
Jan 5, 2011
623
391
😁
yes am soo happy now am dancing :D but how to lock 2nd app :(

---------- Post added at 04:44 PM ---------- Previous post was at 04:35 PM ----------



:( again am sad only 1 app :(((
How about writing complete sentences without all these abbreviations? (Not easy to read)
How about not quoting the complete post posted just before yours?
How about reading loSconosciuto's answer to your repeated question? :rolleyes:
@sgatechwork
Happy now? If you want more learn how to build, I won't do it.

Anyway, thanks loSconosciuto for your work :D :victory:
 
  • Like
Reactions: cukierkas

cukierkas

Senior Member
May 26, 2010
2,158
683
hey, observed funny thing, but I think it should be that way :)
I like my own created melodies, so I manually pushing them to system/media/audio/ringtones with 644 permissions.
after rom upgrade, all system is rewritten, am I right? So all my melodies are gone and I need to play that game again. I'm guessing that is normal and there is no need to play this game again, only to hook melodies from media player or place it in internal memory card and reassign again :) or to add folder media/ringtones to internal and that will accessed after any upgrade?

Regards
 
Last edited:

ALoGeNo

Senior Member
Dec 3, 2007
121
56
android-x86.sceners.org
Oh my GOD..! @loSconosciuto strikes again :D nice news!! hehe, Ok I'm just now downloading your last build (cm-10-20130725-UNOFFICIAL-galaxysl.zip), and looking in the misc folder I was see an update/fix named libcamera-fix3-cm10.1.zip, we need also install this fix?.

Thank you very much for this new build loSco, your extra-work is much apreciated!. :highfive:
 

loSconosciuto

Senior Member
Nov 21, 2011
765
2,817
cm-10-20130726-UNOFFICIAL-galaxysl.zip

Changes:
  • Camera HAL: fixed preview heap usage (third party camera apps should work better)
  • Possibility to lock two apps in memory (maybe, I didn't test it) [1]
  • Android 4.2 Gallery/Camera [2]
  • Brightness no more set to the dim level if lower than it (this was pretty annoying while reading in dark rooms)
  • UPDATE: Try Bluetooth, I made a change related to it.

I wanted to do other changes, but I'll probably want be able to do anything for a while, so I decided to post this since it was already built.

I made this build odexed, just to better use the space available. There should be enough space for gapps and all the system files in /system (EDIT2: now that I think of that, odexed builds are not that different in terms of system space used compared to deodexed builds).
Manually wipe the dalvik cache to free up some space in /data.

[1] ATTENTION: if you previously locked an app, re-lock it following these instructions. I had to change the name of the prop. To lock two apps, you have to manually set the second prop using "setprop". The props are "persist.sys.keep_app_1" and "persist.sys.keep_app_2".
[2] Everything seems to work, I tested voice shutter (gapps required most likely), software HDR (slow and not so "wow"), panorama etc... EDIT: rarely I get a null pointer exception. When it happens, the preview is not shown and if you close the app it will FC. Just reopen it and it will work just fine. I'll try to understand why it happens.

If you hate the shutter sound like me, there's a prop to "easily" disable it
Code:
su
setprop persist.camera.shutter.disable 1    #0 to re-enable it


@cukierkas
I guess you won't need to flash the modded Galley anymore. And no, GB stuff is not helpful, I need source code, not built libraries.
The ringtones should go into /sdcard/Ringtones or /emmc/Ringtones.

@marras
I'd love to use the updated drivers, but the last time I tried nothing worked, but it was a while ago.

@ALoGeNo
Nope, libcamera-fix3-cm10.1.zip was an attempt to port some of my HAL changes to CM-10.1, but I didn't test it properly and preferred not to mention anything about it.

@sgatechwork
I got it, you want to lock more apps, there's no need to post over and over the same thing. I just forgot to update the patch, it could happen when you have around 200 patches. Learn how to build and you'll have whatever you want whenever you want.
I wrote the props to set, lock the second app with terminal emulator.
 
Last edited:

TTMaster

Senior Member
Apr 8, 2013
166
299
Gandía
cm-10-20130726-UNOFFICIAL-galaxysl.zip

Changes:
  • Camera HAL: fixed preview heap usage (third party camera apps should work better)
  • Possibility to lock two apps in memory (maybe, I didn't test it) [1]
  • Android 4.2 Gallery/Camera [2]
  • Brightness no more set to the dim level if lower than it (this was pretty annoying while reading in dark rooms)
.....

Happy holidays
Thanks for your great work :good:
 

Gondya bhau

Senior Member
Jan 28, 2012
481
233
Mumbai
Commands:
Code:
lockapp                    [COLOR=GREY]#show current locked app[/COLOR]
lockapp com.example.name   [COLOR=GREY]#lock com.example.name[/COLOR]
unlock                     [COLOR=GREY]#unlock current locked app[/COLOR]
Reboot required to apply the changes. You have to run "su" first, if you forget, the scripts will tell you to do it.
You have to run the command only once, unless you do a data wipe.

sorry for a noobish question but could anyone tell me how to lock this launcher : Launcher8

https://play.google.com/store/apps/details?id=com.lx.launcher8&hl=en


i searched in the Android, data file and there isnt anything such as com.launcher8

there is a Launcher8 folder in my sdcard having stuff like cache,etc...thats it...so how do i lock it ?

will simply typing "lockapp launcher8" do the trick ?

thanks :laugh:

EDIT :

* on the latest version, bluetooth worked....albeit a bit slow (which could be due to the blackberry it was paired with)
* i am assuming that on wiping cache, the optimizing does not occur for the system apps anymore ( being odexed )..either that or half my apps just went missing :p...just kidding
 
Last edited:

Siddhant Shankpal

Senior Member
Aug 8, 2011
272
100
Hyderabad
sorry for a noobish question but could anyone tell me how to lock this launcher : Launcher8

https://play.google.com/store/apps/details?id=com.lx.launcher8&hl=en


i searched in the Android, data file and there isnt anything such as com.launcher8

there is a Launcher8 folder in my sdcard having stuff like cache,etc...thats it...so how do i lock it ?

will simply typing "lockapp launcher8" do the trick ?

thanks :laugh:

Go to launcher 8 'app info' from app manager, there u may get such content of that launcher under the name of the app. I'm not sure though.:p

Sent from my GT-I9003
 

cukierkas

Senior Member
May 26, 2010
2,158
683
Guys, same gplay link says the process name, com.lx.launcher8

Goona try this tom tomorrow, now short with battery without charger :)
Thanks losco ;)

Sent from my GT-I9003
 
  • Like
Reactions: Gondya bhau

ammar786

Senior Member
Dec 30, 2011
1,036
1,133
Mumbai
Hey,

I just installed the latest version. Everything's working fine, except USB Debugging. I can't get the phone to be detected in Debug mode. After connecting the phone, I get the following in my device manager.

5n09uMl.png


Ofcourse that means the drivers didnt get installed. I tried reinstalling them from windows update, but got the same result. Any way to fix this?

EDIT: I downloaded the latest SAMSUNG USB DRIVERS and installed them. Now everything's fine. Thanks. :)
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 95
    Here is where I'll post my CM10 builds.
    qwerty was the name I gave to the kernel I used to post here before I started to post entire ROM builds.

    This is based on the amazing dhiru1602's work, big thanks to him.

    Dowloads:

    You can't resume downloads with GDrive. If you prefer other hosting websites, you can use the direct link of my builds to remotely upload them somewhere else. Dev-Host allows you to do that and allows you to resume downloads. Feel free to mirror my files.

    Sources:

    Please, read carefully the whole post.

    There are two different versions of the ROM. One is using the kernel 3.0, the other the kernel 2.6.35. Read the known bugs and flash the one you prefer.

    I did some changes to this CM-10, I updated it and added some extra features such as inbuilt SD swap (Settings > Storage > Use external storage), possibility to show the navbar without rebooting (System > Power menu > navbar and enable it from the power menu. It doesn't work perfectly, keyboards and notification panel can go behind it) possibility to limit the number of background apps and other handy options.
    I also backported some performance patches and misc fixes from CM-10.1 and some apps: Trebuchet, Apollo, Gallery (camera), Clock, CM File Manager and Superuser.

    CyanogenMod 10 - kernel 3.0

    Known bugs:
    • Backlight issues for some users: the screen backlight will automatically turn on when it's supposed to stay off.
    • Audio/video sync issues while recording videos at 720p, along with frames and fps drops.
    • Rare reboots. If they happen, post the content of /proc/last_kmsg.

    CyanogenMod 10 - kernel 2.6.35

    Known bugs:
    • Missing HW composer.
    • WiFi doesn't work perfectly. Some users report continuous disconnections or problems connecting to netowroks. Try to use a static IP in case you have problems.
    • Native USB tethering doesn't work. Use a third party app (tested: android-wired-tether).
    • The inbuilt Wi-Fi hotspot can be used only once, sometimes more, and after that a reboot is required to use it again. You can though use this modified version of android-wifi-tether, reboots are not required.
    • HD video playback suffer low framerate issues.
    • The 720p preview framerate is intentionally limited, especially while recording. The recorded video is (almost) fine.
    • There are sometimes lags in the preview while video calling with the front facing camera
    • Poor bluetooth headset sound quality. (I don't own a bluetooth headset, hence it's very hard for me to find the problem) - flash libaudio-BT-NR-fix.zip.


    Release changes:
    Code:
    Look for the name of the zip in this thread to find its changes. This is no more updated.
    ...
    20130425: Camera HAL updates. Removed background apps limit. Use the modified dev settings to choose the number of background apps.
    20130416: Camera HAL: experimental changes
    20130407: Partially working WiFi tethering (perfect with [I]android-wifi-tether[/I])
    20130402: Several kernel changes, UMS regression fixed
    20130329: Video pillarbox. Regression: UMS requires adb
    20130326: Optimized build
    20130320: SSID fetch fixed
    20130319: Better wpa_supplicant support: WiFi scan and disconnecting bug fixed. Missing WiFi signal intensity fixed.



    Instructions

    Stock ROM / CM7 / CM9 / CM10 Alpha3 (or older):
    dhiru1602 said:
    IMPORTANT! READ BEFORE FLASHING THIS RELEASE!
    1. This ROM will wipe data due to different partitioning. The device would reboot while flashing and resume again.
    2. Once on this ROM, the most effective way of going back to any other ROM would be to repartition from Odin.
    3. While converting the filesystem, your efs that has your IMEI is backed up to /emmc/backup/efs. Keep a backup on your PC just in case.
    4. Incase if you don't get a network signal, check if your IMEI and Baseband are proper. If not, go back to stock and try again.
    5. Do NOT use Odin to flash Modems. Due to different partitions, Odin will screw up your existing MTD setup.
    1. Stock ROMs only: Make sure you have CWM. Flash a custom kernel otherwise
    2. Download the zip of the ROM and save it into the internal SD or the external one (*)
    3. Reboot to recovery
    4. Flash the downloaded zip
    5. optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
    6. optional: Flash Google Apps (for Android 4.1.2, many things will break otherwise)
    7. Reboot
    (*) While flashing, the device will reboot and you'll see a different recovery after that.
    If the zip is inside the internal SD, the flash will re-start automatically after the reboot.
    If the zip is inside the external SD, you have to re-start the flash manually re-flashing the zip. If you don't do that, only recovery will work until you flash the zip.


    CyanogenMod 10:
    1. Download the zip of the ROM and save it into the external SD or the internal memory
    2. Reboot to recovery
    3. Flash the downloaded zip
    4. optional: Flash Google Apps (if you have already flashed them once, you can skip this step)
    5. Reboot
    Data wipes are mandatory only if you are not using CM10, it's not required otherwise.
    It doesn't matter if you are going to flash the version with the 3.0 kernel and you are using the other, it should work.



    CyanogenMod 10.1/10.2:
    1. Download the zip of the ROM and save it into the external SD or the internal memory
    2. Reboot to recovery
    3. Flash the downloaded zip
    4. optional: Flash Google Apps
    5. optional: Flash mobiledata_off.zip if you want mobile data off during the first setup
    6. Wipe data/factory reset
    7. Reboot
    Downgrades are probably not expected, that's why you need to do a data wipe.


    Important note:
    The modem is always replaced with XXLE4 modem when this ROM is flashed over a stock ROM, CM9 or CM10 Alpha 3 (or older).
    You can easly replace it. Take modem.bin from the tar of a stock ROM, place it in /radio overwriting the existing one and reboot. This is required only once, modem.bin is never replaced while updating the ROM. I9003L must do this, I9003 users can use the included modem, but it's better to use the modem made for your region.



    Useful informations
    • The latest versions of Instagram are not working due to a problem with related to the GPU binary blob. Instagram 3.4.0 is the latest working version. Probably every device using the same binary blob is affected (Optimus Black for example). You can download a modified version from here that will allow you to login.
    • The latest versions of Skype do not work properly, the preview is stretched and wrongly rotated. Use Skype 2.9.0.315 or see this post.
    • LEDs are not supposed to blink when a new notifcation arrives. They'll light up, but they won't blink. Making them blink would prevent the device from entering deep sleep.
    • (3.0 kernel) Once the battery is fully charged, it will start discharging and it won't be recharged automatically if at least 90 minutes have passed. You can forcefully charge it by unpluggin and re-pluggin the cable. This is an intended behaviour, charging the battery continuosly to keep it at 100% can shortnmyself toer its life.
    • This ROM allows you to force two apps to stay in memory. See this post for more info.
    • I made possible to toggle the navbar state directly from the powermenu modifying the existing expanded desktop feature, however it's not working perfectly. The navbar can go over the notification panel and the keyboard while in landscape. However it works as expected if you enable the navbar by setting qemu.hw.mainkeys or modding framework-res.apk. I have no intention to "fix" this as I can't see the utility of the navbar on our device.
    • (3.0 kernel) For some reason when the screen is turned off during a call by the proximity sensor, if enough time has passed it won't be turned on automatically. You can wake the screen immediately by pressing the home button or the power button or you can increase the backlight timeout from the settings. That will make the proximity sensor work for longer (I'm not sure, but I think the proximity sensor stops working exactly after this timer has expired). this problem is maybe solved.
    • FM radio is available through third party apps, such as Spirit FM
    • "Native" 3G video calls are not supported and most likely never will, flash a stock ROM if you need them. GTalk, Skype and all the other apps works though.
    • (3.0 kernel) if you lost your IMEI, WiFi will probably not work. See this for more info and instructions to fix the problem. No more required.
    • (3.0 kernel) part of the RAM is reserved. You'll see that we have 442MB 454MB of RAM, that's fine, the missing RAM is not really lost, it's still used.
    • If the keyboard keeps crashing, you probably flash the wrong gapps.
    • The magnetic sensor sometimes reports wrong values. When it happens, the field intensity is very high. This was observed with the 3.0 kernel, but probably the same thing happens with a 2.6.35 kernel.
    • (3.0 kernel) my SD card (it's probably a cheap SD card) is not working properly and I often have corrupted files. It worked fine with the kernel 2.6.35, so if you often have corrupted files, try a different SD card or use the old kernel.
    • Weird activity in standby? Read this.
    • (3.0 kernel) 1.2GHz is not stable on every device. I had to disable SmartReflex because it was causing crashes on my device. This means that the voltage of the OPP5 is locked the value I chose is not universally good. I'd prefer not to increase it more, if you have too many reboots, don't overclock. WARNING: don't tick "Set on boot" unless you are sure your device can handle OC. f you are stuck in a bootloop, flash disable_opp5.zip.
      In case the max frequency is 1.1GHz, then SmartReflex is enabled and the option in DeviceParts has no effect.

    If you find a bug not listed, please report.
    Post as many informations as possible, ways to reproduce it and logs.
    You can easily grab (almost) all the logs I need by pressing vol down, vol up and power at the same time ("recent" builds only). LEDs will blink and /storage/sdcard0/logs_qwerty/log_DATE.txt will be created. In case the memory is not ready, you'll find the files in /data/logs_qwerty/log_DATE.txt.



    The standalone kernel is no more mantained. Flash the ROM instead.
    Kernel - 2.6.35


    After months of use, I decided to publicly release my kernel.

    This is for CyanogenMod 10 Alpha 4.

    It's based on the GB kernel sources released by Samsung (GT-I9003_GB_Opensource_Update2.zip), modified (mostly by dhiru1602) to work with CyanogenMod.

    Because of my lack of fantasy I named it "qwerty". It sucks, but at least it's easy to remember.


    Main features:

    • XDA_Bam's code and fixes:
      ◦ 5 OPPs
      ◦ Booting at stock speed (1000MHz)
      ◦ Slight undervolt (3%) on all OPPs
      ◦ Home button double presses fix
      ◦ Lowered processor transition latency
      ◦ Stable Bluetooth connections
    • Modified light sensor driver: [1]
      ◦ Disabled hardcoded filter. CyanogenMod has its own filters, enable it from the settings.
      ◦ Dynamic polling interval
      ◦ Code cleanup
    • Modified battery driver [2]
    • CPU Governors:
      ◦ Ondemand (default)
      ◦ SmartassV2
      ◦ Conservative
      ◦ Performance
    • I/O schedulers:
      ◦ Deadline (default)
      ◦ Noop
      ◦ CFQ
      ◦ SIO
    • Toggable FSync
    • Fixed always ON LEDs bug when used for notifications only
    • VPN networks support (not tested)
    • Slightly increased touchkeys sensitivity (from 45 to 35)
    • Other minor changes and optimizations


    Downloads:
    UPDATE: USB composite is still a bit messed up. Windows can't recognize the phone when RNDIS (USB tethering) is enabled (working fine with Linux).
    If you need RNDIS, flash this kernel release or the previous one.


    Additional zips:

    Changelog:
    Code:
    22/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.1...v4.0"]v4.0[/URL]
    02/04/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v3.0...v3.1"]v3.1[/URL]
    01/03/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.1...v3.0"]v3.0[/URL]
    12/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v2.0...v2.1"]v2.1[/URL]
    09/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/compare/v1.0...v2.0"]v2.0[/URL]
    08/02/13: [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/commits/v1.0"]v1.0[/URL] - Initial release

    Notes:

    [1] I made it compatible with the prebuilt libsensor included in CyanogenMod, but I'm using my own libsensor and maybe I didn't test this kernel with the stock one for long enough. I hence added my libsensor, just in case. If you want to restore the original libsensor, simply remove /system/lib/hw/sensors.latona.so.

    [2] You can modify "samsung-battery" wakelock length through DeviceParts. By default it behaves like the original module. If you see "Android System" or anything else eating your battery with no reasons, increase the delay or restore the default one.

    [3] DeviceParts.apk (System Settings > Advanced) is included because of some additional settings useful when this kernel is used. I'm not a Java dev, so it's probably not perfect, but it works quite well. I took pieces of code from other devices (mostly Crespo, Aries and S2). The source code is available, suggestions are more than welcome.

    [4] Power HAL will make the CPU jump to a certain frequency (I set 800MHz) whenever Android requires it (when the screen is touched for example). Power HAL will also limit the max freq to 800MHz (my choice, not too fast, not too slow) when the screen is off. You can change the boosting freq from my custom DeviceParts. CPU frequencies changes (See XDA_Bam's thread for more info about variable overclocking) are not expected. If you don't like it, simply remove /system/lib/hw/power.latona.so. Few more lines about power HAL here.

    [5] hostap and tiap_drv.ko make WiFi tethering possible using this modified version of android-wifi-tether.

    Special thanks to dhiru1602 and XDA_Bam for their awesome work.
    30
    New build.
    I tried to fix WiFi hotspot using some patches taken from here.
    I've managed to make it work perfectly through a modified android-wifi-tether, however the inbuilt one works only once, sometimes twice and after that a reboot is required to make it work again.

    The kernel is mostly the same, I just added the support for MSS clamping (CONFIG_NETFILTER_XT_TARGET_TCPMSS) to support all the features of android-wifi-tether, there's no need to provide a separate zip.

    Downloads:

    Use the inbuilt hotspot only if necessary, otherwise use the app.

    Here the patch for android-wifi-tether (I've just noticed I made a mistake, it won't work correctly with stock ROMs).

    Big thanks to the CyanogenDefy team.
    29
    Changes:
    • Fix up notification LED behaviour (1, 2, 3. You have to pull down the notification bar to turn LEDs off)
    • MediaProvider changes from 4.2 (scan external SD on boot, wakelock release fixed [according to the commit message])
    • svnet wakelock control (DeviceParts)
    • Expanded Desktop => Navbar (the option is in the power menu, but you have to enable it from the settings)
    • freetype + adobe cff (more info). Not a big difference unlike my previous changes, but I just had to cherry-pick the patch.

    Downloads:
    cm-10-20130519-UNOFFICIAL-galaxysl.zip

    There's a little issue when the Navbar is enabled through the power menu. Fixing it is a bit complex and I'm not going to port the changes to do that from cm-10.1. Basically the size of the window is not recalculated and apps are not reloaded. This makes the notification panel go behind the navbar, same for the recent apps list. Maybe there are some other issues, I don't know, I just verified that the normal behaviour is unchanged.
    If you always use the navbar because your softkeys are broken, enable it decompiling or using the prop as you've always done. In this way, it will behave properly (I didn't try).
    I sadly discover that it's not possible to add custom app shortcuts to it, it's just a waste of space for me like this, but I won't probably modify it to allow this.

    Note: by defauly the action menu is never shown. If you want it, you have to enable it from Settings > System > Hardware keys >
    Show action overflow (usually this menu is hidden if the navbar is enabled and the action menu is always shown)

    EDIT: I updated my public repos and my patches here, including the device and kernel changes not on Github yet.



    Another nice feature would be to tie the wakeocks to profiles, so that, ie. at home, where I have very poor Phone coverage I could rise the samsung-battery etc. But I do not know if this is up to you...
    That's something a bit too complex. For something like that you could use external apps (such as Tasker) and shell commands to change the durations of the wakelocks, but I don't know how much they are integrated with the inbuilt profile system, I guess not much.

    wanna make a suggestion for a navbar option in the next build.. could that be possible? :eek:
    I've already done it time ago, but I had some little but annoying issues I have now solved.

    Oh and another thing, when you swap memories using the Storage Configuration is settings, Mass Storage only shows Internal Memory and not the SD Card. Used to never happen when I used to flash Lola's Swap SD and swap from there.
    That setting shouldn't be the problem. If you are using an old kernel release or build, make sure USB debug is enabled (dev settings).

    Sorry losconosciuto, but what is "dmesg" ?

    Edit: attach dmesg.txt
    The error seems to be:
    Code:
    unregister_netdevice: waiting for tiwlan0 to become free. Usage count = 1
    I don't know why this is happening. It's like as if the WiFi interface is still used. See if when the toggle is stuck tiwlan_drv.ko is still loaded, running from terminal emulator:
    Code:
    lsmod
    If you see tiwlan_drv, it means the driver is still loaded and it's waiting for tiwlan0 to be unloaded. I honestly don't know what's happening and it never happened to me. I did a quick search and found a similar problem which was related to ipv6. That was probably a particular situation, but if you are not using ipv6, disabling is of no harm. Flash this, it will create /data/local/userinit.d/disable_ipv6, which is just an init script. Delete it if needed, it's preserved when the ROM is updated.
    27
    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)
    23
    This is still my daily driver.

    For your information I started to work on the 3.0 kernel more or less since Dhiru got WiFi working so that I could get some logs. I worked on it more than what it seems.

    I just don't have much free time lately to update this ROM. I'm still surprised that I've been able to provide constant updates for months considering that the code of CM10 was frozen when CM-10.1 was released (I manually backported most of the changes from it).
    There's not much left to do: WiFi requires way too much efforts to get fixed properly, same for all the other major bugs of this ROM. There's a reason why Dhiru dropped the old kernel and started to work on the new one. I opened this thread to give you something a bit better in the meantime.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone