• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM] CyanogenMod 10 (qwerty)

Search This thread

loSconosciuto

Senior Member
Nov 21, 2011
765
2,817
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.




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.



  • 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.


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.
 
Last edited:

Hetalk

Senior Member
Sep 30, 2011
3,021
3,135
Ahmedabad
Wow. I'll flash it for sure.
Thanks for sharing.
Update:
Flashed and it works just fine. Just changed max freq to 1200.
Deviceparts looks very professional as well.
 
Last edited:

vishal24387

Inactive Recognized Contributor
May 11, 2011
3,936
1,976
34
Solapur, Maharashtra
Hats off to u buddy. Also kernel name is really good buddy. Dont worry about that :)
Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.
 

imjustafq

Senior Member
Nov 4, 2012
456
185
Ipoh
Re: [KERNEL][CM10] qwerty [08/02/13]

have any issues of wifi connections? like always dc.. and got any problem connecting back?

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

Hetalk

Senior Member
Sep 30, 2011
3,021
3,135
Ahmedabad
  • Like
Reactions: imjustafq

Hetalk

Senior Member
Sep 30, 2011
3,021
3,135
Ahmedabad
^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here. :)
 

rodero95

Senior Member
Jul 11, 2012
307
1,688
Re: [KERNEL][CM10] qwerty [08/02/13]

How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.

Sent from my GT-I9003 using xda premium
 

erickkhhk

Senior Member
Aug 19, 2011
60
3
Sony Xperia XZ3
Razer Phone 2
Re: [KERNEL][CM10] qwerty [08/02/13]

^ Did you flash kernel, then wipe cache/dalvik ... if yes try fixing permissions and see if it works. Else, post in the slimbean thread ... Lolation might be able to advise on how to make it work. I see he did thank the OP here. :)

i post here becoz i wanna flash this kernel:) will try what u say later, thx

Sent from my U9GT2 from moage.com using xda premium
 

Hetalk

Senior Member
Sep 30, 2011
3,021
3,135
Ahmedabad
^ You'll need to wait for users to get thru a battery cycle to report battery drain. I did charge my phone to 100% after flashing qwerty .. so will report my experience tomorrow.
 

imjustafq

Senior Member
Nov 4, 2012
456
185
Ipoh
Re: [KERNEL][CM10] qwerty [08/02/13]

just flashed this kernel.. on top of my cracker that i am using previously.. no problem on boot.. upgrading apps as usual.. ive noticed the speed, scrolling and such.. its faster than cracker .. the speed of gb is there..gonna test for some time.. thanks.. via slimbean 3.1 A4..

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

LoLaTiOn

Senior Member
Feb 2, 2012
2,652
9,124
Tours
I am pleased thank you very much !!!

Governor smartassV2 and IO Scheduler deadline (reputable boost daily)
Mini CPU 300/1000 is an exellent choice (I guess the hotboot fix)
it's just what I need ^^

Thank you for taking us solicitous
 
Last edited:

wee2wee

Senior Member
Oct 24, 2012
124
33
Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?
 

loSconosciuto

Senior Member
Nov 21, 2011
765
2,817
Request : Sorry but I am not exactly getting power HAL description. Can u please explain me a little bit.
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decisions mostly depend on the current CPU load: high load -> high freq.

What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).

I think it's part of the project butter.

The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.

Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).

By the way I updated ondemand, it's faster than in the original kernel.

Suggestion : Can u add SIO schedular? For me smartassv2 (thanks for adding it) with sio works really well.
Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.

have any issues of wifi connections? like always dc.. and got any problem connecting back?
All our kernels based on the sources released by Samsung use a prebuilt module for WiFi. Dhiru tried to use the opensource driver, but it didn't work.
This prebuilt module, taken from our stock ROMs, requires a prebuilt and modified wpa_supplicant which is not completely compatible with Android 4.0+ (Samsung didn't give us the changes required to make the opensource one work). To make things worse there's dhcpcd, we have to use an old version because of the old wpa_supplicant.
In other words: it sucks.
With some access point there are no issues, with others WiFi works, but not so well and with some others nothing works.
EDIT:
Now that I think of that, there are maybe some differences when this kernel is used. I took the prebuilt module from XXLE4 instead of taking it from EDIT2: XXKPM
The warning message I get the first time I turn WiFi (maybe it happens even with the other module, I didn't try it) on suggests me that something was changed in XXLE4, but I don't know if this is a good thing or not.

I am now on slimbean rom, please kindly advise a proper flash procedure becoz I always stuck on the Samsung splash screen …
I'm starting to think the problem is CWM. For now only you and spacebar2011 had issues. I will PM you something when I'll have some free time to find the problem. If nothing works, I'll just give you the tars to flash the kernel with ODIN as I did with my signal fix kernel.

@Hetalk
Thanks for trying to help, but he is a peculiar situation. The problem is not the updated blob or a wrong flash, he (and spacebar2011) tried to flash my signal fix kernel several times over a clean CM10 with no success.

How's this kernel's battery drain? Is it as good as alpha 11 kernel?
I'm so pleased with alpha 11 but I'd love to switch to this kernel.
Dunno, battery life had never been exceptional for me. If you use your phone a lot, any kernel will give you a bad battery life. You can see differences only if you keep your phone most of the time in idle, with mobile data disabled.

Thank you for the kernel...I'm on Dhiru's CM10 A4 with Alpha 11 kernel, now switched to this kernel, I do not find "DeviceParts" installed..is it normal?
As I wrote in note [3]:
DeviceParts: System Settings > Advanced

It's not in the app drawer.
 
Last edited:

vishal24387

Inactive Recognized Contributor
May 11, 2011
3,936
1,976
34
Solapur, Maharashtra
As you may know, what a CPU governor does is to decide when the current frequency needs to be changes and what's the target frequency. These decision mostly depends on the current CPU load: high load -> high freq.

What power HAL does is to require a high CPU frequency regardless the load. This mostly happen on user interactions (ie: the screen is touched)
Its aim is to provide a smoother experience, because basically it's trying to predict high CPU loads. The downside is that sometimes the CPU is boosted for no reasons.
For example if you touch the screen to scroll a page, when the scrolling starts the CPU is already at a high freq and there won't be probably initial lags. If you tap the screen, just for the sake of it, the CPU will be boosted for no reasons (by default a CPU boost will last 500ms).

I think it's part of the project butter.

The only governor with a boostpulse interface between those included is ondemand. The other governors included most likely will never have a boostpulse interface.

Try to use ondemand with and without power HAL. You can "see" the difference with CPU Spy. 800MHz will be used a lot when power HAL is present (you can change the boosting freq from the advanced settings).

By the way I updated ondemand, it's faster than in the original kernel.


Try to use Deadline for a while. I tweaked it to better perform on flash devices. Anyway I don't think that changing I/O scheduler will make a tangible difference.

Thanks for ur simplified explaination :) This means in order to bring smoothness ondemand will keep most of the time freq at 800 mhz (as per ur settings). But definitely its going to affect battery life as just for a simple touch freq will raise to 800 mhz directly. Anyway overall it depends on user who want battery life or smoothness :)
I have used ur fixed signal kernel for longer time. That kernel really works very well when we use phone (even with 2g net). But surprisingly in deep sleep mode (means with gsm network on on and 2g net off) then there is very heavy battery drain :( For me its 25% battery drain in 9hr deep sleep mode. But if we keep our phone phone offline in deep sleep mode then it will drain battery just 4% in 9hr. Strange...!!!
I will monitor tonight also with that signal fix kernel. and final tomorrow I will flash this kernel on clean cm10a4 so that I can compare both ur kernels :)

EDIT : My doubt was right. Your previous signal fix kernel works really good. Yesterday night tested and I found that lost 3% battery in 8 hrs standby. Means my previous 25% battery loss was not a correct observation. Anyway now I will flash this kernel and tell u the results :)
 
Last edited:

rodero95

Senior Member
Jul 11, 2012
307
1,688
Re: [KERNEL][CM10] qwerty [08/02/13]

Well, its obvious that keeping a continuous connection with the network costs battery and that when we are connected with mobile network it will eventually change between signal modes (2g, HSDPA, edge, etc) and that also costs battery.
That's why mobile network use to consume more battery than WiFi or offline.

Sent from my GT-I9003 using xda premium
 

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.




    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.



    • 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.


    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.