No problem, use what better suits your needs.hello, thanks for update.
but for mean time I'll stick to flyongb. Just for bt. That app you told me last time didnt made any improvement. I played for two days, but didn't found any setting to improve bt sound quality.
I like your releases, it was my daily driver, but tired of bt problems and battery life. On gb I do have 6hrs of screen time, while on pre-last cm10 build was max 3,5
I'll sertainly wait for stable release, I do like your work. Thanks.
Yes. There's no need flash N different stock ROMs, format SD cards etc.Can I flash this one over cm10.1 after wipe (data & system)?
Thanks for the scripts, but I don't want to use them.If bt sound quality would be better and ram usage as on gb, I would stay on cm10, don't mind to charge every night, but on flyongb rom ram is always about 150-80 MB free and do fluid, as cm10 never was. Maybe ext4 formatting works so well? Or ram management scripts?
Losco, take a look to them, maybe than can be useful? Gb is fast and battery friendly, but cm10 rocks on eye candy stuff and user friendly handling
Thanks to @LoLaTiOn
Not possible without framework changes.Losconosciuto, can you compose me a script, witch would keep app in memory if that is possible? Gb one. If that possible and would take only some minutes I'm total noob in Linux stuff. Local.prop doesn't work on gb, guessing that this rom lacks of compiled feature to implement app locking
I still need browser to be locked, but thanks to gb memory management, it killed not so often
Thanks.I can make a betterbatterystats statistic file if you wish to.
What kind of screen malfunction?loSconosciuto, thank you for your great work! But I encountered some problems when flashing cm-10-20130816-UNOFFICIAL-galaxysl.zip.
I was on CM10.1 alpha8. I wiped factory/data then flash your CM10.After reboot pass the start screen, I got screen malfunction. Then I took out the battery and did clean flash from DDLF2 FULL to cm-10-20130816-UNOFFICIAL-galaxysl.zip. But then I got boot stuck.
I really want to test your CM10 with kernal 3.0. Can you please help me?
On a different note, I read here and there that sometimes the device loses the phone signal and a reboot is necessary to get it again. I think it happened to me yesterday and it looked like a kernel crash. Unfortuntely after the main crash happened, the WiFi driver kept throwing a warning filling the dmesg with the same message repeated over and over.
The blurred screen is weird, I can't even imagine how it looked like.It's blurred screen, happened after the splashscreen. After taking out battery and reboot it stuck at splashscreen. Clean flashes also stuck at splashscreen.
I guess mine was a different thing then, I couldn't switch to airplane mode, I tried it.Yea, it does loose the phone signal sometimes & to get over that issue i switch on & then switch off Airplane mode. Signals come back to normal then.
And sometimes 2G data (EDGE) doesn't switch on, this issue need a reboot most of the time.
BTW I'm on Dhiru's 10.1 CM built.
I got same issue many times on dhiru rom alpha8: no signal and airplane mode not switching. May be is not a kernel issue: other roms based on alpha8 never happened this.....
I guess mine was a different thing then, I couldn't switch to airplane mode, I tried it.
I don't know about 2G, I never use it, but it shouldn't be that different from 3G, which I keep constantly on.
No problem, use what better suits your needs.
I have a question though. It's been a long time since I used a stock ROM and now that you tried both my CM10 and recently moved to a stock ROM, I'd like to know how's the battery with CyanogenMod. I won't flash a stock ROM anytime soon to do a comparison on my own.
Without looking at the stats, at the end of the day, how different is the remaining battery between a stock ROM and CyanogenMod with the same usage?
At least I know that the few changes I did to the updater are not the problem.I tried 0817 version(kernal 3.0). It still stuck at spashscreen, no matter base on CM10-0812(kernal 2) or DDLF2 clean. Sorry, I don't know how to catch log.
Now I stay on 0812-kernal 2.
It happened only once to me and that time I couldn't see what happened, but it looked like a kernel crash, even if I'm not sure.I got same issue many times on dhiru rom alpha8: no signal and airplane mode not switching. May be is not a kernel issue: other roms based on alpha8 never happened this.
I still don't know how good the battery is with the 3.0 kernel, I started to use it as daily driver only recently and I haven't use the device that recently. However I didn't have a bad impression, it could be that my battery is so old that whatever I use I get a terrible battery life.Hi loSco,
I'm always switching roms, actually my daily rom is x-gamerz, based on your qwerty work. Battery life using Android 4.x kernel 2 is about 20-30 % shorter than GB, but enough for a full day. With dhiru's kernel 3 is about 50% shorter, I don't use it as daily because I have to charge the phone two times per day.
I make few calls (maybe 1 each 2-3 days) but I use a lot whatsapp and web browsing. Usually I get 2-3 hours of screen time on, in GB usually one more.
Losco, so what screen time you've got with kernel 3 on your device? My hands are niesing to try your miracle, but battery life, sods and bt holds me
Sent from my GT-I9003
CyanogenMod 10 - kernel 3.0
CyanogenMod 10 - kernel 2.6.35
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.
dhiru1602 said:IMPORTANT! READ BEFORE FLASHING THIS RELEASE!
- This ROM will wipe data due to different partitioning. The device would reboot while flashing and resume again.
- Once on this ROM, the most effective way of going back to any other ROM would be to repartition from Odin.
- 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.
- 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.
- Do NOT use Odin to flash Modems. Due to different partitions, Odin will screw up your existing MTD setup.
The standalone kernel is no more mantained. Flash the ROM instead.
Kernel - 2.6.35
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
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.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...
I've already done it time ago, but I had some little but annoying issues I have now solved.wanna make a suggestion for a navbar option in the next build.. could that be possible?
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).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.
The error seems to be:Sorry losconosciuto, but what is "dmesg" ?
Edit: attach dmesg.txt
unregister_netdevice: waiting for tiwlan0 to become free. Usage count = 1