yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] sun75:
In many Countries they use it to broadcast anything useful/vital to people life. In Italy it's used by Vodafone to broadcast the Province/CellID in GSM, channel 50, and TIM for the "Arancione" plans (does it exist anymore?) to bill by Province/CellID (I don't remember the channel ID).

The -> real <- thing, in Italy, is the battery drain!
[Miscellaneous Android Development] Melkor_98:
The modified Twrp does not work for me... the original twrp link is offline and the standard 2.8.7.0 is not working on fever, and the working version of twrp that i found online (that is 3.0.something) is not able to install this rom for the error "signal 11" Then i do not know how to install this rom... if someone has advice, or has installed it, let me know.
[Miscellaneous Android Development] sun75:
What problems do you have with the modified Twrp? By the way, the Twrp itself was not modified, only the kernel (stock V39 Fever LL) and I deleted the last page asking to install SuperSu everytime... not so useful, because I use to install it separately, or with the Rom with scripts!

The only issue I have with Twrp 2.8.7.0 (vs. 3.x) is that it's continuosly flickering in upper screen, but it's useable for the two/three items it has to do (format/wipe/install).

These problems doesn't appear on Twrp 3.x, but we can not use it, because it expects MarshMallow filesystem paths format and support,... vs we are using Lollipop format. You got signal #11 because the scripts cannot mount and find the /system filesystem were they expects to find in LL format while you are using Twrp 3.x in MM format!

If you'll try to start Twrp 3.x on kernel 3.10.x (LL), if it starts for whatever miracle, you'll get tons of signal #7 errors bacause the /rootfs of the Recovery image is based on MM files and libraries, while Twrp 2.8.7.0 is based on LL files and libraries and does not start on kernels 3.18.x (MM).

Lastly, have you clicked on the "d-h.st/82jl" link? I clicked on it, now, and I downloaded it with no problems... (the original 2.8.7.0 twrp!)...
[Miscellaneous Android Development] PsychicPterodactyl:
[MENTION=8566975]Melkor_98[/MENTION] [MENTION=253658]sun75[/MENTION] When I installed RR for the Canvas 5 on my Wiko Fever I first had to install the Canvas 5 TWRP recovery. This was because otherwise I got a signal 11 error as the updater-script was setup for the Canvas 5 (changing it cause some other errors...). With the Canvas 5 TWRP I had the strange black lines flickering at the top of the screen and some other minor bugs. But then, when I had to reinstall it because the IMEIs were not working, I first flashed the stock Canvas 5 LL firmware ROM and then the recovery. This time it worked perfectly as if I had a Canvas 5. So this could possibly be related as the issue appears to be similar.
[Miscellaneous Android Development] sun75:
Yes, it can be true, but the problem is Wiko and Canvas have different partition schemes: Wiko has one partition more (Apedata) and different partition sizes and entrypoints vs. Canvas. (refer scatter file...). If you change your phone to Canvas, make sure to FIRST, make a *complete* ROM backup of all 26 partitions to files with SP Flash Tool!

Then you can format all the flash eprom, and restore the Canvas Rom. So you will need the SN Write Tools to restore IMEI/WIFI/BAR Code/BT mac addr using the Canvas mddb database.

Then you have to restore all the Wiko hidden partitions except the system, boot and recovery, but from now on, you have to use the Canvas scatter file, because you changed the partition scheme!

Hidden partitions are important because they contain calibration data, security keys, crts, etc... For sure they are used on Stock Roms, ... I don't know if custom Roms use them...

So, be careful on mixing the correct scatter file being on Canvas or on Wiko type Rom...:cowboy:
[Miscellaneous Android Development] Melkor_98:
I thank you for the answer, yes that link after some ads bring me to a page that do not load... about twrp i should try to bring back to LL the phone with the official tool of wiko and with that situation restart to unlock bootload /flash twrp 2.8.7/ install rom? For exemple i use the tool taken from andoidiani (i can not post link...) that should bring back everything to android 5.1 status? ps on the last version of MM for fever (the one that i have) if i flash a different version of twrp that is not the 3.0.something the recovery do not start, the phone remain on the "wiko" screen and stop here...
[Miscellaneous Android Development] sun75:
No, you shouldn't bring back to LL the phone nor unlock anything! I was on MM, and simply flashed with SP flash tool the boot.img & recovery.img. Once in recovery, I erased all except the microSD, and then, installed the Rom.zip. Done.

What problems do you have with recovery flashing it with SP flash tool? It does not start? Let me know!

For the original TWRP you can see here (Twrp Beta1 for LL): Link! I'm correcting the OP!
[Miscellaneous Android Development] Melkor_98:
I was using adb Fastboot, to first unlock the bootloader (that with the wiko tool return locked if you recover the phone) after i use the fastboot command to flash the recovery img, with the classic "fastboot flash recovery" Should i use SP flash tool to flash the twrp 2.8.7? (the reason of why i was using adb fastboot is becouse fever has not the removable battery and sp flash tool have difficulty do detect him)
[Miscellaneous Android Development] sun75:
Yes, you'll bypass the OS, flashing directly the recovery.img to the flash! I never used adb fastboot, etc. commands on Wiko,... and I never unlocked the bootloader! Maybe with other phones it's mandatory, but with the Wiko Fever, you can flash directly on top with SP Flash Tool! ;)
[Miscellaneous Android Development] Melkor_98:
Okay i will try Sp flash tool, could you just explain better how to make the fever detect by the program? becouse i used it for older phones and i always removed they're battery, but with fever i can not do this and connecting it to the usb it will start the charging screen, i need some particular drivers?... anyway thank you a lot for your help :)
[Miscellaneous Android Development] sun75:
The first time you use the official Wiko Update (V34 MM or V39 LL, it doesn't matter) it installs the Wiko drivers (unsigned drivers, so if you use Win 8/8.1/10 you have to reboot in "allow unsigned drivers install mode" by using the Windows recovery menu' and by pressing F7 (If I remember)) and unpacks the original Rom, then it asks to install it: do not install it, you don't need it!

Once installed the drivers, use the SP Flash Tool (it uses the same drivers installed by the Wiko Update!) to update the required images of the Flash!:cool: The phone must be completely off, attach it to the pc after you have started the download process in SP Flash Tool and it will start by itself!
[Miscellaneous Android Development] Melkor_98:
It worked perfectly, thank you for everything:):)
[Miscellaneous Android Development] pakrett-bm:
I've got huge battery drain especialy when the phone is used (I think it's correct on sleep mode) and I already set up kernel audiutor to 1040 max CPU speed...

Is it normal ?

Two others minor bugs :

Settings app crash at first boot, need to force stop it and re-launch the app to get it to work (I'm in France if it's matter).

Mobile data on LTE can't connect directly at phone boot, I have to switch to 3G then set it back to LTE and it's good.

Also, I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?
[Miscellaneous Android Development] sun75:
Huge battery drain? Are you using this rom or the 5.8.4_r29 for Canvas?

If you're on this Rom, why you have set kernel audiutor to 1040 max cpu speed? I can achieve a normal day full battery chargeless whith no particular settings!

The Settings app never crashed at first boot to me (anyone else?), but, instead, with SuperSu installed, it asked for Root permissions!

For mobile data: I think it depends on where you live! I adapted /system/etc/firmware and /system/etc/mddb for SE (Southern Europe, Italy, etc.) Region. If you live elsewhere, you have to simply replace or adapt the contents of these two folders with the data you can copy from your Stock Rom (same paths). One more config, there is a "ro.telephony.default_network=10" in build.prop in /system that works for sure in Italy..., maybe in other countries the LTE default network is not 10 but another value...
[Miscellaneous Android Development] pakrett-bm:
I have a Wiko Fever 4G and I use the rom you recommended : "RR-N-v5.8.3-20170527-l5460-Official" installed from stock Wiko Fever lollipop v22. (What's better ? Installing from lollipop or marshmallow, and which version ? I can't find lollipop v39 anymore)

I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?

Also why we need superSU ? Can't we use lineage/cm integrated root ?

Mobile data isn't a problem for me, I use a tasker task that send an intent to gravitybox at system start to switch to 3G then switch back to LTE. I'm in France and LTE default network is also 10 I think, it also work with 9 if I remember correctly.

Do you know if I can sent an intent to the system to do the same thing, I mean without needing of gravitybox ?

The Settings app doesn't crash at first boot but sometimes (often) at system start. Same thing, I use a shell command with tasker to open settings in background at system start then another command to force close it, and it works.

Another thing, why there is two camera app exactly ?
[Miscellaneous Android Development] sun75:
It's not a problem what version of LL or MM did you came from...: the problem, maybe is the Region you are for the Baseband. I "statically linked" the SE Baseband (in the Stock MM Rom it is chosen by reading the NVRAM for the suffix _XX and then it loads the right files from /etc/firmware and ../mddb directories). Now, with the custom ROM, all the scripts reading the NVRAM for the suffix are gone, so it loads everytime the _n modem and mddb databases, whatever they are! So I overvritten the generic _n modem and mddb databases with the _SE ones. For your region to work correctly, I suggest you to upgrade to MM Stock, go in Factory Mode Menu and select Version Info -> check your Region Zone! If it's SE, ok, otherwise you have to copy/paste the zone modem/mddb _XX files to _n overwriting it for each group!

I don't know magisk and the other software you mentioned... so I can not help you for the battery drain with them!

For SuperSu... I tried to use /xbin/su but it doesn't work for all apps... Something works, most not! So, because are years I used SuperSu for all, I installed it solving the rooting problems for all apps requesting it!

Idem with Settings: it's requesting SuperSu with Root Permissions from the first start... maybe not installing SuperSu breaked something. You can check it by logging the boot process "adb shell logcat > log.txt" and looking for the cause of the crash! I can not replicate the problem...

For LTE,... in Italy I'm attaching LTE with no problems with two distinct network operators... it switchs automatically from H+ to 4G and viceversa without any interaction from me! I suspect you are on the wrong Baseband Zone... By the way, I got the Baseband from the MM V.34 ROM (the latest!).

Two cameras? Yes... only because every app has some nice features the other app does not have! Feel free to delete the one you don't like/don't use! :)
[Miscellaneous Android Development] sun75:
Some Bugs...

Hi,

I found some bugs in this Rom and/or port on Wiko Fever. I'll describe them so you can confirm them!

- In these days I'm working in a DataCenter at floor -1. Well, there is no GSM/data available here. The problem is that when coming back on ground or upper floors, the phone correctly reattach itself to H+/LTE data connection, but it never establishes an ip connection to the Internet, with the "x" in the LTE signal fixed as no ip was negotiated. This is true until a reboot is done! Once a reboot is done, the problem is solved: data connection and ip connection to the Internet are established automatically! I think it's the MM baseband that is not fully compatible with this Nougat Rom based on LL...: I'll try to substitute the Baseband with the LL V39 one and test it!

- FM radio module: I fixed it. BUT... : it's complaining about a "Alsasound: no defined handler specified for .... " forever (draining battery) and info on radio stations and RDS is not working (but radio and audio is working ok!). I'll investigate more on this!

- AudioFX mixer: apparently working,... but ... it's making no difference on sound, no matter on settings you select on its panel! So it's useless! I'll investigate to correct it, to change it, or the like. There is something wrong on the mixer config.

- As someone suggested me, I found that flashing TWRP 2.8.x and the Rom from MM results in some screen glitches and flickering on kernel boot, on charge and on TWRP operation. These can be annoying! To solve them, flash the Fever LL V39 Stock Rom before flashing anything else. Then flash the TWRP 2.8.x, and then the Rom. Doing so, you will never experience screen glitches and flickering on boot and TWRP operation. I think the big difference from the two versions (LL and MM) is the bootloader.bin that is different from the two releases.

- I added some MTK Engineer Mode Modules... someone asked me to do so....: some modules are crashing, e.g. the audio interface test suite, maybe for the Alsasound interface.

- I updated the OpenGLES driver library with the Fever V39 one: more stability.

- I updated all the audio/mixer interface to make FM Radio module work. Maybe this breaks AudioFX, maybe not...

- I updated the installer scripts to look for /gapps/gapps.zip and for /supersu/supersu.zip, so you can download them separately (the version you want) and integrate them yourself. Zip the Rom, and flash!

- Settings -> Backup & Restore -> Factory Reset : is NOT working (if you press "restore", it does NOTHING!!). Ok ok...you can hard reset by TWRP... I Know! :)

I think it's all... for now!

I'll update the Rom .zip once I'll solve the major issues here explained.
[Miscellaneous Android Development] ninux_android:
I finally saw someone interested in making a rom for wiko fever and here i am. I would like to know if i can install this rom in the wiko fever 16gb/2g ram version. I noyticed by the stock systems version that this is for wiko fever with 3gb ram. Anyways thank you for your goooooooood work!!

Edit: i have an hanuna twrp already installed in my phone, will it work or i have to install the version metion in the rom description??
[Miscellaneous Android Development] pitrazzu:
Error 11 for me :( i with MM and twrp by Hanuma
[Miscellaneous Android Development] pakrett-bm:
I think my problem, the one I talked about last time, is related to this error.

Your advice was to overwrite *_n files with *_n_XX in the /mddb folder that correspond to my region. So I checked the md5 of all files and I've seen that all *_n files are identical to *_n_SE files so I have replaced all *_n files with *_n_EU ones. And it worked a few time but the error reappears after few phone reboots.

AudioFX mixer is working for me, I've tried with bluetooth head-speakers and normal wired/jack headphones.

One more things about sound, audio2bluetooth is working but I have to wait about 20 to 30 seconds after connecting my headphones to hear sound in it. I' don't know why maybe it needs time to sync the two devices ?

I've tested few ways and the best way is to flash FEVER_Lollipop_V39, then your Boot+TWRP Recovery (modified) !

AudioFX mixer was working before.

---------------------------------------------------------------------------------------------------------------------------------------------------------------

Yes I think it will work even with a 2g ram version.

The best way is to flash the stock FEVER_Lollipop_V39 rom (format everything), and after that flash Boot+TWRP Recovery (modified) !

Then :

1. Download the ROM and copy it to your SDcard.

2. Reboot phone to TWRP recovery.

3. Wipe everything except SDcard.

4. Flash the ROM zip.

5. Reboot.

---------------------------------------------------------------------------------------------------------------------------------------------------------------

Same as for ninux_android :

Flash the stock FEVER_Lollipop_V39 rom (format everything), and after that flash Boot+TWRP Recovery (modified) !

Then :

1. Download the ROM and copy it to your SDcard.

2. Reboot phone to TWRP recovery.

3. Wipe everything except SDcard.

4. Flash the ROM zip.

5. Reboot.
[Miscellaneous Android Development] pitrazzu:
thank you :) i try this way
[Miscellaneous Android Development] sun75:
I'm testing the "older" Baseband version (the LL V39 one) that is the same for all Europe and, maybe, more! I found some LTE problems that I'm not having with the older version. Maybe the LL based Nougat wants the LL Baseband... I'll test it until saturday.

I did't try with BT or music playing, but only with FM radio... I'll extend testing with all the scenarios!

I think there will be no problems with the 2GB Ram version: the kernel should see the correct amount of real Ram and allocate it for use. If you'll see 3Gb of usable Ram, then you'll end with a device that will crash, because it'll try to use non existant Ram. To solve this issue, you'll have to "port" the Rom to your device. This is simple bacause the two device are idenctical except Ram size.

Only in that case (3GB reported Ram) you have to:

- use the Rom as "base" for your own

- you have to "unpack" your latest Stock Rom system.img

- modify the boot.img using the carliv_img_tool to extract it and then repack it when done (you have only to change the kernel image with the one of your Stock Rom boot.img)

- if necessary, change one or more hardware libraries "drivers" in /system/[lib|lib64]/hw with the one of your Stock Rom system.img
[Miscellaneous Android Development] ninux_android:
Well i guess i wil give it a shot. If i have any problems i come here saying them. Thank you :good::good:
[Miscellaneous Android Development] sun75:
One question: for "phone reboots" you mean, effectively, Reboot, or simply phone "power on from stand by"?

I mean, the problem it's presenting you after "n" times the phone sleeps in stand-by and you power it on, or after the n-th system reboot?

That question because when I have that problem, a system reboot solves it, until, many stand-by sleeps after, refaces it up!:(
[Miscellaneous Android Development] pakrett-bm:
Yes, a real reboot, not waking up from stand by mode.

The problem appear at each phone "real reboot" but yes, sometimes I wake up my phone and see that mobile data connection was lost. I thought it was because I have "changed my network", move to another place/city and connect to another antena ?
[Miscellaneous Android Development] ninux_android:
Hey, i installed the rom and it worked. I cant beleive this. Thank you very much!!!!!!!!
[Miscellaneous Android Development] pakrett-bm:
Cool :good: You see 2G of RAM in settings ?
[Miscellaneous Android Development] As3ro:
Erase ALL with the twrp 3.0 , then with SP Flash Tool flash recovery and boot.

In the recovery mode flash the system.zip
[Miscellaneous Android Development] ninux_android:
Yeah it showed the right amount of RAM but it was very laggy so i had to unnistall it and put stock again :(
[Miscellaneous Android Development] sun75:
Yeah! :D Stay tuned for the next updates: this rom has some minor bugs to be fixed!
[Miscellaneous Android Development] sun75:
Please log the boot process (adb shell logcat > log.txt) and see what is going wrong... it's strange that it's so laggy. 1Gb Ram less can not be the cause, because on normal operation, I've about 1,6GB free memory out of 2,9GB total RAM reported with an average used RAM of 1,2GB.

So, if the kernel is reporting the correct size of the RAM, there is something wrong elsewhere (mmsdk.so?) to be fixed with your Stock Rom ones.
[Miscellaneous Android Development] ninux_android:
Well, for starters i am very new at this porting things. I'm just and Android enthusiast that like to try new things and im tired of having only MM. So can you please explain in a simpler way what i need to do so i have a fluid rom? Thank you anyway for the great work :)
[Miscellaneous Android Development] pitrazzu:
Finally i have installed this rom and i can say that is amazing, smooth, light but with Trebuchet launcher have some lag instead with pixel is perfect
[Miscellaneous Android Development] PsychicPterodactyl:
Hey there, [MENTION=253658]sun75[/MENTION]. I've just switched from the Canvas 5 RR 5.8.4 ROM to this ROM, after having been reduced to 1 hour of battery life (absolutely insane). I have to say I've very pleased with the amount of bugs that have been fixed.

One thing I especially require to work is the compass, and it is finally working in a custom ROM. Although, I found, that even after calibrating it it appears to be a bit slow compared to stock. That is, if you stop moving the phone it takes a good ten seconds for it to stop changing values and settle on the real value. This can get quite annoying if you're trying to navigate by holding your phone. I was simply wondering if there was any way to make it faster. I am also interested in knowing how you got it to work at all, in case I try to port some ROMs myself.

Furthermore, I am still working on that custom kernel based on the Wiko MM sources, and was wondering if you knew what make/model the WiFi chip in the Wiko Fever is, so I can compile the kernel with the correct WiFi drivers. Also, would switching the zImage in the boot.img work or would the ramdisk need to be changed to accommodate for a new kernel? (I'm only practical on the developer side, don't really know how the Android system works and documentation seems to be hard to find).

Thank you for your time,

- gvlfm78
[Miscellaneous Android Development] sun75:
I removed it from the new version! Now there's only Pixel launcher!:)
[Miscellaneous Android Development] sun75:
The compass solution is a "porkaround": the akmd0991 daemon should be invoked by the msensord daemon that fails for some init.svc misconfigurations (I straced all the process). So I used a "30compass" /etc/init.d simple script to call it and put it in background (&) as a resident daemon. It's not the same thing, because in the first scenario the akmd daemon would be a child of msensord with "direct" communication with it, in the second scenario, is a normal daemon, child of init, whit normal interaction with any other unix process, including msensord (and including lag...).

But it works...:)

Wiko Fever is made basically of two chips: the CPU (mt6753) and the chipset (0x0337), but this one is a combo quad chip (mt6735), named also _consys_mt6735 in header files.

It integrates BT, FM, WiFi and GPS and many other features. You can find the datasheet here: Link!

The FM Radio chip is the mt6227 that is a "spin-off" of the 0x0337 mega-combo...

Apart from the "mega-combo", you have to compile all the sensors (e.g. the akmd0991, etc.) and the other hardware... If you want, I can walk through the /proc and /sys filesystems to get all the info you'll need...
[Miscellaneous Android Development] sun75:
New beta available

This ROM has some FCs on third party apps (such as Facebook, some Bank apps, etc.), so I deleted all the ROM files because they are useless at this time. Due te fact I have no more time to spend on this project, a moderator can close this thread!

Thank you!