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
Related
FIRST OFF: THIS IS FOR UNLOCKED BOOTLOADERS. IF YOU TRY TO INSTALL THIS WITH A LOCKED BOOTLOADER, YOU WILL BRICK YOUR PHONE.
As aGraceful has been mentioning, Here is the CM9 thread dedicated to the R800x.
What it is:
We (myself, aGraceful or anybody else who's interested) will port FXP with every new release that comes out.
I (or if anybody else is interested) will be building & uploading a new version (from source) about mid-week (between FXP release) with the newest CM9 updates.
What it is not:
Neither myself, aGraceful, or anybody else who contributes claim any thing special about the code. Either FXP built it (if it's a port) or it's code from Cyangenmod/Koush/freexperia or anybody else who has contributed to the CM9/Android repos.
Starting 2012 June 06 -- I am using my own device tree and vendor tree to build this, so it should work better with wifi than FXP's builds.
Now, onto the good stuff.
What Works:
Data
Calls
Wifi
GPS
SMS
Accelerometer
MMS (thanks chrono!)
What Doesn't Work:
Bluetooth Media Audio (Thanks chrono!)
Video Recording (Thanks Neoandgeo for pointing that one out)
Facebook account syncing (Thanks DoubleByte) -- Note facebook account syncing looks like it's a problem within 4.0 framework...
Anything else that doesn't work, lemme know, I'll add it to the list.
FXP Changelog: changelog for fxp
Link to All Downloads
What's in it:
1) agraceful's port of FXP 115 116 117 (Current as of 04/22) I'm gonna stop hosting FXP ports through my mediafire, look to agraceful for those
2) mega_fix.zip -- contains Atarii's wifi/gamepad fix & 216monster's mms/carrier name fix
3) My latest build from source (newest date in the title)
4) Older builds
5) Copy of the libs I use for porting, If you're interested in trying to bring another ROM to our phone, these cover mostly everything) dev corner with some libs if you're interested in porting something.
Steps to do a install:
1) Download & copy to sdcard
2) reboot recovery,
3) MAKE A NANDROID!
4) wipe dalvik/cache
5) install from sdcard.
Steps to do a 100% clean install (we're talking if all else fails try this option)
1) Reboot into recovery, MAKE A NANDROID, wipe the 3 major things (data/cache/dalvik)
2) Turn off your phone & connect it in fastboot mode.
3) enter this fastboot erase system (this will erase the /system partition, insuring a clean install)
4) boot into recovery
5) install from zip.
Thanks to Ridder215215, a complete guide on how to install CM9 (just replace the link in line 2 with the link above)
As everybody knows, Flashing roms can lead to issues with your phone. When you decide to flash something, you are taking the responsibility for your phone working into your own hands.
Google apps: http://goo.im/gapps
or goo.im market app: https://play.google.com/store/apps/details?id=com.s0up.goomanager
Rom Update: 2012 April 11
1) Latest CM9 fixes.
2) Gamepad fix added in.
3) Wifi fix is included
4) Kernel is included in the zip this time, so no need to download two separate things
Test update: 2012 April 11
Uploaded a xLoud test version for y'all to try out. Please tell me how well it works for you guys! (If it makes a big enough difference, I'll change out dspmanager for it)
1) Added in xLoud framework (kinda, I think we're missing stuff from framework.jar/framework-res.apk so it doesn't show up in menu-> sound settings) ALSO: It's having an issue with wrong UID (settingsProvider.apk issue) so when I get around to it, i'll tear apart some things and see if it can't be ported.
2) Removed DSP manager
Kernel Update; 2012 April 14
Uploaded a new kernel for people to test out
Enabled governors:
Conservative
MinMax
SavagedZen
SmartAssv2
InteractiveX
Enabled IO Schedulers:
Anticipatory
Deadline
CFQ
V(R)
Disabled ALS (Thank Keiran)
Sources are FXP's (https://github.com/freexperia/semc-kernel-msm7x30-ics/tree/ics) All I did was tweak some minor stuff
Rom Update 2012 April 15
1) Latest CM Sources
2) No xLoud tweaks
3) Wifi fix built in (will be from now on)
4) Gamepad fix built in (will be from now on)
5) Set mmc to "12" in apns-conf.xml (should fix any mms issues, if it doesn't I'll change it to 5)
Kernel uploaded yesterday will still work (am using it right now)
Kernel Update (2012 April 18)
Uploaded a new kernel built from DooMLoRD's Sources (see links above) with wifi modules included (so you won't have to flash 'em) -- NOTE: THIS ONE WILL BREAK H/W DECODING.
Rom Update (2012 April 19)
Uploaded a new version.
1) Latest cm9 fixes
2) Tried adding some of the info from brainard52's post into the apns-conf.xml it it doesn't work, follow the instruction in his post (thanks brainard52!)
Rom Update (2012 April 21)
Uploaded a new version
1) Latest cm9 fixes
{in case mms is still not fixed 2) Tried adding some of the info from brainard52's post into the apns-conf.xml it it doesn't work, follow the instruction in his post (thanks brainard52!)
}
Why? Because 8 hours and still no upload from FXP, so I felt like uploading one
Rom Update (2012 April 25)
Uploaded a new version
1) Latest cm9 fixes
2) Included KeiranFTW's latest DFK-CM9 kernel in the zip, because well, it works. best. way to go keiran!
3) Made sure that ro.board is zeus, not zeusc (once again, thanks Keiran!)
Rom Update (2012 April 29)
1) Latest CM9 Fixes
2) zipalign in /system/xbin
3) OI File Manager From OpenIntents
4) Network Name fix from 216Monster!
Rom Update (2012 May 03)
1) Latest CM9 fixes
2) Change in baseband libs to .57.
Sorry, not too much this time, I got distracted with the 2.3.4 update & got to it late
Rom Update (2012 May 05)
Added Codename-Android to the download list. If you like tweaks, enjoy. Codename Android has it's own thread
Rom Update (2012 May 06)
1) Latest CM9 fixes... including theme manager! (but no themes, yet)
Rom Update (2012 May 09)
1) Latest CM9 fixes
Rom Update (2012 May 12)
1) Latest CM9 Fixes (sorry, nothing big this update, busy)
2) Also packaged latest DFK in zip
3) DO NOT USE FXP KERNEL WITH THIS ROM, I HAD MASSIVE FC ISSUES.
Rom Update (2012 June 6)
1) Been a little while hasn't it
2) Latest CM9 fixes
3) Kernel included was built from source as part of CM's new "inline kernel building" (FXP's kernel)
As Brainard52 Suggested,
Resources:
HOW TO FLASH A KERNEL:
1) Download a working kernel for CM9 (it's in download links, included with FXP zip & stand-alone (will be fixed next update))
2) extract kernel from where ever you downloaded it to where ever fastboot is (unless you add fastboot to $path in windows or /bin||/usr/bin||etc in linux)
3) type the following command "fastboot -i 0x0fce flash boot <name of boot.img>
4) NEVER FLASH RECOVERY.IMG.
Linux users:
If you create a file, 51.android.rules, put this in it
Code:
SUBSYSTEM=="usb", ATTR(idVendor)=="0fce", mode=="0666", GROUP="plugdev",
chmod it to 644 (r+w) & copy it to /etc/udev/rules.d/ you never need to use -i again! (for your play)
Links:
Flashtool:
http://forum.xda-developers.com/showthread.php?t=1351299
Original FXP Thread:
http://forum.xda-developers.com/showthread.php?t=1447542
Team Darkforest CM9 Kernel:
http://forum.xda-developers.com/showthread.php?t=1541482
Recovery:
http://forum.xda-developers.com/showthread.php?t=1130639
In case you want to try out building from source, read this link:
http://forum.xda-developers.com/showthread.php?t=1556971
Note: KeiranFTW forgets one major thing in his post, he assumes that somebody will only do it once! If you plan on doing it more than once, then for every git clone you do (msm-7x30, zeus, zeus-common in device/semc/ & vendor/semc/) you should go through and do a git pull everytime you wanna rebuild source (knowing Keiran, he probably just made a script for it )
If you want to build a kernel from source download this text file:
Kernel Tutorial! (Note: In it I use FXP sources, if you wanna Doom/Keiran just change the git url inside to their kernel sources)
Courtesy of CrimsonKnight13, Here is a list of apps that are a good addition to CM9
CrimsonKnight13 said:
Here's my list of preferred apps over stock CM9/ICS
ConnectBot > Terminal Emulator
Dolphin Browser HD (newest has an ICS-ish look) > Browser (Chrome)
exDialer w/ ICS Theme AC > Phone
Play Music > Music
SuperSU > Superuser
APEX Launcher > Trebuchet
Swiftkey 3 Beta (has a very ICS look) > Default keyboard
OpenExplorer Beta > File Explorer (from any ICS/CM9 iteration)
Alarm Clock Plus > Clock
Click to expand...
Click to collapse
I'm adding a poll on top to see what people want included. If an app is a paid app, then don't even think about asking for it to be added.
LOGCAT
For future reference, I'm going to include here how to use logcat (android debugging tool.)
There are two main ways to do a logcat, within android and through adb.
Logcat within android can be installed by a logcat app:
Two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging.
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you search for an error in the logcat file (it's always e/ for error, f/ for fatal. those are the two main things that matter to me.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService( 203): flags <[down]>
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under <manifest>: supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
How this relates to xLoud. (or any other problem we have with future updates.)
Now, since xLoud is apparently causing all sorts of havoc including not granting root , screwing up volume & messing with equalizers, a logcat done the following way will help me immensely with figuring out how to go about fixing it:
Code:
adb logcat *:E -v long > name of problem.txt
will print out all errors, fatal exceptions (what causes android to crash) that happen with the xLoud (or any other risky) update.
my email (for sending me logcats): [email protected]
Complaints, requests for add-ons, stupid questions, or anything else I feel like will be deleted upon receiving it. Logcats will not.
(If you wanna complain, request something or ask a stupid questions, that's why this thread is here)
Regarding Nightlies:
UPDATE:
Everybody: Head on over here -- http://forum.xda-developers.com/show....php?t=1661091
It's the nightly build for R800
Pax
Click to expand...
Click to collapse
UPDATE: Here is an update.zip file to automatically change any CM9 (AOSP ICS) based R800i download to work with the R800x (all thanks to KeiranFTW & Atarii for the fix)
saved for future use
Very nice.
Is the minmax governor in your kernel?
CrimsonKnight13 said:
Very nice.
Is the minmax governor in your kernel?
Click to expand...
Click to collapse
No, I have not messed with the kernel yet, after I get all the kinks out of my builds, I might start working with the kernel source.
Pax
paxChristos said:
No, I have not messed with the kernel yet, after I get all the kinks out of my builds, I might start working with the kernel source.
Pax
Click to expand...
Click to collapse
Your ROM & kernel will be my templates for my own. Finding time will be the issue...
Bluetooth Media Audio is also broken. Connects to phone audio fine, but media audio plays out of phone speakers.
EDIT: MMS does work as long as the verizon APN is set. I think Chevy includes it as part of his package, because I haven't had to manually set it since 112.
crono141 said:
Bluetooth Media Audio is also broken. Connects to phone audio fine, but media audio plays out of phone speakers.
Click to expand...
Click to collapse
Indeed, I confirmed this in the GSM CM9 Thread. I was watching my logcat as I connected my headphones up, you get a message from the AudioManager during the BT setup that it is changing things and routing audio to the speaker, which is clearly wrong.
It's coming from two separate processes though, so I gotta dust off my regex skillz to write a regex that'll pull in the messages from the BT process and the AudioManager process.
Whohoo! Welcome everyone! Anything cm9 cdma related put here instead of the fxp thread from now on since they won't pick us up for about another few months or so. Other then the obvious common sense things like being decent and patient with each other, it's time to bang our heads together and make our plays eat some ics!
Will be installing right now. Will let you know what I find (if anything)
ohh i know, get xloud working so i can actually hear my phone ring and notification sounds play and alarm go off. ^_^
DoomLoRD's ICS Beta DooMKerneL works with FXP, if you flash his wifi modules and run this command at boot: "insmod /system/lib/modules/bcm4329.ko"
Thanks to chevyowner for that command, I'd have never figured that out.
And if you want to have deep sleep, don't run that command to activate the wifi until you need it. I don't use wifi much, so I've got mine set up as a script in Rom Toolbox. When I need wifi, I run the script, then when I'm finished with wifi, I reboot.
{
"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"
}
A couple of things to mention here, since this is the ALL NEW FXP CDMA Thread !!!
You may recall I reported a problem with PACMAN for Xperia PLAY where it shows up in the market as incompatible, and it won't manually install from my backup of the apk. I have concluded this is definitely a compatibility issue with CM and possibly something needs added or edited in the build.prop to resolve it. I'm no dev, but I'll try to figure this out and get it working, which may also resolve some of the other so-called incompatible app issues.
Second item of note: The caps lock does not work in the standard keyboard. Normally you can click it twice to lock caps in, but not in CM9.
Third - well, there was a third, but now I've forgotten what it was, so I'll add it later!
10 char...
(xda emailed me your earlier post, I'll respond to that.)
FXP will always say FXP in the title, mine will have a date, both well be signed, just not in the title...
Sent from my R800x using Tapatalk
paxChristos said:
(xda emailed me your earlier post, I'll respond to that.)
FXP will always say FXP in the title, mine will have a date, both well be signed, just not in the title...
Sent from my R800x using Tapatalk
Click to expand...
Click to collapse
I swear I read your post about 10 times, I didn't read that part till the 11th
I am an idiot and I need help.I just unlocked tonight and afterwards I downloaded this,transfered to sd and attempted to install.It said the usual and hung at installing update.I did a battery pull(Im an idiot)and when I attempted to get into recovery I am froze at Sony screen.Suggestions?I am very new to the Play.
netizenmt said:
A couple of things to mention here, since this is the ALL NEW FXP CDMA Thread !!!
You may recall I reported a problem with PACMAN for Xperia PLAY where it shows up in the market as incompatible, and it won't manually install from my backup of the apk. I have concluded this is definitely a compatibility issue with CM and possibly something needs added or edited in the build.prop to resolve it. I'm no dev, but I'll try to figure this out and get it working, which may also resolve some of the other so-called incompatible app issues.
Second item of note: The caps lock does not work in the standard keyboard. Normally you can click it twice to lock caps in, but not in CM9.
Third - well, there was a third, but now I've forgotten what it was, so I'll add it later!
Click to expand...
Click to collapse
The real question is has ANYONE been able to install/launch Pacman in ICS on the Play? Perhaps it is a compatibility issue with the game itself that needs an update from Namco in order to support ICS? I think that is more likely...
Taken that in reverse, GTA III will not install in GB, but allows me to install fine in ICS
bob24260 said:
I am an idiot and I need help.I just unlocked tonight and afterwards I downloaded this,transfered to sd and attempted to install.It said the usual and hung at installing update.I did a battery pull(Im an idiot)and when I attempted to get into recovery I am froze at Sony screen.Suggestions?I am very new to the Play.
Click to expand...
Click to collapse
did you flash a kernel? (fastboot -i 0x0fce flash boot boot.img)
Spam the back button upon boot (it might be the volume rocker, I'm not 100% sure)
That should get you into recovery.
Sent from my R800x using Tapatalk
I tried like crazyto get into recovery via volume down which is how i got in before unlocking.I am very new to play and I am absolutely bummed that i have a new brick
---------- Post added at 01:31 AM ---------- Previous post was at 01:30 AM ----------
I was installing via sd just as the post said and when it hung I did a battery pull
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
I have fastboot up.Is there a command you could show me how to run that would help?
---------- Post added at 01:34 AM ---------- Previous post was at 01:32 AM ----------
I appreciate any help given.I feel like such an idiot
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
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.
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.
Testing ROM for Dell Venue 8 3830 (LineageOS 14.1)
Most of resources are available. But has some bugs.
It could be used for fun (Retroarch, E-book readers, etc)
Was build using as base Asus T00F lineage source files
I'm posting here asking for help to implement/fix missing features (if anyone still interested on such old device)
All source code to build is available on github (links bellow).
Working
Boots
Display
Touchscreen
Wi-FI
Virtual Navigation Buttons
Sound
Rotation
Bluetooth (since 2023-05-10)
Not working:
Camera
Known issues:
- ARM apps not working due mismatches with libraries (Houdini)
- Observed battery is draining quicker than expected.
# Testing Image (should be flash using FASTBOOT)
# updated 2023-06-13
# WARNING: MAY BRICK YOUR DEVICE PERMANENTLY! USE AT YOUR OWN RISK!!!!
https://drive.google.com/drive/folders/16iG6I-X83USPGPR13yUbg54S3Mn0Y7Ff?usp=share_link
Boot tablet in fastboot mode (volume down + Power) and use "flash_cmds.sh" (Linux) / "flash_cmds.bat" (Windows) to flash files through fastboot (note that proper driver drivers and fastboot must be installed)
If you wish to submit cmds manually:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase config
fastboot erase data
fastboot erase logs
fastboot erase factory
fastboot oem stop_partitioning
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system_img.img.gz
Source Files
# LOCAL MANIFEST
GitHub - pstglia/local_manifests at DELL_VENUE_LOS_14.1
Contribute to pstglia/local_manifests development by creating an account on GitHub.
github.com
Init a NEW repo
(repo init -u https://github.com/LineageOS/android.git -b cm-14.1)
Copy local manifest to .repo/local_manifests and sync it.
repo sync -c --no-tags --no-clone-bundle -j$(nproc --all)
# Kernel
GitHub - pstglia/linux: Linux kernel source tree
Linux kernel source tree. Contribute to pstglia/linux development by creating an account on GitHub.
github.com
NOTE: must be build using gcc 4.7 [1]. Checkout commit c7931763d41be602407ed9d71e2c0292c6597e00, update prebuilts link to this gcc
and build using kernel_build.sh script. If everything goes as expected, You'll have a new_boot.img created
# device/dell/P801_NoModem
GitHub - pstglia/android_device_dell_P801_NoModem: general device configuration for Dell Venue 8 (P801_NoModem)
general device configuration for Dell Venue 8 (P801_NoModem) - GitHub - pstglia/android_device_dell_P801_NoModem: general device configuration for Dell Venue 8 (P801_NoModem)
github.com
# vendor/dell/P801_NoModem
GitHub - pstglia/android_vendor_dell_P801_NoModem: Vendor files (configs, libs, etc)
Vendor files (configs, libs, etc). Contribute to pstglia/android_vendor_dell_P801_NoModem development by creating an account on GitHub.
github.com
# hardware/libaudio
GitHub - pstglia/hardware-libaudio at DELL_VENUE_LOS_14.1
hardware/libaudio repo (forked from Android-x86.org) - GitHub - pstglia/hardware-libaudio at DELL_VENUE_LOS_14.1
github.com
# external/boringssl
GitHub - pstglia/android_external_boringssl: Boring ssl (libcrypto & friends)
Boring ssl (libcrypto & friends). Contribute to pstglia/android_external_boringssl development by creating an account on GitHub.
github.com
# system/core
GitHub - pstglia/system-core at DELL_VENUE_LOS_14.1
system/core repo (forked from Android-x86.org). Contribute to pstglia/system-core development by creating an account on GitHub.
github.com
# external/tinyalsa
GitHub - pstglia/android_external_tinyalsa: tinyalsa 1.0.2
tinyalsa 1.0.2. Contribute to pstglia/android_external_tinyalsa development by creating an account on GitHub.
github.com
# external/icu
https://github.com/pstglia/android_external_icu/tree/DELL_VENUE_LOS_14.1
# external/external/apache-http
GitHub - pstglia/android_external_apache-http: android_external_apache-http
android_external_apache-http. Contribute to pstglia/android_external_apache-http development by creating an account on GitHub.
github.com
NOTES:- openssl 3.0 (Mint 21.1 - Vera) will not generate a compatible x509 sign key for kernel modules.
OpenSSL 1.1.1f generates an accepted key
Credits / Thanks:
- The LineageOS Team
- Android-x86 Team / Chih-Wei Huang for the amazing project and repositories (used one of them here so far)
- vampirefo for providing CWM recovery and valuable information
- Social-Design-Concepts for providing unlocked firmwares (required to boot custom Image)
- Fabio Júnior Chaves da Silva (again, owner of this tablet)
- Dell for providing kernel source (wouldn't hurt to include some AOSP code also, but it's better than nothing )
- AlaskaLinuxUser AKLU from Youtube. Lot's of explanations about Android & Lineage.
[1] - https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.7/
How can one Help?
ikram.senguen said:
How can one Help?
Click to expand...
Click to collapse
Hi,
This is the list of missing features / issues:
Choose one of your preference and hands on!
update 2022-05-31: Audio and Rotation were fixed.
kernel display driver was updated. Experience is smoother
-[FIXED] Wi-fi is not working:
Help wanted: Fix code and make it work:
Status so far: Fixed.
It will work on boot if you keep it enabled. If you disable Wi-fi from settings and try to re-enable (or switch on/off airplane mode), it will stop working until you boot it again.
update 2022-06-02: Discovered that you can't ioctl wlan0 to up state when you disable it (using root + proper capabilities).
However, if you rmmod bcm4330 and insmod it again, you can enable it.
It seems a driver issue.
update 2022-06-03: Using stock kernel module for network, no issues with ioctl after disbling wi-fi
update 2023-06-13: Using T00F bcmdhd source with some changes to enable 4330, it runs ok.Now it's using compiled drivers for wi-fi instead of stock ones (except for firmwares)
-[FIXED] Sound is not working:
Help wanted: Investigate what's wrong and fix it
Status: Fixed [working since updated 2022-05-29]
Note: libaudio from stock image couldn't be loaded, so generated one from Android-x86 libaudio code (see [2]).
Maybe adjusts are needed on source, config and Boardconfig files.
update 2022-05-22: all libs are being loaded, but there are some errors when trying to load codecs. Config files must be checked (as well libs);
- [FIXED] Navigation menu is not being displayed:
Help wanted: Discover why is not being shown and fix it
Status: Fixed (created a overlay on device tree and made "def_force_show_navbar" to be enabled - see commit 8768b512c08b5fc60a7d7674ffce7c3a23a7857a)
- Camera is not working:
Help wanted: Make it work
Status so far: HALs must be copied. Possibly lot's of shims and Voodoos/Mojos required.
- [FIXED] Sensors are not working:
Help wanted: Make it work
Status: Fixed (replaced sensor_hal_config files)
- [FIXED] Bluetooth is not working:
Help wanted: Make it work
Status do far: Fixed (used harware/broadcom/libbt instead of vendor lib)
- [FIXED] Port/Enable zram to kernel:
Help wanted: Porting
Status: Enabled from stage tree (it was there all the time).
Seems to be working (at least swap was mounted using it)
- [FIXED] Sometimes backlight doesn't light up after resume
Status: Fixed. This ocurred when an out of range bright level was used ( > 100)
Edited liblights code (device/dell/P801_NoModem/liblights) and included a small check to ensure/force valid values ( from 0 to 100)
- [FIXED] ADB only works using network. Not working using USB
Status: Fixed. Copied drivers/usb/gadget changes from T00F Asus kernel and applied to Venue kernel
- Elevated Battery draining (specially on suspend attempt)
Something is blocking system from suspend. If you check dmesg, it keeps an infinite loop of suspend process (disable tasks, disable CPU's) and abort.
At first, wakeup reason is the "misterious" NETLINK. However, even blocking it and some other wakeup_sources it wakes.
This shows suspend backtrace (got from dump_stack):
Code:
[ 697.149972] Call Trace:
[ 697.149984] [<c19f90f3>] dump_stack+0x16/0x18
[ 697.149990] [<c12bc9c1>] resume_irqs+0xa1/0xe0
[ 697.149996] [<c12bca2f>] resume_device_irqs+0xf/0x20
[ 697.150004] [<c156a151>] dpm_resume_noirq+0x1a1/0x2b0
[ 697.150010] [<c156a8d0>] dpm_resume_start+0x10/0x20
[ 697.150015] [<c1288945>] suspend_enter+0xa5/0x260
[ 697.150022] [<c1a03cbd>] ? sub_preempt_count+0x3d/0x50
[ 697.150028] [<c1a03cbd>] ? sub_preempt_count+0x3d/0x50
[ 697.150034] [<c19f4646>] ? printk+0x3d/0x3f
[ 697.150040] [<c1569adc>] ? dpm_show_time+0xbc/0xf0
[ 697.150046] [<c156b952>] ? dpm_suspend+0x132/0x1e0
[ 697.150052] [<c1288baf>] suspend_devices_and_enter+0xaf/0x220
[ 697.150057] [<c1288fb8>] pm_suspend+0x298/0x300
[ 697.150063] [<c1289935>] try_to_suspend+0xa5/0xc0
[ 697.150069] [<c1a0091d>] ? _raw_spin_unlock_irq+0x1d/0x40
[ 697.150076] [<c125ebad>] process_one_work+0x11d/0x3d0
[ 697.150082] [<c14b091e>] ? __delay+0xe/0x10
[ 697.150088] [<c125f239>] worker_thread+0xf9/0x320
[ 697.150093] [<c1a00966>] ? _raw_spin_unlock_irqrestore+0x26/0x50
[ 697.150099] [<c125f140>] ? rescuer_thread+0x2b0/0x2b0
[ 697.150104] [<c1264cf4>] kthread+0x94/0xa0
[ 697.150112] [<c1a07077>] ret_from_kernel_thread+0x1b/0x28
[ 697.150117] [<c1264c60>] ? kthread_create_on_node+0xc0/0xc0
[ 697.150121] Wakeup from IRQ 32 penwell_otg
/sys/kernel/debug/mid_pmu_states and other files can give hints about the root cause.
Anyway, if you want to adventure yourself on trying to solve the problem, be my guest
[1] - https://github.com/pstglia/linux/tree/DELL_VENUE_LOS_14.1/modules/wlan/PRIVATE/bcm43xx
[2] - https://github.com/pstglia/hardware-libaudio/tree/DELL_VENUE_LOS_14.1
Additional info for those interested on improve this:
1) Added a debug service that collects dmesg & logcat 3 times every boot
output is recorded on /data/log_debug_venue8_3030.txt
2) ADB from usb cable is not working, but is working from network. This way, I suggest you enable these on "Developer options":
- Root acess: Select "ADB only".
- Android debugging
- ADB over network (note: You must connect to a network prior - IP and port will be displayed when enabling this option)
Once done, from PC, you can connect to adb:
# (will connect to tablet)
adb connect TABLET_IP_ADDR
# (will restart adbd on tablet, to root mode)
adb root
# (will connect again, now with root acess)
adb connect TABLET_IP_ADDR
Click to expand...
Click to collapse
3) If you want to make any change to /system on living image, you must remount /system with write privileges:
- Ensure you enabled adb over network as described on step 2
- connect to table and remount /system:
adb shell
mount -o rw,remount /system
Click to expand...
Click to collapse
How difficult would it be to port to the 7840? Or alternatively, would it be possible to help me learn how I could build it myself?
theabnormalguy said:
How difficult would it be to port to the 7840? Or alternatively, would it be possible to help me learn how I could build it myself?
Click to expand...
Click to collapse
Hi,
It has a medium/high level of difficult, depending how "perfect" do you want your port.
And more than difficult, it's *extremelly* time consuming. You must be prepared to spent weeks/ months in order to try to make something work.
And before starting anything, be sure is viable. A crucial point is having kernel source files for your device.
without it, don't waste your time.
In your case, take a look at opensource.dell.com
Learning: As a start, I'd recomend you to watch these videos:
https://www.youtube.com/c/AlaskaLinuxUserAKLU/playlists
You'll need to learn all of these (not limited to):
- Learn some C/C++ and java. You'll have to read source code to understand basicallyhow it works
- Learn Unix/Linux terminal commands. I'll need lots of find, grep, cd, cat, etc....
- Learn shell script
- Learn git
- Learn how to compile and cusomize a kernel
- Understand how Android source code/components are strutured (AOSP)
During your development, you'll need to carefully look at log files, include debugging info on scripts/codes, think,research, deduce, test, retest, test again,back some steps an try new appoaches.
And finally, I won't be working on any other device. After finishing this one I'm working on (or giving it up), not going to waste my time on custom roms sonner.... I have a life to live
Good luck
Project die?
FYA_EXel said:
Project die?
Click to expand...
Click to collapse
Not yet. I'm just looking for courage to go on.
If you see courage nearby, tell her that I'm looking for her
I intent to make bluetooth work and improve battery life. Camera is not a priority.
Remember everyone that source code is available. Everyone is free and invited to help improving this image.
Regards
pstglia
When I flash this rom, I get to the Lock Screen and it hard freezes. Anyone else get this problem? Thanks for all your work @pstglia
Update: I fixed it by wiping the data partition. This is incredible; this tablet has never been so smooth. Any advice on adding GAPPs?
the_Victorian said:
When I flash this rom, I get to the Lock Screen and it hard freezes. Anyone else get this problem? Thanks for all your work @pstglia
Click to expand...
Click to collapse
You are able to boot it but when locking screen you can't return to operation, having to boot it again.
Is this your issue?
If so, it's a known issue where backlight bright level goes to zero. If you blindly move the bright slider, you can have image again (or changing bright values bellow /sys using adb)
pstglia said:
You are able to boot it but when locking screen you can't return to operation, having to boot it again.
Is this your issue?
If so, it's a known issue where backlight bright level goes to zero. If you blindly move the bright slider, you can have image again (or changing bright values bellow /sys using adb)
Click to expand...
Click to collapse
Wow, thanks for your quick reply! I was just dumb and didn't wipe my android 4.4 data before installing; that fixed it. I have been tinkering trying to get GAPPs installed but run into error 70 in CWM when I do. Have you had success?
the_Victorian said:
Wow, thanks for your quick reply! I was just dumb and didn't wipe my android 4.4 data before installing; that fixed it. I have been tinkering trying to get GAPPs installed but run into error 70 in CWM when I do. Have you had success?
Click to expand...
Click to collapse
I have installed opengapps (x86, 7.1, pico). Don't remember having issues installing it.
But makes tablet really slow most of time.
pstglia said:
I have installed opengapps (x86, 7.1, pico). Don't remember having issues installing it.
But makes tablet really slow most of time.
Click to expand...
Click to collapse
Hmm that's interesting. I'm trying the same file but every recovery I try has given me error 7. Will continue tinkering. Something to do with system mount permissions maybe?
the_Victorian said:
Hmm that's interesting. I'm trying the same file but every recovery I try has given me error 7. Will continue tinkering. Something to do with system mount permissions maybe?
Click to expand...
Click to collapse
Afaik error 7 means package doesn't match the device. On Lineage images I bypass it by editing update-binary/updater-script inside META dir.
However I think opengapps does not perform these checks...
Have you tried formatting your cache partition before applying opengapps package?
Which recovery version are you using? Is the thethered one from SDC/Vampirefo?
I thought this moment would never come , I always dreamed of a custom rom for this device, I hope you can continue developing it
quevon24 said:
I thought this moment would never come , I always dreamed of a custom rom for this device, I hope you can continue developing it
Click to expand...
Click to collapse
Hi, I'll try to. But my limited knowledge doesn't allow me to advance the way I wish.
So, do not expect something perfect, fast and stable...
If we had some developer that could help on this, maybe you could have a really nice rom.
Note: All sources are available on github. See 1st post.
If I achieve some progress I'll share here.
The image I have is bootable and you can test anything if you understand the risks of potentially brick your device.
If you have nothing to lose, give a try
pstglia said:
Hi, I'll try to. But my limited knowledge doesn't allow me to advance the way I wish.
So, do not expect something perfect, fast and stable...
If we had some developer that could help on this, maybe you could have a really nice rom.
Note: All sources are available on github. See 1st post.
If I achieve some progress I'll share here.
The image I have is bootable and you can test anything if you understand the risks of potentially brick your device.
If you have nothing to lose, give a try
Click to expand...
Click to collapse
I just install the rom using Windows 11, i have the stock rom(android 4.2.2, 4.3 and 4.4.2) in case i brick the tablet.
I used apkmirror to install chrome x86 version, i can't use youtube because the lack of google play services
quevon24 said:
I just install the rom using Windows 11, i have the stock rom(android 4.2.2, 4.3 and 4.4.2) in case i brick the tablet.
I used apkmirror to install chrome x86 version, i can't use youtube because the lack of google play services
Click to expand...
Click to collapse
You can use opengapps for youtube & google stufff.
But at the current stage of this rom, it will make tablet really slow...
pstglia said:
Hi,
This is the list of missing features / issues:
Choose one of your preference and hands on!
update 2022-05-31: Audio and Rotation were fixed.
kernel display driver was updated. Experience is smoother
-[FIXED] Wi-fi is not working:
Help wanted: Fix code and make it work:
Status so far: Fixed.
It will work on boot if you keep it enabled. If you disable Wi-fi from settings and try to re-enable (or switch on/off airplane mode), it will stop working until you boot it again.
update 2022-06-02: Discovered that you can't ioctl wlan0 to up state when you disable it (using root + proper capabilities).
However, if you rmmod bcm4330 and insmod it again, you can enable it.
It seems a driver issue.
update 2022-06-03: Using stock kernel module for network, no issues with ioctl after disbling wi-fi
-[FIXED] Sound is not working:
Help wanted: Investigate what's wrong and fix it
Status: Fixed [working since updated 2022-05-29]
Note: libaudio from stock image couldn't be loaded, so generated one from Android-x86 libaudio code (see [2]).
Maybe adjusts are needed on source, config and Boardconfig files.
update 2022-05-22: all libs are being loaded, but there are some errors when trying to load codecs. Config files must be checked (as well libs);
- [FIXED] Navigation menu is not being displayed:
Help wanted: Discover why is not being shown and fix it
Status: Fixed (created a overlay on device tree and made "def_force_show_navbar" to be enabled - see commit 8768b512c08b5fc60a7d7674ffce7c3a23a7857a)
- Camera is not working:
Help wanted: Make it work
Status so far: HALs must be copied. Possibly lot's of shims and Voodoos/Mojos required.
- [FIXED] Sensors are not working:
Help wanted: Make it work
Status: Fixed (replaced sensor_hal_config files)
- [FIXED] Bluetooth is not working:
Help wanted: Make it work
Status do far: Fixed (used harware/broadcom/libbt instead of vendor lib)
- [FIXED] Port/Enable zram to kernel:
Help wanted: Porting
Status: Enabled from stage tree (it was there all the time).
Seems to be working (at least swap was mounted using it)
[1] - https://github.com/pstglia/linux/tree/DELL_VENUE_LOS_14.1/modules/wlan/PRIVATE/bcm43xx
[2] - https://github.com/pstglia/hardware-libaudio/tree/DELL_VENUE_LOS_14.1
Click to expand...
Click to collapse
sry, lack of response due to lack of knowledge: thought this is about Venue 7840
ikram.senguen said:
sry, lack of response due to lack of knowledge: thought this is about Venue 7840
Click to expand...
Click to collapse
Nope, this is for Venue 8 3830