yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] falex007:
Thanks a lot. After about a month of using CM10.1 I returned back to CM 10. And I found how more free memory the phone has now. Thank you still developing it.
[Samsung Galaxy SL i9003] ASMI1:
hey LoSco i have your cm-10-20130812 rom...till now no bugs at all:D

I'm going to update to cm-10-20130824 now... thanks Losco I really appreciate your excellent work:)
[Samsung Galaxy SL i9003] ageback:
Still no luck with cm-10-20130824 even started clean flash from DDLF2 FULL. Stuck at splashscreen. I'm going crazy!

Now I'll try to flash cm-10-20130812 first...

Edit: failed again base on cm-10-20130812 and unable to get into recovery by volume-up+home+power, as always.
[Samsung Galaxy SL i9003] ndttung8487:
Did you try to push volume up and home button harder? I realize that my home button have problem and have to push hard.
[Samsung Galaxy SL i9003] loSconosciuto:
Did you try this?

You can still use that PDA, it's just not up-to-date. And if that kernel is not working, I just uploaded my 2.6.35 kernel flashable from Odin (kernel2_PDA.tar). The ROM won't boot, but recovery will work and you should be able to flash whatever you want from there without repartitions.

You can find everything on GDrive.

I have a question. When you tried to flash my CM10 with the 3.0 kernel over a stock ROM (if you did that, I'm too lazy to go back and re-read your posts) and the device rebooted during the flash because of the MTD conversion, did it actually rebooted to recovery to continue the flash or it never got past the splash screen? Have you ever had a similar issue flashing anything else from me?

If you know how to use adb, once you have flashed my CM10 with the 3.0 kernel over any other CM10, could you please run the following commands:

mount /sdcard
dd if=/dev/block/mtdblock0 of=/sdcard/boot.img

and then give to me boot.img which should be inside your sdcard?

EDIT: do all of that right after the zip is flashed and without rebooting the device.

______

Anyway, I just brought back the screen sensitivity control and also ported this, which is something our old touchscreen driver did. It should decrease the standby power consumption, probably not that much. If you can perceive really minimal changes in the standby power consumption, please try the last ROM with its kernel for a while and then flash kernel-cm-10-20130825-galaxysl-signed.zip over it and tell me if there's any difference.

Here the patches:

input: atmel_mxt_ts: use deep sleep mode when stopped

input: atmel_mxt_ts: add touchscreen thresholds controls

DeviceParts: update screen sensitivity controls
[Samsung Galaxy SL i9003] ageback:
After flashing CM10 with kernal3.0 it never got past the splahscreen after the 1st reboot

I will try to study adb usage and catch the necesary files.

Never. I've flashed many of your CM10 kernal2 ROMs, no such issue.
[Samsung Galaxy SL i9003] loSconosciuto:
EDIT: There's something wrong. I will reupload the build soon. Link removed.

EDIT 2: It's taking more than expected. I'm getting some weird reboots and I want to know what's causing them before the release.

EDIT 3: I reverted a bunch of commits to fix the problem. Build online.

cm-10-20130827-UNOFFICIAL-galaxysl.zip

Changes:

Disabled again L3 OPP1, few devices couldn't boot because of it ([MENTION=4367511]ageback[/MENTION])

Misc kernel config changes

Don't use early suspend to control the status of the modem [1]

Deep sleep mode for the touchscreen when the screen is off

Allow to change screen sensitivity (DeviceParts)

Trebuchet from cm-10.2 (icon packs support)

[1] I've been using this in my 2.6.35 kernel without problems, but then I reverted it. I'm doing the same here because it might increase the stability of the mobile connectivity, but not necessarily. If you had issues before, tell me if you still have issues.

As you maybe noticed, I updated the first post and I wrote all the bugs that I'm aware of.

I also updated the patches to build the ROM (not those use for this build, I will upload them).
[Samsung Galaxy SL i9003] ageback:
Great! With the latest build I finally get into system. loSconosciuto thank you for your hard work!
[Samsung Galaxy SL i9003] cukierkas:
Yes, really, you made a fine job:thumbup:

Regards.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] marras:
I know that benchmark are no indicative of performance of ROM... I made one with antutu and i get 2800, with 3.0 kernel cm10, and i made an other one with cm10.1 by dhiru, even with 3.0 kernel (i think that kernel is very similar) and i get 3500 points! Why so much different? And cm10 is way smoother than cm10.1... I would understand... IoSconosciuto cm10 has room for improvement! It will be the best and the definitive rom for our phone.

Sorry for bad english :P
[Samsung Galaxy SL i9003] hjs89:
Before Alpha 9 dhiru's had a poor score on benchmark's test too. Maybe losco doesn't upload the last changes to his build.
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20130829-galaxysl-signed.zip

This is the kernel that should have been included in my last build. I found what did wrong.

Changes

Don't use early suspend to control the status of the modem [1]

Misc kernel config changes (disabled a bunch of unneeded options and debugging)

General cleanup and fixes

[1] I've been using this in my 2.6.35 kernel without problems, but then I reverted it. I'm doing the same here because it might increase the stability of the mobile connectivity, but not necessarily. If you had issues before, tell me if you still have issues

Patches on GDrive.

Aaaaaaaaand I stopped reading.

Nah, it's just AnTuTu. This ROM is fast since its first release. I wouldn't have posted it otherwise.
[Samsung Galaxy SL i9003] cukierkas:
Hi losco, thanks for the update. One suggestion. Can you update the op with the biggest plus of your rom - locking application in memory instructions. That would be handy for new users :thumbup:

Sent from my GT-I9003
[Samsung Galaxy SL i9003] vishal24387:
http://xdaforums.com/showthread.php?t=2404331
[Samsung Galaxy SL i9003] loSconosciuto:
Index:

Lock apps

Skype video calls orientation

WiFi and IMEI

I was asked so many times to make possible to prevent apps from being automatically killed that I finally did that.

I made possible to lock two apps, to do that, you have to set two props: persist.sys.keep_app_1 and persist.sys.keep_app_2.

I wrote two simple scripts that does that for you to make things simpler. If they are not included in the build you are currently using, attached there's a flashable zip. They work only with my builds.

You have two slots, 1 and 2, to define which apps need to be kept in memory.

Lock apps:

open terminal emulator and run

su
lockapp N com.android.example

N is the slot number, it must be 1 or 2

com.android.example is the name of the process you want to lock. You can get that in several ways, ie from the Play Store link of the app or by looking at the content of /data/data/, where each app has a directory with its name.

The script will verify that the app you want to lock actually exists.

You can lock apps in occupied slots.

Unlock apps:

open terminal emulator and run

su
unlockapp N

N must be 1 or 2 (you are allowed to lock two apps only).

A reboot is required to apply the changes.

You can run both the scripts without arguments to see the currently locked apps and too see a help message.

Attached you can also find the framework patch required to lock apps in memory using the props.

Video calls in all the recent versions of skype are wrongly orientated. The problem is that Skype is forcing the orientation to fix issues with stock ROMs. This shouldn't be done in CyanogenMod, which uses a totally different camera HAL. I hence wrote a simple script (flashable zip attached) which modifies the dex file of Skype to prevent orientation issues.

open terminal emulator and run

su
skype

You have to do that whenever the dex file is re-generated, ie after each update or whenever you wipe the dalvik-cache.

This script is universal, you can use it with every ROM.

(3.0.8 kernel only)

Each device is shipped with a unique MAC address. The address is stored inside your /efs partition: /efs/imei/.nvmac.info.

If you lost your IMEI, you probably no longer have /efs/imei/.nvmac.info, which is required to create another file necessary to have a working WiFi. (see this script).

WARNING: the commands below will overwrite the existing /efs/imei/.nvmac.info, so make sure you have a backup.

To make WiFi work, you have to manually create that file.

Open terminal emulator and run:

su
mkdir -p /efs/imei/
echo -n 08:00:28:12:03:58 > /efs/imei/.nvmac.info

08:00:28:12:03:58 will be your new MAC address, you can set whatever you want as long as it's a valid MAC address.
[Samsung Galaxy SL i9003] Drizzt_Kueh:
Hi [MENTION=4349695]loSconosciuto[/MENTION].

I've got a doubt. The known bugs for kernel 3.0.8 are only the ones listed before its title? Or the kernel also has the bugs of the kernel 2.6.35?

Just to be clear, with the kernel 3.0.8 this ROM has the hw composer fixed? And also support USB and Wifi tethering out of the box?

Sorry for bothering you!

Thank you!
[Samsung Galaxy SL i9003] loSconosciuto:
EDIT: I forgot to change the permissions for the LED backlight timeout. Give me a couple of minutes, build offline.

EDIT 2: build online.

cm-10-20130904-UNOFFCIAL-galaxysl.zip

The ROM is practically the same, I just did some changes to the kernel.

See the changes here: I included some DSS optimizations (I couldn't notice any difference on my Hitachi panel), simplified the driver of the LEDs (you won't notice any difference), included all the changes I made in kernel-cm-10-20130829-galaxysl-signed.zip (see my previous posts).

It's also no longer possible to change the sensitivity of the touchscreen. I got more than once a hot reboot right after a reboot, when DeviceParts tried to restore the sensitivity. I will maybe see what's the problem, but honestly I don't care much about that feature.

I'm also trying to find the problem with the proximity sensor while in call. The sensor works properly, however the screen is not turned on. The only solution I found is to increase the backlight timeout (I've already added this information to the first post). I don't often make long calls and had a long screen off timeout before, so I'm not sure if this bug had always been there or it started recently (maybe because some changes I did in the framework or maybe it's because of the new GP2A driver).

So, did it happen in older builds?

Do you know when the first time this bug appeared?

Does it happens in any of Dhiru's builds?

Yes

and yes.
[Samsung Galaxy SL i9003] AmmarGitham:
I am on the old cm-10-20130726 build with the old kernel. Proximity sensor is working perfectly. Just FYI.
[Samsung Galaxy SL i9003] Drizzt_Kueh:
Crystal clear! Amazing! Thank you...

I'm using, until you upload your new version, the latest cm10.1 a9 from Dhiru. Just to be sure: when in call, i move my phone away from my ear and the screen turn on just a second after doing it.
[Samsung Galaxy SL i9003] loSconosciuto:
Try this. Make a call and keep the screen off for a lot, more than your screen backlight timeout. I have issues only when the screen stays off for more than that interval.

I tried to add some debug lines here and there and it seems that the sensor is properly sending the events, but the screen is not turned on, so I'm thinking about some ROM issues rather than kernel/driver issues.

Anyway, the build is back online.
[Samsung Galaxy SL i9003] Drizzt_Kueh:
Tried with Dhiru's cm10.1 latest alpha, the display turned on almost instantly.
[Samsung Galaxy SL i9003] cukierkas:
Thanks for update. One question. Does bt sound quality improved with kernel3? Does anyone use bt headset with this rom?

I'm still on gb just for proper bt quality :(

Sick of it, but I talk much with headset, so that is important for me :)

Don't mind to loose 1hrs of screen time, but bt is really needed. For this reason default rom works grant, but it's, lets say, outdated :)

Don't want to install QWERTY and afterwards return to gb just for this reason, so eagerly waiting for some feetback.

Regards.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] ASMI1:
hi Losco, when I was on any dhiru1602 cm10.1 rom (A6, A7, A8, A9) I couldn't turn on the WiFi, but the WiFi is working well on CM10 rom or any other rom and when I installed your CM10 rom with kernel 3.08 WiFi didn't work:confused: So I figure out that the kernel was the responsible for this issue but no one reported such problem:confused:So please could you tell me why I am facing this problem...btw i have fake IMEI...now I am using your cm-10-20130812 rom but I want to use your latest rom build so please help me to fix the WiFi issue...please:crying:
[Samsung Galaxy SL i9003] loSconosciuto:
It seems that the device somehow is allowed to sleep while in call and that's what causing issues with the proximity sensor.

I reverted the followings:

Phone: Prevent immediate screen-off after call-answer

Phone: Disable accelerometer sensor while in-call and screen UI is off

and the device stays awake when in call. I'm not sure that I fixed it yet and probably the problem was caused by the first one, but I got tired testing changes and RILJ is making that a nightmare, it keeps the device awake for a few minutes after each reboot, so I have to wait for its release and then test the changes.

Here the modified Phone.apk, let me know if the proximity sensor works properly now.

Did you try what I wrote here?

There's an init script which reads the MAC address from /efs/imei/.nvmac.info and creates a file (/data/misc/wifi/wl1271-nvs.bin) which is necessary for WiFi to work. However, if the MAC address is not found, that file is not created.

If you lost all your files inside /efs, you probably don't have /efs/imei/.nvmac.info now. The command I posted in my other post will create a new /efs/imei/.nvmac.info.

It's better to add this information to the first post.
[Samsung Galaxy SL i9003] ASMI1:
i have many files in /efs folder and i have imei subfolder and bt.txt and mps_code.dat files within it but i don't have .nvmac.info file in the imei folder...going to try it losco...thanks in advance:)

---------- Post added at 02:11 AM ---------- Previous post was at 01:13 AM ----------

WHAT!!!...hey losco you are genius...thank you very much sir...now my wifi is working again thank you very much:):):):):D
[Samsung Galaxy SL i9003] cukierkas:
Losco, my dear mate, congratulations, rom just flies :)

My curiosity won again.

For mean time some observations :

Dark SMS theme doesn't appears when selected in SMS settings. To say the truth, it was never worked on your releases, but that is not important.

Button backlight can't be turned off if pulse notifications are on :( or am I disunderstood smth? Made it as short as possible, but any way, it can be dismissed :)

Great work in optimizing ram management. About 120mb free without gapps. Will see how it will behave later on.

Lockapp dialog is lovely, even with some help :) Bravo.

Regards, great work became even better. Will see tomorrow how bt will work with car's bt headset and what sound quality we will get. .. Let's keep fingers crossed.

Happy uaer

Sent from my GT-I9003
[Samsung Galaxy SL i9003] loSconosciuto:
Now that I consider the kernel stable, I decided to update it to the latest version available of the 3.0 branch.

I also reorganized my kernel branches. From now on I'll maintain two branches:

latona-3.0: here I'll push the device specific changes

latona-3.0.y: here I'll merge the mainline updates and the changes of latona-3.0

I also renamed the repo, sorry for that. If you had my repo as remote source, update the address.

If you want to test the new kernel, flash kernel-cm-10-20130906-galaxysl-signed.zip.

Flash kernel-cm-10-20130904-galaxysl-signed.zip to restore the kernel of my last build in case you have problems.

I tested it for a while, but I need some days to be sure that everything is fine, consider this as highly experimental.

If you'll flash the new kernel and find any bug, please report. Logs are more than welcome.

PS: the changes I made to Phone.apk seems to work fine. It's weird that there were no problems with the old kernel. Those changes, which are not part of the AOSP code, were only applied to CM10. That explains why there were no issues with Dhiru's CM10.1.

The dark theme is for quick replies, the little popup that appears when you press "reply" in SMS notifications. I guess a theme must be used for the app.

Ops, I forgot to update some paths in DeviceParts after the recent changes to the LED driver. Flash this.

I hope it works. As I said, there were a lot of changes involving bluetooth, but I think you are the only one using my builds and a BT headset.
[Samsung Galaxy SL i9003] AmmarGitham:
Hey loSconosciuto,

I use my phone for Android App development via USB. I read that in the 3.0.y ROM, there is some problem with USB transferring. So will that effect the development too?... I was thinking of flashing the latest version. Any info would be great. Thanks. :)
[Samsung Galaxy SL i9003] cukierkas:
Hello at this lovely day. Yes, bt headset speach quality improved and a lot, especially after pickup. Sound is not perfectly clear, but way better than on kernel 2. That is lovely. But strange noises appears at peeps till pickup, sometimes very loud :(

But, in conclusion, its better. Strong 7 from 10 :)

Proximity sensor works perfectly, screen turns ons instantly. Longest call was 7 mins. Battery life way worse than on gingerbread, but that's the price of jb I guess :)

What else. No sods, but settings sometimes hang up, need to close them manually. I have got Sony panel but no backlight bug noticed. One suggestion. Can you include task managers button in resent tasks? That would be handy.

another thing. As I see, no other CPU governons included. Will you add some later on? And about scheduler ROW, is it better than cfq or sio?

For mean time no other thoughts, thanks for a lovely rom. Applied xperia theme, yes I fell in love with old crappy 9003 again :)

By the way, after reboot button backlight appears off, so no need to install your devicepart edit after all. Notifications works, buttons permanent off. The way I like it :)

Great job dear, you should be proud of yourself:thumbup:

Sent from my GT-I9003
[Samsung Galaxy SL i9003] loSconosciuto:
Just file transfers and the problems seem to be limited to transfers involving the external SD card. I can push big files with adb to my internal memory with no problems, so it's probably my SD card to blame. The thing is that it works correctly with the old kernel.

Apart from that, it works great. You can reboot with the device connected and still having adb working after that and the battery is not indefinitely charged (see the first post). The connection is stable, no random disconnections so far.

In any case, my builds should be compatible. You can go back with no wipes. You'll just have some extra files needed for WiFi in /data, but the drivers used for the two kernels are so different that they don't shouldn't interfere each other. All the other changes are limited to /system.

EDIT: I switched to the new kernel with no wipes and everything is working perfectly.

I'm happy it's better now, I'll if I can find what's causing the noises

It seems to be better than the old kernel to me and that's fine for me.

I don't know about this, I'm not so excited by the idea, I have to think about it. There isn't even a real task manager, I should see if it's possible to open the one included in the settings directly, but I'm not that good with Java.

Probably not.

In my old kernel I tuned Deadline to prefer READ IO operations over WRITE IO operations. Read the introduction here, ROW is made exactly to do what I was doing with Deadline, so I directly switched to it.

That's because I forgot to update some parts of DeviceParts only, so certain things (such as restoring the setting after a reboot) work, other (such as disabling touchkeys backlight after a reboot) don't.

EDIT 2:

The last kernel I posted seems to be as stable as the old ones. Technically, it should be more stable considering that it includes all the fixes of the last two years.
[Samsung Galaxy SL i9003] cukierkas:
Do you remember my issue with alarm clock? When it didn't woke up the screen and rang till the battery pull up? I think, flip action is causing it. When any flip action is off, alarm clock works perfectly. When snoose or dismiss is applied, I do got screen problem. That's maybe only on my device, because no one reported it, but I wanted you to know about it.

Regards.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] AmmarGitham:
Great..!!! Then I'm switching to the latest ROM... Current old one has Wifi Issues. Disconnects a lot. :good:
[Samsung Galaxy SL i9003] loSconosciuto:
I guess I'm going to shamelessly get rid of that option in my next release, that's definitely the problem. Maybe I'll try to fix it, but I really don't care about it.
[Samsung Galaxy SL i9003] abderrezak:
can you add bigman patch for RAM (+15-40 mb)

and OC with 120min and 1350 max

just for testing on our divece ;

good work , keep up :good::good::good:
[Samsung Galaxy SL i9003] cukierkas:
Well, I must admire, kernel 3 with all yours mods holds battery better :)

And this the first charge, with all the restoring.

Good work, no more gb, ever :)

Sent from my GT-I9003
[Samsung Galaxy SL i9003] AmmarGitham:
Few hours after using flashing the ROM, I got a hot reboot. Don't know what happened. Was trying to wake the screen, but just the soft keys would light up. After several tries, the screen did wake up, but then suddenly got the reboot. Looked for /proc/last_kmsg, but there was no file by that name in that folder.

EDIT:

Can't seem to download apps from the play store... Get the following exception...

09-08 15:43:37.795: E/AndroidRuntime(14219): java.lang.SecurityException: Invalid value for is_public_api: null
09-08 15:43:37.795: E/AndroidRuntime(14219):	at android.os.Parcel.readException(Parcel.java:1425)
09-08 15:43:37.795: E/AndroidRuntime(14219):	at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:188)
09-08 15:43:37.795: E/AndroidRuntime(14219):	at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:140)
09-08 15:43:37.795: E/AndroidRuntime(14219):	at android.content.ContentProviderProxy.insert(ContentProviderNative.java:420)
09-08 15:43:37.795: E/AndroidRuntime(14219):	at android.content.ContentResolver.insert(ContentResolver.java:864)
09-08 15:43:37.795: E/AndroidRuntime(14219):	at com.google.android.finsky.download.DownloadManagerImpl$1.run(DownloadManagerImpl.java:47)
09-08 15:43:37.795: E/AndroidRuntime(14219):	at android.os.Handler.handleCallback(Handler.java:615)
09-08 15:43:37.795: E/AndroidRuntime(14219):	at android.os.Handler.dispatchMessage(Handler.java:92)
09-08 15:43:37.795: E/AndroidRuntime(14219):	at android.os.Looper.loop(Looper.java:137)
09-08 15:43:37.795: E/AndroidRuntime(14219):	at android.os.HandlerThread.run(HandlerThread.java:60)
09-08 15:43:41.966: E/DatabaseUtils(15936): Writing exception to parcel

EDIT 2 :

The Play store problem is solved. It seems after the flash, the Play store had become a user app. I had to 'uninstall' it. Extract the app from gapps zip and then place it in the /system/app folder with rw-r-r permissions. And reboot. Problem solved.
[Samsung Galaxy SL i9003] cukierkas:
Hello. Try format system, reflash rom. Checksum is the same? It happened yo me the same after migrating from gb. Reflash helped. Or that newest kernel? Have you cleared the dalvic? By the way, at current cwm couldn't find fixing permission function. Is it absent or not needed any more?

Regards.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] AmmarGitham:
Read my second edit...
[Samsung Galaxy SL i9003] shaktishekhar:
Everything seems to b fine bt one issue am facing with bluetooth audio when music is playing and using wifi am contonusly loosing breaking audio when sending reciving is going on the audio skips plz fix... using latest sep 6 kernel and latest cm 10 4th sep other wise the kernel is fine smooth good