CM10.2 for WAVE and WAVE 2
Android Jellybean 4.3.1
Hi All,
So once again it’s time to upgrade our project to Android 4.3.1
Previous versions:
CM10: forum.xda-developers.com/showthread.php?t=1851818
CM10.1: http://forum.xda-developers.com/showthread.php?t=2400126
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
FEATURES
Android 4.3.1
CM sources of 21.10.2013
Updated to linux kernel version 3.0.101
270 MB RAM
KNOWN BUGS (what doesn't work):
- Network registration don't work with some SIM cards
- GPS - http://forum.xda-developers.com/showpost.php?p=47209249&postcount=1371
- Conference Calls
- Some problems with audio codec settings, but generally it should
- Impossible to shut down phone in android, only restart
- Don't leave phone charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /storage/sdcard1/dmesg.txt"
"logcat -b system -b radio -b events -b main -d -f /storage/sdcard1/logcat.txt *:V"
"logcat -b radio -d -f /storage/sdcard1/radiolog.txt *:V"
Download them from phone, archive and upload them.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
Click to expand...
Click to collapse
If the Badadroid is restarting before you're able to catch any log:
Download http://goo.im/devs/Rebellos/wave/bterm.exe
Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
Connect phone to PC.
Start bterm.exe
Type 4 commands:
Code:
open
dumpram 0x4FF00000 0x100000
close
exit
There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.
Click to expand...
Click to collapse
Bug reports without logs are completely useless.
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
HOW TO BUILD
I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
Of course you have to init with -b cm-10.2 and modify some steps.
local manifest to use: https://raw.github.com/Badadroid/android_wave_local_manifest/cm-10.1/local_manifest.xm
I do it like this:
Code:
cd ~
mkdir wave
cd wave
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
cd .repo
wget [url]https://raw.github.com/Badadroid/android_wave_local_manifest/cm-10.2/local_manifest.xml[/url]
cd ..
repo sync -j8
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
brunch wave
device name is wave so the build invocation can be brunch wave
FIRST INSTALLATION
Bada 2.0 is required
Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
160MB of free "User" memory
400MB of free "Applications" memory
Download BOOTFILES, armlinux_boot for your device:
for 8500:
http://yadi.sk/d/W4RjnjQRC6TfP
http://yadi.sk/d/Yz7_dfpkC6TkC
for 8530
http://yadi.sk/d/kxJ0CZ20C7AKF
http://yadi.sk/d/zqzWZ9LmC7AJA
(please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
Download ROM from CHANGELOG section
Start Bada.
Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
Copy whole .zip to the Bada's User partition or SD Card.
Flash BOOTFILES and FOTA using Multiloader.
Reboot the phone holding Power and Call key.
FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
CWM Recovery starts, pick:
- "install zip"
- "choose zip from from storage/sdcard1"(Bada's User partition) or "choose zip from storage/sdcard0"(SD Card)
- cm-10.2-wave-<release id>.zip
- Yes - install
Reboot holding the Power key
You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
Do not remove zImage file.
Normal bootup is available using Power+Call keys
CWM Recovery mode is available using Power+Volume Up keys
CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.
After first installation i recommend to disable Screen-off Animation by Settings->Display-> uncheck Scren-off animation
And also for better performance activate zRAM. Settings->Performance->Memory Management->zRam-> and choice Value. I use 26%
For activation Performance and Developer Options categories in Settings you need Settings->About Phone and tap 7 times on Build number
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
SLIM GAPPS http://d-h.st/mBO from http://forum.xda-developers.com/showthread.php?p=47934744
Minimized by -CALIBAN666- from PA GAPPS: http://forum.xda-developers.com/sho...ers.com/showpost.php?p=35107469&postcount=393
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen and many others.
CyanogenMod team for base ROM
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
CHANGELOG:
Kernel update
http://www.multiupload.nl/TWJAP1T4C9
kernel with removed +10 RAM patch for v3.1 with working camera and video playback
v3.1 - http://www.multiupload.nl/1E85FRD1ES
- +10mb RAM
- Updated audio codec settings for RCV and HP
- Added 15 volume levels for Calls
- Reworked SMS sending
- Fixed torch toggle in quick settings.
Kernel update for Wave2
for fixinginstallation problems
http://www.multiupload.nl/O2CVN5R9EQ
Replace zImage in Zip with this and re-copy it on Bada User Partition
and after flash step by step.
If you forgot or don't want to pack zImage in zip archive you need again replace zImage on Bada User's partition, because during flashing zImage will be replaced by one from zip archive.
Big Thanks to Rebellos for logs and RedDerRed from badapps.ru for testing all my test versions
v3 Initial CM10.2 release: http://www.multiupload.nl/8UUFOIQQE1
- Updated kernel 3.0.101
- CM Sources 30.11.2013
- CM team fixed power menu on lock key. Now we can show power menu by long press of lock key.
So i don't see any reason to use Navbar. We back to Galaxy S mapping:
Call key = MENU
Middle key = HOME
End Call key = BACK
Lock key = POWER
- Removed VideoEditer, LiveWallpapers, CMUpdater
- Fixed BT headset in calls
- Set of patches for GPRS RIL interface
- Fixed memory leaks in SIM_IO requests
MORE LINKS
Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
Nice Work Volk & Rebellos
Work this Version faster ?
Greets
Sent from my GT-N7100 using xda app-developers app
Nice work
very fast and smooth........awesome work :good::good::good:
incredible speed without gapps
anyway of installing just google calendar and google contact sync? (without the whole gapps package)
thank u so much @volk204.
but this rom still not smooth and its slow , and there is no Bigmem , bigmem 325mb ram will make this rom competely usable and really realy faster and great for gaming
i m 101% sure latest games like asphalt8:airborne , Modern combat 4,5 will not work.
even normal apps will lag too
wave 2 does not work ...
Gunter33 said:
wave 2 does not work ...
Click to expand...
Click to collapse
same too.
gonghwa said:
same too.
Click to expand...
Click to collapse
for me can get into recovery mode but when it's Chose zip from/storage/sdcard0 shows me E: Can mount/storage/sdcard0. hmmm something is strange: (
jon.marius87 said:
for me can get into recovery mode but when it's Chose zip from/storage/sdcard0 shows me E: Can mount/storage/sdcard0. hmmm something is strange: (
Click to expand...
Click to collapse
same too(((
4.3
volk204 said:
CM10.1 for WAVE and WAVE 2
Android Jellybean 4.3.1
Click to expand...
Click to collapse
Sorry to point out but Android 4.3 is CM 10.2...
Gunter33 said:
wave 2 does not work ...
Click to expand...
Click to collapse
djkoloda said:
same too(((
Click to expand...
Click to collapse
Very verbose bug report.
jon.marius87 said:
for me can get into recovery mode but when it's Chose zip from/storage/sdcard0 shows me E: Can mount/storage/sdcard0. hmmm something is strange: (
Click to expand...
Click to collapse
gonghwa said:
same too.
Click to expand...
Click to collapse
Do you have SD CARD? Can you mount storage/sdcard1(Bada user's partition)?
Sandeep Srikantam said:
Sorry to point out but Android 4.3 is CM 10.2...
Click to expand...
Click to collapse
Fixed
Very good job :good:
at the choice of Chose zip from/storage/sdcard0 shows me E : Can mount/storage/sdcard0. at a copy on sd-card the same result. wave s8530
lack of torch in quick settings
Hello. I've noticed there's no torch in quick settings. I think it maye be fixed by adding:
Code:
<bool name="has_led_flash">true</bool>
in:
Code:
https://github.com/Badadroid/android_device_samsung_wave/blob/cm-10.2/overlay/packages/apps/Settings/res/values/config.xml
but i'm not sure (cm-10.1 had this line and torch was in there, as u can see)
Code:
https://github.com/Badadroid/android_device_samsung_wave/blob/cm-10.1/overlay/packages/apps/Settings/res/values/config.xml
i can't find anything that could change it in rom .zip package so i think it will be just information for future roms.
very good sir
Good job
Good job bro continue like that !
Hi volk204,
I am unable to install new ROM on wave 2.
In CWM mode,its showing message..
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
when i click on "install zip"..
it showing "choose zip from /storage/sdcard0"
also,I am able to mount /bada-user.
Thanks,
Waveguru
waveguru said:
Hi volk204,
I am unable to install new ROM on wave 2.
In CWM mode,its showing message..
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
when i click on "install zip"..
it showing "choose zip from /storage/sdcard0"
also,I am able to mount /bada-user.
Thanks,
Waveguru
Click to expand...
Click to collapse
Maybe memory corruption, happened to me also, try to reflash bada then reinstall android
waveguru said:
Hi volk204,
I am unable to install new ROM on wave 2.
In CWM mode,its showing message..
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
when i click on "install zip"..
it showing "choose zip from /storage/sdcard0"
also,I am able to mount /bada-user.
Thanks,
Waveguru
Click to expand...
Click to collapse
I have a same problem with you. it's not working on Wave II
I installed Bada again and tryed once more but same. I'm choosing -choose zip from/storage/sdcard0 but nohing happening. I also formated sd card again and tryed to put 10.2 v3 zip to phone memory but same...
volk204 said:
Very verbose bug report.
Do you have SD CARD? Can you mount storage/sdcard1(Bada user's partition)?
Fixed
Click to expand...
Click to collapse
I referred to this Q&A
Badadroid is stuck in animation with rotating circle where Cyanogenmod is written in
It happens if you don't comply with installation requirements. Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
150MB of free "User" memory
400MB of free "Applications" memory
Solution: make a clean installation of bada: full flash
Related XDA posts: http://forum.xda-developers.com/showthread.php?p=39859136#post39859136
and after I checked the phone the answer is yes, I have less memory than required. After a full flash I got no luck to get v3 running. I guess it is related with the kernel because if I change kernel to v2.1's it can flash the v3 zip and later show some progress during the rolling circle. If I use kernel in v3 zip it just can't mount sdcard0 as others. That's all I can provide.
Related
MOD EDIT: Thread closed at Volk's request. You can find his CM 10.2 here.
CM10.1 for WAVE and WAVE 2
Android Jellybean 4.2.2
READ http://code.google.com/p/badadroid/ and http://code.google.com/p/badadroid/wiki/FrequentlyAskedQuestions BEFORE POSTING (thanks to huntkb for updating it)
FEATURES
Android 4.2.2
CM sources of 21.10.2013
Updated to linux kernel version 3.0.86
272 MB RAM
F4k 720p patch for bigmem kernels (Video Fix)
New key Mapping:
- call key as CALL, Middle as HOME, endcall as ENDCALL
- Long press ENDCALL will show power menu
- lock key as POWER, framework patch is not yet ported
- Navigation Bar activated
- PIE control can be activated with Expanded desktop
GAPPS
http://goo.im/gapps/gapps-jb-20130301-signed.zip full gapps
flash through CWM (recovery)
KNOWN BUGS (what doesn't work):
- Network registration don't work with some SIM cards
- GPS - http://forum.xda-developers.com/showpost.php?p=47209249&postcount=1371
- Conference Calls
- Bluetooth headset in calls
- Some problems with audio codec settings, but generally it should work
- Impossible to shut down phone in android, only restart
- Don't leave phone charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
FIRST INSTALLATION
Bada 2.0 is required
Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
160MB of free "User" memory
400MB of free "Applications" memory
Download BOOTFILES, armlinux_boot for your device:
for 8500:
http://yadi.sk/d/W4RjnjQRC6TfP
http://yadi.sk/d/Yz7_dfpkC6TkC
for 8530
http://yadi.sk/d/kxJ0CZ20C7AKF
http://yadi.sk/d/zqzWZ9LmC7AJA
(please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
Download ROM: http://www.multiupload.nl/HYU95BQ6D6
Start Bada.
Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
Copy whole .zip to the Bada's User partition.
Flash BOOTFILES and FOTA using Multiloader.
Reboot the phone holding Power and Call key.
FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
CWM Recovery starts, pick:
- install zip from sdcard
- choose zip from sdcard
- cm-10.1-wave-<release id>.zip
- Yes - install
Reboot holding the Power key
You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
Do not remove zImage file.
Normal bootup is available using Power+Call keys
CWM Recovery mode is available using Power+Volume Up keys
CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.
HOW TO UNINSTALL
Follow the steps there: http://forum.xda-developers.com/showpost.php?p=35107469&postcount=393
CHANGELOG:
Lite ROM by Hero355 based on v2.1 http://forum.xda-developers.com/showpost.php?p=47351443&postcount=1514
v2.1 http://www.multiupload.nl/HYU95BQ6D6
- CM sources 05.11.2013
- [NETWORK] Added WCDMA only (UMTS900/2100) Mode selection
- Fixed modem power mode transition.
- [GPRS] Added suspend/resume network
- [SIM] Added basic SIM_IO implementation: reading Contacts, Messages, Voicemail number, SPN, ICCID from SIM card
- [SMS] Code optimization and cleanup. Thanks for Rebellos
- [SMS] Added MMS receiving
- Updated audio codec gain table from bada proprietary files
- And included all another updates after v2.0
BT fix for Wave 2 http://www.multiupload.nl/JAPFB1FLNS Thanks Tigrouzen for idea and BenzoX for testing
Just Flash it via Recovery
Kernel update for v 2.0 http://www.multiupload.nl/E68CJFUHGK
- Fixed wave 2 screen calibration. thanks to krischat1001
RIL_update2 for v2.0 http://www.multiupload.nl/E1JBJU4LTS
- some memory leaks fixed
- set low level debug AMSS
- some another fixes, probably can resolve restart in long idle state
RIL Update for v2.0 http://www.multiupload.nl/OP6YZQJ09Z
- Fix for IMSI reading
I hope now mobile internet will be work on all phones
APN settings should load automatically. Most of APN is stored in ROM in system/etc/apns-config.xml
If APN is not loaded automatically check this file and add APN settings in it, if there are no in it.
v2.0 http://www.multiupload.nl/PR4599CF5V
- CM sources 21.10.2013
- Mobile internet is fixed
- Fixed search available networks and select networks
- Fixed PIN and PUK entering
- Fixed SIM PIN enable/disable/change
- Fixed sending MMS, receiving is still not working
- Fixed network indicator
v1.3 http://www.multiupload.nl/DYXUMPUCQX
- CM sources of 26.09.2013
- [RIL] Сompleted CALL interface, except conference call, but i really never use it before.
If you report bug please attach logs with detailed description, i really tested most of causes with hangup, activate and holding calls and etc, but it is too many cases, and probably i didn't meet some and don't know that this cause is exist.
- Some optimization from platform side, ported from aries
RIL Update2 for v1.2 http://www.multiupload.nl/NMIONOUBJ9
- Reworked Call interface
- Just flash it via Recovery
RIL Update for v1.2 http://www.multiupload.nl/CSTPY6UKNU
- [SIM] Corrected reading SMSC from SIM card
- [CALL] Added DTMF support
- Just flash it via Recovery
v1.2 http://www.multiupload.nl/3QF7PV7HJR
- CM sources of 17.09.2013
- Added TARGET_ARCH_LOWMEM for Dalvik
- Fixed gsm voicecall common setting in audio codec (Big Thanks for Tigrouzen)
- Fixed all audio ril pathes except Bluetooth audio pathes
Kernel Update for v1.1 http://www.multiupload.nl/LM89AO62TG
- Audio recording and video recording fixed
- So now we can use VoIP applications on wave with Wi-Fi
- Audio in call is still broken
Big thank to Rebellos. i just found good topic on ALSA forum with solution and Rebellos implemented solution
v1.1 http://www.multiupload.nl/H0THJFGQAQ
- CM sources of 14.08.2013
- Fixed vibrator (Thanks to Rebellos)
- Fixed ENDCALL button behavior(Forgot to include it in v1)
v1 http://www.multiupload.nl/KT7LG7HXDJ
Initial release
CM sources of 8.08.2013
Update compared to Rebellos CM10 ROM http://forum.xda-developers.com/showthread.php?t=1851818
- Android 4.2.2 CM10.1 based
- Updated to linux kernel version 3.0.86
- ROW i/o scheduler
- 272 MB RAM
- F4k 720p patch for bigmem kernels (Video Fix)
- New key mapping
- Navigation bar activated
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen and many others.
CyanogenMod team for base ROM
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
MORE LINKS
Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /storage/sdcard1/dmesg.txt"
"logcat -b system -b radio -b events -b main -d -f /storage/sdcard1/logcat.txt *:V"
"logcat -b radio -d -f /storage/sdcard1/radiolog.txt *:V"
Download them from phone, archive and upload them.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
Click to expand...
Click to collapse
If the Badadroid is restarting before you're able to catch any log:
Download http://goo.im/devs/Rebellos/wave/bterm.exe
Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
Connect phone to PC.
Start bterm.exe
Type 4 commands:
Code:
open
dumpram 0x4FF00000 0x100000
close
exit
There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.
Click to expand...
Click to collapse
Bug reports without logs are completely useless.
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
HOW TO BUILD
I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
Of course you have to init with -b cm-10.1 and modify some steps.
local manifest to use: https://raw.github.com/Badadroid/android_wave_local_manifest/cm-10.1/local_manifest.xm
I do it like this:
Code:
cd ~
mkdir wave
cd wave
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
cd .repo
wget [url]https://raw.github.com/Badadroid/android_wave_local_manifest/cm-10.1/local_manifest.xml[/url]
cd ..
repo sync -j8
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
brunch wave
device name is wave so the build invocation can be brunch wave
good job
you are amazing...:good::good:
I was hoped to my phone again
i will be glad, if some one will make screenshots and/or video review, i will add it in OP
disappointment :'(
.
thanks volk great job u are the best... i must ask a question for cm10.1 installation system memory 370mb free but my wave2 has got 90MB free . how can i delete this memory and which apps use system memory?
What is the main difference between this and FnF? Thanks
ibrahim1170 said:
thanks volk great job u are the best... i must ask a question for cm10.1 installation system memory 370mb free but my wave2 has got 90MB free . how can i delete this memory and which apps use system memory?
Click to expand...
Click to collapse
If you used CM10 Rebellos ROM you don't need check memory, just flash .zip via recovery and full wipe (all data will be deleted in android)
If not, try factory reset or reflash bada(in all cases you will lost all data in bada)
volk Thank you very much. king. I respect you
very good slim gapps for jb 4.2.2 please
nad4321 said:
What is the main difference between this and FnF? Thanks
Click to expand...
Click to collapse
Another Partition Layout: (FNF NAND - remove bada, FNF SD - eat some SD space for android, and as i know need backup SD before installation, restore after installation)
Easy installation
Another key mapping
Navbar and PIE control
Maybe something else
nice work man
but my simcard not detected
rom is fast & smooth
of course you set governor to
there is a alot option in this rom at compare to other rom
if you make call phone You'll all be happy
volk204 said:
reserved
Click to expand...
Click to collapse
Thank u so much volk ,
in new key mapping ,what about back key in android ?
someone plz test , 318mb ram kernel works or not ?
because for high quality games , 318mb ram kernel is important.
thanks a million to volk
blue966 said:
nice work man
but my simcard not detected
Click to expand...
Click to collapse
is it first installation? or you came from Rebellos CM10? do you had the same problem with CM10?
and for checking issue i need logcat -b radio
kktkaran said:
Thank u so much volk ,
in new key mapping ,what about back key in android ?
someone plz test , 318mb ram kernel works or not ?
because for high quality games , 318mb ram kernel is important.
thanks a million to volk
Click to expand...
Click to collapse
Back key is in navbar or in PIE control
But we can navigate in android without back key using touchscreen and home key
Kernel is 272MB RAM,
CM10 kernels will not work with CM10.1
thanks very much, and what about google play market?
monchester said:
thanks very much, and what about google play market?
Click to expand...
Click to collapse
download http://goo.im/gapps/gapps-jb-20130301-signed.zip full gapps and flash via recovery
thanks volk
can i connect my phone to charger when CM10.1 is on ?
Adam-110 said:
thanks volk
can i connect my phone to charger when CM10.1 is on ?
Click to expand...
Click to collapse
the same as for CM10
Don't leave it charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery
added to OP
volk204 said:
the same as for CM10
Don't leave it charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery
added to OP
Click to expand...
Click to collapse
thank you anyway... I appreciated
DELETED
Installation Instructions
Comming from a Pre "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM
Do a back up!
Do factory reset/ wipe (incl. /system)
In recovery: flash ROM zip file. (You WILL get an assert error!)
Read the warning on the screen.
Flash the ROM again!
If you have and international device flash the INT Kernel from the OP.
Flash Gapps
Reboot.
Comming from "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM or later
Do a back up!
Do factory reset/ wipe (incl. /system)
In recovery: flash ROM zip file.
Ignore the warning on the screen.
If you have and international device flash the INT Kernel from the OP.
Flash Gapps
Reboot.
Change Log:
NOTE: All future changelogs will be attached below!
Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839 --> Slim-venturi-4.4.2.beta.1.9-UNOFFICIAL-20131223-1727 changes:
SlimRoms/frameworks_base:
2013-12-22: systemUI: fix notification dissapearing during recreation and possible <@Lars Greiss>
Code:
app crashes due that binded notifications are not there anymore
as well small cleanup
Change-Id: Ieed143088a55693fc56e6526e6b349d72b7b25cc
2013-12-22: Merge "fb: use SlimActions for torch tile and send as qualified user" into kk4.4 <@Gerrit Code Review>
2013-12-22: Merge "fb: lock statusbar recreation and release after ticker is done" into kk4.4 <@Gerrit Code Review>
2013-12-22: fb: use SlimActions for torch tile and send as qualified user <@Lars Greiss>
Code:
the broadcast and do not collape the panel bar
as well send with qualified user the IME switcher broadcast.
Change-Id: Ibad8b4f908e6d701999712f58b9996cd7a805fc4
2013-12-21: fb: lock statusbar recreation and release after ticker is done <@Lars Greiss>
Code:
In rare cases it happens that the ticker call just happened and a recreation
was called which results in a crah due of the missing binder.
To avoid it lock the recreation when a ticker call is in progress
and release it after it is done and notify the recreation to go ahead
Change-Id: Iedbf858bdb2ac2ad97563e344a571b384e17cfc7
2013-12-21: trds:[framework] dark images adjustments <@kroz>
Code:
Change-Id: Ie038c4a1aa535708c23f099fb5e836407e3d1603
SlimRoms/packages_apps_Camera2:
2013-12-22: TrueView Returns! <@Gerrit Code Review>
Code:
This adds the ability to view the complete sensor frame image
rather than the cropped preview used by AOSP to fill the entire
surface.
Change-Id: I79b14a165c66fa4f8b8e43598bd6a80e4de1c08b
2013-12-22: Fix Smart Capture label display <@Lars Greiss>
Code:
Change-Id: Ia3cceda0bf7fec21f2d019f07d416bfe8ebf211d
2013-12-22: Fixes Mako continues focus problem <@Lars Greiss>
Code:
rebase
Change-Id: I25187998003d357ec5ed3b10329fb39941f47bea
Signed-off-by: Josue Rivera <[email protected]>
2013-12-22: camera: Add ZSL support for Samsung/Qualcomm cameras <@Lars Greiss>
Code:
* Preview management for Samsung/Qualcomm cameras
Patchset 3: merge conflicts fixed
build errors fixed
PatchSet 4: codestyle corrections
Change-Id: Ib36bd21c9a76b45bced3eee2f25acc35b5d82b30
SlimRoms/packages_apps_InCallUI:
2013-12-21: Merge "TRDS: Dark InCallUI" into kk4.4 <@Gerrit Code Review>
2013-12-19: TRDS: Dark InCallUI <@kroz>
Code:
PS2:
- moved into right folder
PS3:
- redirect colors of original layout xml
Change-Id: I5bcfeb692bc4653e240df7c47216826452ee7d47
SlimRoms/packages_apps_Settings:
2013-12-22: Merge "First translation of Settings for KitKat" into kk4.4 <@Gerrit Code Review>
2013-12-18: First translation of Settings for KitKat <@gwindlord>
Code:
"Go To Sleep" paraphrased
Removed whitespace
Change-Id: I666cb60da3a0751ba1d4f351c2a46b1b159d9dd3
SlimRoms/packages_apps_Torch:
2013-12-22: Torch: add better error handling and added fallback mechanism <@Lars Greiss>
Code:
The handling of the Torch if an exception occured was very bad and
it was easy to break:
- notify the user with toast if the camera interface is not pressent
- catch the case that sys led controlled devices have wrong permissions
(eg third party kernel) and torch will completly crash.
Checking now if sys init is present.......if not successful
try to switch back to the camera interface.
- send broadcast change only if the state really switched
- when error occured turn off the service and the notification
- cleanup
- send broadcast with qualified users
Change-Id: Iabeb3b5f1c17d784a06c154f9a33e8d3d5214b7d
2013-12-21: make torch to a real system app <@Lars Greiss>
Code:
give it the correct permissions to allow to write
to sys interface with less permissions needed to
keep security alive
Thanks Alex for the hint to the hidden API
and gmillz for the idea
Change-Id: I44f70bdf3ecfb57ccac85eebe61e57a163bdf501
SlimRoms/vendor_slim:
2013-12-22: push to 1.9 <@Lars Greiss>
Code:
Change-Id: I4c4aab6fbd8440cda3649b1d77351aa0563dd15c
2013-12-22: push to 1.8 for weekly <@Lars Greiss>
Code:
waiting for feedback on last patches then we start jenkins
Change-Id: I1b8f5dcb6f8620506dfc4399b75c56802a3bd8e1
Older logs:
2013-12-22: clean up: movefiles.sh is no longer needed... <@Meticulus>
2013-12-22: overlay: SlimCenter overlay for ota. <@Meticulus>
Code:
-I've found that with just a few small adjustments you can redirect
SlimCenter to another url to check for updates.
2013-12-22: overlay: BOARD_USE_LEGACY_TOUCHSCREEN device tree flag. <@Meticulus>
Code:
-Everytime I repo sync my framework base commit to fix the touch screen
gets wiped out. In order to preserve it, I'm putting it in the overlay.
2013-12-20: ota: testing <@Meticulus>
2013-12-20: LVMv2: phase out the use of mmcblk0p14 as extra space. <@Meticulus>
Code:
-With the implementation of LVMv2, we don't need to use mmcblk0p14
(/vendor, /system/vendor) as extra space.
-mmcblk0p14 is now in the logical volume group "lvpool" along with
mmcblk0p13 and mmcblk0p16.
2013-12-20: ota: change device name from venturi to YP-G70 <@Meticulus>
2013-12-20: ota: removed beginning and ending spaces.. <@Meticulus>
2013-12-20: ota: ota update manifest. <@Meticulus>
Code:
-Initial commit of the ota manifest.
2013-12-19: slim.mk: build type switch. <@Meticulus>
Code:
-Switch from common full tablet to common full hybrid...
2013-12-19: init.venturi.rc: fix a small typo.. <@Meticulus>
2013-12-19: LVMv2: add lvm services to init.venturi.rc. <@Meticulus>
Code:
-This was left out of my initial commit here:
https://github.com/Meticulus/slim_device_samsung_venturi/commit/7ccd47c874f9a00c0397c8e8f17f3faaf72e256b
-This is absolutly neccessary for LVM...
2013-12-19: twrp: Correct screen resolution. <@Meticulus>
2013-12-18: LVMv2: initial implementation system(600M) <@Meticulus>
Code:
-Logical Volume Management
-The YP-G70 only has a 290m /system partition and this is not enough
to accomodate KitKat + full gapps. So, I'm implementing LVM so that
we can get dynamic volume resizing without having to change the under-
lying partitions.
-Partitions in Logical Group (Aprox 2.1G)
-- /dev/block/mmcblk0p13 (normally /system)
-- /dev/block/mmcblk0p16 (normally /data
-Logical volumes
-- /dev/lvpool/system (600M)
-- /dev/lvpool/data (100% remaining, aprox 1.5G)
-Installation Notes
--On the first flash, if the system logical volume is not present or
is less than 600M there is an assert error. This is so that if anyone
needs to backup information contained in /data, they can. In order to
proceed with the installation, the zip must be flashed a 2nd time.
--During the 2nd flash partitions in the logical group are wiped and
the logical volumes are created and formated then the /etc/fstab and
/etc/recovery.fstab are switched so that, when we hand everything off
to the normal rom installer, the new logical volumes are mounted.
-Reverting to a PRE-LVM ROM
--In the YP-G70 the "recovery", be it CWM or TWRP and in the kernel's
recovery-ramdisk. So in order to get a different recovery you just
flash a different kernel. So to get back to a PRE-LVM ROM, you just:
1. Reboot to recovery like normal.
2. Flash your PRE-LVM ROM like normal.
-- Note: All we really care about at this point is that the kernel
(boot.img) gets flashed. Ignore any other errors!
3. After the flash, Power off.
4. Hold volume up and power on, till you get to recovery.
5. Full wipe, including /system
6. Flash ROM + Gapps like normal
-Future Considerations
--LVMv2 allows us to quickly change the size of the system partition
as Android grows in size without having to manually repartition.
Manually repartitioning might cause unforseen problems with legacy
software.
-Meticulus
2013-12-17: recovery init: adb without /system <@Meticulus>
Code:
This allows "adb shell" to function when /system partition is not mounted
or for any reason /system/bin/sh is unavailable.
When /system IS mounted then adb uses mksh is used via /system/bin/sh
When /system IS NOT mounted then adb uses busybox via /sbin/sh
2013-12-14: Removed torch from build. <@Meticulus>
Code:
Torch isn't working at the moment anyways. May readd later!
2013-12-14: twrp: defined custom power key and fixed screen timeout problem. <@Meticulus>
2013-12-14: Initial commit <@Meticulus>
Super mine again!
BAH!! y u release while i'm at work....
Gonna test when i get home....
Flashy flashy, its like Christmas but better! no wrapping paper to clean up or relatives to dispose of.
Somehow I knew I would come on today to find KitKat available. Trying it now, will update later.
EDIT: No options for hardware buttons?
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
iurnait said:
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I didn't really solve it, per say. I put in a cheap hack to change the permission of the directory: in the init.venturi.rc. I'll got some clean up to do, but I'll be pushing my device tree tomorrow and submitting some changes to yours so we can get CM11.
Hello! Thanks for your work! I tested this rom, it's pretty nice. The only bug (except known) is that TWRP is not working on INTL kernel.
i'm having problems getting super user access, anyone else got this?
Lorddemonrage said:
i'm having problems getting super user access, anyone else got this?
Click to expand...
Click to collapse
My SU access is ok.
had sometime to mess with it. my sd card is not showing up, lost super user access. other than that almost everything works fine.
elaborating, i can see sd card in file manager, but connecting to windows does not show sd card accessible, just the galaxy players internal memory
Does it need a wipe if coming from 4.3
Sent from my zx spectrum
mr_ggcstop said:
Hello! Thanks for your work! I tested this rom, it's pretty nice. The only bug (except known) is that TWRP is not working on INTL kernel.
Click to expand...
Click to collapse
TWRP is a "known issue", if you read the OP. (workin' on it)
Lorddemonrage said:
had sometime to mess with it. my sd card is not showing up, lost super user access. other than that almost everything works fine.
elaborating, i can see sd card in file manager, but connecting to windows does not show sd card accessible, just the galaxy players internal memory
Click to expand...
Click to collapse
I am aware of the "2 cards in mass storage issue", but for the su problem, haven't had any issues .... developer-options-> root (or something like that)
joemhewitt said:
Does it need a wipe if coming from 4.3
Sent from my zx spectrum
Click to expand...
Click to collapse
yes including system:good:
iurnait said:
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Will you be making a stock cm11 ROM in the upcoming weeks?
I would love to play with this ROM for the time being ^_^
aznflawless said:
Will you be making a stock cm11 ROM in the upcoming weeks?
I would love to play with this ROM for the time being ^_^
Click to expand...
Click to collapse
No I am not. I can't maintain 2 Roms... I submitted patches to get CM11 working but someone else is going to have to build it...
@iurnait ???
Sent from my M470BSA using Tapatalk
When will the TWRP fix be released? My US player now, after the flash using Clockworkmod, will not be recognized in odin when in download mode. I love kitkat but i want to go back to my cm10.2 build. And the only way to do that as i know is to go to gingerbread and upgrade from there. but because of this issue i am stuck with TWRP and no os on my USA galaxy player 5.0. Please advise!!!!
bassbrick15 said:
When will the TWRP fix be released? My US player now, after the flash using Clockworkmod, will not be recognized in odin when in download mode. I love kitkat but i want to go back to my cm10.2 build. And the only way to do that as i know is to go to gingerbread and upgrade from there. but because of this issue i am stuck with TWRP and no os on my USA galaxy player 5.0. Please advise!!!!
Click to expand...
Click to collapse
Do not ask for ETA's!
READ THE OP BEFORE FLASHING!!! THE OP CLEARLY STATES NOT TO FLASH UNLESS YOU KNOW WHAT YOU ARE DOING BECAUSE TWRP IS NOT WORKING!
Been Waiting For This For Awhile Noe. Thanks Guys, I Guess With Patience Good Things Come. Hopefully The Same Can Be Said About The Rear Camera.
Sent from my YP-G70 using xda app-developers app
Meticulus said:
Do not ask for ETA's!
READ THE OP BEFORE FLASHING!!! THE OP CLEARLY STATES NOT TO FLASH UNLESS YOU KNOW WHAT YOU ARE DOING BECAUSE TWRP IS NOT WORKING!
Click to expand...
Click to collapse
Hi Meticulus!
First, let me thank you for all your time and energy spent in making this mod for an old device! I love my Player 5, but it is show it's age. I'm hoping your SlimKat 4.4.1 will breathe new life into it. (A shame Samsung stopped developing this line).
I have a Galaxy Player 5 running a rootedGingerbread 2.3.5 with CWM v5.0.2.7 (no TWRP)
Do you recommend any special preparation before applying SlimKat 4.4.1?
Since I'm using CWM, will I be able to restore back to Gingerbread using a current backup (just in case)?
As you might have guessed, I am not a frequent "mod"-er so I've fallen behind a bit.
Thank you for taking your time to help me and so many others!
CM11 for WAVE and WAVE 2
Android Kitkat 4.4.2
Hi All,
So once again it’s time to upgrade our project to Android 4.4.2
Previous versions:
CM10: http://forum.xda-developers.com/showthread.php?t=1851818
CM10.1: http://forum.xda-developers.com/showthread.php?t=2400126
CM10.2: http://forum.xda-developers.com/showthread.php?t=2550138
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
FEATURES
Android 4.4.2
CM sources of 13.01.2014
Updated to linux kernel version 3.0.101
270 MB RAM
KNOWN BUGS (what doesn't work):
- Network registration don't work with some SIM cards
- Conference Calls
- Some problems with audio codec settings, but generally it should
- Impossible to shut down phone in android, only restart
- Don't leave phone charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad.
You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /storage/sdcard1/dmesg.txt"
"logcat -b system -b radio -b events -b main -d -f /storage/sdcard1/logcat.txt *:V"
"logcat -b radio -d -f /storage/sdcard1/radiolog.txt *:V"
Download them from phone, archive and upload them.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
Click to expand...
Click to collapse
If the Badadroid is restarting before you're able to catch any log:
Download http://goo.im/devs/Rebellos/wave/bterm.exe
Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
Connect phone to PC.
Start bterm.exe
Type 4 commands:
Code:
open
dumpram 0x4FF00000 0x100000
close
exit
There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.
Click to expand...
Click to collapse
Bug reports without logs are completely useless.
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
HOW TO BUILD
I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
Of course you have to init with -b cm-11.0 and modify some steps.
local manifest to use: https://raw.github.com/Badadroid/android_wave_local_manifest/cm-11.0/local_manifest.xml
I do it like this:
Code:
cd ~
mkdir wave
cd wave
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
cd .repo
wget https://raw.github.com/Badadroid/android_wave_local_manifest/cm-11.0/local_manifest.xml
cd ..
repo sync -j8
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
brunch wave
device name is wave so the build invocation can be brunch wave
FIRST INSTALLATION
Bada 2.0 is required
Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
160MB of free "User" memory
400MB of free "Applications" memory
Download BOOTFILES, armlinux_boot for your device:
for 8500:
http://yadi.sk/d/W4RjnjQRC6TfP
http://yadi.sk/d/Yz7_dfpkC6TkC
for 8530
http://yadi.sk/d/kxJ0CZ20C7AKF
http://yadi.sk/d/zqzWZ9LmC7AJA
(please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
Download ROM from CHANGELOG section
Start Bada.
Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
Copy whole .zip to the Bada's User partition or SD Card.
Flash BOOTFILES and FOTA using Multiloader.
Reboot the phone holding Power and Call key.
FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
CWM Recovery starts, pick:
- "install zip"
- "choose zip from from storage/sdcard1"(Bada's User partition) or "choose zip from storage/sdcard0"(SD Card)
- cm-11-wave-<release id>.zip
- Yes - install
Reboot holding the Power key
You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
Do not remove zImage file.
Normal bootup is available using Power+Call keys
CWM Recovery mode is available using Power+Volume Up keys
CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.
For activation Performance and Developer Options categories in Settings you need Settings->About Phone and tap 7 times on Build number
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
SLIM GAPPS: http://d-h.st/users/ZordanKV/?fld_id=28623#files
HOW TO UNINSTALL
Follow the steps there: http://forum.xda-developers.com/showpost.php?p=35107469&postcount=393
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen and many others.
CyanogenMod team for base ROM
Pawitp, kasper_h and all other aries developers
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
CHANGELOG:
v4.4 http://www.multiupload.nl/SX2RTH51BC
- CM sources 2.06.2014
- Patches from SGS
v4.3 http://www.multiupload.nl/QS4A17BXXW
- CM sources 30.03.2014
- Many changes from CM core team
- Kernel with new optimization (Last Mackay Kernel from Nameless ROM)(new Zram algorithm, GPU fixes and etc. )
- Included fix for Wave2 from chemosun. This patch reduce Wave 2 screen wake up bug, i don't know about battery drain. He sent me it several months ago, but i forgot to include it to previous release
- Screen Frame rate path. Thanks to Alberto96
- Disabled 720p recording/playback. Big thanks to Alberto96 for idea and sources. It gave us more RAM.(total available in ROM 283MB) It is correctly disabled in ROM. so Photo camera is fully working, video camera is only 480p. For 720p playback you can use third-party apps like MXPlayer and etc.
If you go from previous releases, you need to clean data for Gallery and Camera application
v4.2 http://www.multiupload.nl/ZGB2Z5YOWD
- CM sources 21.02.2014
- Many changes from CM core team
-Added Basic GPS
v4.1.1 http://www.multiupload.nl/B7M535UJXH
- CM Sources 01.02.2014
- Zram 120Mb by default
- Some improvements for bootanimation
- Fixed some mistake in init, which can be the reason of some wi-fi problems
v4.1 http://www.multiupload.nl/5L9CCWZ4XA
- CM sources 28.01.2014
- Many changes from CM core team: Call delay workaround by pawitp was merged to CM sources, so no need to flash it
- Added test Battery thread to RIL https://github.com/Badadroid/androi...mmit/65d8d549e52761a9b8b673a0620c108773cf9ffd
- Added overlay for hardware camera key
v4 Initial CM11 release: http://www.multiupload.nl/YHC2P74SJZ
- CM Sources 13.01.2014
- Big patch set from mackay kernel http://forum.xda-developers.com/showthread.php?t=2532813 :
updated CPU governors, I/O schedulers, and many other performance patches
- 80Mb zRAM
MORE LINKS
Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
question
thanks for update
this cm11 is running dalvik or art?
black0000 said:
thanks for update
this cm11 is running dalvik or art?
Click to expand...
Click to collapse
Dalvik is default Android Runtime for all kitkat ROMs.
Art is experimental feature from Google and still is WIP:
You can read more here:
http://source.android.com/devices/tech/dalvik/art.html
CM officially don't support Art, though it is possible to switch to Art in developer options
volk204 said:
Dalvik is default Android Runtime for all kitkat ROMs.
Art is experimental feature from Google and still is WIP:
You can read more here:
http://source.android.com/devices/tech/dalvik/art.html
CM officially don't support Art, though it is possible to switch to Art in developer options
Click to expand...
Click to collapse
according to you which one is better dalvik or art gor our wave
black0000 said:
according to you which one is better dalvik or art gor our wave
Click to expand...
Click to collapse
I didn't try Art, i can say that after last optimization changes performance is good enough even with dalvik.
@hero355, what you can say about performance of this ROM after playing Asphalt 7 on it?
volk204 said:
I didn't try Art, i can say that after last optimization changes performance is good enough even with dalvik.
@hero355, what you can say about performance of this ROM after playing Asphalt 7 on it?
Click to expand...
Click to collapse
Firstly I want to say big that's to volk204 for his great work
This time really it's a big step in badadroid development.
I've tested several kernel and I can say The phone is simply flying,The performance and optimization is perfect and we got now almost stable for 4 years old Samsung Wave phones
Secondly I've tested game performance and my tests was on Asphalt 7, (I haven't time for test other games- I'm not a gamer )
As you know there are some kernels with bigmem and zram .
I've tested all kernels with asphalt 7 and while all my tests I used 100~1000 MHz with interactive governor and game was running perfect
The best game performance was zram 120 with 1000mhz, I don't even imagine that with bigmem zram120 + 1400mhz it'll fly
So I can say now time to revert android to default
Thanks again volk204 and all badadroid developers
Question: does the bigmem kernel allow photo taking? I can live without video but not without camera/flashlight...
Stevethegreat said:
Question: does the bigmem kernel allow photo taking? I can live without video but not without camera/flashlight...
Click to expand...
Click to collapse
AFAIK camera is not working at all and photo also on Bigmem, added to OP, but i really don't see anysense to use bigmem, because in normal mode all is OK))
volk204 said:
AFAIK camera is not working at all and photo also on Bigmem, added to OP, but i really don't see anysense to use bigmem, because in normal mode all is OK))
Click to expand...
Click to collapse
Hey, nice work as always! But any chance of NAND version for this ROM?
Or can we use without bada n Tigrouzens Fota?
Stevethegreat said:
Question: does the bigmem kernel allow photo taking? I can live without video but not without camera/flashlight...
Click to expand...
Click to collapse
No, camera app will not work, so no photos and video capturing.
sadiq23 said:
Hey, nice work as always! But any chance of NAND version for this ROM?
Or can we use without bada n Tigrouzens Fota?
Click to expand...
Click to collapse
No correct charger - No NAND version
volk204 said:
HOW TO UNINSTALL
Follow the steps there: http://forum.xda-developers.com/show...&postcount=393
Click to expand...
Click to collapse
The Link is not functional anymore. Shows that the forum specified is invalid.
Sandeep Srikantam said:
The Link is not functional anymore. Shows that the forum specified is invalid.
Click to expand...
Click to collapse
fixed
GAPPs
volk204 said:
fixed
Click to expand...
Click to collapse
There are two files in Slim GAPPs, test(newer) and an older version. Which one to download ?
Is this version noticeably faster than the previous one (3.1)?
WiFi Not Working
@volk204, I was running CM Badadroid v2.1 and today I installed CM11 Badadroid v4. Since then the Wifi is not working on my wave 2 s8530.
Other devices are detecting the Wifi and connecting to it but my wave is not connecting to the wifi.
I have also disconnected other devices and tried to connect only wave 2 but the device doesn't even detect wifi network.
Please help.
WaveII_Jil said:
@volk204, I was running CM Badadroid v2.1 and today I installed CM11 Badadroid v4. Since then the Wifi is not working on my wave 2 s8530.
Other devices are detecting the Wifi and connecting to it but my wave is not connecting to the wifi.
I have also disconnected other devices and tried to connect only wave 2 but the device doesn't even detect wifi network.
Please help.
Click to expand...
Click to collapse
Search for Wifi fix zip , I don't know where is ,I think in 3.1 or 2.1 thread
WaveII_Jil said:
@volk204, I was running CM Badadroid v2.1 and today I installed CM11 Badadroid v4. Since then the Wifi is not working on my wave 2 s8530.
Other devices are detecting the Wifi and connecting to it but my wave is not connecting to the wifi.
I have also disconnected other devices and tried to connect only wave 2 but the device doesn't even detect wifi network.
Please help.
Click to expand...
Click to collapse
anyone with wave2 has the same problem?
Did you do clean installation with removing previous version of android and installing new version or just flashed zip via recovery?
No logs - no problems
florynwk3 said:
Search for Wifi fix zip , I don't know where is ,I think in 3.1 or 2.1 thread
Click to expand...
Click to collapse
It is useless
volk204 said:
anyone with wave2 has the same problem?
Did you do clean installation with removing previous version of android and installing new version or just flashed zip via recovery?
No logs - no problems
Click to expand...
Click to collapse
I did a clean installation by uninstalling previous version and installing new version. Sorry, could not get the logs.
Just wanted to know if this issue exists only in my phone or others also...
BUG: encrypt device ...
hi folks,
great work volk thats really exciting..
the interesting lines are:
ActivityManager( 503): Resuming delayed broadcast
I/ActivityManager( 1035): Timeline: Activity_launch_request id:com.android.settings time:3037005
I/ActivityManager( 503): START u0 {cmp=com.android.settings/.CryptKeeperConfirm$Blank (has extras)} from pid 1035
D/PhoneStatusBar( 658): disable: < EXPAND* ICONS* ALERTS* ticker SYSTEM_INFO* BACK* HOME* RECENT* clock SEARCH* >
I/ActivityManager( 503): Displayed com.android.settings/.CryptKeeperConfirm$Blank: +359ms
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3037409
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41d115a0 u0 com.android.settings/.CryptKeeperConfirm$Blank t4} time:3037702
E/Cryptfs ( 156): Cannot get size of block device
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3047091
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41ca10d0 u0 com.android.settings/.SubSettings t4} time:3047384
D/Tethering( 503): Exception adding default nw to upstreamIfaceTypes: java.lang.NullPointerException
I/ActivityManager( 1035): Timeline: Activity_launch_request id:com.android.settings time:3051736
I/ActivityManager( 503): START u0 {cmp=com.android.settings/.CryptKeeperConfirm$Blank (has extras)} from pid 1035
I/ActivityManager( 503): Displayed com.android.settings/.CryptKeeperConfirm$Blank: +103ms
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3051879
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41cbcb58 u0 com.android.settings/.CryptKeeperConfirm$Blank t4} time:3052206
E/Cryptfs ( 156): Cannot get size of block device
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3060969
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41ca10d0 u0 com.android.settings/.SubSettings t4} time:3061295
I think
E/Cryptfs ( 156): Cannot get size of block device
is the line to be interpreted...
Can someone please have a look into it...
logcat & co are attached
Android Kitkat 4.4.4
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
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.
*/
KNOWN BUGS (what doesn't work):
- Modem in 2G mode work incorrect(Network registration don't work with some SIM cards, permanent full signal straight, problem is with audio in calls)
With 3G all is OK, Use this: Settings -> More.. in "wireless&network" category -> Mobile Network -> Preferred Network type -> 3G only
- Conference Calls
- Some problems with audio codec settings, but generally it should
- After Recovery time to time incorrect capacity of battery
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
INSTALLATION
FIRST INSTALLATION
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel https://yadi.sk/d/PhY11Rvnmq99T
FOTA https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES https://yadi.sk/d/cBPD41VEbP2od
"start" kernel https://yadi.sk/d/xWwb8r3RmpZxK
FOTA https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
wait before on screen you will see "Partitions had been prepared"
if you have external SD card:
- Back -> Back -> Back -> Mount -> Mount USB storage
On PC you will see SD card mounted, and copy ROM there -> Unmount -> Back
- Install -> choose zip with ROM(mount point /external_sd) -> Swipe to Confirm Flash -> Reboot System
if you have no external SD card
- Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
- Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
- Copy Zip with ROM Internal Storage -> Disable MTP -> Back
- Install -> choose zip with rom -> Swipe to install -> wait for flashing -> Reboot system
Enjoy OMNI!
You can remove installation .zip from Android level by connecting through USB in MTP mode.
TWRP Recovery mode is available using VolUp + End keys
Every next update you can just flash .zip through CWM.
UPDATE from OMNI older that 09.09.2014
- Make backup in TWRP(Backup -> Select Data -> Swipe to backup)
- Flash FOTA and "start" kernel via Multiloader
- Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
- wait before on screen you will see "Partitions had been prepared" -> Back -> Back -> Back
- Mount -> Mount USB storage
- Copy zip with Rom from PC to External SD card -> Unmount -> Back
- Install -> choose zip with ROM -> Swipe to Confirm Flash -> Home
- Restore backup in TWRP (Restore -> Select packge for restore -> Swipe to restore)
- Reboot -> System
For activation Performance and Developer Options categories in Settings you need Settings->About Phone and tap 7 times on Build number
ROOT
Omni is without root support from default
To activate root flash zip via Recovery from XDA thread http://forum.xda-developers.com/showthread.php?t=1538053
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
SLIM GAPPS: http://d-h.st/users/ZordanKV/?fld_id=28623#files
HOW TO UNINSTALL
Just reflash bada via Multiloader
CHANGELOG:
26.01.2016 https://yadi.sk/d/lY5ZEJc6noBVH
- Big kernel update from https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/tree/android-5.1
Big thanks to @Coldwindofnowhere
It enable many additional settings in Settings-Performance
Also enabled boost for incall volume in Advanced Settings
- Added Battery saver mode from Omni Gerrit, Experimental- not really tested
- GPS fixes, still we have no A-GPS
11.01.2016 https://yadi.sk/d/pTSrLBykmpVVz
- Omni sources 11.01.2016
- Sensors update and cleanup
- Added Bigmem support in Advanced settings
with default settings we have 270 mb RAM with working 720p video recording
with Bigmem we have 283 mb RAM without working 720p video recording(as was by default in previous versions)
with Max RAM we have 315 mb RAM and camera, video playback and torch is not working at all
- Updated kernel with last omni changes
RIL update 20.12.2014 https://yadi.sk/d/kvYUiq6QdWSdD
- SMS fixes
just flash it via TWRP
11.12.2014 https://yadi.sk/d/80q05wvrdKW3t
- Omni sources 11.12.2014
- Added roaming indication
- Re-worked SMS
- Updated some Zram parameters
maybe something else
25.10.2014 https://yadi.sk/d/qCh-swftcJ7tg
- Omni sources 25.10.2014
- Moved to omni aries kernel
- Updated audio driver
- Updated charger driver
09.09.2014 https://yadi.sk/d/H5lEBmQvbLiSH
- Omni sources 09.09.2014
- New partition layout and new installation procedure(Read carefully! Device will be wiped).
Now you can use android without SD card
- Compass fixed
- Added phone reboot in case of modem crash.
15.08.2014 https://yadi.sk/d/jKCEMrAEZkZGr
- Omni sources 15.08.2014
- Hopefully fixed LCD wake-up bug on wave2, thanks to Blue59 for so many tests
- Corrected voltage for some on-board chips
13.07.2014 https://yadi.sk/d/DoaSRX3EWY9Hk
- Omni sources 13.07.2014
- Fixed updater script
- Fixed power off, thanks to Tigrouzen
11.07.2014
Updated FOTA links
Changed background from white to black
Added start of Bada - Call+End, we can use offline bada charger, in case if battery is fully empty
Added checking kernel size on SD card, sometimes boot.img exist but it is 0mb
04.07.2014 https://yadi.sk/d/Rw2UmkaoVxwdP - forgot to fix updater script, so please re-copy boot.img manually to SD card
- Omni sources 04.07.2014
- Small kernel optimizations
- Bring back Advanced Settings (TVout, vibration intensity and etc )
- Updated framework overlay
- Added OmniTorch
- Added USD OTG support (not tested), based on http://forum.xda-developers.com/showpost.php?p=53803247&postcount=8 Thanks to Tigrouzen
29.06.2014 https://yadi.sk/d/M0XEIgJMVTtCi
- Initial Release
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen, Benzox and many others.
OMNI team for base ROM
Pawitp, kasper_h and all other aries developers
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
Reserved
great work and really great rom thanks @volk204
i want install rom but no mount sd card on recovery wave 2
full flash bada but again no mount sd card
nima.yavari said:
i want install rom but no mount sd card on recovery wave 2
full flash bada but again no mount sd card
Click to expand...
Click to collapse
Mount point for SD card is /external_sd
Today Blue59 installed it successfully on Wave2
Also try to catch recovery.log via ADB http://rootzwiki.com/topic/24120-how-to-get-a-log-from-twrp/
volk204 said:
Mount point for SD card is /external_sd
Today Blue59 installed it successfully on Wave2
Also try to catch recovery.log via ADB http://rootzwiki.com/topic/24120-how-to-get-a-log-from-twrp/
Click to expand...
Click to collapse
change format sd card fat to fat32 correct
thanks blue59 and volk
Quick Review
USB OTG for badadroid kernel KitKat rom :
https://github.com/Tigrouzen/android_kernel_samsung_wave
This example based on ICZen(ICS) KitKat's very different :
vold.fstab :
Code:
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/s3c_otghcd/usb
init.wave.rc :
Code:
mkdir /mnt/usbdisk 0000 system system
symlink /mnt/usbdisk /usbdisk
storage_list.xml (device/samsung/wave/overlay/frameworks/base/core/res/res/xml/) :
Code:
<storage android:mountPoint="/mnt/usbdisk"
android:storageDescription="@string/storage_usb"
android:primary="false"
android:removable="true"
android:allowMassStorage="true" />
Where is the link for FOTA ??
@Tigrouzen
Can i use Zendrokat FOTA and BOOT?
FOTA SD
couldn't find link for FOTA SD on other forums. can anyone supply?
Ok, it works with Zendrokat fota. But me and my friend (he flash your fota) cant install ROM. Because we have error next to formating. Updating partition details and Failed. How to repair it? ;/
thanks man ...
Hey "wavers" how 'bout the performance ?
I am able to install zendrokat v2.2 but this one is so hard.. Always some error please guys a clear demo or a video on flashing will be very helpful. I really love to try this rom as its very slim.Thanks. B.R:good:
msprakashmmc said:
I am able to install zendrokat v2.2 but this one is so hard.. Always some error please guys a clear demo or a video on flashing will be very helpful. I really love to try this rom as its very slim.Thanks. B.R:good:
Click to expand...
Click to collapse
As explained in OP,
-Flash bada 2.0
-Flash BF and Fota (SD fota)
-Put all files on SDcard
-Boot recovery, choose flash zip, go to /external-sd and choose the zip.
-this part is important : "- Wipe -> Advanced wipe -> Check "data" -> Repair or change File Sytem -> Change File System -> Ext4 -> Swipe to change ->Back -> Back ->Back -> Back "
-reboot, enjoy.
if you do this carefully step by step, it will work
BenzoX said:
As explained in OP,
-Flash bada 2.0
-Flash BF and Fota (SD fota)
-Put all files on SDcard
-Boot recovery, choose flash zip, go to /external-sd and choose the zip.
-this part is important : "- Wipe -> Advanced wipe -> Check "data" -> Repair or change File Sytem -> Change File System -> Ext4 -> Swipe to change ->Back -> Back ->Back -> Back "
-reboot, enjoy.
if you do this carefully step by step, it will work
Click to expand...
Click to collapse
where's the FOTA SD
Help help help
I have copied kernel and zip
Run recovery
Wipe all complete no error
Try to install zip
Updating partition details
Failed.
What i make wrong?
//
@BenzoX
Thank you. you are the best. Big thanks Bro for help!
my phone has gone in to boot loop. It starts with samsung 8500 then switches off then again starts and switches off and so on. If i try to go to download moad then it goes but again restarts. I cannot hold on a screen so cant even reflash bada...
If i try to go to download moad then it goes but again restarts.
Click to expand...
Click to collapse
If DL Mode not stable... then 2 reasons possible.
With luck only Battery empty.
So charge battery external... or use other battery...
If no luck...
Then Bootloader could be damaged or something else bad...
Best Regards
nileshlog said:
my phone has gone in to boot loop. It starts with samsung 8500 then switches off then again starts and switches off and so on. If i try to go to download moad then it goes but again restarts. I cannot hold on a screen so cant even reflash bada...
Click to expand...
Click to collapse
Battery probably empty, either boot any recovery and let it charge for a while, or plug phone and let charge on bada charge mode, or do it with some wires and a 5v power supply...
Then you should be able to go on DL mode.
SailfishOS (SFOS) is a GNU+Linux system using libhybris to leverage Android drivers from LineageOS.
About everything should work (except NFC, no userspace support for now).
You're root and you've SSH, set password in developer-mode settings. Use devel-su like you'd use sudo !
To use/flash SFOS (no wipe needed), you should already be using LineageOS 14.1 20181031 build or newer,
and have booted it at least once (otherwise WLAN problems).
See latest release post for OTA update instructions, or flash ZIP download link.
Warning : flashing zip over previous SFOS install erases it ! So use OTA to avoid that, or use integrated backup app...
Note : SFOS only flashes boot partition and install itself in /data/.stowaways/sailfishos/ so :
you can go back to LineageOS only by flashing the LOS boot image
you can reclaim diskspace used SFOS by removing /data/.stowaways/sailfishos/
Reference Wiki page on merproject.org
Kernel | Device | Vendor source trees
Feeling adventurous ?
This is a SailfishOS community port for the 6045 idol3.
This is not Android (just re-using the lower layers), Android apps can't run on it and there's no support for official-ports-AlienDalvik-emulator.
So please don't ask.
During installation, you'll be asked to create a Jolla account, to have access to basic apps (notes, mediaplayer, documents, etc.).
This is not mandatory (though prefered for the full experience) : should you choose not to register (and even if you do),
you still can install an alternative store using OpenRepos client Storeman
Reserved
Hello, installed version 3, everything works fine, data transfer, wifi, all sensors (including case), location, mtp, calls and SMS. There were only problems with the store, some applications are not installed the first time, you have to install again, and so great work is another alternative for the smartphone, thank you.
andrejchern said:
Hello, installed version 3, everything works fine, data transfer, wifi, all sensors (including case), location, mtp, calls and SMS. There were only problems with the store, some applications are not installed the first time, you have to install again, and so great work is another alternative for the smartphone, thank you.
Click to expand...
Click to collapse
I have installated seilfish os some time ago in my moto g2 and the battery life and boot speed its superior then any version of android ... ?
A very fast, fluid, and consistent UI in this ROM. An interesting one to play with. (However, for my needs, I need the PlayStore apps.)
I now understand how your work on Lineage was a foundation for this one.
I am curious Vknecht, what is your interest in this one?
tess1 said:
A very fast, fluid, and consistent UI in this ROM. An interesting one to play with. (However, for my needs, I need the PlayStore apps.)
I now understand how your work on Lineage was a foundation for this one.
I am curious Vknecht, what is your interest in this one?
Click to expand...
Click to collapse
It's all politics, also it's the system I use daily
some sort of hommage to a french industry of old (1898), rough-rided by financialization (see, can't build idol3 themselves)
fighting planned obsolescence
taking the power back on a device
powering it with an OS independent from GAFAM
having closer to classical GNU+Linux distro, though not totally open in the case of SFOS
Since 2010 I've been a Nokia N900 then N9 user (which ran with Maemo, resp. Meego, predecessors to SailfishOS) until summer 2017 when I got a Xperia X for the SailfishX release. Only ever used Android for a month, until the build-SFOS-for-X documentation was released and dived in the OS-building fun...
At the beginning of 2018 I looked for a cheap and decent french-branded-androphone (2Gb RAM, HD display) with a working LineageOS port and found the idol3 to begin a new SFOS port. It's been a long 8 months journey, where rebuilding LineageOS if only for the patch-level was not much, then also wanted to "upstream" some fixes or upgrades (eg. kernel) I wanted in SFOS...
I started using my idol3 again and I love Sailfish OS as soon as I figure out android apps im gonna use it alot more
Everything work fine, but the double tap to wake up the telephone.
Hi vknecht, great job, how can I contribute (donation) to your work? I've installed everything except Anbox, but I think I'll do it anyway, most of my contacts use Wzap ... Everything works fine except for the double tap to wake up the phone, do you know what it can depend on? Is it a function of hardware or software? With Lineage it worked, with Sailfish no. It's not dramatic, but definitely inconvenient to have to use the power switch every time. Thank you.
Best regard.
Antonio from Italy.
vknecht said:
Feeling adventurous ?
This is a SailfishOS community port for the 6045 idol3.
This is not Android (just re-using the lower layers), Android apps can't run on it* and there's no support for official-ports-AlienDalvik-emulator.
So please don't ask.
It's a systemd-based GNU/Linux with 32bits-userspace system, and about every basis function should work.
You're root, set password in developer-mode settings. Use devel-su like you'd use sudo !
To use/flash SFOS (no wipe needed), you should already be using LineageOS 14.1 20181031 build, and have booted it at least once (otherwise WLAN problems).
During installation, you'll be asked to create a Jolla account, to have access to basic apps (notes, mediaplayer, documents, etc.). This is not mandatory (though prefered for the full experience, for now) : should you choose not to register (and even if you do), you still can install an alternative store using OpenRepos client Storeman
*basic Anbox support was added, but don't count on it for now (plz contribute if you can), it may be broken.
If you really want to try it : (don't just copy/paste, fix the URLs !)
Code:
### As root (devel-su), on the phone via SSH :
# Add mal's Anbox for SFOS repository
ssu ar home_mal_anbox [url]http://repo.merproject.org/obs/home:/mal:/anbox/sailfish_latest_armv7hl/[/url]
pkcon refresh
pkcon install anbox-sailfishos anbox-sailfishos-image-mixed-32-64-bit
rm -f /var/lib/anbox/overlay/system/lib64/libGLESv*
cp /vendor/lib/egl/libEGL_adreno.so /var/lib/anbox/overlay/vendor/lib/egl/
# Install a keyboard APK, eg [url]https://f-droid.org/fr/packages/rkr.simplekeyboard.inputmethod/[/url]
mkdir -p /var/lib/anbox/data/app
cp *apk /var/lib/anbox/data/app
### Networking is broken at the moment... ###
### Comment anbox-bridge.sh lines (ExecStartPre and ExecStopPost) ###
### in /lib/systemd/system/anbox-container-manager.service ###
# Restart Anbox
systemctl restart anbox-container-manager
# There's no "back" button for now
# Run Anbox from app screen again to go back to Anbox app launcher
This is a simultaneous release of SFOS 2.2.1.18 and 3.0.0.8, if you have problem with one version, try the other
SFOS 2.2.1.18
SFOS 3.0.0.8
Sorry no screenshot or video for now, you can find for other devices, looks should be the same.
SailfishOS fir idol3 Wiki page
Kernel | Device | Vendor source trees
Click to expand...
Click to collapse
Any chance of seeing it on the Idol 3 4.7 ? It would give me a good reason to use it again. It's okay if not it's just sad that there's no updated ROM for this version... I could beta test it if you ever do that
zorro_tj said:
Hi vknecht, great job, how can I contribute (donation) to your work? I've installed everything except Anbox, but I think I'll do it anyway, most of my contacts use Wzap ... Everything works fine except for the double tap to wake up the phone, do you know what it can depend on? Is it a function of hardware or software? With Lineage it worked, with Sailfish no. It's not dramatic, but definitely inconvenient to have to use the power switch every time. Thank you.
Click to expand...
Click to collapse
Hello, and thank you for the heads up on dt2w... so I had a look, and found how to enable it
(make sure developer mode is enabled and you've set or checked the password)
Code:
host $ ssh [email protected]
,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[[email protected] ~]$ devel-su
Password:
[[email protected] nemo]# echo 1 > /sys/class/tp_gesture/tp_device/tp_gesture_id
[[email protected] nemo]# printf "[EVDEV]\nKEY_APP_SWITCH=KEY_POWER\n" > /etc/mce/99-doubletap-idol3.ini ; systemctl restart mce
The echo command has to be issued when the screen is on, and each time you reboot, for now (don't know why it's not already set to 1 like in LOS)
The printf and systemctl are only needed once to create the configuration file and restart the service.
Hopefuly you'll see no battery drain, so it can be enabled by default in the future...
For donations, maybe it will be possible later.
h3cat3 said:
Any chance of seeing it on the Idol 3 4.7 ? It would give me a good reason to use it again. It's okay if not it's just sad that there's no updated ROM for this version... I could beta test it if you ever do that
Click to expand...
Click to collapse
One thing I could do is try building LOS 14.1 with idol347 defconfig, but afaik it's not really working.
Otherwise one could follow the SailfishOS HADK using a working CyanogenMod base and I'd be glad to help, but don't have time to start it myself at the moment.
Thanks!
vknecht said:
Hello, and thank you for the heads up on dt2w... so I had a look, and found how to enable it
(make sure developer mode is enabled and you've set or checked the password)
Code:
host $ ssh [email protected]
,---
| Sailfish OS 3.0.1.11 (Sipoonkorpi)
'---
[[email protected] ~]$ devel-su
Password:
[[email protected] nemo]# echo 1 > /sys/class/tp_gesture/tp_device/tp_gesture_id
[[email protected] nemo]# printf "[EVDEV]\nKEY_APP_SWITCH=KEY_POWER\n" > /etc/mce/99-doubletap-idol3.ini ; systemctl restart mce
The echo command has to be issued when the screen is on, and each time you reboot, for now (don't know why it's not already set to 1 like in LOS)
The printf and systemctl are only needed once to create the configuration file and restart the service.
Hopefuly you'll see no battery drain, so it can be enabled by default in the future...
Thanks a lot, it worked! I will pay attention to the the battery drain and will informe you. Just another question: i see your OS version is 3.0.1.11, mine is 3.0.0.8 (Lemmenjoki) is it convenient for me to update it? if yes, in what way? The device is a Idol 3 6045K dual-sim, no external sdcard on board.
Thanks again, greet from Italy.
Click to expand...
Click to collapse
zorro_tj said:
Thanks a lot, it worked! I will pay attention to the the battery drain and will informe you.
Just another question: i see your OS version is 3.0.1.11, mine is 3.0.0.8 (Lemmenjoki) is it convenient for me to update it?
if yes, in what way? The device is a Idol 3 6045K dual-sim, no external sdcard on board.
Thanks again, greet from Italy.
Click to expand...
Click to collapse
You're welcome For now I don't see any drain, let's hope it stays like this.
I found out that the ini file is not necessary if one sets tp_gesture_id to 2, but still have to set this value on boot
and/or find why it's not the same as in LineageOS by default.
3.0.1.11 release for idol3 is still in devel phase, once it's ready (~ one week or so) it will be published in testing phase and then you'll be able to do
OTA through commandline.
One can flash a devel-image, but then can't rely on OTA : will have to re-flash a testing-image or do risky/unsupported repository-switch.
Those are generally built using SailfishOS porters' Gitlab-CI group, latest being the 20190227 devel image
SailfishOS 3.0.1.11 beta3
Backup...
Update using OTA : the integrated graphical updater doesn't work for community ports
Easiest is to install sfos-upgrade either through Storeman or direct RPM dowload.
Flash image : (erases previously installed SailfishOS)
sailfishos-idol3-release-3.0.1.11-20190321-beta3.zip
Changes :
SailfishOS 3.0.1.11 release notes (points specific to officially supported devices don't apply)
Kernel : enabled Yama security module
Enabled doubletap to wake
Sorry, Anbox confirmed to NOT work, have to check required overlayfs support, maybe broken with the kernel updates.
SailfishOS 3.0.1.11 beta3 beta2 Constant reboots, hangs and reboots.
andrejchern said:
SailfishOS 3.0.1.11 beta3 beta2 Constant reboots, hangs and reboots.
Click to expand...
Click to collapse
Sorry to hear that... does it happen regularly/systematically and quite early after boot, or after (somehow) extensive usage, especially browser ?
I supposed you tried with flashing as well as OTA ?
A known cause for reboot is fixed in this build (and beta2 iirc) by an updated connman package ("rpm -qi connman" shows ip6tfix in version).
Maybe it's related to Yama security, will make a build without it...
Arbitrary reboots, after the introduction of the account and login starts hanging and rebooting, I immediately rolled back to the backup and did not understand why this is happening.
andrejchern said:
Arbitrary reboots, after the introduction of the account and login starts hanging and rebooting, I immediately rolled back to the backup and did not understand why this is happening.
Click to expand...
Click to collapse
Could you try flashing the ZIP inside the artifact from this devel build ?
It uses the same kernel as 3.0.0.8, ie. without yama, pstore and iirc RTC write support...
This build works fine, no reboots. Thanks.
SailfishOS 3.0.1.11 beta4
Update from any previous betas using OTA :
has to be done from commandline (on device or through SSH, USB prefered) since the graphical client in settings doesn't support community ports.
Code:
# Install sfos-upgrade package like this, or through Storeman
curl -O https://openrepos.net/sites/default/files/packages/5928/sfos-upgrade-2.4-1.noarch.rpm
devel-su
pkcon install-local sfos-upgrade-2.4-1.noarch.rpm
sfos-upgrade 3.0.1.11
reboot
# Patience, it takes an additional reboot to flash boot partition
# Go to commandline again and run :
devel-su post_sfos-upgrade
or install by flashing sailfishos-idol3-release-3.0.1.11-20190329-beta4.zip
(this replaces previously installed SailfishOS and SailfishOS-data, backup if needed)
Changes
Fall back to previous kernel
Hey mate, great job! Everything worked fine with sfos-upgrade from command line! Thanks a lot!!!
Just a question... I haven't prediction text, it's normal? Thanks again.
Antonio from Italy.