Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).:good:
My builds uses all official CyanogenMod sources except the kernel. But I am merging it with all fixes/features from CM kernel repo, Google and kernel.org mainline too.
Downloads
Latest HumberOS
Installation
- First time flashing CM10.1 to your device (or coming from another ROM)?
Root your device and install CwM Recovery* or TWRP.
Reboot into Recovery
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using CwM Recovery* or TWRP
* Check troubleshooting if you are using CwM Recovery.
FAQ
Q&A thread
Please read before posting or reporting bugs!:good:
Troubleshooting
HERE
Reporting Bugs
Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
Please read the thread for known issues before reporting.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow.
Code:
What is your--
Tablet model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
----------------------------------------------------
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
----------------------------------------------------
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
other modifications:
----------------------------------------------------
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
IRC
User channel
#teamhacksung-support
Developer channel
#teamhacksung
#cyanogenmod-dev
Changelog?
A rough changelog is available HERE
Kernel TAGs: HERE
RSS
If you want to be notified by the new builds just install GooManager or add http://goo.im/rss&path=/devs/humberos to any RSS reader.
All Sources
HumberOS
CyanogenMod
SGT7
Special Thanks
@cdesai
@sbradymobile
______________________________________________________________
The CyanogenMod team would like to THANK everyone involved
in helping with testing, coding, debugging enting!
Enjoy!
Troubleshooting
Installation
CwM Recovery users
assert error: < solution >:good:
assert failed: getprop("ro.product.device") == "c0" || getprop("ro.build.device") == "c0" ||
getprop("ro.product.device") == "p4noterf" || getprop("ro.build.device") == "p4noterf" ||
getprop("ro.product.device") == "n8000" || getprop("ro.build.device") == "n8000" ||
getprop("ro.product.device") == "GT-8000" || getprop("ro.build.device") == "GT-8000"
Click to expand...
Click to collapse
More is better
good to have you here for our note 10.1
Re: [ROM][JB][4.2.1][N80XX]CyanogenMod 10.1 Weekly Builds
Sweetness! Thank you!
Sent from my GT-N8013 using Tapatalk HD
Nice to see you over here, have tried your roms from the old days of Galaxy Note 7" P1000.
Re: [ROM][JB][4.2.1][N80XX]CyanogenMod 10.1 Weekly Builds
Thanks for putting an updated nightly thread for our galaxy notes! Good to have it in the developers thread so more people can see it. Thanks again!
Sent from my DROID RAZR using xda app-developers app
Re: [ROM][JB][4.2.1][N80XX]CyanogenMod 10.1 Weekly Builds
So far very fast and the camera works just flashes once you exit.
Pen is working
Haven't tried Netflix as I already know what to expect.
I'll continue to play for a couple days see how she holds up.
thanks again!
Sent from my GT-N8013 using Tapatalk HD
Nice mate! Downloadiinnnggg
Thanks!
hooked to Samsung Keyboard
as it says above
will samsung keyboard work with its handwriting recognition capabilities,
this is the only reason why i'm opting out from these excellent roms
if any body did it pls let me know
drhassan said:
as it says above
will samsung keyboard work with its handwriting recognition capabilities,
this is the only reason why i'm opting out from these excellent roms
if any body did it pls let me know
Click to expand...
Click to collapse
I don't think so.. Because it needs TouchWiz Framework files.
Thanks :good:
[ROM][JB][4.2.1][N80XX]CyanogenMod 10.1 Weekly Builds
Congratulations on your good work.
I note (no pun intended) that although the header states the ROM is for the N80XX intimating that it will be OK on the N8010, on the Downloads it only has the N8000 & N8013 annotated, does this mean it is not for use on the N8010 or if it is which is the appropriate zip??
manxexile said:
I note (no pun intended) that although the header states the ROM is for the N80XX intimating that it will be OK on the N8010, on the Downloads it only has the N8000 & N8013 annotated, does this mean it is not for use on the N8010 or if it is which is the appropriate zip??
Click to expand...
Click to collapse
Actually, I don't have the N8000 or N8010 model. My device is the N8013.
Please correct me if it is wrong, but I think that N8000 and N8010 are compatibles.
Like I said, just make a nandroid backup before flash and let us know if it is true.
Thank you!
Re: [ROM][JB][4.2.1][N80XX]CyanogenMod 10.1 Weekly Builds
humberos said:
Actually, I don't have the N8000 or N8010 model. My device is the N8013.
Please correct me if it is wrong, but I think that N8000 and N8010 are compatibles.
Like I said, just make a nandroid backup before flash and let us know if it is true.
Thank you!
Click to expand...
Click to collapse
can't install it on my note 8010... on start on installation in recover it gives strange error...
Sent from my GT-N7100 using xda app-developers app
We have a function called "assert" into install package.zip.
If you unzip your downloaded package you'll see it in: /META-INF/com/google/android/updater-script
Code:
assert(getprop("ro.product.device") == "c0" || getprop("ro.build.product") == "c0" ||
getprop("ro.product.device") == "p4noterf" || getprop("ro.build.product") == "p4noterf" ||
getprop("ro.product.device") == "n8000" || getprop("ro.build.product") == "n8000" ||
getprop("ro.product.device") == "GT-N8000" || getprop("ro.build.product") == "GT-N8000");
If you remove this function then the recovery will install the package.:good:
Thanks!
Re: [ ROM ][ JB ][ 4.2.1 ][ N8000 | N8013 ] CyanogenMod 10.1 Weekly Builds
humberos said:
Oh! Sorry!
We have a function called "assert" into install package.zip.
If you unzip your downloaded package you'll see it in: /META-INF/com/google/android/updater-script
Code:
assert(getprop("ro.product.device") == "c0" || getprop("ro.build.product") == "c0" ||
getprop("ro.product.device") == "p4noterf" || getprop("ro.build.product") == "p4noterf" ||
getprop("ro.product.device") == "n8000" || getprop("ro.build.product") == "n8000" ||
getprop("ro.product.device") == "GT-N8000" || getprop("ro.build.product") == "GT-N8000");
If you remove this function then the recovery will install the package.
I will check N8010 kernel source and let you know about.
@ALL
Also, I will update the thread name.
At least we have only 2 official models: N8000 and N8013.
Thanks!
Click to expand...
Click to collapse
thanks! works fine after removing asserts function.
Sent from my GT-N7100 using xda app-developers app
pinku1 said:
thanks! works fine after removing asserts function.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Please, let me know if your N8010 is working fine.
I will submit the N8010 device name to official CM.
Thanks!
humberos said:
Please, let me know if your N8010 is working fine.
I will submit the N8010 device name to official CM.
Thanks!
Click to expand...
Click to collapse
yes works perfect on my n8010! no issue at all, restored all apps using titanium backup.
N8010 - using N8000 modified zip
Well sad to say I have attempted to install the ROM several times with the deletion of the "insert" and to no avail. The ROM is detected in recovery and starts to load immediately followed by it being aborted. :crying:
Is it perhaps that I should be using the N8013 zip as I have never been clear which models are similar. Isn't the N8000 3G?
Re: [ROM][JB][4.2.1][Kernel 3.0.61][N80XX] CyanogenMod 10.1 Weekly Builds
manxexile said:
Well sad to say I have attempted to install the ROM several times with the deletion of the "insert" and to no avail. The ROM is detected in recovery and starts to load immediately followed by it being aborted. :crying:
Is it perhaps that I should be using the N8013 zip as I have never been clear which models are similar. Isn't the N8000 3G?
Click to expand...
Click to collapse
N8010 and N8013 are Wi-Fi only devices.
N8000 have GSM support.
I was wrong.
So, N8010 and N8013 should be compatibles.
##Edited
I can confirm that: N8010 and N8013 are compatibles models.
N8010 is an european version and N8013 is an american version. But both are Wi-Fi only devices.
I am making a new N8010 device repo properly and will build new one soon!
Sent from my GT-N8013 using xda premium
This is a CM10.1 (Jelly Bean, Android 4.2) ROM for Atrix HD.
I'm not responsible by phone bricks of any kind, or any other damage this firmware may cause to you, to your phone or any accessories conected to your phone.
Click to expand...
Click to collapse
This firmware requires an unlocked bootloader.
Download links and information about what is working can be found on the website (Firmware section):
http://www.linuxmobile.org/razrhd/cm10-1
Instructions:
Download the zip (cm-10.1-*-UNOFFICIAL-epinter-mb886.zip) and copy to your sdcard.
Boot into recovery.
Backup your firmware and data!
Format /system.
Install the firmware (install zip from...).
Install gapps (install zip from...).
Wipe data/cache (don't wipe if you plan to upgrade from CM10 to CM10.1)
Reboot.
NOTICE - I don't have a Atrix HD to know exactly how it works with this firmware, so developers needed.
People are saying this firmware is laggy, slow. Some work is needed.
DEVELOPERS (April/2013):
EPinter - Kernel Development, Build Setup, XT925 & MB886 Support
DHacker - Kernel Development, Build Setup, XT926 Support
Hashcode - Kernel Development, Build Setup, XT926 Support
Nadlabak - Kernel Development, Build Setup, XT897 Support
Skrilax_CZ - Kernel Development, Build Setup, XT897 Support
OTHER CREDITS:
progrockguy - For the very big patience and more than 10 tests on MB886.
Screenshots below are from XT925
{
"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"
}
Nice
These guys work magic, so support your developers!
YES!!!!!
Sent from my XT925 using xda app-developers app
Yeah!!!
You're amazing,epinter!! Nice to see you here after all your amazing work on Atrix. Thanks a lot. I'm downloading it now.
Sent from my XT897 using Tapatalk 2
Thanks so much!
The gapps link is not working..... Hoping not to sound retarded but can I use any gapps that are recent or are they specific to the ROM/kernel? First time I've ran into this problem and it has me thinking if there is a universal gapps then I have a ton of wasted space in uniquely named duplicate files :-/
Sent from my MB886 using Tapatalk 2
Could someone please re-upload the ROM and Gapps to another service like d-h.st? The link in this thread almost froze my PC once, then I tried again to make sure it was that specific site that did it, and sure enough, it crashed my PC. Malwarebytes says there's nothing, but IDK what's up.
Seems sluggish at the very first build. But,this is a good start.
Sent from my MB886 using Tapatalk 2
Just finished porting the PAC-MAN ROM!!!!!! IT IS AMAZING! WILL BEING UPLOADING NOW.
EcHoFiiVe said:
Just finished porting the PAC-MAN ROM!!!!!! IT IS AMAZING! WILL BEING UPLOADING NOW.
Click to expand...
Click to collapse
Two new modded roms in a row! It's modding time!
Sent from my MB886 using Tapatalk 2
Yep, extremely sluggish. Won't release till lag is fixed. As for now, here is a teaser
Sent from my MB886 using xda premium
Amazing, trying to flash now.
Sent from my MB886 using xda app-developers app
Is the cam working I'll give a try in evening
Sent from my DROID RAZR using xda app-developers app
just tried it very laggy & slow compared to stock JB, im sure it will get better as this is just beta phase @L7iharsha yea the camera works
My current recovery is the CWM from the Photon Q, which I used to flash progrockguy's CM10 build successfully. However, when I tried to flash this ROM, CWM gave me a build.prop error and I was unable to flash.
-- Installing: /sdcard/Download/cm-10.1-20130421-UNOFFICIAL-epinter-mb886.zip
Finding update package...
I:Update location: /sdcard/Download/cm-10.1-20130421-UNOFFICIAL-epinter-mb886.zip
I:using /data/media for /sdcard/Download/cm-10.1-20130421-UNOFFICIAL-epinter-mb886.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.product.device") == "xt925" || getprop("ro.build.product") == "xt925" ||
getprop("ro.product.device") == "xt926" || getprop("ro.build.product") == "xt926" ||
getprop("ro.product.device") == "xt926dev" || getprop("ro.build.product") == "xt926dev" ||
getprop("ro.product.device") == "xt926vzw" || getprop("ro.build.product") == "xt926vzw" ||
getprop("ro.product.device") == "xt907" || getprop("ro.build.product") == "xt907" ||
getprop("ro.product.device") == "vanquish_u" || getprop("ro.build.product") == "vanquish_u" ||
getprop("ro.product.device") == "vanquish" || getprop("ro.build.product") == "vanquish" ||
getprop("ro.product.device") == "scorpion_mini" || getprop("ro.build.product") == "scorpion_mini"
assert failed: getprop("ro.product.device") == "xt925" || getprop("ro.build.product") == "xt925" || getprop("ro.product.device") == "xt926" || getprop("ro.build.product") == "xt926" || getprop("ro.product.device") == "xt926dev" || getprop("ro.build.product") == "xt926dev" || getprop("ro.product.device") == "xt926vzw" || getprop("ro.build.product") == "xt926vzw" || getprop("ro.product.device") == "xt907" || getprop("ro.build.product") == "xt907" || getprop("ro.product.device") == "vanquish_u" || getprop("ro.build.product") == "vanquish_u" || getprop("ro.product.device") == "vanquish" || getprop("ro.build.product") == "vanquish" || getprop("ro.product.device") == "scorpion_mini" || getprop("ro.build.product") == "scorpion_mini"
E:Error in /sdcard/Download/cm-10.1-20130421-UNOFFICIAL-epinter-mb886.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Consider your self my xda-bestfriend! I can't believe someone got it ported, it took me 4 ROMs to realise its not gonna boot so I quit.
@EcHoFiiVe
Sent from my MB886 using xda app-developers app
I have used few roms by epinter for my Atrix 4G. I always have a felling that roms by epinter are not I upgraded that quickly to rectify the bugs.
I am sure he must be b busy in many projects but the thing is I have faced the most annoying moments using his ROMs.
I feel if you can't support your ROM fire the users comfort there is no meaning to make it public. Just a personal opinion. Sorry if it hurts you.
Sent from my MB886 using xda app-developers app
endlesssnowfall said:
My current recovery is the CWM from the Photon Q, which I used to flash progrockguy's CM10 build successfully. However, when I tried to flash this ROM, CWM gave me a build.prop error and I was unable to flash.
Click to expand...
Click to collapse
I forgot this detail. I will fix it.
bankanidhi said:
I have used few roms by epinter for my Atrix 4G. I always have a felling that roms by epinter are not I upgraded that quickly to rectify the bugs.
I am sure he must be b busy in many projects but the thing is I have faced the most annoying moments using his ROMs.
I feel if you can't support your ROM fire the users comfort there is no meaning to make it public. Just a personal opinion. Sorry if it hurts you.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
This don't hurt me. I don't have to support your need for a daily release, if you need this, get the source and build yourself on a daily basis. I want to contribute to the community, that's it. I release a new version when worth it, when people will see some difference, not to just release it so I can talk I'm working.
XT925, XT926 and MB886 are very similar. That's why I released this. You can help to solve the bugs if you want. If you see the OP, I said I don't have the phone, my plan is to create a base so other developers can continue the development and make a stable firmware.
Are you saying I should stop the development for Atrix HD ? If your opinion is shared with all the users, no problem for me, the source code is available at razrqcom-dev-team github anyone can get it.
del
centipedes said:
Is anyone else having issues with lag?
Click to expand...
Click to collapse
I don't know exactly it works because I don't have the phone, but people are saying this firmware is laggy, slow. I think some work is needed to make it better. Any developer that want to contribute and fix the bugs, are welcome.
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 4.4 KitKat, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working:
RIL
Camera
Mobile Data
Microphone
Audio
GPS
Vibration
SD Card
Airplane Mode
WiFi
Auto Rotation
Tethering
Bluetooth
zRAM
Signature spoofing for MicroG
Not working:
FM radio
Download links:
ROM
Android File Host | XDA
GApps
Open GApps
Recovery
TWRP with F2FS | TWRP
Installation instructions:
Download ROM and GApps.
Boot into recovery.
Wipe System, Data, Cache.
Flash ROM and GApps.
Reboot to system.
Thanks to:
LineageOS Team
androidlover5842
zim555
berkantkz
XDA:DevDB Information
LineageOS 11.0 kylevess, ROM for the Samsung Galaxy Fresh GT-S7390
Contributors
HardLight
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2017-06-18
Last Updated 2017-11-11
Changelog
Code:
[B]20171110[/B]
- Android Security Patch Level: October 1, 2017
Patched 'KRACK' (Key Reinstallation Attacks) WPA/WPA2 vulnerability
Patched 'Cloak and Dagger' accessibility service vulnerability
Patched Dnsmasq vulnerability (CVE-2017-14496)
Other security and stability fixes
[B]20170725[/B]
- Added overclock to 1700 MHz (default max clock 1200 MHz, feel free to upload benchmark results with higher frequencies)
- Fixed video playing (thanks to @EduardoClasheiro)
- LZ4 compression for zRAM
- Added f2fs support (TODO: build recovery that also supports f2fs)
- Added FIOPS and ROW I/O schedulers (default FIOPS)
- Backports of zRAM from 3.17 kernel
[B]20170527[/B]
- Initial release
Hi, thanks for the rom. What gapps package should I choose? Upd: Flashed with twrp 3.1.1.0, with the nano gapps pack - wouldn't launch OS, stuck at the loading animation. Without flashing the Gapps the OS loads fine. With the pico pack launches fine, maybe because I also downloaded the md5 checksum file?
Jon891451984 said:
Hi, thanks for the rom. What gapps package should I choose? Upd: Flashed with twrp 3.1.1.0, with the nano gapps pack - wouldn't launch OS, stuck at the loading animation. Without flashing the Gapps the OS loads fine. With the pico pack launches fine, maybe because I also downloaded the md5 checksum file?
Click to expand...
Click to collapse
Maybe nano did not fit to system partition or zip was corrupted. I would recommend MicroG as an opensource lightweight google play services alternative for all older phones. At first it may appear to be a bit tricky to setup everything (all instructions in project website and github) but once it's done, system will feel much snappier compared to google play services.
I have few questions, if I may. 1. Can the recovery type(stock, twrp, cwm) impact performance? 2. Where's ram info? Long press on home button reveals only the recent apps.
---------- Post added at 01:15 PM ---------- Previous post was at 12:49 PM ----------
In developer options I see the minimum and maximum cpu clocks are 999mhz. Is it this way in stock rom as well? Wouldn't it drain battery fast?
---------- Post added at 01:18 PM ---------- Previous post was at 01:15 PM ----------
There is also an issue with simcard contacts and sms. I can't access them. I you know how please tell me.
---------- Post added at 01:46 PM ---------- Previous post was at 01:18 PM ----------
Youtube videos unwatchable. I guess I go back to stock rom. This phone is hopeless)
Jon891451984 said:
I have few questions, if I may. 1. Can the recovery type(stock, twrp, cwm) impact performance? 2. Where's ram info? Long press on home button reveals only the recent apps.
---------- Post added at 01:15 PM ---------- Previous post was at 12:49 PM ----------
In developer options I see the minimum and maximum cpu clocks are 999mhz. Is it this way in stock rom as well? Wouldn't it drain battery fast?
---------- Post added at 01:18 PM ---------- Previous post was at 01:15 PM ----------
There is also an issue with simcard contacts and sms. I can't access them. I you know how please tell me.
Click to expand...
Click to collapse
1. No it cant impact performance, also you can't use stock to flash custom roms.
2. You can simply use terminal emulator to check it (with "free" or "htop" command) also there is a lot of 3rd party sysinfo apps.
Ram info with long press home in not in LineageOS (CM) feature list, and you do not need to worry about ram usage, android uses smart algorithms to manage that.
3. With lower frequencies system feels not as smooth. While screen off frequency should not be 999MHz, so there should be no huge battery impact. But if you want you can check and report battery on different frequencies.
4. There should be a setting in contact app to view contacts on sim card. If it does not work for you, try using stock rom to sync all sim contacts to google account or just export them to file and then import it from contact app.
Currently using this Rom and gotta admit it you've done real nice job here
NO BUGS so far if anyone is wondering, real smooth...
BIG THUMBS UP THE WORK MATE
Thanks for this ROM! ABout the SIM Issue (Cant Read Contacts fom SIM Card), I got same Issue in the Past Time for my Samsung Note 4. Now it was Fixed by the Dev @_mone ! Take a Look into his Commits, if You can Use them for the GT-S7390. Here: https://github.com/underscoremone/android_device_samsung_trlte-common/commit/a6e075e490efe605898bdb582312b3df1cd168a3
Hope this will Help to Fix the SIM Issue
Kernel update
Hi everyone,
I'm new to this so excuse me if I missed something ^^
I installed this ROM with pico GAPPS and this is just AWSOME !!
A new life for my old S7390G
I can't find a way to OC it, to increase a little his speed. I saw some post about Kernel 3.5.7 but it seemed to fit only for S7392, even if some say it's OK for S7390.
When I tried to install it through TWRP 3.1.1-0 I have the following message :
This package is for device : kyleve , S7392
hawaii; this device is kylevess
Updater process ended with ERROR: 7
Any idea ?
Thanks
---------------------------------------------------------------
In fact I found this here :
https://forum.xda-developers.com/android/software/kernel-t3313105/page3
I flash the phoenix kernel with wifi module and it's good.
But don't know if phoenix is better than 3.5.7 OC ...
Arkhorail said:
Hi everyone,
I'm new to this so excuse me if I missed something ^^
I installed this ROM with pico GAPPS and this is just AWSOME !!
A new life for my old S7390G
I can't find a way to OC it, to increase a little his speed. I saw some post about Kernel 3.5.7 but it seemed to fit only for S7392, even if some say it's OK for S7390.
When I tried to install it through TWRP 3.1.1-0 I have the following message :
This package is for device : kyleve , S7392
hawaii; this device is kylevess
Updater process ended with ERROR: 7
Any idea ?
Thanks
---------------------------------------------------------------
In fact I found this here :
https://forum.xda-developers.com/android/software/kernel-t3313105/page3
I flash the phoenix kernel with wifi module and it's good.
But don't know if phoenix is better than 3.5.7 OC ...
Click to expand...
Click to collapse
to flash in S7392 just open the .zip file and edit(with any unix text editor) the file
updater-script in META-INF\com\google\android\
change the first lines to this:
assert(getprop("ro.product.device") == "kyleve" ||
getprop("ro.build.product") == "kyleve" ||
getprop("ro.product.device") == "S7392" ||
getprop("ro.build.product") == "S7392" ||
getprop("ro.product.device") == "GT-S7392" ||
getprop("ro.build.product") == "GT-S7392" ||
getprop("ro.product.device") == "hawaii" ||
getprop("ro.build.product") == "hawaii" ||
abort("This package is for device: kyleve,S7392,GT-S7392,hawaii; this device is " + getprop("ro.product.device") + ".");
The Rom will flash now :victory:
but i have a problem with video players they all show video greenish
is that problem on S7390??
if not i can try to fix :fingers-crossed:
Thanx for your answer but it does not work : my device is an s7390.
I have the same vidéo problem : greenish & laggy
Phoenix is a little faster ans appear stable. I think I'll not go further for now.
THIS FIX might help you guys with the video bug... I tested it on all other cm11 and it worked unfortunatly the resolution limit is only 360p so if you exceed that then you should use software rendering instead of hardware.
credit to @Mm7
trying to fix greenish video :fingers-crossed: ,but i didnt know what was changed on the tree to have omx working like your rom
I'll try this as soon as possible !
I finaly found the problem with OMX encoders/decoders :victory:
after a try messing and logging with this HardLight Build
i put the stock /system/etc/media_codecs.xml in the rom
the codecs stops to working but are a call beeing made on /dev/h264_ol getting no permissions :silly:
analising ueventd.hawaii_ss_kylevess.rc theres no permissions related and i just put the line
/dev/h264_ol 0660 media media
build image and flash
thats it OMX is working like on stock rom :highfive:
made a flashable zip and here are the link:
edit: i made a litle mistake kkkk put only S7392 ZIP
for GT-S7392: https://mega.nz/#!LxZAmATb!NDast2UHJ8F6ZO1REZaq9DicjtdlPJYADBrnLaJYrP0
For GT-S7390: https://mega.nz/#!Ko5VhbCT!I4xpU-cu_eGhSjkN2jFV85GSNm-6_BpcgpGxh6HRtpw
now we have cm-11.0(aka lineageos 11 now) fully working
still don't found HardLight s7390 kylevess device tree on github
waiting a new build with the fixes :fingers-crossed:
edit: video playback not working in some browsers here a a list
Not working on browser in rom,CM Browser,UC mini,Opera Mini
Working on Firefox,Uc Browser,Google Chrome and Opera
i will enjoy to start cm-12.1 (aka lineageos 12.1 now) development
Hi !
Still not working for my S7390, always the same message.
Arkhorail said:
Hi !
Still not working for my S7390, always the same message.
Click to expand...
Click to collapse
i recomend you to flash kylevess most recent twrp
https://dl.twrp.me/kylevess/
if still not working
open flashable zip as i said before and remove these lines
assert(getprop("ro.product.device") == "kylevess" ||
getprop("ro.build.product") == "kylevess" ||
getprop("ro.product.device") == "S7390" ||
getprop("ro.build.product") == "S7390" ||
getprop("ro.product.device") == "GT-S7390" ||
getprop("ro.build.product") == "GT-S7390" ||
getprop("ro.product.device") == "hawaii" ||
getprop("ro.build.product") == "hawaii" ||
abort("This package is for device: kylevess,S7390,GT-S7390,hawaii; this device is " + getprop("ro.product.device") + ".");
if don't flash now you are on a crusade
do not do this for other devices roms, this is possible only with GT-S7390 and GT-S7392 because of the same hw
i'm not responsible for hard bricks if you try kkkkkkk
Hi EduardoClasheiro !
Thanx for your work, Video I tried thus far work fine
But I did not have access to WiFi anymore ...
As I mentioned before, I'm using phoenix kernel with wifi module.
I tried to reflash the wifi module but it didn't work.
I'll try a new install but not sure about the order of flash.
rony raj wrote this for his patch :
flash pac rom or any rom cm11 based
flash modules in attachment/download
flash pheonix kernel done
Click to expand...
Click to collapse
I'll try to flash your video module just after the ROM.
Or I'll just let go phoenix kernel
Arkhorail said:
Hi EduardoClasheiro !
Thanx for your work, Video I tried thus far work fine
But I did not have access to WiFi anymore ...
As I mentioned before, I'm using phoenix kernel with wifi module.
I tried to reflash the wifi module but it didn't work.
I'll try a new install but not sure about the order of flash.
rony raj wrote this for his patch :
I'll try to flash your video module just after the ROM.
Or I'll just let go phoenix kernel
Click to expand...
Click to collapse
to use the fix with other kernel you need to unpack boot.img from flashable zip unpack boot.img itself and unpack ramdisk edit ueventd.hawaii_ss_kylevess.rc in ramdisk and add the line
/dev/h264_ol 0660 media media
repack everything backwards and flash
i coud do the work for you,leave the link of the kernel them i reply the flashable zip :good:
last build rocks (lineage-11.0.1-20170725-kylevess.zip)
don't know what HardLight did but it's Blazing fast,smooth and stable :laugh:
the rom has only minor bugs
1. needs a good browser to play videos online like chrome,firefox,uc browser,opera. (mini browsers bug's playing)
2. youtube has 360p max resolution
i will keep this rom in my device.
Starting this because other folks than @Alberto97 are cooking from the LineageOS 15.x repository. This is unmonitored - ymmv.
reserved
Althaf:
lineage-15.0 from latest source https://www.androidfilehost.com/?fid=889964283620761059
Anyone try it with fire kernel or udkernel?
by the way, great job on cooking that! I won't play with it as I need to stay Alberto so I can help at other thread but hopefully others will grab it.
Does VOLTE works with this one?
guitarsslave2 said:
Hi there,
I not sure this is the right place, but here is my feedback:
- it was installed on a XT1543 dual sim, it worked for calls, but mobile data was always active, even with all of flip switches turned off
- the mobile data flip switch had no influence on each other, I could have it on at settings ui and off at notification bar
- battery didn't last much
- camera, as noted before, didn't work, it crashed for photos sometimes and no videos could be taken
- assistant worked flawlessly
- haven't found any problems with WiFi
- didn't tested Bluetooth
- haven't found LOS related settings, like expanded desktop, double tap on notification to sleep, volume buttons action changing with device orientation, gestures, and brightness control in notification bar, and etc, I figure it might be later added
Besides that everything was fine, I couldn't keep it installed thought because of the mobile data issue.
Hope this helps somehow. Thanks for the good work!
Click to expand...
Click to collapse
Have you used any kernel to flash with this?.. Before flashing this you're on which ROM? have you flashed any gapps with this ?
---------- Post added at 05:59 PM ---------- Previous post was at 05:56 PM ----------
althafvly said:
Althaf:
lineage-15.0 from latest source https://www.androidfilehost.com/?fid=889964283620761059
Anyone try it with fire kernel or udkernel?
Click to expand...
Click to collapse
I was trying to flash this with UDkernel latest version which supports Oreo.. but TWRP gives error.. sorry but i have forgot to capture that error
Why does everyone use lineage as a base?
Is it because they have already done most of the work? Seems like almost every N rom is based on it. Not complaining, just trying to learn.
Big thanks to ALL developers and those of you here helping others.
LineageOS has many hundreds/thousands of developers and perhaps another 100,000 folks helping in the device threads.
althafvly said:
Althaf:
lineage-15.0 from latest source https://www.androidfilehost.com/?fid=889964283620761059
Anyone try it with fire kernel or udkernel?
Click to expand...
Click to collapse
No luck flashing this. Received error 7?
No idea what that means.
melp57 said:
No luck flashing this. Received error 7?
No idea what that means.
Click to expand...
Click to collapse
google
twrp error 7
melp57 said:
No luck flashing this. Received error 7?
No idea what that means.
Click to expand...
Click to collapse
"E3004: This package is for device: osprey,osprey_umts,osprey_u2,osprey_ud2,osprey_uds,osprey_cdma,osprey_sprint,osprey_udstv
I also got same error while flashing with UD kernel @althafvly
rahul9999 said:
"E3004: This package is for device: osprey,osprey_umts,osprey_u2,osprey_ud2,osprey_uds,osprey_cdma,osprey_sprint,osprey_udstv
I also got same error while flashing with UD kernel @althafvly
Click to expand...
Click to collapse
Wondering what the cause of it is.
melp57 said:
Wondering what the cause of it is.
Click to expand...
Click to collapse
I think this issue is due to TWRP..
TWRP needs to be updated .. I'm currently on Squid2 latest TWRP 3.1.1 r3
Also i have seen that Althaf have modified updater script in his LOS15 to avoid this error.. so that i only got this error while flashing UD Kernel not with the ROM
rahul9999 said:
I think this issue is due to TWRP..
TWRP needs to be updated .. I'm currently on Squid2 latest TWRP 3.1.1 r3
Also i have seen that Althaf have modified updater script in his LOS15 to avoid this error.. so that i only got this error while flashing UD Kernel not with the ROM
Click to expand...
Click to collapse
Squid2's TWRP causing problems when flashing kernels.
rahul9999 said:
"E3004: This package is for device: osprey,osprey_umts,osprey_u2,osprey_ud2,osprey_uds,osprey_cdma,osprey_sprint,osprey_udstv
I also got same error while flashing with UD kernel @althafvly
Click to expand...
Click to collapse
remove the assert lines from updater_script and try
KrisM22 said:
google
twrp error 7
Click to expand...
Click to collapse
Error 7 usually show when the firmware are not match with the ROM
Ahmed Hady said:
remove the assert lines from updater_script and try
Click to expand...
Click to collapse
Could you make a Zip for me if possible ? because i have tried this already but TWRP gives me error while flashing that Invalid Zip format
rahul9999 said:
Could you make a Zip for me if possible ? because i have tried this already but TWRP gives me error while flashing that Invalid Zip format
Click to expand...
Click to collapse
sorry my internet connection is so slow right now .. if u get error 7 so u have to update the TWRP recovery version ..
but if the error is unknown device name so remove these lines from updater-script
Code:
assert(getprop("ro.product.device") == "osprey" || getprop("ro.build.product") == "osprey" || getprop("ro.product.device") == "osprey_umts" || getprop("ro.build.product") == "osprey_umts" || getprop("ro.product.device") == "osprey_u2" || getprop("ro.build.product") == "osprey_u2" || getprop("ro.product.device") == "osprey_ud2" || getprop("ro.build.product") == "osprey_ud2" || getprop("ro.product.device") == "osprey_uds" || getprop("ro.build.product") == "osprey_uds" || getprop("ro.product.device") == "osprey_cdma" || getprop("ro.build.product") == "osprey_cdma" || getprop("ro.product.device") == "osprey_sprint" || getprop("ro.build.product") == "osprey_sprint" || getprop("ro.product.device") == "osprey_udstv" || getprop("ro.build.product") == "osprey_udstv" || abort("E3004: This package is for device: osprey,osprey_umts,osprey_u2,osprey_ud2,osprey_uds,osprey_cdma,osprey_sprint,osprey_udstv; this device is " + getprop("ro.product.device") + "."););
Ahmed Hady said:
sorry my internet connection is so slow right now .. if u get error 7 so u have to update the TWRP recovery version ..
but if the error is unknown device name so remove these lines from updater-script
Code:
assert(getprop("ro.product.device") == "osprey" || getprop("ro.build.product") == "osprey" || getprop("ro.product.device") == "osprey_umts" || getprop("ro.build.product") == "osprey_umts" || getprop("ro.product.device") == "osprey_u2" || getprop("ro.build.product") == "osprey_u2" || getprop("ro.product.device") == "osprey_ud2" || getprop("ro.build.product") == "osprey_ud2" || getprop("ro.product.device") == "osprey_uds" || getprop("ro.build.product") == "osprey_uds" || getprop("ro.product.device") == "osprey_cdma" || getprop("ro.build.product") == "osprey_cdma" || getprop("ro.product.device") == "osprey_sprint" || getprop("ro.build.product") == "osprey_sprint" || getprop("ro.product.device") == "osprey_udstv" || getprop("ro.build.product") == "osprey_udstv" || abort("E3004: This package is for device: osprey,osprey_umts,osprey_u2,osprey_ud2,osprey_uds,osprey_cdma,osprey_sprint,osprey_udstv; this device is " + getprop("ro.product.device") + "."););
Click to expand...
Click to collapse
I know this mate.. you have not got my point.. I said i have already done all this steps.. but while flashing that file getting error that Incorrect Zip format
rahul9999 said:
I know this mate.. you have not got my point.. I said i have already done all this steps.. but while flashing that file getting error that Incorrect Zip format
Click to expand...
Click to collapse
The big problem that i didn't try this zip so that's all i know about it .. u but i can send u my los15 META-INF folder for testing this zip