Guest PaulOBrien Posted July 31, 2015 Report Posted July 31, 2015 From the ZTE website, for the 'VF-995N on Lollipop' (that ID is on the back of the device and in the about page).Found on the Open Source Notices page, this file. P
Guest Andrei221 Posted July 31, 2015 Report Posted July 31, 2015 Any idea why the minimum cpu speed is 960? Or is it normal ?
Guest PaulOBrien Posted July 31, 2015 Report Posted July 31, 2015 Same on the Blade S6, it can be changed with root I believe.P
Guest Frankish Posted July 31, 2015 Report Posted July 31, 2015 Yeah I knew the kernel source was there but thought it a bit useless without unlocked bootloader to flash a custom kernel.
Guest Frankish Posted July 31, 2015 Report Posted July 31, 2015 Risky Paul ha ha. Is there no way of testing first if the image is checksum validated or is there a recovery tool for ZTE devices?
Guest KonstaT Posted August 5, 2015 Report Posted August 5, 2015 (edited) Merged the ZTE source release on top of the closest CAF tag and pushed it to my github.https://github.com/KonstaT/android_kernel_zte_msm8916 It also been tested that kernel and dt built from the source actually boots on a device. My TWRP test builds still have the same touchscreen issue that's been there since the very first build. No idea what's causing the problem either. :( Edited December 22, 2015 by KonstaT
Guest KonstaT Posted December 17, 2015 Report Posted December 17, 2015 Looks like another rebrand of this device as SFR STAR EDITION STARXTREM 4. ZTE released slightly updated kernel source but it still doesn't match one shipped with 5.1.1 on Vodafone Smart Ultra 6. http://download.ztedevice.com/uploadfiles/copyright/smartphones/source/STAR_EDITION_STARXTREM_4_Lollipop_Kernel(3.10.X).tag.gz
Guest lunario Posted December 17, 2015 Report Posted December 17, 2015 Zte will not release updated kernel for 5.11 they answered my email.
Guest KonstaT Posted December 17, 2015 Report Posted December 17, 2015 30 minutes ago, lunario said: Zte will not release updated kernel for 5.11 they answered my email. Linux kernel is released under GPLv2 so they're legally obligated to release it. Their customer service probably doesn't even know what that is or it just got lost in translation. ZTE has actually been surprisingly active lately releasing kernel sources for all kinds of strange devices. There's been more activity in past couple of months than in past few years combined.http://opensource.ztedevice.com/https://github.com/ztemt?tab=repositories
Guest KonstaT Posted December 22, 2015 Report Posted December 22, 2015 (edited) I sent them an email requesting updated kernel source for Vodafone Smart Ultra 6 and they released it. This matches the MR02b (Android 5.1.1) build.http://download.ztedevice.com/uploadfiles/copyright/smartphones/source/VF-995N_Lollipop_Kernel%EF%BC%883.10.X%EF%BC%89.7z It's based on a newer CAF tag than the previous one and I haven't yet pushed this new source to my github (I will when I get around to it). Edit. Pushed it to my github. Old source is now in lollipop-5.0 branch. New source is in lollipop-5.1 branch. Both can be found in lollipop branch with the new CAF tag merged in between. Edited December 28, 2015 by KonstaT
Guest c0d3x42 Posted March 2, 2016 Report Posted March 2, 2016 I figure this is probably a good enough place to ask. Bit of background, I'm trying to get an Android 5.1.1 based build (Resurrection Remix) working on the Smart Ultra 6. I've been using the original ZTE sources for 5.0 along with the CAF WiFi driver. It kind of works but i'm struggling with a suspend/resume problem and i'd like to use the ZTE 5.1.1 sources as there's quite a few driver updates and i'm using blobs from a 5.1 stock firmware, so would prefer to match up kernel and userspace. The problem though is the VF-995N (5.1) kernel fails to get as far as mounting /data and creating files/directories, so probably failing to get as far as running init. It's only a few seconds after the welcome screen that it switches into maintenance mode. The device/BoardConfig.mk is otherwise unchanged except for the kernel source directory so i'm fairly sure its not something simple like the wrong offset/address. Was there anything you had to-do when building the 5.1 TWRP recovery to ensure it'd work? Did you just build it using the msm_P839V55_defconfig and that was it? Cheers dude if you can give me a pointer or two.
Guest KonstaT Posted March 2, 2016 Report Posted March 2, 2016 (edited) 36 minutes ago, c0d3x42 said: Was there anything you had to-do when building the 5.1 TWRP recovery to ensure it'd work? Did you just build it using the msm_P839V55_defconfig and that was it? 5.1 TWRP uses prebuilt stock kernel from Turkish update. That TWRP was released quite some time before this source was out. Ramdisk offset was changed in 5.1 update but nothing special besides that. Though, I'm not even sure that is the reason why the old TWRP build doesn't work after 5.1 update and vice versa. I don't know if someone has tried building/booting kernel from this source. I sure haven't. Edit. Looking at it, you might want to try making these changes to your fstab. https://www.diffchecker.com/q1pywixa Edited March 2, 2016 by KonstaT
Guest gitanillo87 Posted March 2, 2016 Report Posted March 2, 2016 25 minutes ago, c0d3x42 said: I figure this is probably a good enough place to ask. Bit of background, I'm trying to get an Android 5.1.1 based build (Resurrection Remix) working on the Smart Ultra 6. I've been using the original ZTE sources for 5.0 along with the CAF WiFi driver. It kind of works but i'm struggling with a suspend/resume problem and i'd like to use the ZTE 5.1.1 sources as there's quite a few driver updates and i'm using blobs from a 5.1 stock firmware, so would prefer to match up kernel and userspace. The problem though is the VF-995N (5.1) kernel fails to get as far as mounting /data and creating files/directories, so probably failing to get as far as running init. It's only a few seconds after the welcome screen that it switches into maintenance mode. The device/BoardConfig.mk is otherwise unchanged except for the kernel source directory so i'm fairly sure its not something simple like the wrong offset/address. Was there anything you had to-do when building the 5.1 TWRP recovery to ensure it'd work? Did you just build it using the msm_P839V55_defconfig and that was it? Cheers dude if you can give me a pointer or two. i have a test init.d support from stock rom,maybe it helps you....if you want, tell me and good luck with the rom seems to be complicated
Guest c0d3x42 Posted March 2, 2016 Report Posted March 2, 2016 12 minutes ago, KonstaT said: 12 minutes ago, KonstaT said: 5.1 TWRP uses prebuilt stock kernel from Turkish update. That TWRP was released quite some time before this source was out. Ramdisk offset was changed in 5.1 update but nothing special besides that. Though, I'm not even sure that is the reason why the old TWRP build doesn't work after 5.1 update and vice versa. I don't know if someone has tried building/booting kernel from this source. I sure haven't. Ahhh, i'd assumed you built the recovery using kernel sources, yep, i think thats exactly why the 5.0 TWRP didn't work. I ran into it after updating to stock 5.1, the only changes i had to make after the update was for the base and offsets. Looks like i'll be cherry picking after all then.
Guest c0d3x42 Posted March 2, 2016 Report Posted March 2, 2016 (edited) 18 minutes ago, gitanillo87 said: i have a test init.d support from stock rom,maybe it helps you....if you want, tell me and good luck with the rom seems to be complicated I'm not sure what it is you are offering but compiling init and modifying rc scripts i'm fine with. I guess the bigger question here would be has anyone successfully run the 5.1 source drop? Edited March 2, 2016 by c0d3x42
Guest KonstaT Posted March 2, 2016 Report Posted March 2, 2016 9 minutes ago, c0d3x42 said: Ahhh, i'd assumed you built the recovery using kernel sources, yep, i think thats exactly why the 5.0 TWRP didn't work. I ran into it after updating to stock 5.1, the only changes i had to make after the update was for the base and offsets. Looks like i'll be cherry picking after all then. In case you missed the edit. Looking at it, you might want to try making these changes to your fstab. https://www.diffchecker.com/q1pywixa
Guest gitanillo87 Posted March 2, 2016 Report Posted March 2, 2016 6 minutes ago, c0d3x42 said: I'm not sure what it is you are offering but compiling init and modifying rc scripts i'm fine with. Sorry i am spanish and my english is terrible....only thing i have is init.d support for the last stock rom....
Guest c0d3x42 Posted March 2, 2016 Report Posted March 2, 2016 26 minutes ago, KonstaT said: In case you missed the edit. Looking at it, you might want to try making these changes to your fstab. https://www.diffchecker.com/q1pywixa Cheers for the heads up. Didn't help with mounting /data but i'll try tomorrow to see if it make any difference with the 5.0 kernel. I'm guessing not but who knows.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now