I contacted one of the qt devs, and I was told I have to wait qt 4.7.1 to solve that bug…
a new qt package will be released together with 4.7.1, and the new faenilator too hopefully π
I contacted one of the qt devs, and I was told I have to wait qt 4.7.1 to solve that bug…
a new qt package will be released together with 4.7.1, and the new faenilator too hopefully π
Talking about modding, I have modified the settings for the comments π
FROM NOW ON, ONLY REGISTERED AND LOGGED IN USERS WILL BE ABLE TO POST COMMENTS! π
this avoids two problems:
1) fake faenils posting comments
2) spam comments being published (this happened many times during the last week)
so just REGISTER, and LOG IN to write a comment! π
ENJOY! π
ps. I HAVE ALSO ADDED THE POSSIBILITY TO REPLY TO COMMENTS IN A MAX OF 5 NESTED LEVELS!! THIS LETS ME AVOID THE USE OF “BOLD” CHARACTERS TO ANSWER YOUR COMMENTS! π
Hi guys, I’m very happy because the QT bug I talked to you about has been processed as P1: Critical, and has been fixed by the QT team in not even 1 day! π
I added the bug to the QT bug tracking system, and it was fast put in the Critical section, and solved in not even 24 hours π I’m happy to have contributed ^_^
It seems like the problem was in Nokia’s code examples, which I used as a tutorial…and it was a conceptual problem…(should we trust Nokia’s devs?)
You can have more details here http://bugreports.qt.nokia.com/browse/QTBUG-14058
to those who told me I’m stupid coz I shared n2o4’s sources: Β just no comment because I don’t want to sound rude nor impolite π but just think about a life without opensource projects…
I have not clearly understood what I should do to fix that problem, so I’ll ask for more info, and the faenilator will have all its features! π
NOTE: I AM NOT LEAVING, I AM JUST DOING WHAT SHOULD HAVE BEEN DONE MUCH TIME BEFORE BY EVERYONE!! π
Hi guys, I waited for long enough, I think that n2o4 is now ready has the whole world of i8910 users has betatested it for more then 3weeks π
I keep the promise I made months ago : “I will share the source of my next coming firmware” and there we go!
I wanted it to be as bugfree as possible, that’s why I waited for so long, but I think the time is right now π
I hope cookers from all over the world will find these sources useful, and my work will be of help to many people π
README: ONLY DOWNLOAD IT IF YOU KNOW HOW TO COOK A FIRMWARE, I WILL NOT OFFER SUPPORT FOR MODDING SINCE TOO MANY PEOPLE WOULD ASK FOR IT AND I WOULD END UP WITH A FULLTIME JOB MADE FOR FREE, I HOPE YOU UNDERSTAND ME π
By the way, from now on all advanced users and people who are willing to learn will be able to modify one of the most used custom firmware for free! π
Use the file, do what you want, publish it wherever you want!
JUST ONE THING: IF YOU USE THE SOURCES OF n2o4, OR IF YOU LEARN NEW THINGS THANKS TO n2o4’s SOURCES, OR IF YOU WANT TO MAKE AND PUBLISH YOUR CUSTOM FIRMWARE BASED ON n2o4, PLEASE GIVE CREDITS AND, MOST IMPORTANT, DROP A DONATION TO SUPPORT MY FUTURE WORK, THESE SOURCES ARE THE RESULT OF MORE THAN 1000 (YES, ONE THOUSAND! ^^) HOURS OF WORK (most of them spent learning new things)!!! :)THANKS
Here are the links π I published the source of every version!! To make your life easier π
GADG FIXED WDROFF SOURCE
NOGADG FIXED WDROFF SOURCE
NOKSMENU NOGADG WDROFF SOURCE
SWYPE GADG WDRON SOURCE (the name of the file is WDROFF but it’s WDRON actually, just change line 23 of 101f8808.txt in “int 0 0x1000000 cap_rd=alwayspass cap_wr=WriteDeviceData” to have the WDROFF by default)
LANGUAGEPACKS SOURCE
I REPEAT: I DO NOT OFFER SUPPORT FOR FIRMWARE COOKING! (for the reasons I stated above)
ENJOY!!!!!!! π