Hi,
I've started to investigate what is needed to build CyanogenMod 11 for the slte. I need to understand what we need to compile for exynos5430. There are extra repositories available. If anbody knows how to port a ROM or knows C/C++ and want to work together, feel free to contact me! Reading and understanding strace output is essential.
I will post my progress in this thread.
TODO
# RIL
Add WB (wide band) support to audio ril and add missing mixer values to mixer_paths.xml (WORK IN PROGRESS)
Test usb and wifi tethering.
Fix VoIP calls
# WIFI
Try to find a better solution for getting wifi working. Currently it is a hack in the wifi nl80211 driver. We should check if the kernel can indicate that the p2p device can't be set into station mode.
Revisit macloader and network patches to set nvram path. Maybe only the macloader should set the path. (WAITING FOR REVIEW)
# Media
Fix video decoding
Fix video recording
# CMHW (Samsung specific hardware configuration)
Add BOARD_HARDWARE_CLASS += hardware/samsung/cmhw in BoardConfig.mk
VibratorHW.java is wrong, copy to device tree and modify it? Check other devices how to fix it.
# MMS
Create overlay/packages/apps/Mms/res/xml/mms_config.xml
# Audio
Revisit sound recording, capture volume to low?
Check if CM DPS Manager is working.
Do we need voicefx in audio_effects.conf
# USB OTG
Fix attaching usb sticks and disks with CM. Need to look what CM expects and then fix init.rc
# MTP
MTP doesn't work, it uses not the standard mtp gadget driver.
Debug MTP server and driver to find out what is going wrong ...
mtpg_read() fails with a dev error and returns EIO ...
# NFC
Get NFC working (low priority) (maybe remove it, needs to much battery)
# DRM
Try to fix mobicore
If you know how to write C code or Java code, please pick an item and send patches. The java task is to reverse engineer the MTP server code. Use JAD for this. The rest is C/C++ code. You should know how to use strace and gdb.
-- modpunk
Package Complete: /home/asn/workspace/projects/cyanogenmod/system/out/target/product/slte/cm-11-20141109-UNOFFICIAL-slte.zip
My USB OTG cable should arrive tomorrow, then I can do a backup of the stock ROM and see if CM will boot. The slte SoC looks similar to the the manta SoC. At least they have the same GPU. Maybe it works with the 4250 sources ...
It doesn't look good. The hardware is much more different from exynos5420 than thought. I'm not sure if a port is possible without deeper insight into the SoC.
You said, you tried it with the mantas kernel? Thats google nexus 10 with a Exynos 5250?
I think, the google note 3 or google note 10.1 2014 might be better choices to start with - they use the Exynos 5420, form what i see it looks like 5430 is a advanced version of it using the 20nm process.
Both are octacores where every core is accessible.
- there seems to be a cyanogenmod repository holding 5420 kernel code...
on Samsung OSRC there seems to be source code for the Alpha available - but i can't download it, and can't make a login - i can't make a password that is accepted by that page... weird.
DThought said:
You said, you tried it with the mantas kernel? Thats google nexus 10 with a Exynos 5250?
Click to expand...
Click to collapse
No, I didn't. I tried it with the manta hardware support which is a exynos5420 chip. I fixed the Kernel sources for the slte and it is working just fine.
DThought said:
I think, the google note 3 or google note 10.1 2014 might be better choices to start with - they use the Exynos 5420, form what i see it looks like 5430 is a advanced version of it using the 20nm process.
Click to expand...
Click to collapse
The gpu seems to be differnt too. I've looked at the sources and the kernel interfaces they access are different too.[/QUOTE]
I have that kernel running already. I have to dive deeper. Maybe just the HDMI support is different and we don't need that.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-G850F
Two painfully slow download links, haven't had much experience with Samsung source before, is there a difference between the two variants listed for download that i'm missing before I start to download one ? I note one has SEA in the title of the file and the other doesn't.
You need the KK version. At least the source is cleaner However it needs a bunch of bugfixes that it even compiles! You can find my kernel tree (with fixes) here:
http://git.cryptomilk.org/projects/android/android_kernel_samsung_slte.git/log/?h=cm-11.0
This kernel is running on the recovery and I'm working on the exynos5 sources to prepare them for this kernel. I'm currently trying to fix hwcomposer so it works with decon-fb.
modpunk said:
It doesn't look good. The hardware is much more different from exynos5420 than thought. I'm not sure if a port is possible without deeper insight into the SoC.
Click to expand...
Click to collapse
Well, two days later the world looks different ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
modpunk said:
Well, two days later the world looks different ...
Click to expand...
Click to collapse
congratulations man :victory:
as i've said earlier, i'm glad to have a dev like you on our device
modpunk said:
Well, two days later the world looks different ...
Click to expand...
Click to collapse
Dude. Awesome. Tell me there's some way I can donate to show my appreciation? Can't wait to try it out man. Keep it up!
tnicko said:
Dude. Awesome. Tell me there's some way I can donate to show my appreciation? Can't wait to try it out man. Keep it up!
Click to expand...
Click to collapse
Thanks, the question is if I will get it fully working. It is still a long way to go. However there is a donation button on the left I guess ...
modpunk said:
Well, two days later the world looks different ...
Click to expand...
Click to collapse
you are the man m8,nice job
as neofral said, nice to have you hire
ps .if you lake tester I`m hire...also your kernal will work only with Cyan or with TW
Awesome dude !
Downloading sources at 9kb/sec so should be done sometime this year !!
Sent from my SM-G850F
Congratulations from France !
Are you on FreeNode ?
Is there a channel we can hang in and collaborate in ?
DangerMUK said:
Are you on FreeNode ?
Is there a channel we can hang in and collaborate in ?
Click to expand...
Click to collapse
Yes, I am. I do not get Wifi working and I don't know what is going wrong. I suspect it is a kernel issue cause I don't get any messages in the kernel ring buffer. No work till next week ....
Could you post us some experimental build, i'm sure all of us would appreciate it?
What for? The only thing which works is that it boots. Everything else is broken so what I will get is a load of bug reports which tells me nothing works.
The sources are available. If you want to help with development, feel free to build it yourself
I will try publish the changes to the exynos5 tree soon.
I still do not understand how Android sends the START command to the wifi driver to give it power and load the firmware and start it up. If someone could shed some light on this it would be really helpful!
modpunk said:
I still do not understand how Android sends the START command to the wifi driver to give it power and load the firmware and start it up. If someone could shed some light on this it would be really helpful!
Click to expand...
Click to collapse
can you look at this page and see if you get your answer?
http://blog.linuxconsulting.ro/2010/04/porting-wifi-drivers-to-android.html
edit: also this one is interesting http://boundarydevices.com/android-wlan-the-rest-of-the-story/
and this:
Wifi module initialization:
To in SystemServer start will generate an instance of ConnectivityService, ConnectivityService the constructor creates WifiService the WifiStateTracker will create WifiMonitor receiving from the underlying event, WifiService, and WifiMonitor is the core of the whole module. WifiService is responsible for starting off wpa_supplicant itself which is a bit more tricky, to start off WifiMonitor monitor thread and the command to the wpa_supplicant WifiMonitor is responsible to receive event notifications from wpa_supplicant.
WiFi module to start:
WirelessSettings the initialization configuration by WifiEnabler Wifi button
When the user presses the WiFi button Android will call WifiEnabler of the onPreferenceChange, and then the call WifiManager by WifiEnabler setWifiEnabled interface functions, AIDL actual call is the WifiService setWifiEnabled function the WifiService then send itself an MESSAGE_ENABLE_WIFI message in the message code to enable real work: First, load the WiFi kernel module (the module position hard-coded "/ system / lib / modules / wlan.ko"), and then start wpa_supplicant (hard-coded configuration file "/ data / misc / wifi / wpa_supplicant.conf "), then WifiStateTracker to start monitor thread WifiMonitor.
from here: http://www.programmershare.com/3736477/
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Like a few of you knows I'm working on a CM10 (Android 4.1.2) port from source for our device, so I open this thread, to discuss the work in progress, so... NOBODY THAT DON'T KNOW HOW TO BUILD ROM FROM SOURCE IS ALLOWED TO POST NOTHING HERE.
Our device
Our platform it's U8500, subversion U8430, codename montblanc, a SoC developed by Sony, but our manufaturer is Samsung, and our device codename is golden. The default clock cpu speed is 1 Ghz and our GPU renderer is Mali-400, our wifi/bluetooth/fm-radio receiver version is bcm4334 using a bcmdhd module.
What means that?
That means that our processor it's one completely closed, there's no source nor documentation about none of the strange binaries with what we must to work. Officially our latest android version is 4.1.2, the one I'm porting, so there's a big possibility of that finally all becomes to work, but also there's a big possibility of that evertyhing will work buggy and slow.
When will you release it?
I've a few interesting ideas about quality, at least it must to have everything working, and the UI must to be more or less fast. That means between one week or ten years. I'm a 16 years teenager studying and with girls in mind, so DON'T ASK FOR ETAS/UPDATES
Will you support or Galaxy S3 Mini variants?
I DON'T LIKE TO SUPPORT A DEVICE I DON'T OWN, SO THE ANSWER IS NO, I'll only support GSM version without NFC chip.
But the source code it's on my github, and I don't think that can be too much difficult to port it to another variant.
I've found a bug!
You're awesome men! But this is full of bugs, and most of them are know.
If you want to report bugs please read THIS HOWTO first. Please try to provide logs if you see errors (logcat and dmesg). If you don't know how to do that check google or ask people here to help you. Contact me on:
[email protected]
My source code:
https://github.com/OliverG96?tab=repositories
Alpha3 (23-02-13)
- Camera (Only pictures, no camcorder, slow panorama)
- Minor things with Audio and Sensors
Alpha2 (22-02-13)
- Audio
- HW Decoders
Alpha1 (07-02-13)
- Internal SDCard
- SMS and Calls
Alpha0 (02-02-13)
- Wifi
- Bluetooth
- External SDCard
- USB Mounting
- Sensors (Orientation&Brightness)
NOTE: I'll now release none of the Alpha0, that's are for testing myself, if you want it build from source.
Oliver, have a gtalk?
Sent from my GT-I8190 using xda app-developers app
ppero196 said:
Oliver, have a gtalk?
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
That's exactly the kind of questions I don't expect here...
Yeah, but please next time ask me over a pm or directly on email.
Keep this clean.
Enviado desde mi GT-I8190 usando Tapatalk 2
Congratulations Oliver I've not been very active lately, but I've followed your progress and it is remarkable! Cheers! Will be trying a first build, and try to implement the button-reboot-into-recovery combo into init (so that in case the system fails to boot and adb was not enabled, booting into recovery does not require a full /system reflash over Odin/Heimdall)
It's already built into cm
Well, now internal sdcard works too, it also asks for pin code, sms works, and calls too, but you can't use them really because sound is not working... xD
Data can't work, but still is asking for some binaries, so there's still a possibilitie
Looks like the issue with no internet over data is apns missing, there isn't anyone especified, so I tried to add it, but didn't get saved...
Enviado desde mi GT-I8190 usando Tapatalk 2
OliverG96 said:
Looks like the issue with no internet over data is apns missing, there isn't anyone especified, so I tried to add it, but didn't get saved...
Enviado desde mi GT-I8190 usando Tapatalk 2
Click to expand...
Click to collapse
Have you tried looking at system/etc/apns-conf.xml? If you need it you can download it here: http://www.mediafire.com/?wnj7d723bwi7wfc
dariolob said:
Have you tried looking at system/etc/apns-conf.xml? If you need it you can download it here: http://www.mediafire.com/?wnj7d723bwi7wfc
Click to expand...
Click to collapse
Yeah I've checked it and the file it's where it must to be...
Enviado desde mi GT-I8190 usando Tapatalk 2
Then it's probably a bug in the radio, cause data is connected to the network carrier.
Well that's the actual situation, Sound, Mobile Network and Camera aren't working, and I'll not release CM10 without them. What actually it's scaring me is just Data and Sound, specially sound, since looks like a really STE thing.
I've the parts of logcats reporting those errors:
- Data Mobile:
Code:
I/SystemServer( 1999): Connectivity Service
D/ConnectivityService( 1999): ConnectivityService starting up
E/MobileDataStateTracker( 1999): default: Ignoring feature request because could not acquire PhoneService
E/MobileDataStateTracker( 1999): default: Could not enable APN type "default"
I/WifiService( 1999): WifiService starting up with Wi-Fi disabled
D/WifiWatchdogStateMachine( 1999): Disabling poor network avoidance for wi-fi only device
The important part is the one saying "Ignoring feature request because could not acquire PhoneService", cause after it the code breaks, and forces the data network to stop. I've located the java function there:
https://github.com/CyanogenMod/andr.../android/net/MobileDataStateTracker.java#L546
It happens inside the apns function, that's why it's nor possible to add apn and there's no one defined, so data mobile don't work.
This is catched when the variable mPhoneService is null, so we must to find a way to make it to not be null.
I hope there's someone with more java knowledge than me, so we can found the problem.
- Sound:
This is making me to feel bad, because the prebuilt samsung sound binaries are already added, and I cannot see any other missing. Looks like a problem with the specific STE binaries missing things, I suppose this is the problem:
Code:
E/ADM ( 2262): [ERR] omx_log:258 Init --> OMX_ErrorInsufficientResources
E/ADM ( 2262): [ERR] vendor/st-ericsson/variant/multimedia/audio/adm/src/ste_adm_main.c:60 il_tool_log_Init() failed!
E/ADM ( 2262): [ERR] vendor/st-ericsson/variant/multimedia/audio/adm/src/ste_adm_main.c:91 unlink() No such file or directory
I/ADM ( 2262): 4: 73949998: [INFO] db:622 DB closed, res = 0
I/admsrv ( 2261): ADM server terminated
I'll try to contact Jerpelea, one of the most active members of sony novathor devices on oficial CyanogenMod team, maybe he can give me some interesting points.
- Camera:
This is the less important thing for me, there're still some binaries to be added and also some keys to be added for libcamera_client.so source. I suppose it's not the most difficult thing. Sound and data mobile are more important...:highfive:
Anyway this is where it's failing, but as I've already said, are just some simple things:
Code:
I/CameraService( 1681): CameraService started (pid=1681)
E/HAL ( 1681): load: module=/system/lib/hw/camera.montblanc.so
E/HAL ( 1681): Cannot load library: link_image[1916]: 1681 could not load needed library 'libblt_hw.so' for 'camera.montblanc.so' (load_library[1118]: Library 'libblt_hw.so' not found)
E/CameraService( 1681): Could not load camera HAL module
For a full logcat from first boot until it shows UI check this:
http://pastebin.com/u0Uvy3rZ
OliverG96 said:
Well that's the actual situation, Sound, Mobile Network and Camera aren't working, and I'll not release CM10 without them. What actually it's scaring me is just Data and Sound, specially sound, since looks like a really STE thing.
I've the parts of logcats reporting those errors:
- Data Mobile:
Code:
I/SystemServer( 1999): Connectivity Service
D/ConnectivityService( 1999): ConnectivityService starting up
E/MobileDataStateTracker( 1999): default: Ignoring feature request because could not acquire PhoneService
E/MobileDataStateTracker( 1999): default: Could not enable APN type "default"
I/WifiService( 1999): WifiService starting up with Wi-Fi disabled
D/WifiWatchdogStateMachine( 1999): Disabling poor network avoidance for wi-fi only device
The important part is the one saying "Ignoring feature request because could not acquire PhoneService", cause after it the code breaks, and forces the data network to stop. I've located the java function there:
https://github.com/CyanogenMod/andr.../android/net/MobileDataStateTracker.java#L546
It happens inside the apns function, that's why it's nor possible to add apn and there's no one defined, so data mobile don't work.
This is catched when the variable mPhoneService is null, so we must to find a way to make it to not be null.
I hope there's someone with more java knowledge than me, so we can found the problem.
- Sound:
This is making me to feel bad, because the prebuilt samsung sound binaries are already added, and I cannot see any other missing. Looks like a problem with the specific STE binaries missing things, I suppose this is the problem:
Code:
E/ADM ( 2262): [ERR] omx_log:258 Init --> OMX_ErrorInsufficientResources
E/ADM ( 2262): [ERR] vendor/st-ericsson/variant/multimedia/audio/adm/src/ste_adm_main.c:60 il_tool_log_Init() failed!
E/ADM ( 2262): [ERR] vendor/st-ericsson/variant/multimedia/audio/adm/src/ste_adm_main.c:91 unlink() No such file or directory
I/ADM ( 2262): 4: 73949998: [INFO] db:622 DB closed, res = 0
I/admsrv ( 2261): ADM server terminated
I'll try to contact Jerpelea, one of the most active members of sony novathor devices on oficial CyanogenMod team, maybe he can give me some interesting points.
- Camera:
This is the less important thing for me, there're still some binaries to be added and also some keys to be added for libcamera_client.so source. I suppose it's not the most difficult thing. Sound and data mobile are more important...:highfive:
Anyway this is where it's failing, but as I've already said, are just some simple things:
Code:
I/CameraService( 1681): CameraService started (pid=1681)
E/HAL ( 1681): load: module=/system/lib/hw/camera.montblanc.so
E/HAL ( 1681): Cannot load library: link_image[1916]: 1681 could not load needed library 'libblt_hw.so' for 'camera.montblanc.so' (load_library[1118]: Library 'libblt_hw.so' not found)
E/CameraService( 1681): Could not load camera HAL module
For a full logcat from first boot until it shows UI check this:
http://pastebin.com/u0Uvy3rZ
Click to expand...
Click to collapse
i'm an experienced developer and today i will get a galaxy s3 mini and then i will help you for the first problem....try to comment these lines of codes so cycle doesn't break and then rebuild. for the second problem...yeah this is a mess honestly and we must work around soemthin'.....for the third problem you have missed libblt_hw.so in lib folder or in hw folder check that
Audio is workinggggggg!
Well and hw decoders are working too now, video watching on gallery I mean, haven't tested youtube.
I'm gonna give an attempt to add missing camera binaries, the idea for mobiledata of commenting out where the code break didn't worked...
Enviado desde mi GT-I8190 usando Tapatalk 2
Most of the bugs you have can be fixed using objdump!
I do not respond to tech support via PM
OliverG96 said:
Audio is workinggggggg!
Click to expand...
Click to collapse
So cool! Congrats
https://github.com/OliverG96/androi...mmit/7d42e1173e3fe23bf3cbc67a2c3fd3c7f71c1a4d
:fingers-crossed:
Let's gonna fix HW Decoders/Encoders (I broke them again) and Data Mobile.
After those things you'll receive a BETA0 build full of minor bugs and superlaggy, but usable for daily if you're awesome.:laugh:
Very Nice.
DocMAX said:
Please give me a tutorial of how to compile.
Send with GT-I8190
Click to expand...
Click to collapse
Everything is documented on the README from my repo
Enviado desde mi GT-I8190 usando Tapatalk 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 10.1 for the Xperia U
Brought to you by TeamCanjica
TeamCanjica
We've been discussing to officialize the team a while ago and as Pablo (Paul-L) joined us we finally did it.
Our build server was then set up using Jenkins (Pablo's idea) and now and we'll are able to push nightly builds of Cyanogemod to Goo.im easily.
Also we are now joined by Pawel (DevSwift) which is now extending 4.2.2 development to Sony's Xperia devices
.
Diego Porto aka diego-ch -- CyanogenMod
Huang Ji aka cocafe -- CoCore Kernel
Federico Melano aka fedevd -- Miui
Franco Rapeti aka frapeti -- CyanogenMod
Matthew aka CallMeVentus -- NFC Variant
Pablo Lunarenko aka Paul-L -- P.A.C 4.2.2
Shantanu Londhe aka Shaaan -- Paranoid Android 4.2.2
Pawel aka DevSwift -- Xperia U, P, SOLA and GO
Working
RIL
Mobile Data
WiFi
USB tether
GPS
Leds
Audio
SD Card (internal storage)
App2SD
MTP & USB Mass Storage
Sensors
Vibrator
Project Butter
Camera (rear and front) with camcorder
Torch
Youtube HQ
CPU sleep mode
OMX -> Hardware Decoders / Encoders
Ambient Light Sensor
Known Issues
WiFi Tethering and WiFi Direct.
Bluetooth
Source
Check out the ROM Source available on TeamCanjica' s Github.
Feel free to submit any fixes, Just remember to give proper credits when using other people's source.
Credits
Alin Jerpelea aka FreeXperia
Daniel Hillenbrand aka Codeworkx
Oliver Garcia aka OliverG96
Installation
Download the ROM from the link below
Download gapps on http://goo.im/gapps
Flash kernel via fastboot (kernel from rom zip)
Put the zip files on your SDCard
Reboot on Recovery
Wipe Data / Factory Reset
Select "Install the Zip from External Storage"
Choose CM zip file (don't worry about error)
Choose GApps zip file
Reboot to system
Attention
First boot takes a while.
Wait at least 5 mins for it to boot.
Download
Nightly builds:
http://goo.im/devs/STEAndroid/kumquat/cm-10.1-sony/nightly
Latest build V3:
http://d-h.st/KpC
Want to contribute to development? Drop me a PM or submit your patches via pull request to our GitHub
__________________________________________________________________________________________________
The first full boot of our ROM was at 24/06/2013, current explaination of what works / does not
WiFi Tethering and WiFi Direct:
Wi-Fi Direct will probably NEVER work, we are working on Wi-Fi Tethering, which is probably going to work.
OMX -> Hardware Decoders / Encoders.
ST-Ericsson fault for NOT giving sources, it will NEVER work without them.
Camera
It's just missing symbols, it WILL work
Torch
Needs configuration, it WILL work
Audio
ST-Ericsson NEVER gave the sources, it's KIND of working, BUT is probable it never work at it's FULLEST
Bluetooth
Needs vendor configuration, it WILL work
_______________________________________________________________
Installation things for the paranoic ones:
YOU MUST INSTALL boot.img VIA FASTBOOT/FLASHTOOL IF GIVES YOU ERRORS
So, someone surely will see...set perms failed, this is because we must add a custom edifier/ota tools packager script written in Python 2.x
IF you see the some set_perms failed. IT doesn't mean that the ROM failed to install, just SOME of the files permission weren't applied because mostly THEY DON'T EXIST.
What to do? stay at recovery, go to advanced settings and select "fix permissions". THIS is not required, if you find any problems, just try, it will not do harm to your phone.
_______________________________________________________________
Please discuss NON dev related things at http://forum.xda-developers.com/showthread.php?t=2334423
OTHERWISE, I WILL HAVE TO CALL A MODERATOR HERE, GET A NICE READ OF XDA RULES
Awesome work and thanks.And btw i saw on some other devices (samsung galaxy ace) that omx libraries were adapted from ics, i suppose we could do the same ?, because correct me if im wrong but without omx libraries then bye bye to video recording - hardware video acceleration.
Just installed the ROM. And the rom is, impressively smooth, right after boot. I am unable to make calls, and play audio, etc. But this is some terrific work you guys have done. Every thing is running silky smooth with out a bit of lag. Thank you very much.
vamsi_krishna said:
Just installed the ROM. And the rom is, impressively smooth, right after boot. I am unable to make calls, and play audio, etc. But this is some terrific work you guys have done. Every thing is running silky smooth with out a bit of lag. Thank you very much.
Click to expand...
Click to collapse
We will work out the calls problem like we did on Galaxy S Advance, probably.
If by audio you mean...music? (Apollo crashing) Yes, it's because the sdcard (internal storage) isn't actually mounted/available for system use.
Paul L. said:
We will work out the calls problem like we did on Galaxy S Advance, probably.
If by audio you mean...music? (Apollo crashing) Yes, it's because the sdcard (internal storage) isn't actually mounted/available for system use.
Click to expand...
Click to collapse
It's very interesting because now I can play music and sdcard works we must test it more
Paul L. said:
We will work out the calls problem like we did on Galaxy S Advance, probably.
If by audio you mean...music? (Apollo crashing) Yes, it's because the sdcard (internal storage) isn't actually mounted/available for system use.
Click to expand...
Click to collapse
Yes, apollo crashing problem. Sorry for not being specific. I wish you guys all the best.
Cheers.
hello mates
set_perm: failed to change
status 7 error
may be updater script error
fixxxxxx:cyclops:
I think you should add to all bugs that, at least for now, /sdcard is not working
mirco_pa said:
I think you should add to all bugs that, at least for now, /sdcard is not working
Click to expand...
Click to collapse
Check mnt directory for sdcard,most probably needs to linked.
Sent from my rk30sdk using Tapatalk HD
which one I need to download ?
VocaloidBoy said:
which one I need to download ?
Click to expand...
Click to collapse
Latest
VocaloidBoy said:
which one I need to download ?
Click to expand...
Click to collapse
the latest
@DevSwift1 is there a place where we can read the daily changelog? It would be useful!
TeamCanjica, Hi just wanna help here,
The same problem of missing OMX drivers was there for the Zte Blade, The solution of which is found by developer KonstaT. check out this link:
http://www.modaco.com/topic/359832-devrom145-cyanogenmod-101-android-422/
Glad if i helped!! and Keep up the good work!!
samuelrf said:
take a look to your pm please
Click to expand...
Click to collapse
nothing error,whn copy the META-INF in privious post into
cm-10.1-20130625-NIGHTLY-kumquat and replace..nothing error and no take permission..sory for my bad english
BlueHack said:
i already read and test this method and it won't work :c
Click to expand...
Click to collapse
these rar file ,ok open in rar and extract on desktop,,and zip file of rom open and replace meta info and then achive to zip and copy on ur memorycard and then flash without any permission..sory for my bad english
Paul L. said:
Please discuss NON dev related things at http://forum.xda-developers.com/showthread.php?t=2334423
OTHERWISE, I WILL HAVE TO CALL A MODERATOR HERE, GET A NICE READ OF XDA RULES
Click to expand...
Click to collapse
Please stop spamming this thread and do what OP has kindly told.
Sent from my Xperia U using xda app-developers app
samuelrf said:
it's disabled, it blinks but i don't know why :'(
Click to expand...
Click to collapse
You are on a ENG build, this is force-enabled, you can't disable it
Later we will upload a USERDEBUG build, that should make red lines gone (along with the extra debugging)
nirajkaushik said:
why does the phone hard-brick after rebooting?
I'm even unable to take screenshots and after flashing the rom it says installation aborted, that means some files are not flashed properly...
Click to expand...
Click to collapse
with hard-brick you mean...you're now using it as a doorstop?.
Please people, just DON'T go ahead and flash WITHOUT READING THE FIRST THREE POSTS
No internal storage means...screenshots can't be saved, want to take a screenshot?
You need adb on linux, or adb and ffmpeg on Windows.
adb pull /dev/graphics/fb0 fb0
ffmpeg -vframes 1 -vcodec rawvideo -f rawvideo -pix_fmt rgb32 -s 480x854 -i fb0 -f image2 -vcodec png image.png
sv2hqx said:
i was waiting from a answer from devs or someone who tested
i need bt ....most on the way so i work headset
thanks anyway
Click to expand...
Click to collapse
No, bluetooth doesn't work, yet.
Why? well, we need to FIND the actual bluetooth UART Port, once that's is found (it's somewhere in init the files), we just need to add it in the bluetooth configuration files (they are the same in S Advance), compile, and done
Why I haven't done it yet? I'm repairing my computer (my actual Quad-Core computer, not the slow Single core with 1GB I'm using now). And also, I don't have the device so it needs to be tested by DevSwift first
***ABANDONED***
I am sorry but I stopped supporting this kernel because I don't have much time recently.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is first custom kernel for Xperia Z4 Tablet SGP712/SGP771.
Download
Download from official website
How to root
See my blog post:
https://androplus.org/Entry/626/
I won't create kernel for device which I don't own.
If you want me to create, please give me the device.
Donate:
PayPal
XDA:DevDB Information
AndroPlusKernel for Z4 Tablet, Kernel for the Sony Xperia Z4 Tablet
Contributors
AndroPlus, Tommy-Geenexus, DHGE, dl12345, andip71, nilezon
Source Code: https://github.com/AndroPlus-org/android_kernel_sony_msm8994
Kernel Special Features:
Version Information
Status: Testing
Created 2015-08-02
Last Updated 2017-05-04
Features and changelog
I won't answer questions or requests for older version (e.g. "Please update kernel for old firmware!")
Moved to here
SONY has a 28.0.A.7.31 under "Android Downloads"
Have not found a changelog yet.
DHGE said:
SONY has a 28.0.A.7.31 under "Android Downloads"
Have not found a changelog yet.
A device tree is in the attachment.
Click to expand...
Click to collapse
Oh I meant set of files such as "android_device_sony_karin" or "android_device_sony_msm8994-common". (you can see some device tree for other devices on cyanogenmod's Github)
This is also called device tree.
@AndroPlus:
Hello, I'm seriously considering to buy this device but first I want to make sure (before buying a new tablet) that (a) it supports root (which obviously you were able to do) and (b) to support linux running on the device's framebuffer.
Since running linux on my 10 inch + tablets has become a 2nd nature to me (tablets make some of the best netbooks, being so light and battery-efficient compared to regular netbook) may I venture a suggestion?
Can you try enabling the config_VT on the kernel's option (i.e. the Virtual Terminal feature)? I know some devices to be unbootable after enabling that feature, others do boot. I mean I would be happy to try it myself, but for that I would need to buy the device first, and I much prefer to have a confirmation first.
So yeah great work there (creating the first custom kernel et al). Enabling a single feature would -at worse- cause a boot loop, so I'd guess it would be an easy experiment to do (in case of bootloop you just reflash a "proper" version of the kernel).
Thanks.
Code:
# Character devices
#
CONFIG_TTY=y
# [COLOR="Red"]CONFIG_VT is not set[/COLOR]
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
# CONFIG_LEGACY_PTYS is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
# CONFIG_N_GSM is not set
# CONFIG_N_SMUX is not set
# CONFIG_TRACE_SINK is not set
CONFIG_DEVMEM=y
CONFIG_DEVKMEM=y
I do not have the time ATM to test VT.
When I have the itch to work in terminal mode I either use adb from my Debian box or the app "Terminal Emulator".
What would VT give us more?
I'd like (as a challenge, not too useful) to port Perl 5.22 to the device and some tools...
But that should be possible with my above mentioned terminals at hand.
I have disabled SONY's RIC and that prevents the bootloops when fiddling with the configuration.
No guaranty for CONFIG_VT though.
Next thing I will try (not this week I suppose): work with the latest ..31 version from SONY and try to enable SELinux again. AndroPlus used my sources and with "his" kernel SELinux is disabled - necessary for me in rooting in the first attempt but I'd like to have SELinux again (stagefright etc.)
Virtual Terminal gives us the chance to output whatever image "we wish" directly to Android's framebuffer.
To make a longer story short, it lets us run Linux on a chroot environment almost natively.
The alternative to that would be running a whole X-server on top of Android or -worse- establish a VNC connection to the chroot environment. In both occasions running a (Desktop) linux distro would be a pain both for every-day use purposes but also kill the battery.
So -yeah- enabling the VT feature lets us -basically- turn our android tablet into a linux tablet with a press of a button (a script that starts the chroot environment and outputs to android's framebuffer) and then back to android through a second script.
I find the concept of Android/Linux netbooks/tablet very appealing as unlike Surface pro it lasts a longer (battery wise), it's half the weight and much better for tablet purposes.
Anyway testing VT would be a godsend (just see whether it boots at least). If it does boot I will buy the tablet in a heartbeat, and probably even write a guide of how to turn it into a full featured Linux machine with the press of a button (without having to dual boot)
I'll try to build config_VT enabled kernel.
For ric problem, maybe this commit works, so I'll try this.
https://github.com/fxpdev/android_k...mmit/a1223a90286f3a59eadb82c709c8d3c427e7bb78https://github.com/fxpdev/android_k...mmit/a1223a90286f3a59eadb82c709c8d3c427e7bb78
maybe this commit works
Click to expand...
Click to collapse
This is straight disabling RIC.
Fine but when I went this route my device bootlooped. I suppose because RIC-calls are hardcoded into SONY's init binary and we do not have the source for that.
So my "solution" was just to patch the calls to RIC and give OK on every call.
When AOSP sources will be available we have a modifiable init and you get your device tree.
@Stevethegreat
It booted successfully after adding CONFIG_VT and patch to arch/arm64/kernel/setup.c.
https://github.com/AndroPlus-org/an...mmit/18db9f30bc60bdb5ec0e91826e1ebba313b762a0
How do I check if it really works?
AndroPlus said:
@Stevethegreat
It booted successfully after adding CONFIG_VT and patch to arch/arm64/kernel/setup.c.
https://github.com/AndroPlus-org/an...mmit/18db9f30bc60bdb5ec0e91826e1ebba313b762a0
How do I check if it really works?
Click to expand...
Click to collapse
Wow those are great news. Thanks!
A quick way to check if it worked is to open Terminal emulator. Then navigate to dev/graphics and make a mental note of the different fb files that exist in that folder (for example fb0, fb1, etc)
When you do that you simply type "su" (to gain super user access) and lastly:
cat /dev/urandom > /dev/graphics/fb0
If all goes well you should get a flashing screen or even a solid screen with urandom's gibberish on top of the screen (a screen fillled with characters). You should *not* get "static" (non specific image) or an error code, really. After trying fb0 , please try the rest of FBx that you found in /dev/graphics. At least one should work as above (generally fb0 does).
Once again thanks man, much appreciated. If all goes well, I'm buying this tablet
I built a new kernel from the 28.0.A.31 sources with SELinux enabled (Yeah!! :laugh.
On a second run I set CONFIG_VT=y.
cat /dev/urandom > /dev/graphics/fb0
Click to expand...
Click to collapse
gives:
tmp-mksh: ... No space left on device
attempting to write on fb2 (three framebuffers 0-2) gives No such device
So no sport here ...
Hmmm pity :/.
Hope you ran the command as a super user.
Also maybee trying it w SeLinux in permissive may give different result.
Still I may buy the tablet annyway. As long as it boots with VT on I may find a way to make it work once I have it in hand...
yes I used the root account
I really like the tablet:
http://forum.xda-developers.com/showpost.php?p=62033395&postcount=17
Was fortunate to get it for 465 EUR, otherwise I'd have used my Tablet Z longer.
DHGE said:
yes I used the root account
I really like the tablet:
http://forum.xda-developers.com/showpost.php?p=62033395&postcount=17
Was fortunate to get it for 465 EUR, otherwise I'd have used my Tablet Z longer.
Click to expand...
Click to collapse
Since I'm very much interested, where did you find it (selling it) at 465 Euros? Everywhere I look is close to 600 Euros (shipping included) and that's kind of too much.
edit: sorry for the off-topic, I just remembered that this thread is about the OP's kernel, not our discussion (still PM me the answer if you wish, thanks).
I use this way to disable RIC:
CONFIG_SECURITY_SONY_RIC=n
I did diff command to check what files are changed in 28.0.A.7.31 and... no diff
Well I uploaded v2, now kernel has some new features such as KCAL and CPUQuiet.
I could build TWRP from source but it didn't boot, so I need to brush up my dirty device tree...
I compile a dtbtool from this git: https://github.com/scotthartbti/android_device_common_qcom.git
and use this command: dtbtool --force-v2 -o dt.img -s 2048 -p scripts/dtc/ arch/arm/boot/dts/
thus I have made a dt.img for my xperia z4
I tried to build TWRP and build succeeded, but didn't boot
here's last_log
kitakami device tree
https://github.com/AndroPlus-org/android_device_sony_karin
I could build and boot Cyanogen Recovery (useless...):
Download
If someone want to try useless recovery, enter into fastboot mode and type
Code:
fastboot flash recovery cmr.img
then reboot and hit power key when LED turn on.
[UPDATE]
OK, TWRP now boots!
...but no touch input:crying:
Build from official source didn't boot at all, and this multi-language fork boots.
Recap please
I've been following this thread intrigued for about a month, as long as I've had the tablet. I see that people have been successful in getting their tablets rooted and even gotten TWRP to work on some of them.
What I'm interested is getting simple instructions on how to get root access and of course TWRP would be a big plus since I'm using it on my phone
So, since the Pixel and newer Nexus devices are now getting their Oreo updates, I think it's time that we, the developers who still own Nexus 6's, to look into porting Oreo to this device. I am looking into the source code as we speak for feasibility. If anything, I will probably do like I have done with most of my devices in the past, forge the path and create a guide, and let everyone else do the creative stuff. I just happen to like stock Android.
There is already one dev who got Oreo to boot on the Xiaomi Mi 3, runs on SD800 (32bit)
konradit said:
There is already one dev who got Oreo to boot on the Xiaomi Mi 3, runs on SD800 (32bit)
Click to expand...
Click to collapse
Looking promising,fingers crossed
Sent from my Nexus 6 using Tapatalk
There ARE people working on Android O port, even back when it was still in developer preview status. You'll see releases whenever they are ready, I'd give it a few weeks or months.
I won't argue if you're a developer or not, I'm sure you are. But you are not a "recognized developer". Your title is member
Dopamin3 said:
There ARE people working on Android O port, even back when it was still in developer preview status. You'll see releases whenever they are ready, I'd give it a few weeks or months.
I won't argue if you're a developer or not, I'm sure you are. But you are not a "recognized developer". Your title is member
Click to expand...
Click to collapse
Getting it to build is easy. Ive already done as much but without updated binaries (which I havent seen for any device) it wont boot. There are likely some kernel changes needed as well though I havent dug to much into that yet. Then there is the whole GApps for Oreo issue. I would say we are definitely a week or so away from anything working.
Things are in the works and if gapps don't work for 32 bit.. I suggest you gentlemen familiarize yourself with microG
I built it from developer preview 2 a couple months ago. Booted and everything, but nothing as far as any of the radios worked. I had to modify franco kernel to get it there, but it did work..
I tried re-building it after the stable source dropped and can't seem to get passed this error:
frameworks/native/include/gui/IGraphicBufferProducer.h:35:10: fatal error: 'hidl/HybridInterface.h' file not found
The file is there and where it should be... So I'm kinda scratching my head as to where the switch is that causes it not to pick up that location.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So the development for Xiaomi Mi3/Mi4 has gone online: https://forum.xda-developers.com/xiaomi-mi-3/development/8-0-aosp-t3662028
The source code is not available yet but is on it's way. Maybe there might be hints on what's needed for us to make stuff work on the shamu once the source is online(?). I'm aware they are completely different devices but the architecture are closer as they both are 32bit rather than the newer devices running 64bit.
I was able to get a build to complete but it doesn't boot. I don't have the time today to go over it, but if anyone has some free time, feel free to take a look at the logcat and see if anything jumps out immediately.
boot.log
kkozma said:
I was able to get a build to complete but it doesn't boot. I don't have the time today to go over it, but if anyone has some free time, feel free to take a look at the logcat and see if anything jumps out immediately.
boot.log
Click to expand...
Click to collapse
@followmsi build had a similar issue yesterday on the Nexus 7 2013 forums. I tested the build and it would not get to the boot animation and would restart to the bootloader after about a minute. After returning to TWRP the data partition was either corrupted or unreadable. OP said that it was probably the fact of missing SDcardFS support in the recovery/kernel.
https://forum.xda-developers.com/nexus-7-2013/development/rom-t3569067/page60
the struggle continues.
wavedashdoc said:
@followmsi build had a similar issue yesterday on the Nexus 7 2013 forums. I tested the build and it would not get to the boot animation and would restart to the bootloader after about a minute. After returning to TWRP the data partition was either corrupted or unreadable. OP said that it was probably the fact of missing SDcardFS support in the recovery/kernel.
https://forum.xda-developers.com/nexus-7-2013/development/rom-t3569067/page60
the struggle continues.
Click to expand...
Click to collapse
He is wrong. The sdcardfs is a file system for sdcard enabled devices. Nothing to do with the nexus 6. It was even removed in most other builds for the device. The only people that added it were people that didn't understand what they were doing.
wrongway213 said:
Things are in the works and if gapps don't work for 32 bit.. I suggest you gentlemen familiarize yourself with microG
Click to expand...
Click to collapse
Late reply here.
I have tried MicroG before - on a custom Galaxy S4 ROM - and I like MicroG about as much as I like Xposed. If MicroG is required I won't be upgrading.
wrongway213 said:
Things are in the works and if gapps don't work for 32 bit.. I suggest you gentlemen familiarize yourself with microG
Click to expand...
Click to collapse
People are not gonna do that. Microg is known for causing its own issues.
Strephon Alkhalikoi said:
Late reply here.
I have tried MicroG before - on a custom Galaxy S4 ROM - and I like MicroG about as much as I like Xposed. If MicroG is required I won't be upgrading.
Click to expand...
Click to collapse
zelendel said:
People are not gonna do that. Microg is known for causing its own issues.
Click to expand...
Click to collapse
It's been confirmed that gapps for arm are working since I posted that, so it's a moot point now, thankfully.
zelendel said:
He is wrong. The sdcardfs is a file system for sdcard enabled devices. Nothing to do with the nexus 6. It was even removed in most other builds for the device. The only people that added it were people that didn't understand what they were doing.
Click to expand...
Click to collapse
Oh mate, you're so wrong. SDcardFS is a virtual FS for emulating /sdcard/ (/storage/emulated/0) and EVERY android device has it. It's just a replacement for vFAT (virtual FAT). One of the most important fixes is that the file timestaps won't get corrupted anymore (this bug existed in android for years).
Lawstorant said:
Oh mate, you're so wrong. SDcardFS is a virtual FS for emulating /sdcard/ (/storage/emulated/0) and EVERY android device has it. It's just a replacement for vFAT (virtual FAT). One of the most important fixes is that the file timestaps won't get corrupted anymore (this bug existed in android for years).
Click to expand...
Click to collapse
vfat is a real filesystem for block devices. Think of it as being in between FAT and FAT32. What it adds over FAT is a virtual file NAMING convention in order to exceed the standard "8.3" filename format that FAT was stuck with. vfat is also the NAME of the linux implementation of FAT (FAT12, FAT16), VFAT, and FAT32.
What you are thinking of as being present on "EVERY" android device, is this; https://android.googlesource.com/pl...197870433386fb809d34b58b30fc0/sdcard/sdcard.c
You should pay attention to the README section of it starting at line 32.
When Android devices used to have an actual sdcard, it was formatted using vfat (the linux implementation of FAT32), with a mount point of /sdcard.
When they stopped including real sdcards, they started emulating sdcards using that FUSE simulated vfat I linked to above.
Now what sdcardfs is, is (a) a replacement for the FUSE filesystem I linked to above, and (b) a replacement for FUSE itself. Think of it as a scaled back and simplified FUSE+sdcard.c. The problem with FUSE is that it is too complex and with too high of an overhead. It causes performance degradation. And I'm not talking about the general userspace degradation that you would get with, for example, NTFS-3g compared to a native implementation, but rather the sdcard.c adds some problems because it is actually *abusing* FUSE. FUSE isn't designed or intended to wrap one filesystem with a simulation of a different one. FUSE is intended to actually implement a filesystem proper. What that means is that the kernel performs certain filesystem operations on the FUSE filesystem, which calls back to essentially perform the same operations on the base filesystem (ext4). Double the operations. Also double the caching, which is horrendous because it means that you are storing the same cached file in RAM twice. That is the kind of thing that sdcardfs is intended to solve.
Now personally, I completely disagree with this approach. Sdcardfs (as with FUSE+sdcard.c) is a backwards compatibility layer that really should be removed altogether. Instead, access controls to the data really should be by way of ACLs. Yes, this will break some very old software, but its the right way to move forward.
kkozma said:
I was able to get a build to complete but it doesn't boot. I don't have the time today to go over it, but if anyone has some free time, feel free to take a look at the logcat and see if anything jumps out immediately.
boot.log
Click to expand...
Click to collapse
Well, the first thing that stands out is this;
03-13 02:38:08.029 0 263 W VendorServiceManager: failed to open binder driver /dev/vndbinder
Indeed, the factory kernel does not have any such driver. This is probably something related to "Project Treble", which is supposed to make it simpler to update the android platform while leaving the *vendor* platform unchanged. Sounds like this driver will have to be added to the kernel.
https://android-developers.googleblog.com/2017/07/shut-hal-up.html
There is also this, which happens immediately before the SIGABRT for surfaceflinger:
03-13 02:38:09.975 298 298 F Gralloc2: gralloc-mapper must be in passthrough mode
Code:
Mapper::Mapper()
{
mMapper = IMapper::getService();
if (mMapper == nullptr || mMapper->isRemote()) {
LOG_ALWAYS_FATAL("gralloc-mapper must be in passthrough mode");
}
}
That gralloc issue could be a consequence of the vndbinder issue.
Hmm... https://github.com/SiXROM/platform_device_moto_shamu/commit/86ebb7db1b0a23c4d0a09568a6414d3b9f140596
Note that their changes to the BoardConfig.mk are bogus, none actually apply to this hardware. But the additional PRODUCT_PACKAGES are possibly meaningful.
Might try a build using these three projects;
<project path="device/moto/shamu" name="platform_device_moto_shamu" groups="device,shamu,broadcom_pdk,generic_fs,pdk" remote="sixoreo" revision="oreo" />
<project path="kernel/moto/shamu" name="platform_kernel_moto_shamu" groups="device,shamu,broadcom_pdk,generic_fs,pdk" remote="sixoreo" revision="oreo" />
<project path="vendor/moto" name="platform_proprietary_vendor_moto" remote="sixoreo" revision="oreo" />
sixrom has also made a whole lot of other changes, but I suspect that they are more related to customizations rather than actual device functionality.
I had seen the vndbinder thing the other day and added it to the kernel I'm using. I actually had it booting yesterday, but managed to hose it up trying to fix bluetooth and then ended up losing my boardconfig.mk and device.mk so I have to start over on those two.
I actually tried building with that sixrom repo and it wouldn't boot at all. I suspect it's because it's based on Lineage whereas mine is straight from AOSP.
Getting ready to play around with it some more, hopefully I can get back to a booting rom again!
kkozma said:
I had seen the vndbinder thing the other day and added it to the kernel I'm using. I actually had it booting yesterday, but managed to hose it up trying to fix bluetooth and then ended up losing my boardconfig.mk and device.mk so I have to start over on those two.
I actually tried building with that sixrom repo and it wouldn't boot at all. I suspect it's because it's based on Lineage whereas mine is straight from AOSP.
Getting ready to play around with it some more, hopefully I can get back to a booting rom again!
Click to expand...
Click to collapse
How do you lose your make files? Did you forget to commit them to your git?
Commit often, ESPECIALLY when you have things (anything) working.
Then if you bugger it up, just roll it back, of git diff it to see what you changed.
I don't see any evidence of sixrom being based on anything besides aosp (certainly not lineage/cm)
Take a peek at their manifest, there's a few frameworks that they've messed with, a bunch of applications, but its mostly AOSP;
https://github.com/SiXROM/manifest/blob/oreo/default.xml
Yeah, that was a real derpasaurus moment for me there, but I'm back to a bootable situation.
- Bluetooth is still broken
- No Cellular Radio
- WiFi connects but causes a reboot immediately
- Not able to view anything on the SD Card & Camera asks for an SD card to be inserted. Oddly enough I am able to play the music that's on my sdcard.
I'll get everything pushed up to my github later so if anyone else wants to tinker with it...
They probably haven't pushed the working updates to device to get to where they. As I said, I built directly from their repo and it didn't work at all.
Edit: my github is https://github.com/vwmofo
if you want to put together a local manifest and pull it down, feel free.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With Great power comes great responsibility.
Disclaimer::
Please use this Kernel in accordance with local law and with the privacy of yourself and others in mind. Not responsible for any charges you might accrue, bail money or fines if you choose to use it for unlawful reasons
Warning your warranty is now void. Do this at your own risk. The mad clown is in no way responsible for the chaos, worldwide disease, nuclear destruction, laughing fish, costumed caped crusaders or damage caused to your device by performing the steps involved.
The mad tech clown is back with another Kernel for all of the Kali-linux-nethunter users wanting the portability of kali-nethunter for their Pixel 6 and 6Pro devices codenamed Oriole and Raven .
I now bring you the
Mad-Kali-Maxhunter kernel for raviole
Some of the features include:
-power efficient workqueues
-fsync switch
-boeffla wake lock blocker
-force usb fastcharge
-mm: oom_kill: Reduce some verbose logging
-cpufreq: add cleanslate battery optimizer feature
-/dev/tmp and /dev/tmp/ mount
-full bluetooth support
-Wifi injection
-dvb / sdr support
Plus:
-Everything neeeded to use kali properly on your device plus some systemd stuff
-dns resolver support
-full usb/otg support
See source commits for more
This is not a super fancy pot luck kernel with every allowable feature. This is tuned out quite effeciently and ive found that adding certain features or too many causes heat to rise and we all know thats not good with this device.
Source
GitHub - Biohazardousrom/android_kernel_google_raviole
Contribute to Biohazardousrom/android_kernel_google_raviole development by creating an account on GitHub.
github.com
Download
16.68 GB folder on MEGA
74 files and 20 subfolders
mega.nz
How to Flash:
pre-requisites:
Franco Kernel Manager & root
Download zip to the internal storage of your device.
Open FKM and tap 3 line menu and choose flasher.
Choose manual flash and navigate to the zip file, select it and choose reboot after flash.
Enjoy
For more support
gs101 and gs201 development/support
Pixel 6/pro & 7/pro discussion group for general support and development
t.me
Thanks to
acuicultor
freak07
tbalden
arter97
andip71
for all your development
reserved
Some notes to help you get the Kali-nethunter system set up on your device.
1. Please install the Kali-nethunter magisk modules. These will have the firmwares needed to use the various USB dongles for wifi/bluetooth.
2. Visit this site to download and install the Kali-nethunter store https://store.nethunter.com/en/
3. After installing the store app let it update and then install these 3 apps
-Kali-nethunter installer updater and interface (aka kali-nethunter gui)
-Kali-nethunter terminal
-Kali-nethunter bvnc and kex manager
once installed open the kali gui app and ok any permissions it asks for. it will then force close.
Note:: Since android 12 the gui quit asking for several permissions needed for running scripts in the terminal so you will need to download the attached file kadb.sh to your pc then connect your device to the pc and open a command prompt and run
./kadb.sh
this will grant the missing permissions and allow the gui to open again without it force closing. script was written for linuxed based pc's. if you use windows just open it up and copy and paste the comnands one by one.
or if you have another rooted device you can connect the two via otg and run from the extra rooted device
4. open the gui app once more and navigate to install and start chroot. if you have your own just add the location to the given box when you choose install. for everyone else let the app download it and install from the Kali repository.
Note:: this will take some time please do not exit the app while in the process of downloading or installing
5. to make it easier to enter the kali nethunter terminal app create a custom comnand in the gui. it can be anuthing ls, apt-get update just what ever. then save it to kali and use it when ever you want to use the terminal
Note:: If you want to use the Kex manager/vnc you will need the root password to run programs as root. That password is toor.
Also you can activate wlan0 and wlan1 without a usb dongle. But for some reason it wont allow use of bluetooth without a dongle. i never could find a rhyme or reason for this but i have found when using bluetooth on my pc that kali would not use the built in bluetooth either and i would have to use a dongle. this is probably by design for stealth reasons but dont quote me.
I have found dual wifi and bluetooth adapters in the past and they work simultaneously
This is great! Will it be possible for you to share the kernel build instructions here? I cloned you repo into private/gs-google and ran BUILD_KERNEL=1 ./build_slider.sh -j$(nproc) after that. I do see the kernel files in out/mixed/dist. I flashed them, and it gave me boot loops.
It would be awesome if you could share some build instructions as well.
you can find more info on building kernels here....
Building Kernels | Android Open Source Project
source.android.com
but the steps i took were to initialize and sync the repo listed in the link above. then from there i made my cherry picks. next i went to /arch/arm64/configs and edited the gki_defconfig to match the needed configs i needed for kali linux. after that i ran build/build.sh.
it will error after that because the abi_symbol_allowlist in /android/abi_gki_aarch64_generic file will need updated with the new symbols now compiled in the newly customized kernel.
then after you have corrected all the errors and its built a kernel you will have 4 items to flash..
boot.img
dtbo.img
vendor_boot.img
vendor_dlkm.img
dtbo and boot are flashed in fastboot while vendor_boot and vendor_dlkm are flashed in fastbootd.
but the easiest way to flash is by making an anykernel.zip
also need to point out that some custom roms will not allow you to flash custom kernels so i would hop on tg and ask the maintainer if that rom permits flashing kernels else your gonna have a hard time
thanks for the build @Duhjoker. I managed to flash it on a Pixel 6 and install NetHunter but wifi monitoring mode doesn't work. This is the output from `airmon --debug`
Hey Duhjoker! Thanks for your work on this! Its a dream come true! I just have one question. Is there any chance we will see a pixel 6a version of this kernel with wifi injection? Or is this a pipedream?
evansfromza said:
thanks for the build @Duhjoker. I managed to flash it on a Pixel 6 and install NetHunter but wifi monitoring mode doesn't work. This is the output from `airmon --debug`
View attachment 5705665
Click to expand...
Click to collapse
i am aware of the problem and im looking into it. to be honest i never could get airmon-ng to work on any android.
im thinking monitor mode may need to be enabled first through /sys/ like qualcomm but i could be wrong. this is my first exynos kernel and im having to relearn stuff.
gahndii said:
Hey Duhjoker! Thanks for your work on this! Its a dream come true! I just have one question. Is there any chance we will see a pixel 6a version of this kernel with wifi injection? Or is this a pipedream?
Click to expand...
Click to collapse
I can but i dont own a pixel 6a. The build would have to completely blind but if your willing to test i can try. i did the same for the pixel 3 so it shouldnt be a problem but read next post to see whats up on the current state of building
ok so i dont know whats up with android 13 kernel source but so far none of the builds are booting. ive been at it since release and no go.
but be assured i am working on stuff
Duhjoker said:
I can but i dont own a pixel 6a. The build would have to completely blind but if your willing to test i can try. i did the same for the pixel 3 so it shouldnt be a problem but read next post to see whats up on the current state of building
Click to expand...
Click to collapse
Though I wouldn't mind testing something like that, however would not consider myself a reliable tester. I'm more of a tinkerer honestly. I haven't flashed a rom in 4-5 years haha I gave up years ago on a kernel with wifi packet injection drivers baked in. (for a model I owned) I would not be able to give you solid reliable feedback but id happily try it out for fun. From what ive been reading looks like im staying on Android 12 for a bit longer.
The ramdisk provided by Google for A13 is the issue, you must extract it from vendor_boot and replace it inside prebuilts folder, thanks to freak07 for the solution.
Here's the commit from him.
acuicultor said:
The ramdisk provided by Google for A13 is the issue, you must extract it from vendor_boot and replace it inside prebuilts folder, thanks to freak07 for the solution.
Here's the commit from him.
Click to expand...
Click to collapse
Thank you so much for that. it was driving me crazy and couldnt understand what the problem was.
so now we have kali coming for a13 in a couple days
ok guys Mad-Kali-MaxHunter-Raviole-T for android 13 is now live and linked in op.
I have been researching the wifi monitor mode and packet injection properties on the wlan and heres the state of the driver from my google searches
The bcm4389 wifi 6e client set of chips was announced in 2020 by broadcom and can be found in the Samsung galaxy s21 and google pixel 6, 6pro and 6a models along with some xiaome phones.
For us that means that the drivers and firmware are so new that theres been very little development for it. i myself was only able to find a bluetooth patch that im sure has already been picked up by the google source kernel devs.
from what i can tell of the other drivers by looking at the nexmon github page and further reading the previous wlan modules needed patched firmware to enable airmon-ng.
im still doing research into how to fix this but if anyone has any clues please speak up.
but for now if you should be able to get by using a usb wifi dongle.
Hi, @Duhjoker I was able to install everything successfuly but it seems like the kernel is missing some features not directly related to Kali but that would be nice to add.
HID attack support from Rucky, and ISO usb host from DriveDroid.
I'm using a Pixel 6 Pro on A13
Thanks for your work
Unfortunately, usb wifi dongles aren't working even if they're supported, even after installing their firmwares. Something's wrong with the kernel.
I have good news. Seems google did the hard work for us on hacking the firmware for monitor mode and it looks like we can now use monitor mode to catch packets "NATIVELY".
please read here for the details.
Get BCM4389 into monitor mode for WIFI sniffing
Hey all, I was trying to watch beacon frames transmitted by my access point, but had no capable hardware in my house to sniff it. Or did I? Turns out, Pixel 6 / Pixel 6 Pro can do it. Here's my howto...
forum.xda-developers.com
i havent tested this fully yet but a friend in my tg chat helped me snag the binaries rc files and best of all the firmware.
i dont currently have a magisk module yet but with root copy the vendor folder in the zip to /data/adb/modules pick any module for example
/data/adb/modules/busybox-ndk/system
reboot and enjoy
edit: you made need to chmod the binaries after placing them
deleted
tried that, it doesn't work.
also, wifi dongles are recognized by lsusb but not mounted (airmon-ng only shows phy0 - internal wlan interfaces)