Klin's Custom Kernel for YP-G1 USA and INTL
Latest Version: R3
This is a custom kernel that I made based off of STeVE's 3.0 sources. (He gave me permission to release this) I will be adding more features and continue to develop it. The sources are here: https://github.com/klin1344/Galaxy-Player-4.0-Kernel
Please be patient if there are problems as this is my first kernel and everything is still a learning process for me. (I'm completely new to Linux) Enjoy .
Disclamer: I will not be responsible if you brick your device or if any weird stuff happens.
R1 features:
- EXT4 support (See instructions in 2nd post on how to convert to EXT4)
- Insecure kernel (root in ADB)
- All features from STeVE's 3.0 kernel
R2 features:
- Improve touch screen responsiveness
- Custom bootanimation support; the kernel will look in both /data/local/ or /system/media/ for bootanims
- Netarchy/coolbho3ks SoD patch from Entropy512's source (allows you to use screen off profiles of under 800Mhz)
- Lots of tweaks and mods for overall performance and responsiveness
R3 features
- Ported ClockWorkMod 5.2.0.7 from semaphore kernel source for the I9000
- Raised FPS cap to 72
- Raised RAM from 341 MB to 352 MB
--Doing this would break HD video recording and taking photos while taking videos on the I9000, but our device has none of those features, so it shouldn't have any issues.
- More reliable and easier way of converting to EXT4 (see below) (thanks zaclimon for the advice)
How to install:
Check the PDA slot and flash the .tar in ODIN. Or if you're on Linux, extract the zImage from the .tar and flash with Heimdall.
All releases are here: http://www.mediafire.com/?m1bjqojv5ln6o
Thanks to:
- Entropy512 and rumirand for their kernel sources
- STeVE for his custom kernel and source
- Many kernel devs in other SGS and Nexus S forums for their kernel sources as well
- zaclimon for testing initial release and helping me with MD5 mismatch issues
How to convert to EXT4Instructions are for R3 only
1. Flash my kernel.
2. Make sure you have about 14 MB free space on /system.
3. Boot into CWM recovery and do a full nandroid backup.
4. Reboot, and from your computer go to the CWM backup directory on your sd card.
5. Change all the files from ".rfs.tar" to ".ext4.tar".
6. Open nandroid.md5 with a text editor and change all the ".rfs.tar" to ".ext4.tar". Save and close.
7. Eject the device from your computer FIRST. This step is crucial. Then disconnect from your player.
8. Reboot to CWM recovery and do a full restore.
Note: If you're using R5 of my KlassicROM then system is already EXT4.
Thanks to zaclimon for advising me to eject from computer first
If you appreciate my work and want to encourage me to continue developing, don't post "thanks", just click it!
Reserved for future use.
Thanks for your continual development for this player with the custom kernel. Is the CWM the same version from Steve's kernel, or have you put in a newer version?
Regarding your new rom release, I'm always reluctant to change things when they are working well. I hesitated (slightly) going from R3 to R4 and now I'm doing the same thing going to R5.
Quite frankly, R4 works great for me but I'll probably change over to R5 soon enough. LOL Also, if I'm understanding your release notes correctly for R5, I can no longer replace sanim zip with my own boot anim in /system/media, is that correct?
Thanks again, klin.
Mike T
webdroidmt said:
Thanks for your continual development for this player. Funny, I'm always reluctant to change things when they are working well. I hesitated (slightly) going from R3 to R4 and now I'm doing the same thing going to R5.
Quite frankly, R4 works great for me but I'll probably change over to R5 soon enough. LOL Also, if I'm understanding your release notes correctly for R5, I can no longer replace sanim zip with my own boot anim in /system/media, is that correct?
Thanks again, klin.
Mike T
Click to expand...
Click to collapse
Yes bootanimation is no longer supported, but thats an easy fix I will add to this kernel.
Sent using Tapatalk
How long should the device stay at the boot animation after converting the filesystems? Mine has been sitting for more than 5 minutes. I'm on Klassic R5
EDIT: Didn't know R5 was already using EXT4 until I read the note at the top of the page. Change it to a larger font and make it bold so people can read it better.
Screenshot
anyone ??
pentatonicfunk said:
Screenshot
anyone ??
Click to expand...
Click to collapse
It's a KERNEL not a ROM.
There is not screeshot. The kernel is the core of a linux architecture, the one that handle the drivers, the filesystem etc ...
The Rom is the "software" that is around the kernel with all the apps.
See the kernel and the rom as a onion, kernel as the centre and rom as the rest.
What is the benefit of EXT4?
Ext4 file system is much faster than Samsung's proprietary rfs filesystem. It is basically voodoo lagfix, except you have to manually convert instead of it doing it automatically.
Sent using Tapatalk
klin1344 said:
Ext4 file system is much faster than Samsung's proprietary rfs filesystem. It is basically voodoo lagfix, except you have to manually convert instead of it doing it automatically.
Sent using Tapatalk
Click to expand...
Click to collapse
So that makes closer to how others like HTC does it?
caseyatbt said:
So that makes closer to how others like HTC does it?
Click to expand...
Click to collapse
I'm not sure what HTC uses, but the Linux standard us ext4.
Sent using Tapatalk
Updated to r2.
Edit: oh yeah, some suggestions for a kernel name would be nice.
Sent using Tapatalk
Hmm, how about "Klin's kool kernal"
Or "Klin's kustom kernal" might be better?
"Netarchy/coolbho3ks SoD patch from Entropy512's source"
What is that, btw? Nvm about that, just read about it in entropy512's thread.
One more thing: you said somewhere that you had ported a newer version of cwm than what is in Steve's rom, is that in here?
Sent using Tapatalk
iJimaniac said:
Hmm, how about "Klin's kool kernal"
Or "Klin's kustom kernal" might be better?
"Netarchy/coolbho3ks SoD patch from Entropy512's source"
What is that, btw? Nvm about that, just read about it in entropy512's thread.
One more thing: you said somewhere that you had ported a newer version of cwm than what is in Steve's rom, is that in here?
Sent using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestions.
The CWM had too many problems than it was worth to sort everything out so I'll have to stick to steves cwm implementation for now.
Sent using Tapatalk
Nice!
Can I just flash this over the current kernel? (R1)
I'm on your r5 ROM.
And also, does this version fix the lagging issues in internet browsers and games?
Se7enex said:
Can I just flash this over the current kernel? (R1)
I'm on your r5 ROM.
And also, does this version fix the lagging issues in internet browsers and games?
Click to expand...
Click to collapse
Yes it is compatible with my ROMs. I'm not sure if it fixes the issues because I'm not using Klassic anymore so I can't test it. But I'm using rooted/deodexed stock with this kernel and it is pretty smooth.
Sent using Tapatalk
klin1344 said:
Yes it is compatible with my ROMs. I'm not sure if it fixes the issues because I'm not using Klassic anymore so I can't test it. But I'm using rooted/deodexed stock with this kernel and it is pretty smooth.
Sent using Tapatalk
Click to expand...
Click to collapse
Found a problem. If you are to flash r2 from stock and follow the steps you get suck and the logo. You have to flash r1 follow the steps and then r2.
Edit: On a side note I only see system and cache are the only ones that are converted to ext4. Is that supposed to happen?
{
"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"
}
Hey klin, can you post screenshots of the mounts like mine on the post above so I know I'm not alone? The app is Android system info. I feel bad for you cause it seems like i'm annoying you with problems
Related
I bring you an eclair rom on baseband .67. It has a couple of tweaks... more to come. it is edited and has some of my usual flavor in a rom. for those that care about quadrant it gets in the 800's... this is actually a base to work on a dual boot rom and has market and several gapps apks... small size and smooth. Use at your own risk as I am not responsible for anything you do to your phone.
ECLAIRbasicFlaVor.zip.html
{
"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"
}
reserved for future use
???
Planning to make a barebones 2.1 rom?
sent from x10 CM7 (FreeXperia Project)
yup. made one but not as small as the other and I want it to work on bb .67
just have to wait to get to a linux computer to resize ext2
I left in some of the gapps for now
rdannar said:
yup. made one but not as small as the other and I want it to work on bb .67
just have to wait to get to a linux computer to resize ext2
I left in some of the gapps for now
Click to expand...
Click to collapse
no need to use linux computer to resize!!!
[APP] Windows: Create Your Own Data.img Maker Application, +/- From Existing data.img
there u go.... u can use the above app to resize any ext2/4 fs image in windows!
Good going....
few pointers
if you want to keep bare bone 2.1
data partition either eliminate completely i.e. edit the boot.img file init.rc
or create a simple 100 MB file 100 seems to be the idea value that worked for me
and system i am down to 175 MB and going down.... Will post my system.ext2 once i have some stable one.
anantshri said:
Good going....
few pointers
if you want to keep bare bone 2.1
data partition either eliminate completely i.e. edit the boot.img file init.rc
or create a simple 100 MB file 100 seems to be the idea value that worked for me
and system i am down to 175 MB and going down.... Will post my system.ext2 once i have some stable one.
Click to expand...
Click to collapse
yup system down to 170mb here with gapps intact... but first boot is taking LONG...
DooMLoRD said:
yup system down to 170mb here with gapps intact... but first boot is taking LONG...
Click to expand...
Click to collapse
I am plaining on removing everything and just use it for camera.
sort of a widget on my normal screen to boot to camera mode.
and camera mode being this custom rom.... that smallest image could be camera alternative for all till we get gingerbread.
anantshri said:
I am plaining on removing everything and just use it for camera.
sort of a widget on my normal screen to boot to camera mode.
and camera mode being this custom rom.... that smallest image could be camera alternative for all till we get gingerbread.
Click to expand...
Click to collapse
precisely...
lets start tailoring it down for a full working img... i had deleted LOTS of stuff but then could get it to be stable
so now restarting... currently have 200MB system img testing now
DooMLoRD said:
precisely...
lets start tailoring it down for a full working img... i had deleted LOTS of stuff but then could get it to be stable
so now restarting... currently have 200MB system img testing now
Click to expand...
Click to collapse
you can use any thing I post up here if you want... I am working on a slimmer one and will have it done by the end of the weekend. just use any bb changer to add files for bb you want. I think this one will be stable has jit2 and has some tweaked libs from other roms in it.
posting rom in a few minutes
i am using it as a regular rom first to see how stable it is... And it is down to 153mb with some gaps installed
cheers
ps.. don't forget you can edit any image in any file to gain size also
@rdannar
looking at ur modified OP i am slightly confused...
u want to use the ROM u release here as a base rom? or as the one inside the .ext2 files?
also the boot.img provided by Z will not work on bb2.1.67... unless u strip out the ramdisk and use only that to boot...
rdannar said:
i am using it as a regular rom first to see how stable it is...
cheers
ps.. don't forget you can edit any image in any file to gain size also
Click to expand...
Click to collapse
@rdanaar
can u provide the current size of this rom (finally the size which it shows on /system)
DooMLoRD said:
@rdannar
looking at ur modified OP i am slightly confused...
u want to use the ROM u release here as a base rom? or as the one inside the .ext2 files?
also the boot.img provided by Z will not work on bb2.1.67... unless u strip out the ramdisk and use only that to boot...
Click to expand...
Click to collapse
hey rdannar, do suggest which method you used.
also i my stripping is down to 160 MB right now hope i could go more down and then will post all updates as a new thread...
@anatshri, rdannar
i think lets keep the dual boot discussions to z's dualboot proof-of-concept thread...
that way it will be lot easier to follow... and will keep all relevant info at one place...
DooMLoRD said:
@rdannar
looking at ur modified OP i am slightly confused...
u want to use the ROM u release here as a base rom? or as the one inside the .ext2 files?
also the boot.img provided by Z will not work on bb2.1.67... unless u strip out the ramdisk and use only that to boot...
Click to expand...
Click to collapse
this will be inside the ext2 file by replacing files... trust me doom... I have already had his dual boot with calls working on my phone. just replace the core bb files. this is close to the same rom he has with some image changes
rdannar said:
this will be inside the ext2 file by replacing files... trust me doom... I have already had his dual boot with calls working on my phone. just replace the core bb files. this is close to the same rom he has with some image changes
Click to expand...
Click to collapse
ofcourse buddy...
OT:
damn it feels so weird to go back to Eclair after using FreeX10 & CM7 for almost 4 months now
@rdannar,
as you are using it for daily rom can you confirm following stuff working.
1) Wifi
2) BT
3) market
Rdannar, you could do with the ARC data/wifi icons etc.
Ill see if i can get these!
dualboot_DooMLoRD_MOD_rdannar_2.1.B.0.1
Since zdzihu wanted to encourage devs & users to switch to new xRecovery I am releasing this proof-of-concept as an Edify update.zip compatible with xRecovery v1.0.0… the concept being that we can convert ANY rom’s (nandroid/recovery) backup to dual boot image (yaffs to ext2 img) which actually boots!!!!
Also I am not saying that this is the only way but rather that this is the way I achieved it…
A BIG THANK YOU TO ZDZIHU FOR GIVING US THIS NEW TOOL TO PLAY WITH
all credits for the base 2.1.B.0.1 ROM goes to rdannar cause I have modded rdannar’s 2.1.B.0.1 ROM from this thread!!!!
THANK YOU rdannar for ur awesome work!!
to check out the dualboot update.zip here:
http://forum.xda-developers.com/showthread.php?p=14488760#post14488760
really appreciate your answers
Sent from my U8150 using xda premium
faux123 said:
What is a Kernel? The Kernel is the Foundation in which everything else builds upon in any software system.
[Car Analogy]: Kernel is like the Engine, Electrical system and the Transmission to a car. The Library, Framework and the Apps [AKA ROM] are the body frame and the rest of the Car.
Click to expand...
Click to collapse
In other words, you can sort of think of a ROM as your "version of the OS" on this phone, while the kernel is the thing that manages memory, tasks, etc and contains the drivers to the input/outputs. (This is probably highly inaccurate.) If you have options for, say, volume waking, changing the navigation bar, changing general OS settings, that's probably the ROM. Kernel changes are usually to subtly increase speed/reduce battery drain, but they can also be driver features like color control, vibration level, touch wake and so on.
A ROM comes with a default kernel when you flash it. However, the kernel can often be changed, by flashing a different one (the files just get overridden). Not all kernels are compatible with all ROMS/devices, so this does involve a bit of reading (and nandroid backuping, of course).
---
ROM literally stands for read-only memory, but I'm not sure this is true. I think the access is only limited by permissions, as root explorer seems to have access to everything. (Once again, I could be quite wrong.) The name probably comes from that the phone manufacturers intended for it to be read-only, since phones were originally intended to be far more locked-in than computers, for some reason.
ROM
(previously) During the production process, the whole operating system was written on ROM [Read Only Memory]
(now) They write it on a Flash-ROM [rewrite-able (Read Only) Memory]
In XDA or Android,
ROM stands for the whole packages, which the manufacturer otherwise write at manufacturing
Package includes:
-Operating System
-Kernel
- diverse Platforms (depending on) [Java is always for Android required]
-Applications
Kernel
Android is based on Linux or it just uses the Linux - Kernel
- the Word kernel comes from Linux and that means Core, because it comes from German Noun [Kern] {I speak German, so understandable for me ;-)}
- Kernel is a bridge between Hardware and Software, which manage the whole Calulating process
{
"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"
}
in XDA or Android Modifier
-try to modify the Kernel to accelerate the phone or to activate new/better function
Know-how
Flashing a new ROM/Kernel --> it means new/other version of firmware/Kernel onto your phone
custom ROM/Kernel --> a ROM/Kernel which was not developed manufacturer, it means someone else has modified/tuned/pimped/hacked a ROM
---Recommandable ROM is "CyanogenMod"
Stock ROM/Kernel --> a firmware/Kernel that comes from manufacturer or default/non-Modified ROM/Kernel
Links
http://en.wikipedia.org/wiki/Kernel_(computing)
http://en.wikipedia.org/wiki/Read-only_memory
http://en.wikipedia.org/wiki/ROM_image
_______
If it was useful, so don't forget to press the Thank-Button
thanks for the info. :good:
i dont get it...& also i cant find a thread for flashing details...can u help plz
Sent from my GT-S5360 using xda app-developers app
a kernel is the backbone of the rom
both have to be compatible with each other.
a kernel influences the battery usage of the rom, it also helps it to boot after flashing. a wrong kernel if flashed will make the phone get stuck at logo. a kernel will decide how safe it is to wipe/format your system or if some chips will be triggered to brick the emmc.
it determines root issues too. certain features of the rom will not work unless the kernel supports it like multiwindows in JB. the kernel decides if
your phone will support bootanimations. it will also decide from its nature if you can overclock your phone or undervolt it and to what extent.
custom kernels are released by highly knowledgeable developers and usually it is released in the forum set up for your device. All details of flashing etc are written in the OP. Feedback is given in following posts by those who have used it for reference of new users. usually kernels are paclaged in CWM zips which can be flashed from recovery. sometimes you may come across tar files that can be flashed with mobile or pc odin (depending upon device.
Sent from my NEO L using xda app-developers app
---------- Post added at 09:33 PM ---------- Previous post was at 09:29 PM ----------
Dhaval Bhatt said:
i dont get it...& also i cant find a thread for flashing details...can u help plz
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1508585
Look in this u will get an ida about fashing Rom / kernal
Sent from my NEO L using xda app-developers app
Nice info
Really superb explanation.
What ROM and Kernel to install. Confused
Hi Guys. Ive been reading through the forums here and there but im still confused on what rom and kernel do i need to flash on my Samsung galaxy s3 I9300 international version. I really dont want to mess up this phone thats why i wanted some help from the experts . Ive already rooted my phone and backup everything using titanium backup.
Baseband version : I9300DXELK1
Kernel : 3.0.31 stock
Build Number : I9300XXEMA2
Basically what i really wanted was to have a better battery life, ofcourse new themes/looks/feel, remove all the bloatwares, and hopefully to add items on my multiwindow would really be great. Im doubtful of what version of omega rom and siyah kernel to flash as ive read that they should harmonically match with each other not to mess up the phone. Your help would really be appreciated specially for noob like me
[email protected] said:
Hi Guys. Ive been reading through the forums here and there but im still confused on what rom and kernel do i need to flash on my Samsung galaxy s3 I9300 international version. I really dont want to mess up this phone thats why i wanted some help from the experts . Ive already rooted my phone and backup everything using titanium backup.
Baseband version : I9300DXELK1
Kernel : 3.0.31 stock
Build Number : I9300XXEMA2
Basically what i really wanted was to have a better battery life, ofcourse new themes/looks/feel, remove all the bloatwares, and hopefully to add items on my multiwindow would really be great. Im doubtful of what version of omega rom and siyah kernel to flash as ive read that they should harmonically match with each other not to mess up the phone. Your help would really be appreciated specially for noob like me
Click to expand...
Click to collapse
As for ROM i would say get Cyanogenmod 10/10.1
And for kernel - franco kernel
That's What i would say is awesome + safe
Or if you prefer paranoidandroid or aokp go for them , it is a matter of personal preference.
Franco kernel will help with battery life.
Guide To Install Franco Kernel - Click here
Guide to Installing Cyanogenmod 10.1 - Click
here
Known issues/bugs - click here
Hit the tanks button if i helped
Thanks Techmasta :good: i would give it a try. But is there anything that i need to look for like compatibilities? or are most of the kernels and roms compatible with my baseband/firmware. Thats what i am really afraid of before proceeding with flashing
Custom ROM on Stock Kernel
Thanks for the information!!
Will a custom rom work on Stock Kernel tooo????
Will it work smoothly????
{
"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"
}
YOU CAN NOT DUAL BOOT THIS.
This is a project page to get the Galaxy SII i9100 back to a tier 2 device,
it is currently using the latest Firefox OS source code from the v1.1.1.
We've done it guys! We have reached the first milestone, BETA! This ROM is now considered stable enough for daily use.
- Microphone (needs testing!)
- Wrong DPI
- Hardware acceleration
- Camera
- Others I may not have discovered yet.
Installation Instructions said:
1. Go to cwm recovery and do a complete backup of your phone.
2. Extract the content of firefoxos_beta_v1_10102013.zip file to your hard drive, using your preferred rar/zip archiver (ex: WinRAR)
3. From your phone, go to mounts and storage, and select the last option, mount USB storage.
4. Copy the folder you extracted from the archive 2013-10-10.16.12.39 to your sdcard in the folder clockworkmod/backup (if you don't have that folder, create it)
5. Wipe data/factory reset (make sure you have a backup)
6. From your phone go to backup and restore -> restore -> 2013-10-10.16.12.39
7. reboot system now
Click to expand...
Click to collapse
As a final note DO FRICKIN' NOT format your /system, /data or /cache partitions
through the Firefox OS CWMR if your device is susceptible to a eMMC brickbug.
You have been warned.
This release is purely for testing, I need to know what does and doesn't work.
But I'm no programmer, fixes may take a while to be released unless others decide
to contribute.
Download links are here: REMOVED
XDA:DevDB Information
Firefox OS - GT i9100, a ROM for the Samsung Galaxy S II
Contributors
abtekk
ROM OS Version: 4.0.x Ice Cream Sandwich
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Must be rooted with Clockwork Mod Recovery
Based On: B2G - Boot2Gecko
Version Information
Status: Beta
Current Beta Version: v1
Created 2013-10-07
Last Updated 2014-02-03
Reserved
Download mirrors:
REMOVED
Reserved
Thanks for reviving the project mate Almost forgot about this OS until I saw this thread :good:
-Grift- said:
Thanks for reviving the project mate Almost forgot about this OS until I saw this thread :good:
Click to expand...
Click to collapse
No worries, I'm happy to be working on it
Preliminary/quick sneak peek into the alpha...
The Setup Wizard cannot seem to detect the Time Zone and whatnot in the specific section, but the time adjusted itself after the phone was setup
Messages work (send and receive)
Sound notifications work. Not sure for music/audio.
Importing of contacts via vcf works
Notification Center/Status Bar is laggy.
No built in screen off when in call ( I assume proximity is not working?)
Calls do not seem to work
Lock/unlock/power button works
Menu and Back button are useless (I assume we can use these somehow?)
For an alpha, this is good progress.If we get HW acceleration working, it would be much bearable. As much as I want to be a tester for it, I'm afraid that will have to wait. Good luck with the project!
EDIT @abtekk once I find the time, I'll try to setup a dualboot with it as well and see what I can do.
!n0x said:
Preliminary/quick sneak peek into the alpha...
The Setup Wizard cannot seem to detect the Time Zone and whatnot in the specific section, but the time adjusted itself after the phone was setup
Click to expand...
Click to collapse
I think that's to do with geolocation. I'll take a look, though.
!n0x said:
Notification Center/Status Bar is laggy.
Click to expand...
Click to collapse
I believe that is hardware accel.
!n0x said:
No built in screen off when in call ( I assume proximity is not working?)
Click to expand...
Click to collapse
Probably not.
!n0x said:
Calls do not seem to work
Click to expand...
Click to collapse
No microphone support, that's why.
!n0x said:
Menu and Back button are useless (I assume we can use these somehow?)
Click to expand...
Click to collapse
Firefox OS isn't designed for use of these buttons. I could maybe bind them to another function.
!n0x said:
Good luck with the project!
Click to expand...
Click to collapse
Thank you.
Is possible to install as second rom?
marbutina said:
Is possible to install as second rom?
Click to expand...
Click to collapse
You can with Siyah Kernel.
abtekk said:
You can with Siyah Kernel.
Click to expand...
Click to collapse
Thanks. Maybe I try it then.
marbutina said:
Thanks. Maybe I try it then.
Click to expand...
Click to collapse
Great, let me know how you get on.
!n0x said:
Preliminary/quick sneak peek into the alpha...
EDIT @abtekk once I find the time, I'll try to setup a dualboot with it as well and see what I can do.
Click to expand...
Click to collapse
Sounds good. Could you report the bugs you found in to the bug tracker, please.
WiFi now works.
The camera is next on my list.
It is possible dual boot with dorimax kernel?
hocruxx said:
It is possible dual boot with dorimax kernel?
Click to expand...
Click to collapse
You can dual boot with any kernel that has the dualboot feature. Siyah is the recommended, though.
Ok i will try as secondary rom
I tried with the latest Dori 9.41 stable, and it doesn't seem to boot to the Firefox partition properly. Needless to say, I'll have to try Siyah later.
EDIT: Seems that prealpha 2 is way smaller than 1. Why is this so? Do we flash it on top of alpha 1 or is it good to go for clean flash?
!n0x said:
I tried with the latest Dori 9.41 stable, and it doesn't seem to boot to the Firefox partition properly. Needless to say, I'll have to try Siyah later.
Click to expand...
Click to collapse
Siyah must be the only compatable one, then.
!n0x said:
EDIT: Seems that prealpha 2 is way smaller than 1. Why is this so? Do we flash it on top of alpha 1 or is it good to go for clean flash?
Click to expand...
Click to collapse
Just manage to purge useless crap out of the second release. It's good for a clean flash .
https://bugzilla.mozilla.org/show_bug.cgi?id=755405
This might help you with the microphone
Sent from my MB886 using xda app-developers app
wildchild048 said:
https://bugzilla.mozilla.org/show_bug.cgi?id=755405
This might help you with the microphone
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Thank you. I'll see if I can sort it.
{
"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"
}
***Disclaimer***I am not responsible if you break your stuff. Use at own risk!
I am not a developer and do not pretend to be one. I'm an Android enthusiast.
Why no Aroma?
Because I've made this ROM to my liking for myself, removing apps I'd never use. I have no need for a customized installer. I'm sharing this with you all because I'm sure there's somebody else who wants a simple, optimized ROM with the basic, stable features. If you want more options or customizations, this ROM isn't for you.
No complaints
I do this in my spare time.
Special requests
I'll accept special requests, but that doesn't mean they'll come true.
Bug Reports
Bug reports are welcome! Keep in mind: This is mostly stock and most bugs will be official firmware bugs.
Updates will come along when I have time and when I see something I'd like changed :good:
ROM: Terok Nor
Based on UEU2CNE2 US Official Firmware
DeKnoxed system and kernel
Deodexed
build.prop improvements
Slimmed down
Busybox
AOSP 4.4 KitKat system sounds
Added AOSP 4.4 ringtones, alarms, notifications, and UI sounds
Removed power on sound
Custom, smaller S Pen pointer
Scrolling Wallpaper enabled in SecLauncher3.apk (TouchWiz Launcher)
Android L Keyboard
Galaxy S5 Boot Animation
SELinux: Permissive
Special Feature: @civato SphereKat blazing fast kernel with S Pen fix! For more info on his kernel, please see the SphereKat thread!
*
Samsung Milk Music - Powered by Slacker
- Milk is supposedly available for all Galaxy devices, except it's not available for all Galaxy devices. I've added it here for you all to enjoy
*
Amazon Kindle for Samsung
Special Note:
* Images are copyright to their respective owners
A GT-N5110
One of the latest recoveries that supports Andoird 4.4. I recommend the latest PhilZ recovery: Found here, flash in ODIN
Bootloader upgrade: With Civato's SphereKat kernel, the 4.4 bootloader upgrade is no longer required!
IF YOU DO NOT MEET THESE REQUIREMENTS.. STOP HERE!
A full wipe is only necessary if coming from a different ROM, including Terok Nor v2. All updates to v3 r1+ can be dirty flashed (unless otherwise noted).
1. BACKUP BACKUP BACKUP!
2. Flash
3. Reboot
(click the image ^)
MD5 hash: 25e41bad0695fc543dd75bde681fefb0
Don't forget to hit the thanks button!
XDA:DevDB Information
Terok Nor v3, ROM for the Samsung Galaxy Note 8.0
Contributors
MrHyde03
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: 4.4.2 Bootloader and TZ
Based On: UEU2CNE2 Official 4.4.2
Version Information
Status: Stable
Created 2014-05-26
Last Updated 2014-08-18
2014-06-30
Release 6
Added Android L Keyboard!
Added Galaxy S5 Boot Animation
Updated @civato 's SphereKat to v4.0
2014-06-10
Release 5
Removed S Note 3.1 (If you want, the install this APK S Note 3.1 APK
Rebuild on UEU2CNE2 US Official Firmware (XAR)
Now released with @civato's SphereKat kernel! Make sure you hit THANKS in his SphereKat thread and send him a beer!
Bootloader upgrade: With Civato's SphereKat kernel, the 4.4 bootloader upgrade is no longer required!
2014-05-28
Release 4
Deodexed /system/app, /system/framework, and /system/priv-app
2014-05-27
Release 3
Corrected issues brought on by R2 where the device would not boot after a clean flash.
2014-05-26
Release 2
Enabled Scrolling wallpaper in SecLauncher3.apk (TouchWiz Launcher)
Corrected Text Cursor offset in framework-res.apk, Thanks Civato
2014-05-26
Release 1
Initial release
Civato
All others who've made modding Android possible
Thanks to all who have donated I hope I can continue bringing a stable, smooth experience to the great people here at XDA :good:
Each * represents an additional donation! Much appreciated!!
rfb813 *
There are currently two versions of S Note installed. The orange-red icon is the new version which is available on the GS5 as a "Galaxy ESSENTIAL". The brown icon is the stock Note 8 version. I may remove one of them in future updates.
STOCK KERNEL AND RECOVERY
Download this zip file and extract. The kernel (boot) and recovery are in their own .tar.md5 archives. Flash each in ODIN.
yay!
@MrHyde03
Regarding the S-pen cursor offset (cursor when hovering above a text with the pen), I fixed it in the framework (for the s-pen pointer I'm still waiting for kernel source, I mailed samssung yesterday for the source)
Here is the file for the framework file.
Decompile the framework and drop it in res/drawable-tvdpi.
When compiling the framework again it will throw some errors.
To slove this:
Go to res/drawable-tvdpi and remove the following files
tw_scrubber_control_focused_holo_red.PNG
tw_scrubber_control_holo_red.PNG
Then go to res/values/strings
open that file and on the line 1795 remove the % before the d and before the 2$s
it should look like this
Code:
<string name="wifi_p2p_enter_pin_dialog_message">Enter the PIN and tap Connect within d seconds to connect to 2$s.</string>
now compile and the errors will be gone.
civato said:
@MrHyde03
Regarding the S-pen cursor offset (cursor when hovering above a text with the pen), I fixed it in the framework (for the s-pen pointer I'm still waiting for kernel source, I mailed samssung yesterday for the source)
Here is the file for the framework file.
Decompile the framework and drop it in res/drawable-tvdpi.
When compiling the framework again it will throw some errors.
To slove this:
Go to res/drawable-tvdpi and remove the following files
tw_scrubber_control_focused_holo_red.PNG
tw_scrubber_control_holo_red.PNG
Then go to res/values/strings
open that file and on the line 1795 remove the % before the d and before the 2$s
it should look like this
Code:
<string name="wifi_p2p_enter_pin_dialog_message">Enter the PIN and tap Connect within d seconds to connect to 2$s.</string>
now compile and the errors will be gone.
Click to expand...
Click to collapse
Awesome. You just saved me some time.:highfive: Also, you don't have to delete the two PNGs, just change the extension from PNG to png. I also emailed Samsung on Saturday but have not had as much as a peep from them. Aren't they required under GPL to release the source when their software is released?
Anyways, thanks again Civ.
Updated to Release 2! Check Change Log for details.
Clean flashing to R2 is broken. Only works if dirty flashing. Because of this I've pulled R2 from the download. Go back to R1 if you're having issues with booting. I know what the issues are, I just don't have time tonight. It's late.
I've udpated the download URL to reflect R1.
MrHyde03 said:
Awesome. You just saved me some time.:highfive: Also, you don't have to delete the two PNGs, just change the extension from PNG to png. I also emailed Samsung on Saturday but have not had as much as a peep from them. Aren't they required under GPL to release the source when their software is released?
Anyways, thanks again Civ.
Click to expand...
Click to collapse
Yep they should release it . But some delay is expected.
Fixed the issues from R2. R3 is out and stable.
I could not get R2 to boot at all past the Samsung splash. I'll download R3 tonight. Thank you.
Sent from my GT-N5110 using XDA Premium HD app
glockman4519 said:
I could not get R2 to boot at all past the Samsung splash. I'll download R3 tonight. Thank you.
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
Yep.. that was my fault.. sorry. I didn't properly recompile a few APKs, but we're all good now.
Release three working fine! Thanks and have one on me:4C4716763M934291T.
rfb813 said:
Release three working fine! Thanks and have one on me:4C4716763M934291T.
Click to expand...
Click to collapse
Glad you're enjoying it! Thanks!
2014-05-28
Release 4
Deodexed /system/app, /system/framework, and /system/priv-app
I was beginning to think this ROM wasn't going to install for me. I did an MD5 check - it passed. I flashed the new bootloader firmware and then flashed the PhilZ recovery. Tried to install the ROM and got an Error: Status 7. Tried the newer CivZ recovery and same thing.
Finally got it to install using TWRP 2.6.3 (my favorite, anyway).
Now going to try restoring data from v2.1 and see how that goes.
mletchworth said:
I was beginning to think this ROM wasn't going to install for me. I did an MD5 check - it passed. I flashed the new bootloader firmware and then flashed the PhilZ recovery. Tried to install the ROM and got an Error: Status 7. Tried the newer CivZ recovery and same thing.
Finally got it to install using TWRP 2.6.3 (my favorite, anyway).
Now going to try restoring data from v2.1 and see how that goes.
Click to expand...
Click to collapse
That is odd.. I flashed and reflashed and wiped then reflashed over and over to make sure I didn't have any more duds like R2 was and haven't had any issues with R4. Regardless, I'm glad you got it to flash.
Let me know if you have any other issues.
MrHyde03 said:
Let me know if you have any other issues.
Click to expand...
Click to collapse
Well, don't try restoring data from v2.1, it'll just cause tons of crashes and an error message that the Android UID doesn't match. Guess I'll be TiBU-ing this morning. Just as well, I see that R4 just posted...
mletchworth said:
Well, don't try restoring data from v2.1, it'll just cause tons of crashes and an error message that the Android UID doesn't match. Guess I'll be TiBU-ing this morning. Just as well, I see that R4 just posted...
Click to expand...
Click to collapse
If you're restoring from the same version recovery the backup was created with, then you shouldn't have any issues. That's been my experience. I've always had things break if I restore with a different recovery.
Should you update the firmware to the new Canadian firmware found on samfirmware? It was released after the UK firmware and Canada is closer to the US but there are probably no differences... just asking
Well here's the continuation of Barren, but now with ZV6.
{
"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"
}
Proudly Presents...
BarRin
What is has:
This Rom will install the modem, kernel, and the Rom
Rooted
busybox
zipaligned
V2 - init.d support through the kernel
Install
In TWRP, select Advanced, Wipe, then /system, /cache, /dalvic, and /data. DO NOT select internal or ext SD!
Flash Rom
Update profile/prl
Go to "Settings, More, Mobile network, and select anything but "Global
Change logs :
Code:
[B]V3.0.1[/B]
Just an update that is mostly Themed. Flash V3, then this. This works without xposed. So it MAY work with any ZV6 Rom.
Themed Messaging. No more Gawd Awful Yellow!!! Blends with stock theme now.
Themed Navbar - To get the Navbar to work with apps, Select "White Gradation" in Settings>Display>Home Touch Buttons>Color.
New bootani. - Courtesy of @HPTesla
Added oversharpening script from Skin1980 to the kernel. - so, new Stock kernel.
[B]V3[/B]
Updated SuperSU so we shouldn't have to update binaries - installs a whole different way
Stock ZV6 kernel with init.d and kexec support - MultiRom compatible
Native host files - you don't need an ad blocker app anymore
executable zipalign binaries - it'll run in terminal
Updater-script will delete a lot of junk files now
Qslide fix for WIFI calling - no longer stuck at the 4th slot
build.prop changes - removed some, fix a couple
init.d scripts - removed a couple that weren't doing anything
Most of everything since V2
This took a lot of work so there's probably other small things I forgot
V 2.3.1_beta
This can be used on any stock ROM and any ZV6 version.
1.Using the APN from Vanir as it's the most thorough one out. It SEEMS to give better reception for phone, data, and the handshake between LTE/eHRPD/3G is better. THIS is why this is beta. [B]You must have your phone all setup before using this!!![/B] It will not work on a fresh install. Also, it doesn't allow APN changes other than Sprints. Hotspot MAY work but unknown.
2. Removed MLT, and LGLIA apk's. More LG tattletales.
3. Fixed a couple of my goofs in build.prop. Got rid of the hiccup as I call it.
4. Added LG KB Black Theme for those that use LG KB.
5. init.d script changes
V 2.3 Includes everything from V2, and
build.prop edits for battery, speed and reception
Added LG FM Radio to /data (uninstallable) - It requires the headphone but will play through the speakers when plugged in. Headphones seem to act as the antennae. Thanks to @anvicota for this
Updated Sprint VoiceMail
V2.2 -Includes 2.1 plus-
Hopefully fixed install of bootani for people coming from Stock or Flashtool
Modified platform.xml - SD card fix?
Modified mixer paths- less increase on BT only. - Hopefully fixes distortion some were having
Install of Rin Kernel - installing a different way for the very few - again, hopefully
build.prop to reflect BarRin_2.2 in Software info
V2.1 - New Rin Kernel and BarRin bootani.
V2 - Like the original Barren. Nice and slim.
Removed most all, LG, Sprint apps
Added xposed and Tweakbox - removable
Some apps moved to /data
init.d scripts
Increased and FIXED Aux_out mixer path
Now installing with "Rin" kernel.
V1
Many apps removed but still giving the LG Stock experience. Still has Concierge, Smart Cards, Weather, OK Google on all screens, etc
A few build.prop mods - LG's mistake, All split window apps
Sd card fix
mixer_paths
Updated LG Keyboard, Quickmemo, Sprint voicemail - all can be uninstalled
Donators - ( Never asked for, but very much appreciated. Thank you )
Previous Barren
** @mjjcb
** @nkyer
BarRin
* @mjjcb
* @Kemocybr
Downloads:
______________________________
BarRin_D_V3.0.1 - Just an Update. Flash V3, then this. See Changelog.
BarRin_V3 - This is the full ROM. ZV6 Multirom Kernel, Modem included. Strongly suggest a CLEAN INSTALL! AND MAKE SURE YOU DISABLE ANY "SET ON BOOT'" OPTIONS YOU HAVE IN TRICKSTER/FAUX!!
- You can read this also if you'd like. Ramblings of this Stooge
BarRin_2.3.1_beta This is NOT a rollup of the previous. This is considered beta for now and can be used on ANY stock ROM. See change log above.
BarRin_2.3 - Must have at least V2 installed. Then flash this. It has everything up until now.
Barrin_2.2 - Another update. You must have V2 installed first, then flash this. If you installed 2.1, update to this as there were some changes we need.See change log - READ HERE for more info/fixes - Also, Software info is going to say "BarRin_D_2.2 regardless. Sorry bout that.
BarRin _2.1 - This is just an update. You must have BarRin V2 installed first. Then flash/update to this. This is just an update.
BarRin _D_V2
BarRin_O_V2
BarRin_D_V1
BarRin_O_V1
XDA:DevDB Information
BarRin, ROM for the Sprint LG G3
Contributors
engine95, HPTesla, seanskiT!, Tectas
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Stock
Version Information
Status: Stable
Created 2014-11-23
Last Updated 2015-01-21
Added files and extras
BarRin V1 to BarRin V2 for Concierge/Weather
You'll need to flash either BarRin V1 Odexed or Deodexed first. Then flash this. This SHOULD work on both and update you to V2.
I'm not supporting this, so if you install it you're on your own. That's just because I'm not including it since V1.
BarRin_2.2_mixer_paths - Same as below, but with less BT increase. Some were getting distortion.
Fixed Aux-out mixer_paths
This will update ANY ZV6 mixer paths to increased volumes.
Stock_ZV6_mixer_paths
Stock ZV6 Kernels
Stock and Stock with init.d support.
1-21-15 -And now with MultiRom support
Flashable APN's
Flashable_Stock_Hosts
Issues/Fixes
SD cards
SD cards are becoming an issue for some reason. If you've followed ALL the instructions in the OP, and are still having issues, you may need to wipe your ext SD. And sometimes Internal as well.
Remove your ext SD and boot up.
If the problems are solved then you need to format your SD card in Windows or Linux as Fat32 no matter what size your card is. DO NOT USE TWRP to format Ext SD.
Root
If SuperSU has issues updating it's binaries, you may need to flash This when you flash the ROM.
Thanks Holmes. Downloading now.
One more...just in case
Thanks Team Stooge. Downloading now, will report back with any issues I come across.
After boot getting android process error. Cant get past selecting language selection
ssaggy said:
After boot getting android process error. Cant get past selecting language selection
Click to expand...
Click to collapse
Check your md5 and or re-download. I personally recommend downloading to pc then move to phone. I have flashed it about 4 times since last night and no issues like that. Be sure to wipe cache, dalvik, system and data.
Any major upgrade to Barren3 with Rin1.8?
gorillaz1 said:
Any major upgrade to Barren3 with Rin1.8?
Click to expand...
Click to collapse
Right now nothing major, just using ZV6 as a base. And right now only has stock kernel. New Rin is in the works.
Roger that. I'll be patient then. Keep up the great work!
Running great. Thanks guys.
Does this zip include the new radio?
Sent from my LG-ls990 using XDA Free mobile app
chrisctb said:
Does this zip include the new radio?
Sent from my LG-ls990 using XDA Free mobile app
Click to expand...
Click to collapse
It's in the OP. Yup
Just so you guys know, read this. http://forum.xda-developers.com/showthread.php?p=56991878
This won't effect this rom too much as @HPTesla had the kernel about ready for Primtime.
But it does/will effect the future of our beloved G3. When we finally get L, were screwed. Just thought I'd let you all know.
engine95 said:
It's in the OP. Yup
Click to expand...
Click to collapse
Apparently I can't read haha thanks
Sent from my LG-ls990 using XDA Free mobile app
engine95 said:
Just so you guys know, read this. http://forum.xda-developers.com/showthread.php?p=56991878
This won't effect this rom too much as @HPTesla had the kernel about ready for Primtime.
But it does/will effect the future of our beloved G3. When we finally get L, were screwed. Just thought I'd let you all know.
Click to expand...
Click to collapse
That's horrible.
Mahapederdon said:
That's horrible.
Click to expand...
Click to collapse
Tell me about it. It's friggin ridiculous what some people try and pull.
I started looking at n6. If I bought on from Sprint to play with is there gonna be any kind of lock. Or is it strait forward. I still love this phone but reading that article made me a little nervous.
So when we actually do get an official L there's no way of making it flashable?