Related
CPUFreq Successfully Installed and Running
Please visit my website for additional information
After receiving alot of positive results from my Kernel and several releases later. We have arrived at RLS 5.9, a prototype build incorporating CPUFreq for CPU Scaling and Idle control, and a modified version of Power Management. We are at a release stage of this Alpha build, and approaching Beta, where it is as follows:
Each build that is released that has an update to CPUFreq will have an update to the first subversion in the build version (eg. RLS5.9.1.0)
Each build that is released that has an update to Power Management will have an update to the second subversion in the build version (eg. RLS 5.9.0.1)
And of course each upgrade to a specific subsystem of the Kernel will up the version number of that specific subversion.
Current Release: RLS 5.9.2.2
RLS 5.9.2.2 will mark the beginning of the Beta stage out of Alpha stage. This release is showing far more promising results than my initial CPUFreq release.
I just want to personally thank all who have been supporting me and reporting any and all bugs that have been coming in, as I have been squashing them left and right in preparation to improve our Kernel for our phones to make them more feasible for everyday use.
Currently Being Tested:
Power Management - Reverted some old changes to the power management code, switched too Apps Sleep. Made some minor changes to the original pm.c source code and results are promising. Running VanijlEclair RLS11, and in rare cases the phone still crashes while sleeping, which I believe is related to the phone hiccuping when going to sleep, which in theory could completely blow up the timer that Apps Sleep uses for sleeping. I will investigate this part further, but so far, RLS 5.9.2.2 is much more stable than my previous release.
CPUFreq - No changes to the source code, still attempting to modify permissions so Android can modify the files that are required.
HAReT Users - Thanks in large part to V3rt!g(o) HAReT users can now boot the Kernel. I have made a slight modification to the default.txt file provided in the RLS 5.9 HAReT archive that uses Apps Sleep instead of Power Collapse. From what was reported, the Kernel takes about 2 minutes to initialize from WinMo, but after about 1min30sec to 2min, Android should begin loading.
Radio ROM - Currently Testing Radio 1.71.09.01, and so far it seems very stable and provides better battery usage.
Current Release (RLS5.9.2.2):
Kernel - HTC Polaris support re-introduced.
CPUFreq - Has been installed, and working inside the Kernel only. Android does not recognize CPUFreq correctly.
Processor - MSM-7201 processor increased from 384MHz to 528MHz
Stability - Has been improved further. Phone correctly sleeps and wakes properly. Still occasional crash occurs, but is random. Could go a full day without a crash, or could crash every 4hrs. Issue might be related to how much the CPU is being utilized at the time of wake up.
Power Management - Power Management restored to near WinMo states, still not as good as RLS5.7, but within range. Phone will last a full day of occasional use, and about 80% of the day on moderate use.
Initrd - New BootLogo has been made, and inserted into initrd. Unfortunately boot menu is not accessible. Made install scripts to compensate.
YAFFS2 - Exclusively does ECC checking on it's own without any help from the NAND driver. This should help with data corruption, but is not a permanent solution.
YAFFS2 - Disabled Forced erase chunk checking, slight increase in response time and decrease in read-time.
MTD - Disabled Verify NAND Page Writes
MTD - Disabled GPIO NAND Driver
EXT - EXT2 is currently disabled inside the Kernel. EXT4 has been fully enabled, aside from journaling, and is fully supported in the kernel and install scripts.
System - Switched from DG (High Resolution) Timer, to GP (Low Resolution) Timer.
System - Fully disabled High Resolution Timer -- Provided a decrease in kernel size without loss of performance.
sysfs - Enabled configfs. This will unavoidably increase RAM usage, but allow easier access to sysfs.
MSM - Performance Counter Driver enabled.
FrameBuffer Driver - Decreased fake-vsync delay from 10 to 5. Less times snow effect appears.
Known Issues:
Internal CPUFreq coding is unable to scale the processor, but the hacked msm_cpufreq_* functions are able to control the processor speeds. This will explain why CPUTuner and other Android software is reporting the CPU running at max speed. Will continue to investigate and work out problems with the coding.
JIT Compiler causes issues with framework.acore. Avoid using if possible.
CompCache not the cause of untracked PID errors -- Still investigating cause, though now understanding that it is related to data corruption.
Possibly depending on Radio, GPS takes quite awhile to acquire if not at all. -- Will investigate by flashing an older/newer radio.
Standby code not fully working due to being incompatible with clock code changes. Attempting to re-write power management code to be better compatible with the new clocks code.
CPUFreq Specifics:
Governors - Currently CPUFreq supports the following governors and can be changed while in Android using the Terminal: ondemand, conservative, powersave, performance. Userspace is currently disabled inside the Kernel.
Frequencies - Baseline frequencies the CPU will scale to but not limited too are: 81920 (82MHz), 122880 (123MHz), 245760 (246MHz), 384000 (384MHz). These are just placeholders to control where the CPU needs to scale too base on usage, it will go between lets say 82MHz and 123MHz or use one of the two.
Userspace - Until I can verify CPUFreq is fully operational without any issues, I will not enable Userspace Governor at this time.
Kernel Modules
File Attached to this Post, see below.
This Kernel has been tested with the AT&T Tilt variant of the Kaiser. Using it on any other Kaiser would in theory produce the same results, but due to minor changes in the hardware of each variant of the Kaiser, I'm still going to stress caution when using this Kernel with any other variant of the Kaiser
Things to note about EXT4: This file system will increase read/write cycles to your SD Card. Use with caution as it will decrease the life of your SD Card. Though since Journaling is disabled, read/write cycles will have decreased, but they are still higher than what they would be if EXT2 was used. If you do not feel comfortable having EXT4 on your SD Card, do not use this Kernel as there is no way to use EXT2. You have been warned.
Things to take note with this Kernel: Do not enable JIT compiler under Settings, as this has produced constant FCs with the acore framework. It is recommended that you enable CompCache and set it to the default 18%, as this provides a significant performance boost, and decreases Home screen closures while running other apps.
USE THIS KERNEL AT YOUR OWN RISK. I TAKE NO RESPONSIBILITY FOR ANY DAMAGES DONE TO YOUR PHONE WHILE USING THIS KERNEL.
Woohoo ! First Post!
Thank you Krazy-Killa! Will definitely try this now will post after testing!
I am liking what I am seeing. Thanks for putting the effort into creating this. I'm just curious about one thing, you said that Scoot's CM7 RLS1 build has the modules for this kernel included. Is there a separate download of the modules for anyone that might not be using this build?
Hello Krazy-Killa,
Appreciate your effort !
I just installed it on my TYTN II and so far going well -edited .ngh to change the key mapping to normal.
3G works fine. yet to see BT,WiFi &GPS and overall otherwise.
I have tried Scoot's CM7 RLS1 build 2 days ago.is there any major changes you did - i feel some audio notification alerts changed w. r. t. Scoots.
how can i use those audio files if reqd-i mean can copy&dump to a specific folder and repack.
but its not really matter..
At the moment 'push' works fine and eager to see any 'server connection' problem will occur later with the email client.
i have radio 1.70.19.09
Thanks once again for the post.
Cheers !
cerebralgenius said:
I am liking what I am seeing. Thanks for putting the effort into creating this. I'm just curious about one thing, you said that Scoot's CM7 RLS1 build has the modules for this kernel included. Is there a separate download of the modules for anyone that might not be using this build?
Click to expand...
Click to collapse
I will release the modules as a seperate androidupdate file this evening.
@chandra_100,
All my testing shows BT, WiFi, and GPS working. This Scoots CM7 build I released is just repackaged with my built modules for easy install.
Sent from my AT&T Tilt using XDA App
“Removed support for HTC Polaris”
That’s too bad，poor Polaris，555555555555555~
The untracked PID errors are related to froyo only (maybe Gingerbread too). And its related to init.rc provided with each build. Not kernel's fault
dark_prince said:
The untracked PID errors are related to froyo only (maybe Gingerbread too). And its related to init.rc provided with each build. Not kernel's fault
Click to expand...
Click to collapse
Interesting... Well, I had a looping untracked PID this morning, had to reinstall, but that's mainly the only problem I'm now having... If I could I would build a new init, but the bootenv isn't updated.
Krazy-Killa said:
Interesting... Well, I had a looping untracked PID this morning, had to reinstall, but that's mainly the only problem I'm now having... If I could I would build a new init, but the bootenv isn't updated.
Click to expand...
Click to collapse
The bootenv is fully up to date The untracked PID's aren't caused by the init.rc, they are caused by corrupt filesystems or files which mean that the paths that sysinit.rc is trying to mount aren't there or it can't change permissions on a file because it is corrupt.
for me kernel can't find data.img
Ive go some kind of problem. Im using fresh froyo and when I installed your modules update than I got hang in boot. Excatly at "adb_open" line. Without update everything is ok except wifi.
Sorry for my poor english
Neo2SHYAlien said:
for me kernel can't find data.img
Click to expand...
Click to collapse
I'll look into it. Though I may know the reason why, so I'll do some more testing, and will release once I have it fixed.
scooter1556 said:
The bootenv is fully up to date The untracked PID's aren't caused by the init.rc, they are caused by corrupt filesystems or files which mean that the paths that sysinit.rc is trying to mount aren't there or it can't change permissions on a file because it is corrupt.
Click to expand...
Click to collapse
I'll update my local bootenv, thanks.
Good release. Slightly slower than Clemsyn's kernel (tested in quadrant), but good stability. One thing drives me crazy - I have to wait 5-10 seconds after pressing power button to wake device
MaRekRM said:
Good release. Slightly slower than Clemsyn's kernel (tested in quadrant), but good stability. One thing drives me crazy - I have to wait 5-10 seconds after pressing power button to wake device
Click to expand...
Click to collapse
That was mentioned in the known issues, don't worry my next release will fix that (currently testing). Plus it'll add full EXT4 support like with clemsyn's kernel but you can format your SD card with the device now as I have updated initrd.
Sent from my AT&T Tilt using XDA App
Flashing
I'll try... flashing right now.
what about ipv6 support?
*EDIT* nevermind, i just saw that ipv6 is implemented.
Cannot restore databackup.img trough install menu...
I think this kernel canot handle the img fs. Mount is failing.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
It's because of EXT2 support being turned off... I'm currently testing a new kernel that'll be using EXT4. Running into the same problem you are having with img mounting.
I'm working on isolating the issue why img mounting isn't working.. It's possibly an issue with the init scripts. I'll dig more into it and hopefully get it isolated.
Backup FS
Krazy-Killa said:
It's because of EXT2 support being turned off... I'm currently testing a new kernel that'll be using EXT4. Running into the same problem you are having with img mounting.
I'm working on isolating the issue why img mounting isn't working.. It's possibly an issue with the init scripts. I'll dig more into it and hopefully get it isolated.
Click to expand...
Click to collapse
Probably the script that is generating databackup.img still using ext2.
tiagoclc said:
Probably the script that is generating databackup.img still using ext2.
Click to expand...
Click to collapse
Yep, it was exactly that. Just made the necessary changes, and compiled a new kernel. I'll go ahead and throw it out, but for now I'll point out that I haven't tested it so, please let me know the results.
Init itself is already setup to mount all loopback and SDcard partitions as EXT4 where applicable.
Just use atools to configure the kernel to use /system and/or /data on NAND or SDCard.
Why did you remove polaris support? I think that are plenty of polaris users that want to test your kernel
Thanks
Hello,
I have just tested most of the custom roms (wildchild3, Kim's Mod, WhateverMod etc) comes with DUST V9 Overclocked Kernel. I used MiniPartitionTool and created (1gb Ex2 Primary, 512Mb Swap, 2.5GB Fat32 Primary Active).
All of the above Rom builds mentioned that they support SWAP partition. I just want to know that do i need any apk to Configure SWAP or those custom roms comes with pre-configured Swap support. Is there a tool to see swap stats?
Hi friends,
This post is to share the important things,concepts related to android......
In this post, many things like roms,kernels,overclocking,undervolting,I/O shedulars,governars,RAM, swap,differnt swaps ,partitions (ext2, ext3, ext4 )are ported....
If something missing or wrong plz tell me and i will add in this post...
I hope this post will help you to improve knowledge...
So lets start....
[1] ANDROID:
Android is the linux based operating system, designed primarily for touchscreen mobile devices like smartphones and tabs..
Android is an open source and google releases the code under the Apache Licence
Following are the versions of android :::
1) 1-1.5 --- Cupcake
2) 1.6 --- Donut
3) 2.0-2.1 --- Eclair
4) 2.2-2.2.3 --- Froyo
5) 2.3-2.3.7 --- Gingerbread
6) 3.0-3.2 --- Honeycomb
7) 4.0-4.0.4 --- Ice Cream Sandwich
8) 4.1-4.2.2 --- Jelly Bean
After knowing about Android,
Lets move towards deep....
[2] Android Rooting:
Android Rooting is process of allowing users which are using Android system to attain privileged control (i.e. Root access) within Android Subsystem.
Rooting is required for more advanced and potentially dangeorous operations like deleting,modifyig system files etc..
Their are many methods for rooting our galaxy y
Most easy method i found is at the thread
http://forum.xda-developers.com/showthread.php?p=29960454
[3] ROM ::
A file containing the executable instructions (the system image ) of an Android operating system & apps is ROM (read only memory)
after rooting your phone you are free to flash any custom rom
FLASHING ROM: flashing rom means installing the system image into device's internal flash memory...
Their are many custom roms available for our galaxy y..
Cyanogenmod, BeautySense, Creeds Rom, Fusion Rom ,
Repencis ROM, Infected ROM Blazed, COD Rom , U.S.S.R, Thunder ROM , EVO-X, CHOBITSDIGITALIS ROM ,
WeUI by amal das, M.U.R, MySS, emralD, xXxxxX MIUI XxXxXx, WinterMod Evo , WP8-Monochromatic 6.0
ACCEND
Links of all these roms will get from thread:
http://forum.xda-developers.com/showthread.php?p=31329931
[4] KERNELS::
Kernels isn't something unique for android, but all O.S. i.e. Windows, Ios, Blackberry, have kernels..
Android devices uses Linux Based kernels
In simply words, the hardware and the software communicate each other by using kernels...i.e. When software needs hardware to do anything it sends that request through kernels..
Most of the things like brightness of screen, volume, is controlled by kernels...
Kernels decides minimum and maximum frequency of CPU,
Overclocking, undervolting are all done by using kernels....
Some of the kernels available for galaxy y are Savie kernel, Merruk kernel, Hells Fusion Kernel, Kuro kernel, White kernel, Repencis Kernel, Deviant kernel etc.
( their are many other kernels list of all the kernels is impossible)
[5] Governers and I/O shedulars::
For understanding both the above terms please read the following post::
http://forum.xda-developers.com/showthread.php?p=19846276
[6] Overclocking:
Android
overclocking increases the
maximum frequency (or speed)
that your CPU can run, thereby
increasing performance of your
Android smartphone or tablet.
Many kernels for our galaxy y uses overclocked frequency..
By overclocking, overall performance of phone increases, we can play hd games lag free..
Only the disadvantage of overclocking is that mobile gets heated fastly....
Most famous kernel for overclocking galaxy y is merruk kernel...
[7] Undervolting::
Kernels are used to undervolt phone...
Undervolting means force the smartphone to work at lower voltage than normal voltage..
Due to undervolting battery backup of phone increases...
After all such part.....
[8] RAM (Random Access Memory)::
It is temporary data storage that the CPU uses during calculations. The more RAM a device th more calculated results the CPU can store.
Which means less time the CPU has to do the same thing over and over again.
In other words, th CPU can check RAM to see if it has already made a particular calculation in the recent past. If it has, it can use the pre-computed results instead of wasting proccessing time in recomputing the same calculation.
In short , more RAM means more efficient the device....
[9] Swap:
swap is nothing but virtual RAM. Using swap a small portion of hard drive is set aside and used like RAM
The great guide how to increase RAM using swap file and swap partition is given here :
http://forum.xda-developers.com/showthread.php?p=26220059
ZRAM:
To know about ZRAM please click the link:
http://forum.xda-developers.com/showthread.php?p=34877656
[10] Cache:
Many times you read the word cache...so
Cache is general type of temporary and quick access data used by the system or user(third party) applications...
Or any temporary information used or created by app is cache..
[11] Dalvik cache:
This word is also read by us many times..
Dalvik is the process virtual machine (VM) in Google's Android
operating system . It is the software that runs the applications on Android devices. Dalvik is thus an integral part of Android, which is typically used
on mobile devices such as mobile phones and tablet computers
Programs are commonly written in Java and compiled to
bytecode. They are then converted from Java Virtual Machine - compatible .class files to Dalvik-compatible .dex
(Dalvik Executable) files before installation on a device. The compact Dalvik Executable format
is designed to be suitable for systems that are constrained in terms of memory and processor
speed.
[12] JIT ::
JIT stands for
"Just In Time," and we use it to
describe a Dalvik JIT compiler,
which was added to Android with
the 2.2 release. It compiles
bytecode into native machine code at runtime. Essentially it takes the code for an app, analyzes it and converts it into something that runs faster. It does all this while the application is running, and that's where the "just in time" tag comes from. The JIT compiler designed for Android also can do this with a very short "warm up"
time, meaning it doesn't take very
long to analyze the code before it
starts working. It stores information in a cache in your
phone's RAM, which means it's not an ideal solution for devices with low memory.
[13] a2sd or app to sd:
app to sd is nothing but to move the app in external storage instead if internal storage....
Some apps are used to move apps in sd card
Some of the kernels also support a2SD....
[14] Linking app to SD:
their is difference between app 2 sd and link 2 sd ...
Link 2 sd means to create a separate part in external storage by specific linux file system such that it bahaves as internal storage and then move the app to that particular memory...
Following are the mainly used file systems....i.e. Partitions...
Partitions:
ext2, ext3 and ext4 are all
filesystems created for Linux i.e. For android..
Ext2
Ext2 stands for second extended
file system. This was developed to overcome
the limitation of the original ext
file system.
Ext2 does not have journaling
feature.
On flash drives, usb drives, ext2 is
recommended, as it doesn’t need
to do the over head of journaling.
Ext3
Ext3 stands for third extended file
system. The main benefit of ext3 is that it
allows journaling. Journaling has a dedicated area in
the file system, where all the
changes are tracked. When the
system crashes, the possibility of
file system corruption is less
because of journaling. You can convert a ext2 file system
to ext3 file system directly
(without backup/restore).
Ext4
Ext4 stands for fourth extended
file system. Supports huge individual file size
and overall file system size.
You can also mount an existing
ext3 fs as ext4 fs (without having
to upgrade it).
Several other new features are
introduced in ext4: multiblock
allocation, delayed allocation,
journal checksum. fast fsck, etc. All
you need to know is that these new
features have improved the
performance and reliability of the
filesystem when compared to ext3.
In ext4, you also have the option
of turning the journaling feature
“off”.
I hope this thread helpded you if anyone wants more about something then plz post in the thread ...
If anything in the post is wrong ,missing tell me.....
Special thanks to
CarlDeanCatabay,
droidphile,
-CALIBAN666-,
manornjan2050,
Omaxe,
And all other devs........
You can press thanks if it doesn't cost you....
Sent from my GT-S5360
Reserved
Sent from my GT-S5360
Well that is some nice compilation ....
u cud make it more attractive...adding more formattings and stuff :good:
This is unofficial cm11 kitkat android 4.4.4 for the Virgin Mobile Optimus V (runs on Sprint Optimus S as well)
Uses my 3.08 kernel.
I'm offering this over here because skinbark has been busy for quite a while and my builds are way more updated these days.
Purely experimental builds. No real support, I'm sharing my personal builds plus making equivalent internal builds for those of you who like them.
newest builds offering f2fs os2sd!
also fixed camera, and kernel updated to 3.0.101 with HardLight's patchset.
second post mostly outdated, now it's opengapps instead of pa for example. I haven't been updating this in literally years.
now using some of
[COMMIT] [AOSP] JustArchi's ArchiDroid Optimizations - Increases performance up to 6x
go thank justarchi for source of optimizations.
not right now said:
now built with linaro gcc 4.7 (kernel is built with homebrew ct-ng armv6k tweaked linaro gcc 4.7) with -O3 optimizations, except -Os thumb.
Click to expand...
Click to collapse
Wifi AP will reboot if turned on/off/on.
Everything else should work, tell me if it doesn't.
OS2SD /data mounting tweaks from HardLight's OS2SD version.
Smaller, more limited, standard nand-flashable internal builds offered for backwards compatibility or the less adventurous.
Use only THIS RECOVERY (info) (download)
archived said:
OS2SD friendly TWRP recovery, handles partitioning of sd card for OS2SD thanks techvendetta
Click to expand...
Click to collapse
download folder for internal builds:
download folder for OS2SD builds:
here's partitioning info for the OS2SD recovery.
advise: whatever leftover on your card for VFAT/sdcard, either 1Mb or 864Mb swap, 512Mb-768Mb for system, 1Gb or more for data.
expand /sdcard and/or /data as preferred if you use a bigger card. more space in /system? dunno why. doubt there's enough armv6 system apps to fill 512Mb.
current internal build: cm-11-20141014-EXPERIMENTAL-bigsuperROM_internal-thunderc.zip
current OS2SD build: cm-11-20141018-EXPERIMENTAL-f2fs_os2sd_bigsuperROM-thunderc.zip
this should be considered a dev thread since it's on XDA, there's an earlier and discussion thread here.
Sprint and Verizon fix zips attached. Flash in recovery after the ROM before first boot.
OS2SD info in 2nd post.
almost forgot: source
https://github.com/bigsupersquid/android_roomservice
Gapps:
advise: Skinny_4.4_Gapps_new_internal.zip for easy gapps. From here Optimus S won't fit the larger Skinny_4.4_Gapps-new.zip but the V should.
Be patient on first boot. Some reports are as long as 10 min to get past the bootanimation. Takes me at least 5 min.
Carrier Fixes:
Sprint and Verizon. Want another? Got an apns-conf.xml, then post it and your other carrier info.
Basic instructions for internal install:
in twrp, wipe internal data, internal system, and cache.
flash rom, internal carrier fix, gapps.
reboot system.
androidarmv6 turned on TLS in the kernel, and swapped the /system and /data partitions for more room on /system, so you have to use the newest TWRP-multi now as well.
thanks androidarmv6, cyanogen, aosp, thekraven for TheJBC and help, skinbark for initial booting and much work on kitkat for these phones, and techvendetta for his TWRP port. Thanks androidarmv6 and thunderg devs for 3.08 kernel I ported over to thunderc, and HardLight for f2fs in kernel and fstab flags.
OS2SD
OS2SD information
I have been playing with rom-from-sd for quite a while.
kitkat and cm11 make it easy, just by changing the fstab you can mount the ext partitions instead of the mtd partitions in init.*.rc
OS2SD (skinbark named it, it was my mod) uses the regular VFAT plus 3 extra ext4 (or one linux-swap and 2 ext4) partitions on the SD card to hold /swap, /system, /data. Recommend in order: leftover after other 3, 512MB, 512Mb, 1024Mb.
This allows virtually unlimited storage without link2sd methods of any kind. /system can handle whatever you want to flash to it without running out of space, which is handy because kitkat has to be trimmed down to fit an Optimus S or V with their respective 15*Mb or 165Mb of /system space.
when android is running from the card, mount external storage allows manipulation of /system and /data from your linux file manager.
Yeah, yeah, it's all a security hole, but I don't care. It's experimental and fun, and you can fit hundreds of apps on this four year old phone that is labelled 'obsolete' by LG and Qualcomm both.
I still need to remove the 'format sd' and 'unmount sd' from the storage menu in settings to avoid crashes.
Gapps:
advise: Skinny_4.4_Gapps-new.zip for easy gapps. From here
if you want a REAL gapps package...
I made pa_gapps flashing facilitator for twrp/os2sd.
Go get current micro pa_gapps, don't touch the zip.
flash after rom, pa_gapps_modular_micro*.zip no reboot needed.
then after flashing pa_gapps you flash the facilitator (it gets rid of armv7 keyboard libs and installs compatible play services framework.)
Click to expand...
Click to collapse
if you want to use any bigger pa_gapps packages (and you can even install the 200+Mb Stock package on os2sd!) you'll have to follow the instructions for the pa_gapps remover zip TKruzze posted up to remove Google+ (or you'll have fc'ing nightmares) and don't let it install Chrome either (there's another text file needed on the card like the remover, TKruzze left instructions.)
Remember, if you install Google Now (Search) go as quickly as possible into app drawer>Google settings>Search and Now>Voice>Hotword Detection and turn it off, then back up one submenu to Voice again and turn off all the checkboxes.
You can install voice search and talkback from market (enable talkback in accessibility settings) for those functions without fc. (and voice search wrapper from xda if you want voice control over Search.)
or just go the easy way on os2sd and use the Skinny_4.4_Gapps_new.zip which don't need a facilitator. But it's harder to get current Google Search that way since Play thinks we can't handle it.
Basic instructions for OS2SD install:
Use NEW twrp.
Wipe system, data, cache. Flash ROM carrier fix, gapps.
reboot.
reserved
Thanks for this! Just got this as a replacement phone, good to see support. Any recommended gapps? And is art supported?
Edit: Neither Banks nor PA gapps seem to work past setup. slimgapps or whatever its called in the other forum is all that goes then it seems.
Sent from my LG-LS670 using xda app-developers app
I cannot believe this phone is still going. You are the man, bss!
Sent from my SPH-L710 using xda app-developers app
Maestertk said:
Thanks for this! Just got this as a replacement phone, good to see support. Any recommended gapps? And is art supported?
Edit: Neither Banks nor PA gapps seem to work past setup. slimgapps or whatever its called in the other forum is all that goes then it seems.
Sent from my LG-LS670 using xda app-developers app
Click to expand...
Click to collapse
I forgot to link gapps. the skinnygapps from ac are the basic model.
I just tried pa gapps and they work ok without onetimeinitializer and setupwizard,
I haven't seen reference to art running on any armv6. I tried to walk it thru compilation early on, but ran out of free time to keep translating the thumb2 asm to thumb1 (or finding source where others had already done so) so it'd work.
new os2sd build.
zram turned on, p500 ami304d to match their kernel drivers (long-standing whoops there.)
probably other cm changes. I don't track em I just build and use it.
update. new builds up.
Excellent rom, but every so often it will freeze up and reboot. Is this normal? Im doing nothing but basic tasks like listening to music and then it freezes and reboots itself....
Sent from my GT-N5110 using xda app-developers app
ghostswagking said:
Excellent rom, but every so often it will freeze up and reboot. Is this normal? Im doing nothing but basic tasks like listening to music and then it freezes and reboots itself....
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
check your overclock, if it's too high you'll get random reboots. Best way I've found is run gallery while OC'd and play with it until it reboots. Set OC down on notch below where it doesn't reboot in gallery or camera.
If you're not OC'd then I'm not sure why it's doing that. some apps cause issues. logcat or /data/tombstones may have stuff you can pastebin if you want me to look into why.
4.4.3 update later today .
bigsupersquid said:
4.4.3 update later today .
Click to expand...
Click to collapse
bump... rom update, carrier fixes need updated but should work as long as you don't mind settings showing old build.
bump for really new release.
now using
[COMMIT] [AOSP] JustArchi's ArchiDroid Optimizations - Increases performance up to 6x
go thank justarchi for source of optimizations.
now built with linaro gcc 4.8 (kernel is only linaro gcc 4.7) with -O3 optimizations.
4.4.4
Looks like next rev be along here soon.
4.4.4
Gotta see if anything really changed.
big update
requires new recovery.
carrier fixes updated to 4.4.4
new release.
BUG:
ADB debugging needs toggled off and on to recognize cable.
Otherwise, optimized, with linaro kernel.
Might need to update your TWRP (since this is experimental, after all, things change.)
bugfix release.
takes care of adb toggle to connect cable issue.
adds armv6k-specific toolchain optimizations.
bump
new kernel toolchain (I built a linaro 4.7.4 with crosstool-ng with armv6k-specific flags)
p500 config imports... zram reenabled and selinux enforcing.
probably other upstream changes.
no screenshot
(I posted this question at FP support as well, but maybe this is also of interest to others considering to buy a FP)
Does Fairphone OS allow tweaking of CPU and kernel options (like overclocking, choice of governors, I/O profiles, memory management etc.)? If so, what options are available?
Is there built-in support for an sd-ext partition, or are there other supported means of enabling sd-ext?
Is there built-in support enabling sd-swap (or even better a data swap), or are there other supported means of enabling this?
What is the file system used (ext3 / ext4/ ...)?
Has anyone tried to use 4Ext as recovery platform?
Thanks in advance,
Lothar