Related
Please stay ON TOPIC to kernel DEV and missing code. Don't report every bug the Android build your using is having or it will be deleted as OFF TOPIC
As you all might be knowing that hd2 is pretty much a android native device now. Its just like any another snapdragon device. The current kernel code we are using in HD2 is pretty obsolete and missing a lot of things. It more like something working at its minimal efficiency. While i was porting over all the HD2 board files getting it on par with the other snapdragon devices I found out a lot of code was missing and some was obsolete. Eg. The gsensor code from microp was pretty minimal, a lot of things were missing in microp code. I suspect that it isnt the only code, a lot of bluetooth related stuff was missing and much more. I am not really gonna work on backporting the stuff to .32 kernel so i would like the kernel devs here to backport the stuff to the .32 kernel so a lot of bugs can be fixed and stuff can be made more stable until the .37 kernel is ready. All the commits can be found here
https://github.com/charansingh/cm-kernel/tree/master
There might be some bravo or passion instances in there cuz i am comparing the code with these two devices and taking what is necessary and sometimes i have to leave my work due to some other work and forget which file i was working on so would appreciate the more bugs.
Also Mods can we get this a sticky so we can track the progress here
Yap.. i'm not a really pro developer but i suspected those bugs before.. finally a real developer suspected that.. eager to see who's going to help fixing them
charnsingh_online said:
Also Mods can we get this a sticky so we can track the progress here
Click to expand...
Click to collapse
Ok sticky for the moment to see if it helps.
@charnsingh_online
I am really happy that you put so much power in this project big respect for that.
The reason for the missing code is because most of the drivers are reversed engineerd from winmo by cotulla. Wich make it possible to make working android parts but they don't work optimal by that. Also we miss some skilled active coders. After cotulla almost everything is created by markinus he did a incredible part big credit to him but looks like he isn't that active anymore..
Current development are mostly little things a guy who sees a little part from that and a little part from that like : you, tytung, darkstone, gauner,letama, the guy from the bluetooth fix.
We probaly don't have so much real kernel programmers because they buy a native linux / android phone.
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
memin1857 said:
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
Click to expand...
Click to collapse
actually i think the gpu drivers are kinda unstable when comparing to the performance of other phones that carry the similar gpu...
@charnsingh_online
Good start.
After reading the github commits, I still don't understand what kernel devs can do so far.
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
hi charansingh,
i am willing to help, but i think it would be helpfull to define packets to take over.
By looking in the kernelsources it looks good to me, but i know from own expiriences with porting that i have to look deep...
best regards
trilu
charnsingh_online said:
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
Click to expand...
Click to collapse
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Ok I'll do it tomorrow n also maintain the list in the op
I may be wrong, but this thread is not supposed to become a bug fix request thread. It is aimed at developpers, so that they collaborate on a merging of HD2 specific stuff onto a cyanogen 2.6.37 kernel...
This would most likely result in the resolution of a lot of our issues, but in the mean time, [DEV] in the thread title means it is for devs only......
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
I looked pushed code and it's ok, at least for first few commits. But it needs some deep cleaning an optimization, also there is some bravo naming convention used in leo specific files. You should put this tree on gitorious so we can do more work on it, but anyway i will clone tree and do some cleaning and porting new stuff.
This could be of interest, and not too much off-topic.
This kernel: http://forum.xda-developers.com/showthread.php?t=966786
is being abandoned and it had some patches for performance that I think are valuable. It had linpack scores that can be achieved only with heavy overclocks on other kernels... The problem is, the source is being distributed by a .zip, no commits, nothing... the only way to get those would be to issue a diff with... something and guess where they are. Staying on topic, I've already adapted cm-kernel for another device so I think I'll be able to help when I get enough free time to spare.
D4rk50ul said:
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
Click to expand...
Click to collapse
Yes you are right. Unfortunately many threads like this one get's filled with off topic chatter, complaints etc. I will try to keep my eye on this thread so the dev's can communicate. If your not contributing to the DEV work on the HD2 kernel's, please don't post your wishes and thanks post as this will quickly clog up the thread. I'd hate to lose progress due to this. That's why many DEV's end up not using XDA and reverting to IRC only. Thanks
noellenchris
Hi,
Few days back there are some conversation about libsurfaceflinger.so for color banding issue http://forum.xda-developers.com/showthread.php?t=1012278 . Since Rom is changing continuesly with libs can we port the change for color issue.
HD2 GB-2.33-SENSE-2.1 LOCKSCREEN SENSE-3
tytung said:
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Click to expand...
Click to collapse
tytung, has any1 of you done so? please let us know..
g30rg10u said:
tytung, has any1 of you done so? please let us know..
Click to expand...
Click to collapse
No, I didn't work on 2.6.37 kernel so far.
I didn't see that charnsingh_online added a TODO list in the OP.
Fried my laptop charger. New one on way. Hd2 arrived
FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's Changelog:
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse
Layman's Changelog
(As in, the changelog I wrote )
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually. See Detule's post on this topic.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup
Caveats:
BT - works now! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
NOTE: BT must be disabled in WinMo before booting Android or else you'll run into all sorts of odd issues...
WEP on wifi doesn't work. I heard an app called 'wifi-ace' (on the Market) fixes WEP!
If auto-brightness is enabled, the keyboard/button lights will fail at random. See this post for more scant details .
Yay! No more "when is FRX07 coming out?" posts!
highlandsun said:
Yay! No more "when is FRX07 coming out?" posts!
Click to expand...
Click to collapse
And to that effect, I would like to personally apologize to everyone for how long it took. Life has been crazy busy the past couple months. Hopefully we'll get GRX01 out in a more timely manner.
Woooohooooo!!! Thanks to all of the dev's on this, Stine, Hyc, Emwe, Arrrghhh (for putting up with all the BS!), and anyone else involved.
Can't wait to try this out. Thanks to all who contributed =)
highlandsun said:
Yay! No more "when is FRX07 coming out?" posts!
Click to expand...
Click to collapse
Just to get a sense of things, is it too soon for a "when is FRX08 coming out" post?
Diam 500 endlessly repeats smd-tty buffer mismatch on first boot (same as last 2? Kernels). Thanks for your work on this aargh and xda team.
Sent from my LG-P999 using Tapatalk
bluenote73 said:
Diam 500 endlessly repeats smd-tty buffer mismatch on first boot (same as last 2? Kernels). Thanks for your work on this aargh and xda team.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Ah yea... I need to test this on a RAPH800 I just got my hands on, thanks for reminding me!
Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?
wmg316 said:
Quick question. Prior to right now I've been running Hyc's 5/30 build very successfully and very happily. With that build, sound was working when recording a video. With the new FRX07, no sound comes when recording a video. Any ideas on how to get the sound to work with recording video on FRX07?
Click to expand...
Click to collapse
His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...
arrrghhh said:
His build has the new acoustic code seen here. It routes audio in a much better fashion, for sure... but it's not stable. Still needs some work, so it's not in FRX07...
Click to expand...
Click to collapse
Thank you sir!
Big thanks to every one on the dev team for FRX07. You guys are awesome.
Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.
"Error reading file. Expected 4096 got 0"
Anyone know what it means? Search did not turn up many useful hits.
webxplore said:
Big thanks to every one on the dev team for FRX07. You guys are awesome.
Just extracted FRX07 on to a newly formatted sdcard, copied startup & calib from FRX06 and when I launch haret, i get the following error.
"Error reading file. Expected 4096 got 0"
Anyone know what it means? Search did not turn up many useful hits.
Click to expand...
Click to collapse
Figured out...Had a corrupt zimage file. Able to launch now.
After a few hours of testing, great job!
The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!
The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?
I also love the recent apps on end long press, fancy
First Impressions
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.
I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.
The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.
I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while
EDIT: Figured I'd list what is and isn't working for me. Again, I'm using all the default components like kernel and whatnot on the Tilt2 and have the phone overclocked to 710.400MHz now:
WiFi - Works
Data - Works (most stable I've experienced)
Bluetooth - Works (haven't tried headset)
WiFi HotSpot - Buggy; Turns on, but disabling keeps the notification icon and enabling again causes reboot. Different kernel doesn't fix.
USB Tethering - Works/Turns On (Don't have the driver to test quite yet )
Camera/Camcorder - Works (Camcorder doesn't record sound.. known issue?)
Phone - Works flawlessly
MMS - Incoming/Outgoing Works
maff1989 said:
Coming from FroyoB Hercules, this is a step up in my opinion. A HUGE step up.
I am running the Tilt2 with a 2GB Class 2 SD card and the provided FRX07 package .zip.
The build is running smooth and silky (making me have more faith in looped builds heh heh) with slight overclocking (633.600MHz). Had one hot reboot while accessing the Notification bar at the same time Market was updating Google apps, but after that the updates proceeded without issue. Everything else has yet to be tested, but I'm sure I won't run into anything major.
I'm 110% satisfied running the build. Accessing menus is quick and not laggy at all. To me, that's what's important: user functionality. You guys nailed it big time, and for that I thank you all very much. I won't be using CWM for a looong while
Click to expand...
Click to collapse
+1
Come from FroyoB Hercules v2.
Any possible to run FRX07 on CWM?
FRX07 on cwm is being worked on by Eodun,wich sadly yesterday released FRX06 for cwm
rtrip said:
After a few hours of testing, great job!
The battery status actually tracks really close to where windows mobile says it should be. It also seems to go to sleep, and stay sleeping!
The only thing that's keeping me from using it full time is the phone and speaker phone have noticeable static that windows mobile doesn't have. Does the beta audio routing fix this, or are there some new settings I can try?
I also love the recent apps on end long press, fancy
Click to expand...
Click to collapse
I would bet that the new audio routing stuff fixes the static problems. It definitely cleaned things up for me. But at this point I think we need a newer kernel in addition to the new audio libraries, the stuff in that audio routing thread is rather out of date at the moment.
I've been running most of this stuff for more than a month without issues. It's definitely going to be a lot more solid than any previous builds...
In celebration of almost 1/2 a MILLION BOCA Downloads!
I proudly present the XDA release of:
The SGT7's *original & first GSM CM9 port:
>click pic to begin<
or; http://magrathearoms.weebly.com/
image created by supagforce
*first icedBOCA went out to testers 11/30 in heimdall form. V2 went out: 12/16
Original in no way describes quality of performance or relate to updates or features.
First relates to public availability.
if my timeline is wrong, please pm.
FEATURES
Partial addition list:
*Added CombinedBar (statusbar) Auto on/off, upon fullscreen option.
*Fixed SystemUI FC when disabling Notifications
*Additional options and toggles
*Improved caller id.
*Car charging
*Touch outside a notification window to shove to background. Without halting install actions! Really helps with installing multiple side loaded apps. You don't have to wait for each to finish.
*contacts picture and name fix for incomming/outgoing calls
*6 new drawer and screen transitions (cm9 launcher)
*Smoother/faster rotations
*Screenshots fixed
*Long press menu soft key (3/4 seconds) for persistent back-lights lights on/off
*Recent apps view rotation fixed
*Tablet screen fling (Action to change screen or scroll shortened to fit a tablet screen size)
*Smoother volume adjustment - more steps
*Scrollable Tablet Settings Bar
*Power Widget added to Combined Bar
*More Tablet Settings Bar options
*Better performance and battery life
*Smoother scrolling
*Working init.d scripts
*Smoother audio level adjustment
*3g
*Auto zip align at boot
*Messaging
*Ability to script inject
*New/more browser options
*New/more settings options
*Working Bluetooth audio
*New performance options
*More options through out the entire system
*Auto Ext4 conversion (check sdcard for icedBOCA.log)
*Ability to use Zram (compress memory for increased virtual capacity) and also choose compression level!
*Dalvic tweaks
*BMLwrite
*Carrier/Voicemail identification fix
*JIT (Just In Time compiler)]
*Quicker screen rotation
*UI improvements
*Game play improvements.
*Ps3 Bluetooth controllers
*Bluetooth upgrades
*Faster responces
*much much more!!
*Hot Reboot
*BOCA extra screen timeouts
*A few of the new settings
dont comply yet,
basically awaiting
merge/development/& build.
* All claims, or suggestions
of improvements or updates,
are only held in claim over
previous versions of icedBOCABROKEN
*Camera (lol dont even open it!)
*True HW accel
*USB Computer mounting (use supplied USB Storage app)
*Global Action Recovery/Download mode (use supplied rootbooter)
*Hot Reboot???
*Phone?? I remember there was a simple fix in other ics thread, Ill research it and apply it
KERNEL
Some things that I contributed directly to this kernel were suggestions about voltages, tips on recovery, showed changed the bootclass path (to make it an ICS kernel. From original ics boot spilt thread, but modded to build from source, as ours doesn't split) some other small things, alot of random work(as it is based off BOCA kernel - we used to share sources) and I ported/patched the following: SIO, VR NOOP, INTERACTIVEX, SAVEDZEN, GREASEDLIGHTNING, DARKSIDE, ONDEMANDX, SCARY, SMARTASSV2, SUPERBAD. Maybe a bit more, but nothing else comes to mind, directly.
Therefore I feel that I have contributed enough to include this kernel in my release.
If you notice, I didnt "spiff" the recovery up to its usual vibrant self this time.
Maybe next time, if users liked it in BOCA RC1.
ROM
This creation was ported and built by me.
I did get various ideas and configurations from developers around the web. And shared oh-so-many ideas also.
PLEASE DO NOT DISTRIBUTE BOCA IN WHOLE OR PART. NOR RE-UPLOAD
TREBUCHET
This version of the launcher uses hardware accel.
In can also upload a version that uses cpu /software accel.
Let me know.
Feel free to distribute the link (when uploaded) Its cyanogens product, but VERY heavily modded by me. Others on different devices (if it'll install) may appreciate it. Just kindly give me credit.
Info to read about the future:
http://forum.xda-developers.com/showthread.php?p=22086399#post22086399
post 286 down
THANKS
Its truely impossible to thank everyone, so I chose a very few who stood out in my short development stint.
spacemoose1
Koxudaxi
Ultramag
nobleskill
Fattire
reborn
Ronis
Alroger
Reborn
jt1134
Humbertos
tecknomancer
google
github
xda galaxyTab section developers
cyanogen and its gerit system
my users
Every single person who added to the development of ics for the sgt7..........
.......................................and every single android developer!
If I have missed anyone, it was not intentional. Please, PM me, and I will add you.
Thank you!!
As per request i have supplied a link that goes directly to rom.
DOWNLOAD link~ http://www.4shared.com/zip/7bZNGPJh/icedBOCA_prequel_2-2.html
NOTES
**FIRSTLY before posting, READ THE THREAD
**Replies requesting help, or reporting UNREPORTED bugs must include the following information:
Carrier
Country
Original device branding (sgh-t849, P1000L ect)
ROM you came from
BE HONEST in the steps you took to get here
If possible, include a link to patsebin, where you have uploaded your LOGCAT of the error
The more info the better
-IF YOU CAN NOT DO THESE SIMPLE THINGS, IT WILL BE DIFFICULT TO CORRECT THE PROBLEM-
As a user, you are very important to me, as is my quality of work and enjoyment of such work.
But if you cant be bothered to offer up some very simple info, Then I can hardly be bothered to beg you for it, just to help you.
*The red boarder still persists, infequently
*THERE IS NO HARDWARE ACCEL!!
*NOT EVERYTHING WORKS!!!!!!!!!!!!!!!
This is a DEVELOPMENT site, not a polished product site. DONT COMPLAIN!! Be helpful instead!
*We (all sgt7 cm9 ports) use the wrong graphics driver and graphics resolution. (its all thats available) So some video may not react up to your standards.
*This is a WORK IN PROGRESS!!!!!
I am a ONE PERSON development team.
I do this all in my free time, for the pure joy of it. Dont kill my joy by being a "GIMMIE-GIMMIE" or a Complainer
I (and every single developer here) am nice enough to share our work with you, be gratefull.
Or build it yourself.
*Doing things like porting and building a source code (especially an unfinished VERY alpha one) IS VERY TIME CONSUMING.
Each new build takes two full days to compile. Ive learned how to wait.
Total time ive spent doing this, added up probely equals over 700,000 hours. Again, for the joy of it.
So be patient on updates, or mistakes. There is never, ever an ETA. Dont ask.
About the download link
Its 4shared ;(
My server went down last night.
After I complete repairs, All my work will be uploaded to it.
Hi diz, just to let you know the image at the top is not clickable, and can only be viewed when users are logged in. Also there is a version of the image with (CM9) added to it in the boca rc1 post, you might want to copy these to your hosting and link them from there.
Gonna give this rom a try NOW!! thanks again for all your hard work.
supagforce said:
Hi diz, just to let you know the image at the top is not clickable, and can only be viewed when users are logged in. Also there is a version of the image with (CM9) added to it in the boca rc1 post, you might want to copy these to your hosting and link them from there.
Gonna give this rom a try NOW!! thanks again for all your hard work.
Click to expand...
Click to collapse
thanks for the headsup.
wierdly now it wont even show up while loged in.
but does when i go to edit post.
ill take a look at it.
Thanks again for the great artwork
hey diz, top work on releasing a new version of icedBOCA, looks like you put a lot of work into it
ive been kinda quiet for the last week (got a new computer from work which ive turned into a media centre and it was a pain to get the old clunker of a video card working in it)
i know what you meant in your other thread by the other one taking off the way it has, i was gonna try to manually add all their added stuff to your AOSEP version just to see how it went, but it wouldve taken forever just to get it to where they have, and keeping up with the updates would be hard (although i still want to do it just to learn more).
anyway, i thought id thank you yet again for your AOSEP idea and all behind it, even though i started fiddling before you had the idea, it pushed me to take it further.
with that, id thought id offer up one piece of information i learnt from another thread that fixes the red borders completely, on top of:
Code:
persist.sys.strictmode.visual=0
the other line that ive found that removes it completely is:
Code:
ro.build.type=user
so if the build type is set to user it seems to get rid of the red borders completely. hope this helps in some way and best of luck in the future.
just when i'm gonna download this ROM i found out that phone is broken, too bad >.<
gonna taste it when it fixed. great job diz!
Thank you mate! Like allways a great job!
Just experienced a small bug.
When rom installs I got allways a FC of a chineese aplication.
Thanks again, performance is very good.
Changing default keyboard and laguage to English in settings (Language & input) helped stop this for me. No need to freeze the launcher.
testadeferro said:
Thank you mate! Like allways a great job!
Just experienced a small bug.
When rom installs I got allways a FC of a chineese aplication.
I´ve frozed the launcher with titanium backup and its fine.
Thanks again, performance is very good.
Click to expand...
Click to collapse
Use the fix from the cm9 thread.
Sent from my GT-P1000 using Tapatalk
Download link
Would the Chef be kind enough and put in post 1 or 2 in bold letters where we could all DOWNLOAD the Rom. Thank you for your hardwork and sleepless nights. More people will follow you!
Derrian said:
Use the fix from the cm9 thread.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Could you be more precise? cm9 thread is quite long.... which fix?
thanks in advance
dabrowsk said:
Could you be more precise? cm9 thread is quite long.... which fix?
thanks in advance
Click to expand...
Click to collapse
You need to alter a couple of lines in the build prop and swap the phone. Apk for the one in cm 9
Sent from my GT-P1000 using Tapatalk
hey diz
hey i am a member on ur site i am the guy with the riffbox and stuff and if there is anyway i can help u i have a new quad core desktop that i compile with and at the most my compile times are 3 hours.i also thought i hear u say that u needed some ram i have some old ddr and ddr3 ur welcome to ...maybe i can help u compile or something andf i would like to pick ur brain on some stuff
my device is p1000 and I'm on overcome android 2.3 . due to hardware problems (my device crashed) I can't access recovery. can you make a flashable (via odin) TAR instead of ZIP please? if not say why it's impossible
Derrian said:
You need to alter a couple of lines in the build prop and swap the phone. Apk for the one in cm 9
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
ahh, the one with RIL thing
back then when i was on alpha 3 i used the method to solve the phone's FC but no good. Im on red rebel's now and its all working fine
If I pull the one from red rebel's , would it be as good as the phone.apk posted there or it's gonna be different?
hummy15 said:
Would the Chef be kind enough and put in post 1 or 2 in bold letters where we could all DOWNLOAD the Rom. Thank you for your hardwork and sleepless nights. More people will follow you!
Click to expand...
Click to collapse
im in talks with the mod about it.
a thread restructuring may be comming soon.
As per moderator request i have supply a link that goes directly to rom.
op has been updated to comply.
thank you for your work -
I`ve flashed it on clean safe gb from overcome with overcome kernel
battey drain is significantly better in your rom, although its unstable.
sometimes its 9 mah per minite )radio off, screen off
sometimes its 120.
Killing apps in backgroung helps though
I`m using battery monitor widget for monitoring
all my video players seem to work better than in cm9 build
the browser is very slow to render and load, cm9 is way better
but 3g is more than 1.5 times faster
other glithches
the mentioned red border, scrolling stutters sometimes, application names in all application screen sometimes are not displayed fully, its get choped and the rest is shown at the side of the screen.
Dizgustipated, Thank you so much, for making it easier to download your Rom. More grease to your elbows.
Hi everyone. Im one of the developers of SwitchMe, and app that allows multiple secure logins into separate installations of android on a single device. The pr is after the break.
I really need a few people to check into some issues people on some ROMs have been experiencing. There are some warnings involved:
- testers must perform a full nandroid backup before using the app, it is not our responsibility if you start getting boot loops
- if you report results or bugs, please use the "Write to us" function in the app whenever possible, and always describe the issue in the header of the logs you send
- if you post here, bes sure to include your device type and rom
- if you have apps installed on sd, be sure to mention that as well
--------------------------------------------------------------------
SwitchMe is a unique application for root users that allows you to log in and out of multiple installations of Android just as you would on a desktop computer.
The technology behind SwitchMe saves all of your applications and data, protects it and stores it as a file in memory. You can then log out of an
account and log into a fresh installation of Android or another account with its own unique content.
You may create as many profiles as the memory is capable of holding. Some of these may require very little free memory because they contain few apps,
others will be larger as they contain many applications and lots of cache and data.
Why is this functionality useful?
Privacy - the most obvious benefit is that you can securely share one device among multiple users, which gives you privacy and peace of mind.
Testing - if you are a developer, you can use profiles as clean sandboxes to test your applications and their interaction with the system.
Gaming – with multiple installations of Android on a single device, you can now play online MMOs as different characters.
Speed - the games your kids play slow down your tablet, but with SwitchMe you can easily create profiles without games or instant messengers.
Battery life - when the battery is low but there are important emails or documents to edit later, switch to a profile which only contains these essentials.
These of course are only suggestions - there are plenty of other uses for the functionality SwitchMe offers.
Market link:
https://market.android.com/details?id=fahrbot.apps.switchme
The Lite version allows the creation of two profiles, enough to test on.
Screens:
SwitchMe 1.2 has been rolled out and now includes a lockscreen replacement:
1.2
Added lock screen for logging in and out
More stable Fast switch implementation
Reworked UI colors
Now, its very important that we get some feedback on how this big new feature works, so please read up on it in the help and post your thoughts!
1.2.2 - HOTFIX 2
Reworked widget on qHD+ displays
Fixed widget text on HC and ICS
Fast switch improved on older devices
Nice, thanks!
Thank you! Any issues to report?
What do you think of yesterday's update?
1.4.3.7
Fixed device specific switch screen crashes and issues
Fixed UI bug in switch screen preferences
If anyohe had problems with superuser before, this should fix them. Please let me know if that is the case, its important we get some feedback here!
This is working perfectly with CyanogenMod 9. Will this continue to work if I update to a newer nightly?
xethor said:
This is working perfectly with CyanogenMod 9. Will this continue to work if I update to a newer nightly?
Click to expand...
Click to collapse
I dont see why not. Just make sure you back up your profiles to the SD card if you do a wipe.
They are in /data/.profiles. Next release will have an im-app backup function.
1.5.3.0
Enabled full support for MIPS and x86 architectures
Many root daemon code fixes and optimizations implemented
Sorry backup is relegated to the next release.
Thought I should let you guys know of the issue I had with the paid version of this earlier.
Running Hyperdroid Androidmeda 6.1.17, I rebooted my phone and SwitchMe would ask me to log in, however it wouldn't list the username, wouldn't log in when I put the info in myself, and wouldn't even say the password was wrong when I entered it wrong on purpose. I tried multiple reboots etc, the issue persisted.
Unfortunately I don't have a logcat or anything since I was in a rush to get my phone working properly (had to leave soon) so I restored a nandroid from before I installed SwitchMe
This was all before the 1.5.3.0 release btw, happened last week.
Yes, that was hotfixed a few hours later. The main thread also has a flashable zip which will "unswitchme"
THANKS good
ftgg99 said:
Yes, that was hotfixed a few hours later. The main thread also has a flashable zip which will "unswitchme"
Click to expand...
Click to collapse
thanks goo work
Enjoy! And spread the word
This thing is rock solid thanks very much
Thanks, by the way we released a new app today some of you might also find useful, you can find it here:
http://forum.xda-developers.com/showthread.php?t=1538222
PLEASE CHECK IT OUT AND BE KIND
Touch Blocker Beta - a simple but useful app that makes holding and using your device easier
There are two basic functions:
- create dead zones where touches do not register
- filter the screen when reading in low light
We are already in a relatively stable Beta release - whats left now is adding new features and making it all look pretty. You can follow this process at the thread here.
Please be sure to write suggestions - we are looking forward to engaging the community and building a useful and nifty application that many will enjoy!
Market link
https://play.google.com/store/apps/details?id=fahrbot.apps.touchblocker
Screens
Debugging
If you experience issues, the best way to help is by reproducing them and then clicking "write to us" - be sure to include a description of your error or we may not read the logs.
1.5.3.1
Fixed issue with lock on boot
Fixed some rare crashes on lock screen
Fixed MIPS and X86 Key compatibility
Any issues with the latest version?
I take it everything is fine?
Any issues to report?
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
PHONES CAN BE LIVE SAVERS. THIS DEVICE IS NOT SUITABLE AS YOUR ONLY MEANS FOR COMMUNICATIONS AND IS NOT BEEN TESTED TO SUPPORT EMERGENCY CALLS. MAKE SURE YOU HAVE ANOTHER PHONE WITH YOU.
CyanogenMod/CWM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This is a rom for fairphone FP1 - 1st edition, repartitioned as of Cherry 1.6.
Do not install on any other device than the FP1 - I have not tested it on other devices and I do not have the FP1U1 (second edition).
This is basically the same rom as the KK build I do for the Wiko Stairway with a few FP1 changes (esp of course the kernel, magnetometer service, other minor differences). It uses a blob from the Wiko mtk-ril.so as the original FP1 blob crashes the rild.
What works:
- SIM1 for phone calls (incoming/outgoing) and SMS, data (2g, 3g)
- SIM2 is a WIP
- Audio (microphone - now also outside phone calls, loudspeaker, headphones, OK google)
- Sensors
- Wifi (not wifi direct)
- GPS (no A-GPS yet nor EPO assist files, so the fix can take a bit)
- hw composer
- camera for taking pictures (not video)
- wifi and usb tethering
- battery usage stats (expect the usage for Display to be very unprecise)
- candy crush, facebook and twitter
What doesn't work, known bugs:
- 2nd sim card 3G switch
- Dual SIM is a WIP and has some bugs (data connection instability, etc.)
- camera for "movies" does not work
- (hw) video en/decoding not enabled
- bluetooth not available
- FM radio not available
- A-GPS does not work, GPS works though but slowish
- rest of MTK specifics (what?)
- ... you tell me
Credits: many thanks go to the omnirom project as they have done lots for mt6589 already (https://gerrit.omnirom.org/#/q/topic:mt6589,n,z). Esp to xplodwild and drshadow, pawitp, dhacker29, keesj, tmp_
Installation guide:
- Install latest CWM linked in this thread (for installation see in: http://forum.xda-developers.com/showthread.php?t=2615613) - if you don't have it yet, make sure you backup recovery.img
- Make a backup with CWM - you will want to go back to stock, don't blame me if you don't have a backup!!!
- copy the .zip to the phone and flash the zip with CWM
- copy the gapps to phone and install the zip (see: http://wiki.cyanogenmod.org/w/Google_Apps - this is CM11)
- Wipe
Sources:
Kernel: https://github.com/chrmhoffmann/android_kernel_fp_FP1
Device: https://github.com/chrmhoffmann/android_device_fp_FP1
Android: https://gerrit.omnirom.org/#/q/topic:mt6589,n,z - more to come
Changelog 0.2:
- sync with CM (~M10)
Downloads:
http://goo.im/devs/chrmhoffmann/cm-11.0/fp1/cm-11_FP1-ota-UNOFFICIAL-FULLOFBUGS-0.2.zip
md5sum:
a5fc95a59748d08c0944420b8ddcd026 cm-11_FP1-ota-UNOFFICIAL-FULLOFBUGS-0.2.zip
Older Downloads:
Downloads:
http://goo.im/devs/chrmhoffmann/cm-11.0/fp1/cm-11_FP1-ota-UNOFFICIAL-FULLOFBUGS-0.1.zip
md5sum:
fc5cba4eace4eaadf2b94f4513950f38 cm-11_FP1-ota-UNOFFICIAL-FULLOFBUGS-0.1.zip
reserved
Thank you very much !
I tried it (this was my first experience with CM so far) and I think I wont go back to android anytime soon
Despit the name of the download (FULLOFBUGS ^^), I found it actually quite stable (It's true I haven't done extensive testing)
The only not known bug I encountered (and I absolutly dont care, please dont waste time fixing it ) was with the grass animated walpaper.
I also encoutered the
very minor glitches in animations (like turning your phone by 90 degrees) with smaller stripes
Click to expand...
Click to collapse
described by @madde- in this thread (which you might want to check out)
Thanks again, a lot !
chrmhoffmann said:
This is a rom for fairphone FP1 - 1st edition, repartitioned as of Cherry 1.6.
Click to expand...
Click to collapse
there are any news about this rom? seems stopped....
Dede525 said:
there are any news about this rom? seems stopped....
Click to expand...
Click to collapse
I am exicted and interested in news as well.
But:
It's barely been a week. @chrmhoffmann made something great here, but is probably working on this in free time. Please show some patience and don't make this Fairphone forum look like other threads here on xda.
First of all: many many thanks for even trying to bring CM11 to the Fairphone!! I don't own one (yet) as up to now I felt that this project might lead into a dead end (i.e. a device that after some rather short time is no longer supported). Now the perspective is quite different.
chrmhoffmann said:
What works:
- SIM1 for phone calls (incoming/outgoing) and SMS, data (2g, 3g)
- SIM2 is a WIP
...
What doesn't work, known bugs:
- 2nd sim card 3G switch
Click to expand...
Click to collapse
Fairphone states this on the specs page (http://shop.fairphone.com/specs-page.html):
Dual SIM, Dual Stand-by. One SIM: 3G; one SIM: 2G. Standard format miniSIM card (not included).
Click to expand...
Click to collapse
Could this mean that SIM #2 is by design restricted to 2G?
Out of curiosity: one more question regarding phone and kernel: can the CPU be overclocked? If so, what steps are available, has anyone encountered stability issues?
fredflegel said:
I am exicted and interested in news as well.
But:
It's barely been a week. @chrmhoffmann made something great here, but is probably working on this in free time. Please show some patience and don't make this Fairphone forum look like other threads here on xda.
Click to expand...
Click to collapse
I didn't see that is just been a week. My fault.
lm089 said:
First of all: many many thanks for even trying to bring CM11 to the Fairphone!! I don't own one (yet) as up to now I felt that this project might lead into a dead end (i.e. a device that after some rather short time is no longer supported). Now the perspective is quite different.
Fairphone states this on the specs page (http://shop.fairphone.com/specs-page.html):
Could this mean that SIM #2 is by design restricted to 2G?
Out of curiosity: one more question regarding phone and kernel: can the CPU be overclocked? If so, what steps are available, has anyone encountered stability issues?
Click to expand...
Click to collapse
These "developer forums" are usually only for bug reports and the like, so I hope it's ok for me to post this here.
Yes, nice observation lm089, I now remember reading that too. Hardware doesn't seem to be able to go 3G with the second SIM card! So this isn't even a bug of this ROM
In regards to overclocking it's probably best to open a new thread
Unrelashade said:
Yes, nice observation lm089, I now remember reading that too. Hardware doesn't seem to be able to go 3G with the second SIM card! So this isn't even a bug of this ROM
Click to expand...
Click to collapse
Actually it does support 3g for the second SIM. You can choose which card is restricted to 2g.
Greetings,
paalsteek
0.2
0.2 released.
Nothing much changed in terms of mtk specific. Just sync to current cyanogenmod sources (approx. M10).
Chris
PS: Files need some time to show up on goo.im.
PS2: It is there now.
Thanks Chris for your wonderfull work. Will you also port Android L when it is available?
Awesome work on the your port of cyanogen! I bought the FP1 at launch with high hopes for the phone, especially as it aimed to be open and community driven. Sadly, the hardware vendors fell a bit short of that promise. But finally I'm able to install a CM based ROM for my FP1! I use it as my backup phone and for the longest time it was the only phone that wasn't CM based.
Keep up the good work! I'll follow this post for any updates you may post.
Thanks again mate!
Time Clock
Thanks for this beautiful work chris,
What for me doesn't work is the the alarm clock when the devis is turned off.
I liked it when i can shut down my dev. and it wakes me up in the morning
But no as essential as the "(hw) video en/decoding"... short question:
Why does Youtube work, and other video-streaming programs per example "Twitch TV" not?
Has the Youtube Software decoding included and Twitch probably not?
Best regards
shooter_92 said:
Thanks for this beautiful work chris,
What for me doesn't work is the the alarm clock when the devis is turned off.
I liked it when i can shut down my dev. and it wakes me up in the morning
But no as essential as the "(hw) video en/decoding"... short question:
Why does Youtube work, and other video-streaming programs per example "Twitch TV" not?
Has the Youtube Software decoding included and Twitch probably not?
Best regards
Click to expand...
Click to collapse
well android (cm11 as well) is not able to run the alarm clock when the device is turned off...is not a problem of this particular rom... however the stock rom of FP1 can turn on the phone at a certain hour, but maybe you already know it.
Merge OS?
Dede525 said:
well android (cm11 as well) is not able to run the alarm clock when the device is turned off...is not a problem of this particular rom... however the stock rom of FP1 can turn on the phone at a certain hour, but maybe you already know it.
Click to expand...
Click to collapse
Yeah, I thougt that it will be something like that... Thanks
But the Sourcecode of de Stock ROM of Fairphone ( https://fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions- )
and from Cyanogenmod is available too on GitHub ( https://github.com/CyanogenMod )
Isn't it possible to put the code from Fairphone OS which refers to the Alarm-Clock-wake-up-mode into the CM-code?
When the Fairphone OS is installed, then it's possible, in cause of this it has to be a OS/Software-Problem...
I really don't understand many things from Android, sorry for that, but I'm working on it
Any news on bluetooth functionality?
Is there any prospect of bluetooth working in with this ROM soon?
I know questions like this can be a pain in the ass for developers, so please don't get it wrong, but I'm eagerly waiting for Android 4.4 (especially CM) on the Fairphone for such a long time now. In combination with the Pebble Smartwatch, the notification system with Android >= 4.3 is so much better. But obviously, the smartwatch functionality relies on bluetooth.
Thanks, Tobi
first, thanks again for your wonderful work!
then, I'd also need these gaps to be filled so that this could be a productive version:
- BT working
- the timing / auto-shutdown / auto-start function from FP OS
- Optimized Battery Life
- maybe a FP branding (I really like the startup screen, fonts and wallpaper from FP OS)
Is there still any involvement with the FP guys? Could they help out regarding the details or are they involved somehow? What can the community do to help?
shooter_92 said:
Yeah, I thougt that it will be something like that... Thanks
But the Sourcecode of de Stock ROM of Fairphone ( https://fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions- )
and from Cyanogenmod is available too on GitHub ( https://github.com/CyanogenMod )
Isn't it possible to put the code from Fairphone OS which refers to the Alarm-Clock-wake-up-mode into the CM-code?
When the Fairphone OS is installed, then it's possible, in cause of this it has to be a OS/Software-Problem...
I really don't understand many things from Android, sorry for that, but I'm working on it
Click to expand...
Click to collapse
I'm not a developer and I don't know if what you are thinking is actually possible
prinz.z said:
Is there any prospect of bluetooth working in with this ROM soon?
I know questions like this can be a pain in the ass for developers, so please don't get it wrong, but I'm eagerly waiting for Android 4.4 (especially CM) on the Fairphone for such a long time now. In combination with the Pebble Smartwatch, the notification system with Android >= 4.3 is so much better. But obviously, the smartwatch functionality relies on bluetooth.
Thanks, Tobi
Click to expand...
Click to collapse
we all are wondering a total functionality of this rom, but pushing the developer is never a good thing. He is not paid for his work, is just volunteer work so if he has free time maybe he will do it, maybe not. Don't expect that everything will be done soon.. .
huedrant said:
first, thanks again for your wonderful work!
then, I'd also need these gaps to be filled so that this could be a productive version:
- BT working
- the timing / auto-shutdown / auto-start function from FP OS
- Optimized Battery Life
- maybe a FP branding (I really like the startup screen, fonts and wallpaper from FP OS)
Is there still any involvement with the FP guys? Could they help out regarding the details or are they involved somehow? What can the community do to help?
Click to expand...
Click to collapse
this comment seems to be a bit pretentious... keep calm, he make volunteer work, and have no relation with the FPs Soft Developer, also because the development section of FP is from an external company.. so keep calm and wait, if he will have free time to spend on it, maybe will continue to develop, maybe not, but don't push him
Dede525 said:
we all are wondering a total functionality of this rom, but pushing the developer is never a good thing. He is not paid for his work, is just volunteer work so if he has free time maybe he will do it, maybe not. Don't expect that everything will be done soon.. .
Click to expand...
Click to collapse
I would be interested if we could issue a bounty for @chrmhoffmann to get him working in the port again?
fredflegel said:
I would be interested if we could issue a bounty for @chrmhoffmann to get him working in the port again?
Click to expand...
Click to collapse
I think I would contribute to that