hello guys
I'm presenting you first TRİM enabled kernel for Galaxy W
first of all big thanx to my brother @lafactorial ı didnt use to make this without him
he compiled kernel for me(my pc is still broken )
kernel base is lafactorial's Khan kernel so every feature in khan kernel are included in this kernel
this kernel is also including especially TRİM support
We need an explain of TRİM support
So What is TRİM?
Fragmentation occurs on traditional hard drives. When a file is deleted from a hard drive, its space is “liberated” when the file system erases the pointer to the start of the file. When the next file is to be written, the controller finds the first free spot on the disk, and starts writing the file. If the file is too big it fills up the empty spot, then puts a pointer to the next free spot on the disk, and then starts writing again. This process is repeated again and again until the file has completely been written. As more files are deleted and new ones written, the disk becomes more and more fragmented. As fragmentation increases, performance decreases. To remedy the situation we must defragment our hard drives — which takes quite a bit of time.
Data stored on NAND flash is saved differently than on traditional hard drives. Similar to HDD storage, NAND also keeps a map of where data is stored. When you delete a file, rather than freeing up that spot for re-use, most of the time it’s simply marked as “not in use”. The data is still there, and, more importantly, the entry in the file system is still there. (We just can’t access because it’s “not in use”.) That means as you write and delete files, the file map has to get bigger, and it takes more time to find the files that you’re looking for. While technically not “fragmentation”, this ”I/O lag” becomes more pronounced with use– causing your device to operate more slowly the more you use it. This problem has been present in virtually every Android-powered device (and almost every other device that uses NAND flash for storage), we just haven’t noticed it too much — until now.
TRIM to the rescue!
TRIM essentially goes through the file records and frees up blocks that you’ve deleted by telling the controller to stop keeping track of them. Now the controller only has to keep track of the files that haven’t been deleted, which speeds things up significantly!
TRIM support was included in the desktop Linux kernel in 2008. Microsoft’s desktop operating systems didn’t get support until 2009 with Windows 7. Apple didn’t pick up TRIM support on OS X until 10.6.8 in 2011. Android, however, didn’t pick it up until version 4.3.
Unfortunately, if your device isn’t running Android 4.3, it’s unlikely that your OEM has built in TRIM support. For those of you who have new devices running Android 4.3 and later, you’re all set — TRIM is set up and running automatically. If you’re using a device that was running a down-level version of Android and you upgraded it to version 4.3, you probably want to do a factory reset to regain your lost speed, though you shouldn’t notice any further slowdowns if you opt not to start from scratch.
At the moment our roms (cm10.2 and cm11) is supporting TRİM feature but our kernels doesnt
so if you want to see TRİM is working or not on your phone then you can enter the following commands in Terminal emulator
su
fstrim -v /cache
you will see the following message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so your kernel doesnt support TRİM
but if you install this TRİM supported kernel
then result will be like this
:good:
Download:
big ram(360 mb) TRİM kernel:http://yadi.sk/d/q25Hb5VORq4uR
stock ram(340 mb) TRİM kernel:http://yadi.sk/d/AOTJrl01Rq5Fv
Just flash it via cwm and do not forget to wipe cache and dalvik cache before and after installation
For Devs
we(lafactorial and me) just gave erase capability to emmc chip by reverting the following commit in kernel https://github.com/arco/samsung-kernel-msm7x30/commit/797ddcb9bf1b30d4cdac45e81568e19797ffad19
yep you can see sir arco's warning in commit message but dont worry for about bricks because our emmc chip is good one(Sandisk SEM04G) not a bad one(like MAG2GA)
we published this kernel in another turkish forum(http://www.maxicep.com/forum/konu/kernel-cm11-khan-kernel-trim-destekli.893317/) and lots of peoples used this kernel for 1 month and still using(you can look date of thread) and no one faced brick or something like that
just ı trimmed 3 partition (/data /system and /cache) 100 times and ı didnt face any brick yet :victory:
Thats all
Enjoy!
NOTE!!!
This kernel is only compatible with latest cm11
do not forget that
and also Once you boot with a trim-enabled kernel, trim function will run automatically in the background and cannot be disabled by the user!
but if you want to trim partitions manually you can use this app https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix&hl=tr
have a nice day
Thank you for such a good kernel!
GT-I8150 cihazımdan Tapatalk kullanılarak gönderildi
for cm10.2, I just flash it ? thanks in advance
@sir mordred
My 8150 no longer exists.Can't Test it.
But I do wish you success.My young brother.
The way is clear.
The entrepreneurial spirit.
I very much appreciate
jglory said:
for cm10.2, I just flash it ? thanks in advance
Click to expand...
Click to collapse
sorry mate kernel is just for cm11
Thank you sir morderd!
May you give us the source link of this kernel?!
Madridii said:
Thank you sir morderd!
May you give us the source link of this kernel?!
Click to expand...
Click to collapse
sure here you go: https://bitbucket.org/LafactoriaL
but as far as ı can see kernel sources isnt published yet.
sir mordred said:
sure here you go: https://bitbucket.org/LafactoriaL
but as far as ı can see kernel sources isnt published yet.
Click to expand...
Click to collapse
You should publish it and the commits of Trim
Thank you again
Sent from my GT-I8150 using XDA Premium 4 mobile app
Madridii said:
You should publish it and the commits of Trim
Thank you again
Sent from my GT-I8150 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ı already did it
ı explained to devs in the OP you can look "For Devs" section
Is this compatible with 0525 build? I can't turn WiFi on
ayesse said:
Is this compatible with 0525 build? I can't turn WiFi on
Click to expand...
Click to collapse
I have 0525 too. Can someone confirm it's not working? I can't backup at the moment
Inviato dal mio GT-I8150 utilizzando Tapatalk
Prodromodinverno said:
I have 0525 too. Can someone confirm it's not working? I can't backup at the moment
Inviato dal mio GT-I8150 utilizzando Tapatalk
Click to expand...
Click to collapse
WiFi isn't working, and I don't want to install the last build, it's giving me problems with google services
P.S. Italian?
ayesse said:
Is this compatible with 0525 build? I can't turn WiFi on
Click to expand...
Click to collapse
as i said in the OP this kernel is only compatible with latest cm11(5/28)
can you try this kernel on 5/28 build and give me feedback bro?
sir mordred said:
ı already did it
ı explained to devs in the OP you can look "For Devs" section
Click to expand...
Click to collapse
OK, so I just need to revert that commit in my source, right? ?
Sent from my GT-I8150 using Tapatalk
LeroViten said:
OK, so I just need to revert that commit in my source, right? ?
Sent from my GT-I8150 using Tapatalk
Click to expand...
Click to collapse
Yes You are right bro you need to revert only that commit
Revert only that commit and TRİM will work
Thanx Lero
Regards
sir mordred said:
Yes You are right bro you need to revert only that commit
Revert only that commit and TRİM will work
Thanx Lero
Regards
Click to expand...
Click to collapse
OK, I'll try... Thanks for the heads up.
And have a nice day... ✌
Sent from my GT-I8150 using Tapatalk
Sorry @sir morderd ..
But we should ask Mr. @arco68 to check this .. Reverting that commit what will do ? Just for Trim?!
Sorry again and good job
Sent from my GT-I8150 using XDA Premium 4 mobile app
Madridii said:
Sorry @sir morderd ..
But we should ask Mr. @arco68 to check this .. Reverting that commit what will do ? Just for Trim?!
Sorry again and good job
Sent from my GT-I8150 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Firstly why are you sorry i dont understand why you are sorry
And secondly if we revert that commit users can use trim,erase,secure trim
Here is a proof
https://code-review.phablet.ubuntu.com/gitweb?p=CyanogenMod/lge-kernel-mako.git;a=commit;f=drivers/mmc/host/msm_sdcc.c;hb=31a45ce6faa0f2e150eed6777cbb3ae8f2f08219
sir mordred said:
as i said in the OP this kernel is only compatible with latest cm11(5/28)
can you try this kernel on 5/28 build and give me feedback bro?
Click to expand...
Click to collapse
Tried with latest build 0528, wifi still doesn't work
Related
Hi all.
I am sharing a new git repository providing :
z4control : An Android application to control some system settings, most notably - implement a full/partial lagfix.
initramfs : A z4mod initramfs template for I9000 for kernel modders. You will notice it only contains a simple wrapper for init - all lagfix implementation is outside the kernel scope.
To use:
1. Either use a z4mod compiled kernel, or compile your own using the provided initramfs, or patch an existing kernel to use the z4mod initramfs using z4build.
2. Install the z4control apk and enjoy.
As always, everything is open-sourced and released under the GPLv2.
Some z4control screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---
I am terribly sorry the lack of documentation and further information. I will try to find the time to elaborate if no-one else will.
Check the links. They are funny...
What did you based the initramfs on?
**Using my own JPX kernel, z4mod, 346MB Ram and ext2 filesystem**
Does this support /system conversion? Thanks.
Sent from my GT-I9000 using XDA App
jaju123 said:
Does this support /system conversion? Thanks.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
You can convert them all.
I have used this app for some time now and its safe to use i think its even better then the z4mod app.
But think that's only /data has power backup. So you can loose data on the other if you are unlucky.
I don't know how.. I still have no error and a have done a couple of wired stuff.. Lol
**Using my own JPX kernel, z4mod, 346MB Ram and ext2 filesystem**
Hi, z4ziggy,
Welcome back! Wishing you a happy new year ahead of you.
Sent from my GT-I9000 using XDA App
Hello z4ziggy,
I've used Z4mod Lagfix on my I9000B whith JPA and i have a 3G problem. For me, this connection did'nt work after apllied the patch.
I did unlagfix, restore RFS and Kernel, but the problem remains.Finnaly, I had to reinstal my rom, with Rom Manager, and only then the connection works again.
My phone shows a great performance after this lagfix, but i would like to know if is there some change, in this new app, about my related issue?
And sorry man, but where's the apk to download?
Thankyou
Cool.. the android application link does not work. Even if you take the extra http:// out.
Sent from my GT-I9000 using Tapatalk
Tricky103 said:
Cool.. the android application link does not work. Even if you take the extra http:// out.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
right click..save target...on the link.............without tapatalk !
Oright. As it says on my signature using tapatalk. The right button takes me back to the previous screen
Thanks.
Sent from my GT-I9000 using Tapatalk
Tricky103 said:
Oright. As it says on my signature using tapatalk. The right button takes me back to the previous screen
Thanks.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
oh you changed your post, where is the word "*****".. well i changed mine too you *****.
BTW thanks for your work ziggy, trying your work right now.
Yes I thought about my actions, sorry about that. Your right in the fact, its beginner level, I will know for next time.
+ testing now works well. Thank you
Sent from my GT-I9000 using Tapatalk
Ok, I'm lost all my data, the app did the backup in system.z4mod.tar, and the backup is fine but I can't access to my app and lost all; I have only my SMS
This is my z4mod.log
esticbo said:
Ok, I'm lost all my data, the app did the backup in system.z4mod.tar, and the backup is fine but I can't access to my app and lost all; I have only my SMS
This is my z4mod.log
Click to expand...
Click to collapse
Thanks for the info, and sorry about the inconvenience...
If i'm reading the log correctly, your /system partition was 100% full which prevented it from converting to ext2. Can you please confirm this by comparing the size of /sdcard/system.z4mod.tar and your /system partition?
the relevant lines from the log:
+ tar xf /sdcard/system.z4mod.tar -C /
tar: write error: No space left on device
If you will confirm my deduction, than I will try to add some check for future versions. Unfortunately, your only fix atm is complete reflash your rom. I am TERRIBLY sorry.
Hmm. Cant you do a function that check for this backup file and put that back?
Would be great if something goes wrong.
You could even use it for backup...
Sent from my GT-I9000 using XDA App
z4ziggy said:
Thanks for the info, and sorry about the inconvenience...
If i'm reading the log correctly, your /system partition was 100% full which prevented it from converting to ext2. Can you please confirm this by comparing the size of /sdcard/system.z4mod.tar and your /system partition?
the relevant lines from the log:
+ tar xf /sdcard/system.z4mod.tar -C /
tar: write error: No space left on device
If you will confirm my deduction, than I will try to add some check for future versions. Unfortunately, your only fix atm is complete reflash your rom. I am TERRIBLY sorry.
Click to expand...
Click to collapse
Don't worry for the inconvenience, I have lost only the score of Angry bird Season, I've a backup of the other app.
I had the JPB (froyo spanish rom) with z4root + z4mod that with it I changed my filesystem in ext2, and with your last app z4control I try to change the other partition in ext2 too.
The system.z4mod.tar size is of 282.890.752 bytes (269 MB).
I'm flashing my Sgs and now try again to convert my partition
Edit: Nothings don't work very well or I'm no good to use your app. I'm flash my SGS then put z4root 1.3.0 / reboot / z4mod 0.93 (patch the kernel, and flash the new kernel) / reboot / z4control and try to convert all to ext2 / reboot and nothing.
Tricky103 said:
Yes I thought about my actions, sorry about that. Your right in the fact, its beginner level, I will know for next time.
+ testing now works well. Thank you
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
nah i was wrong first, i shouldnt make you feel dumb, sorry for that.
you seem to be a good guy
Ok, I've change my filesystem in ext2 with z4mod 0.93, in z4control I see that only the Data are in ext2, so I try to change DBData and System in ext2, reboot and start to change and all work great but when reboot I lost all again.
Subscribing......
Kol HaKavod
« »
esticbo said:
Ok, I've change my filesystem in ext2 with z4mod 0.93, in z4control I see that only the Data are in ext2, so I try to change DBData and System in ext2, reboot and start to change and all work great but when reboot I lost all again.
Click to expand...
Click to collapse
As I've said, apparently you don't have enough free space in /system which breaks your system once you try to convert it. either dont convert /system (after all, only /data radically speeds up your system...) free some stuff manually.
Can you please send me your /sdcard/z4mod.system.tar so I can take a look?
In my z4control app I don''t have the theme options as are shown in your screenshots.
If you change any one can wait for me a boot.img to mount the SD card, and CM10 rom as it is now because it does not do so. Thanks in advance!
aaduo01 said:
If you change any one can wait for me a boot.img to mount the SD card, and CM10 rom as it is now because it does not do so. Thanks in advance!
Click to expand...
Click to collapse
what?
chromium96 said:
what?
Click to expand...
Click to collapse
Sorry for my bad English! This QISS me jb rom boot.img. I ported CM9 for the video recorder and it works with ICS version, but I can not find the CM10 rom the SD card because there is not only linked to storage/sdcard0 sdcard. This should be changed in the ramdisk to have external storage, I just can not get a computer for a week me to do. If someone is changing and it would be nice to fill it.
:cryinglease help gay!
aaduo01 said:
:cryinglease help gay!
Click to expand...
Click to collapse
Haha.. Lol.. You gotta love google translate.
Unfortunately, we can't help you unless we clearly understand what you're trying to do. Try asking someone that knows English to post for you.
abaaaabbbb63 said:
Haha.. Lol.. You gotta love google translate.
Unfortunately, we can't help you unless we clearly understand what you're trying to do. Try asking someone that knows English to post for you.
Click to expand...
Click to collapse
:silly:You just should change this init.bravo.rc and repackaged.
?????¿??
Nobody wrap this init.bravo.rc the boot.img file into this?
aaduo01 said:
Nobody wrap this init.bravo.rc the boot.img file into this?
Click to expand...
Click to collapse
the android system somehow I can pack the boot.img and then return? Thanks for the answers!!
Guys! Someone has to unpack this file in the boot.img into init.bravo.rc above. Damn this is a working solution for video recording all jb rom
aaduo01 said:
Guys! Someone has to unpack this file in the boot.img into init.bravo.rc above. Damn this is a working solution for video recording all jb rom
Click to expand...
Click to collapse
does this guy know some magical method that will make the desire the best phone ever?!
lol everyones ignoring his posts and he might have some major breakthrough that he cant explain to us.
I'll try this out later and see if it does anything. :laugh:
chromium96 said:
does this guy know some magical method that will make the desire the best phone ever?!
lol everyones ignoring his posts and he might have some major breakthrough that he cant explain to us.
I'll try this out later and see if it does anything. :laugh:
Click to expand...
Click to collapse
Believe me my friend! I have the modified files, plus OMX videoencoder.so and videodec.so should this boot.img init.bravo.rc the modified file. We are please to help someone pack it and upload it here. This team is based QISS me!
It's not that anyone wants to help, such a small thing?
I have done a month ago for quiss kernel and it is working fine with video and also fixed SD card and everything else. But the performance is very slow. So I have not released it. I have done it for miui, cm10 and aokp as well
Sent from my Full Android on Bravo using xda premium
vijendrahs said:
I have done a month ago for quiss kernel and it is working fine with video and also fixed SD card and everything else. But the performance is very slow. So I have not released it. I have done it for miui, cm10 and aokp as well
Sent from my Full Android on Bravo using xda premium
Click to expand...
Click to collapse
I can read! But the kernel does not matter. that when installing a new kernel performance will be good and will work with the spies. Please give me a link to a modified boot.img which work with the sd card mounts. And if you did evervolv to upload the latest rom zImage then I would do an update zip. And who could throw a huge ruins
aaduo01 said:
I can read! But the kernel does not matter. that when installing a new kernel performance will be good and will work with the spies. Please give me a link to a modified boot.img which work with the sd card mounts. And if you did evervolv to upload the latest rom zImage then I would do an update zip. And who could throw a huge ruins
Click to expand...
Click to collapse
work with the camera (not spies. idiot google translate)
Sorry I am not getting you..
I can only say if you are using some other kernel it wont work. Only thing is use QUISS kernel and make your ROM to work with it.
It is not just init.rc changes for SD card mounting, there are many changes required at ROM level as well and with this QUISS kernel hell lot of changes to make the ROM to boot and work as expected.
So if you can get some update from QUISS kernel and if that update can work with any other kernel let me know.
vijendrahs said:
Sorry I am not getting you..
I can only say if you are using some other kernel it wont work. Only thing is use QUISS kernel and make your ROM to work with it.
It is not just init.rc changes for SD card mounting, there are many changes required at ROM level as well and with this QUISS kernel hell lot of changes to make the ROM to boot and work as expected.
So if you can get some update from QUISS kernel and if that update can work with any other kernel let me know.
Click to expand...
Click to collapse
I di:angel:d CM9 rom and flash boot.img QISS Shaky kernel and it works! Please upload the modified boot.img file and send me a pm. I promise I will not tell you and you do not want to share!
aaduo01 said:
I di:angel:d CM9 rom and flash boot.img QISS Shaky kernel and it works! Please upload the modified boot.img file and send me a pm. I promise I will not tell you and you do not want to share!
Click to expand...
Click to collapse
What is going on?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 01:49 PM ---------- Previous post was at 01:47 PM ----------
vijendrahs said:
Sorry I am not getting you..
I can only say if you are using some other kernel it wont work. Only thing is use QUISS kernel and make your ROM to work with it.
It is not just init.rc changes for SD card mounting, there are many changes required at ROM level as well and with this QUISS kernel hell lot of changes to make the ROM to boot and work as expected.
So if you can get some update from QUISS kernel and if that update can work with any other kernel let me know.
Click to expand...
Click to collapse
Please guys,
Trust vijendrahs, he is a good developer and knows where he is talking about. You could also look into this: http://forum.xda-developers.com/showthread.php?t=2095658
I think he did the same.
Thanks,
- TheRinseM.
He must have done some fix for JB camera! at least he can type in his own language, it would be easyer to undrestant( we can google translate it) lol.
farpadana said:
He must have done some fix for JB camera! at least he can type in his own language, it would be easyer to undrestant( we can google translate it) lol.
Click to expand...
Click to collapse
Good point
Sent from my HTC Desire using xda app-developers app
**** WARNING *****
This is highly experimental, flash at your own risks!
Messing up with baseband is dangerous
**** WARNING *****
This is for Xperia S (LT26i) only
Please read the firsts posts very carefully
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
As I saw various posts regarding flashing baseband from another firmware, I decided to take a look at a way to do it properly.
First, let me clarify something: flashing baseband partitions from flashtool is not enough! In fact, baseband firmware is composed of multiple files stored in /system/etc/firmware. Proof of this is that if you only flash baseband from flashtool, version won't change in the about box. Just replace files in /system/etc/firmware and version changes.
So copy file is enough? Well, not exactly as many reported that flashing partitions has an impact. Looking at partitions extracted from firmware, amss_fs_1 and fs_2 are empty but fsg is not. I suspect that it contains parameters that are used by the baseband firmware.
That's why I came up with these zip files, they install baseband files in /system/etc/firmware and flash amss partitions at the same time.
I'm looking for beta testers, I currently have .211 and .55 basebands. Send me a PM if you are interested in testing.
Instructions
Download the baseband you want to replace
Copy the zip file at the root of your internal storage/sdcard
Optional, but *highly* recommended, copy the md5 at the same location
Reboot to recovery and flash baseband
Reboot to your rom and check version in settings/about box
Please report success or failure to the thread.
FAQ
Is it safe ?
Well, I did it multiple times without any bad consequence. I can't promise it won't kill your phone though. As far as I know, this is the first time that amss partitions are flashed this way.
What are potential issues ?
First, using baseband from another firmware could lead to problems as rom are tuned for the matching baseband firmware. It could lead to disconnections, problem with calls, bad reception...
One effect I noticed is that agps seems to be reset after flashing. No big deal but first gps fix will take longer.
Where are the files ?
I want to do a private beta-testing before releasing them in the open. Contact me in PM if you want to be in the beta-test phase.
Good Job! Nice Feature to Add At my ROM ... GG.
Thanks bro,required it desperately
Sent from my Xperia S using xda premium
and what do i get from flashing them
i think you should mention that
sorry for my NOOB question
zaidx said:
and what do i get from flashing them
i think you should mention that
sorry for my NOOB question
Click to expand...
Click to collapse
U can solve 2g bug on new jb
Sent from my Xperia S using xda premium
RISHI RAJ said:
U can solve 2g bug on new jb
Sent from my Xperia S using xda premium
Click to expand...
Click to collapse
Well, you can try at least, but I'm not sure that baseband is the only issue.
I had a problem today with the 2.55 baseband on my aosp 3.4 kernel, I couldn't call when I was on 2G. It could be a random operator fluke, but it could be related to the baseband. Difficult to say. It's not exactly JB firmware, so your results could be different.
I'll do more test in coming days, but flashing baseband could give more troubles than it solves.
2g is still not working properly? even on official .200 and .211 ?
trust me its working better than ics .....for me(at least)...
just put the write APN settings there and it will be fine...
@letama, are you going To release your 3.4 aosp kernel in near future?
androidlover007 said:
@letama, are you going To release your 3.4 aosp kernel in near future?
Click to expand...
Click to collapse
Sure. I have small details on my aosp build to fix before, but it shouldn't be too long.
letama said:
Sure. I have small details on my aosp build to fix before, but it shouldn't be too long.
Click to expand...
Click to collapse
So you were faster than me, I already suspected that .
Few questions on your kernel: does it follow mako or CAF guidelines?
And did you 'bulk' update the video/ion drivers or did you merge them cleanly.
Last but not least, did you watch out for the new V4L2 camera drivers so we can use the camera blobs from Sony's official JB releases?
Ping me in GTALK (now Hangouts) so we can chat a little
Which is the Baseband version for .211 fw? If it is something beyond -32 then I can test it, but if not will be a waste of time...
RaymanFX said:
So you were faster than me, I already suspected that .
Few questions on your kernel: does it follow mako or CAF guidelines?
And did you 'bulk' update the video/ion drivers or did you merge them cleanly.
Last but not least, did you watch out for the new V4L2 camera drivers so we can use the camera blobs from Sony's official JB releases?
Ping me in GTALK (now Hangouts) so we can chat a little
Click to expand...
Click to collapse
Well, it's Sony one with mako video bulk update, I only separated gpu/fb/ion, but same method as 3.0.x.
I'm using exclusively Sony JB proprietaries, camera is fine with the same 1080p stuttering problem as Sony one though.
I'll ping you tomorrow, a bit busy tonight
Felimenta97 said:
Which is the Baseband version for .211 fw? If it is something beyond -32 then I can test it, but if not will be a waste of time...
Click to expand...
Click to collapse
baseband is -35
letama said:
Well, it's Sony one with mako video bulk update, I only separated gpu/fb/ion, but same method as 3.0.x.
I'm using exclusively Sony JB proprietaries, camera is fine with the same 1080p stuttering problem as Sony one though.
I'll ping you tomorrow, a bit busy tonight
baseband is -35
Click to expand...
Click to collapse
ok, good to hear my work isn't useless, cause I didn't bulk update mine, but merged the jb_2.5 CAF branch into our kernel.
Because nozomi really isn't mako, eventhough we can get along with mako drivers pretty well. Nontheless, staying in sync with CAF is much more future-proof and once Android 5.0 or whatever drops, it'll take me a simple 'git merge' to be up-to-date.
A little OT : why do you think Sony has made Camera driver using Video4linux?
I also saw that, but I can't understand Sony
Sent from my LT26i using xda app-developers app
Forzaferrarileo said:
A little OT : why do you think Sony has made Camera driver using Video4linux?
I also saw that, but I can't understand Sony
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
Because of Sony Motion Eye support, Xperia P Have it.
Sent from my LT26ii using xda app-developers app
TrinityHaxxorX said:
Because of Sony Motion Eye support, Xperia P Have it.
Sent from my LT26ii using xda app-developers app
Click to expand...
Click to collapse
That can't be the reason, they could add motion eye support without V4L, lol.
I think they wanted to implement a more generic driver than their ICS implementation and somebody decided on V4L.
That could alsp explain their struggles with 1080p encoding/recording.
My 3.4 CAF kernel has higher vidc clocks and different ION allocation than Sony's kernel for 1080p, so let's see if I can get this stutter fixed without Sony.
RaymanFX said:
That can't be the reason, they could add motion eye support without V4L, lol.
I think they wanted to implement a more generic driver than their ICS implementation and somebody decided on V4L.
That could alsp explain their struggles with 1080p encoding/recording.
My 3.4 CAF kernel has higher vidc clocks and different ION allocation than Sony's kernel for 1080p, so let's see if I can get this stutter fixed without Sony.
Click to expand...
Click to collapse
I Just sae it here
https://github.com/nicolassp/XPERIA-P/blob/master/kernel/Documentation/video4linux/meye.txt
But your correct, you have a point to.
Sent from my LT26ii using xda app-developers app
// Moto-Xoom Everest/Wingray/Stringray
// Android 4.2.2
// Current Version [ 4.2.14 ]
// All Languages
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MIUI ROM 4.2.14 Full Changelog
[Lock screen, Status bar, and Notification shade]
New - Added the option to customize carrier name (Settings-Notifications-Additional settings-Edit service provider name)
Optimization - Improved pulldown notification shade and displayed some information in the status bar
[Weather]
Fix - Location issues of places outside China
[Security Center]
Fix - Display error of phone internal storage in Cleaner
Click to expand...
Click to collapse
Everest
2-20-2014: MIUI v5 4.2.14
Working
- Everything, maybe
Stingray
2-20-2014: MIUI v5 4.2.14
Working
- Everything, maybe
Wingray
2-20-2014: MIUI v5 4.2.14
Working
- Everything, maybe
Working:
- We'll find out soonish
MIUI General FAQ
Q: How do I root this?
A: Enable root in the perm manager, which can be found in the security folder.
Q: Why is G-Apps not listed for Download?
A: Too Bloaty, add a Google account and install the play store as an APK, I suggest using Aptoide to find it.
Q: 4G LTE isn't working
A: Load the Phone, dial *#*#4636#*#*, goto Phone information, Set preferred network type to LTE/CDMA auto (PRL).
Q: Help! Phone/SystemUI/Keyboard Isn't working/Is Force Closing!
A: Make sure to do a completely clean wipe, also I'm not sure how well this will work if flashed in CWM.
Q: The Browser looks terrible.
A: Settings -> Advanced -> User agent string -> MiOne (It Renders much better & more naturally!)
Q: My Filesystems won't mount/My PC can't see my device/My phone won't act as a MTP/USB Mounting isn't working!
A: Settings -> Developer Options -> Enable Development / USB Debugging (switch both to on)
Hi, I'm Tquetski from en.miui, please gimme a few days to get this all set up and in order :S
Looks good
Sent from my falcon using Tapatalk
Awesome, another ROM, can't wait to give this a try.
Looking forward, to this port or built with patchrom?If this port which device is taken for donor?:good:
You have an error in the topic title Wingray -2 times.
Isnt it too late for building 4.2.2 now? Why not go for kitkat? Looking forward to this though since ive never tasted miui on any tab
superbay said:
Isnt it too late for building 4.2.2 now? Why not go for kitkat? Looking forward to this though since ive never tasted miui on any tab
Click to expand...
Click to collapse
MIUI not built on kitkat yet - this is the highest android version for miui.
---------- Post added at 11:51 AM ---------- Previous post was at 11:47 AM ----------
@Tquetski - Looks awesome, can't wait thanks!!!
Q: have you enabled landscape for miui home, and modified the row/column count to make more suitable for our form factor? I did a hack job some time ago, and it looked quite reasonable in landscape after the mod.
amazing
MIUI for XOOM!? I really like to have it since I got that device and now my prayers get heard!!:highfive: cool, really really cool :good::good:
superbay said:
Isnt it too late for building 4.2.2 now? Why not go for kitkat? Looking forward to this though since ive never tasted miui on any tab
Click to expand...
Click to collapse
Tonights the night, and because 4.4 isn't on MiCode yet.
As a matter of fact outside of MI devices, 4.2.2 is the 'supported' android version because development has finished
These releases aren't one-night stands; I'm actually going to provide weekly updates once the bases are sorted lol
Since you guys have a MDPI device you may have to fk around with DPI mods, but the code is solid; with love
Wingray version don't work.
With stock part: update fail
With bigpart: update work fine, but stuck on moto logo.
Sorry
murigny64 said:
Wingray version don't work.
With stock part: update fail
With bigpart: update work fine, but stuck on moto logo.
Sorry
Click to expand...
Click to collapse
me too on everest bigpart.:crying:
did clean install and tried three times but no chance. needed to say that i only tried with big part.
murigny64 said:
Wingray version don't work.
With stock part: update fail
With bigpart: update work fine, but stuck on moto logo.
Sorry
Click to expand...
Click to collapse
Same here, just sits at the logo.
@ Tquetsky
Do you have testing your builds ?
Nothing work.
Can you explain ?
murigny64 said:
@ Tquetsky
Do you have testing your builds ?
Nothing work.
Can you explain ?
Click to expand...
Click to collapse
These devices lack the RAM needed so although the code is right it won't boot.
I'm going to need to slim down a lot of **** and adjust resources to MDPI when I get a chance; all the MDPI devices are in a situation where it won't boot/finish booting or doesn't look right if it does because the only resources avail officially are HDPI
Edit: I also made this ROM without regard to the RAM the device has as well, if I removed all the translation stuff it would prob. be ok; I'll have to check into this.
Tquetski said:
These devices lack the RAM needed so although the code is right it won't boot.
I'm going to need to slim down a lot of **** and adjust resources to MDPI when I get a chance; all the MDPI devices are in a situation where it won't boot/finish booting or doesn't look right if it does because the only resources avail officially are HDPI
Edit: I also made this ROM without regard to the RAM the device has as well, if I removed all the translation stuff it would prob. be ok; I'll have to check into this.
Click to expand...
Click to collapse
Hope you get it worked out, no complaints from me.
Appreciate you working on it! Thanks!
Tquetski said:
These devices lack the RAM needed so although the code is right it won't boot.
I'm going to need to slim down a lot of **** and adjust resources to MDPI when I get a chance; all the MDPI devices are in a situation where it won't boot/finish booting or doesn't look right if it does because the only resources avail officially are HDPI
Edit: I also made this ROM without regard to the RAM the device has as well, if I removed all the translation stuff it would prob. be ok; I'll have to check into this.
Click to expand...
Click to collapse
Tquetski, you did a blind-build? you don't have a XOOM to work with/test?
Tquetski said:
These devices lack the RAM needed so although the code is right it won't boot.
Edit: I also made this ROM without regard to the RAM the device has as well, if I removed all the translation stuff it would prob. be ok; I'll have to check into this.
Click to expand...
Click to collapse
Lack the ram needed? Please explain this......
Sent from my HTC6435LVW using XDA Premium 4 mobile app
ThePunisher said:
Lack the ram needed? Please explain this......
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh you're right, It has 1 GB.
I really don't know why it doesn't move past the boot logo; do you load the kernel via 3rd pt injector or use zImage? I found the GNex builds which had this issue needed a zImage kernel
Who has Stringray replace the boot.img on it and check
Please read the original Thread before doing something..
Q: Can I use it on other devices?
A: Yes, you can use this patch on every Krait device that uses AOSP-based ROM (examples: Nexus 5, Nexus 7 2013). Don't flash it on stock ROM on non-Nexus devices, as they already include these optimizations (that includes Galaxy S4 and HTC One Google Play editions!).
I saw this thread in Nexus 4 forum [4.4/4.4.x][PATCH] Qualcomm-optimized Dalvik & Bionic libraries Then I download and test with
[CM11][4.4.2][D802/800/801][ROM]temasek's UNOFFICIAL Build - V63 [07/04] it's OK my phone can boot.:laugh:
I can not confirm this patch can use very well with g2 or have benefit for we.
please consider with yourself.
Have you ever wondered why your Nexus 4 performs worse than other flagship devices with the same quad-core CPU in benchmarks? Not any more! I present you with a very simple patch that will boost your performance to what other APQ8064-based devices offer.
Q: Can I use it?
A: Yes, if you're on any 4.4/4.4.x ROM.
Q: How does this work?
A: This patch consists of two files that include optimized bionic and Dalvik libraries for any KitKat ROM.
Q: What is bionic?
A: It is a vital system library that provides i.a. basic math and memory access functions to every other library and application in Android.
Q: What is Dalvik?
A: In short, Dalvik is a virtual machine in which every not-native-code app runs. You can read more about it in a Wikipedia article.
Q: How do I benefit from this patch?
A: In two ways: bionic patch provides faster memory access and optimized some of the math operations, dalvik provides optimized Dalvik Virtual Machine library that allows faster code execution.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
somboons said:
Q: Can I use it?
A: Yes, if you're on any 4.4/4.4.x ROM.
Click to expand...
Click to collapse
That is not my experience. I have even had boot loops on different AOSP based ROMs. So make a backup before flashing system files as always.
Gnarfsan said:
That is not my experience. I have even had boot loops on different AOSP based ROMs. So make a backup before flashing system files as always.
Click to expand...
Click to collapse
good:good:
deleted.
Bootloop:silly:
all_x said:
Bootloop:silly:
Click to expand...
Click to collapse
what'rom?
I'm on the stock KK V20b Europe open,
flashed the dalvik one. my phone did boot up, but after that, the weather widget FC, then my phone became unusable,
superbonto said:
I'm on the stock KK V20b Europe open,
flashed the dalvik one. my phone did boot up, but after that, the weather widget FC, then my phone became unusable,
Click to expand...
Click to collapse
sorry.not for stock rom. please read original thread before
somboons said:
sorry.not for stock rom. please read original thread before
Click to expand...
Click to collapse
Please write it more clearer?
Q: Can I use it?
A: Yes, if you're on any 4.4/4.4.x ROM.
Click to expand...
Click to collapse
No one, including me, is in the mood to read the original thread. You posted it here, so write whats in the original thread so prevent confusing guys...Just cause you found an "AWESOME SUPER DUPER EPIC" patch which is kinda placebo, doesnt mean you can do whatever you want
In red: 4th and 5th lines of the op
"Don't flash on stock ROM on non-Nexus devices"
I think that's pretty clear, always have to read the op in its entirety.
I'll give this a shot and will report back, running vs980 3.25 build of beanstalk.
sent from an organic spaceship spinning through space
grehdaemon said:
In red: 4th and 5th lines of the op
"Don't flash on stock ROM on non-Nexus devices"
I think that's pretty clear, always have to read the op in its entirety.
I'll give this a shot and will report back, running vs980 3.25 build of beanstalk.
sent from an organic spaceship spinning through space
Click to expand...
Click to collapse
True, and if you keep reading the entire OP, then you will read this:
Q: Can I use it?
A: Yes, if you're on any 4.4/4.4.x ROM.
Click to expand...
Click to collapse
Anyways, this mod isnt something special, like any other script, mod and placebo things.
Guys expecting some rocketboosting thingy, when you apply an patch without changing the hardware.
The G2 itself IS already pretty powerful, why you wanna hurt it with putting such stuff on it... i dont get it.
kewkie said:
The G2 itself IS already pretty powerful, why you wanna hurt it with putting such stuff on it... i dont get it.
Click to expand...
Click to collapse
Yes, it is powerful but the overall user experience is much improved if the battery last longer with optimized libs.
Optimization means lower operating temperatures and longer life for your device.
Every AOSP rom suffers from proper optimization. This patch is most welcome!
kewkie said:
True, and if you keep reading the entire OP, then you will read this:
Anyways, this mod isnt something special, like any other script, mod and placebo things.
Guys expecting some rocketboosting thingy, when you apply an patch without changing the hardware.
The G2 itself IS already pretty powerful, why you wanna hurt it with putting such stuff on it... i dont get it.
Click to expand...
Click to collapse
If this is not for you, please move on.
kewkie said:
Please write it more clearer?
No one, including me, is in the mood to read the original thread. You posted it here, so write whats in the original thread so prevent confusing guys...Just cause you found an "AWESOME SUPER DUPER EPIC" patch which is kinda placebo, doesnt mean you can do whatever you want
Click to expand...
Click to collapse
U sir should not root your phone or use this forum if u want quick awesomeness and no knowledge... Ur not in the mood? he provided you with a link to something great and your complaining because you don't want to read how to use it???? I've read that thing three times and countless articles on dalvik just to learn about my device .... U need stock ...bad
Sorry everyone else it had to be said...thanks for sharing OP...and thanks for linking as well
Sent from my LG-VS980 using Tapatalk
can i use this to cloudy flex 2.0?
DracoPiece said:
can i use this to cloudy flex 2.0?
Click to expand...
Click to collapse
Only AOSP based KitKat roms
Sent from my HP Slate 7 using Tapatalk
From my experience on AOSP Roms, only the Bionic libs work on our LG. The Dalvik libs will cause a boot loop
Sent from my VS980 4G using XDA Premium 4 mobile app
goodguy25 said:
Only AOSP based KitKat roms
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
how to know if it is bases on AOSP? sorry im a newbie
[url="http://forum.xda-developers.com/showpost.php?p=51547944&postcount=1220]Here's a link[/url] @Hammer_Of_The_Gods posted some time ago. It's the bionic optimizations only. If you choose to install either the bionic or the dalvik (which shouldn't be necessary but w/e floats your boat), then I'd recommend using the links in that thread only. The thread OP linked hasn't been updated in a month, whereas @jphilippon's thread was updated a less than a week ago.
Also, what the hell is wrong with these commenters... "I flashed on stock ROM, boot loop..." "this is all placebo..."
Read the directions. You can't blame anyone but yourself for not adhering to the directions. I don't blame Kraft for making bad Mac n' Cheese because I decided to replace the water with orange juice and put it on the grill...
And if you don't think this mod does anything, ignore it. I saw a thread where some guy ported the stock LG keyboard to AOSP ROMs. That sounds stupid as hell to me, but I sure didn't go in that thread and poop-post.
P.S. DON'T FLASH THE DALVIK zip on PA4.2b3. The bionic optimizations worked fine for me, though.
DracoPiece said:
how to know if it is bases on AOSP? sorry im a newbie
Click to expand...
Click to collapse
Most ROM posts say that somewhere.
But heres a list of some AOSP based ROMs and ROM bases:
CM/CyanogenMod based ROMS
PA/ParanoidAndroid based ROMS
AOKP/Android Open Kang Project based ROMS
P.A.C/PA+AOKP+CM
OmniROM
MoKee
And others that I don't remember right now.
All of the ROMs in G2 Original Android Development I think are AOSP based. But beware. You will get boot loops with this patch in some of them. I can't remember which though.