[DEV] CyanogenMod10 for GT-I8190 [WIP] - Galaxy S III Mini Android Development

{
"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

Related

[ROM] [NIGHTLY] [TeamCanjica][UB] Unofficial CyanogenMod 10.1

{
"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

[SOURCES][DEVONLY] CyanogenMod 11.0

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/

[Q&A] [ROM][EXP] AOSP Lollipop 5.0 for Evo 3D - November 12

Q&A for [ROM][EXP] AOSP Lollipop 5.0 for Evo 3D - November 12
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][EXP] AOSP Lollipop 5.0 for Evo 3D - November 12. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Good job! It's looked very sexy :fingers-crossed::fingers-crossed::fingers-crossed:
Awesome!!!
Gapps
Hi, I got a problem with gapps. I tried 4.4 gapps and cyanogenmod 12 gapps. Everytime I boot there is an error saying process *.wizard has failed. Basically all google services fail. So what gapps should I use. Thank you Hahaburger for this rom which works fine without gapps.
flashed
Hi, i flashed this rom earlier today and now I am stuck. when the phone turns on it tells me in a different language then english roughly translated "sorry but wizard application for settings has quit" and when i click OK the same message pops up. it just repeats. when I shut off and enter bootloader using the power and volume down buttons and try to go to recovery to restore the phone just shuts off which i can not turn back on without taking out the battery. HELP ME i am stuck. what can i do to fix this or restore back to a previous build
i did a full wipe, flashed this rom, then supersu.
after that i manually installed some apps via adb.
so far my experience has been very good considering this early stage of development!
its running smooth, no major problems so far, even the flashlight is working (although System-UI fcs when i activate it)
after a full day of light usage (no calls, no sms) only using wifi for chat/mail/browser and installing some apps, i still have over 80% left.
but when i try to call someone i just get an error saying something like "call not connected."
Here is a logcat: pastebin com /ZrbZTGtL
i think the error happens around these lines:
80. Telephony( 752): TelephonyConnectionService: Could not get subId from account: E
115. PhoneInterfaceManager( 752): [PhoneIntfMgr] getIccId: ICC ID is null or empty.
+ some more like the last one
---------- Post added at 07:53 PM ---------- Previous post was at 07:31 PM ----------
here is a logcat of the flashlight crashing System-UI
pastebin com /tsusu00p
i think it has to do with the camera not working yet but here are some errors:
D/QualcommCameraHardware3D( 189): getBuffersAndStartPreview: setPreviewWindow(320 x 240), iTotalBufferCount 5, mIs3DModeOn: 0
E/ ( 133): unrecognized pixel format: 0xf0
E/ ( 133): Format 240
W/GraphicBufferAllocator( 133): alloc(115200, 76800, 240, 00000100, ...) failed -22 (Invalid argument)
E/ ( 133): GraphicBufferAlloc::createGraphicBuffer(w=115200, h=76800) failed (Invalid argument), handle=0x0
E/BufferQueueProducer( 1281): [unnamed-1281-1] dequeueBuffer: createGraphicBuffer failed
E/QualcommCameraHardware3D( 189): getBuffersAndStartPreview: dequeueBuffer failed for preview buffer. Error = FFFFFFEA
Click to expand...
Click to collapse
the funny thing is i can hear the camera making shutter noises, so it's at least doing something with the camera
echs said:
i did a full wipe, flashed this rom, then supersu.
after that i manually installed some apps via adb.
so far my experience has been very good considering this early stage of development!
its running smooth, no major problems so far, even the flashlight is working (although System-UI fcs when i activate it)
after a full day of light usage (no calls, no sms) only using wifi for chat/mail/browser and installing some apps, i still have over 80% left.
but when i try to call someone i just get an error saying something like "call not connected."
Here is a logcat: pastebin com /ZrbZTGtL
i think the error happens around these lines:
80. Telephony( 752): TelephonyConnectionService: Could not get subId from account: E
115. PhoneInterfaceManager( 752): [PhoneIntfMgr] getIccId: ICC ID is null or empty.
+ some more like the last one
---------- Post added at 07:53 PM ---------- Previous post was at 07:31 PM ----------
here is a logcat of the flashlight crashing System-UI
pastebin com /tsusu00p
i think it has to do with the camera not working yet but here are some errors:
the funny thing is i can hear the camera making shutter noises, so it's at least doing something with the camera
Click to expand...
Click to collapse
@HaHaBuRGeR
echs said:
80. Telephony( 752): TelephonyConnectionService: Could not get subId from account: E
115. PhoneInterfaceManager( 752): [PhoneIntfMgr] getIccId: ICC ID is null or empty.
+ some more like the last one
Click to expand...
Click to collapse
Thanks for detailed explanation and logcats . I'm aware of this erros.
I'm trying to debug rild to find problems. Also for camera it seems codec error.
I'll look at that too after mobile data. And I can make calls I don't really know why you can't.
Are you using usim? If you would like to test more please send me a PM.
@HaHaBuRGeR:
i don't know how to find out if i have an USIM. according to some older posts regarding my provider all newer sims should be USIM.
i found some code examples but in most cases CDMA was detected as a USIM and GPRS as SIM.
on the sim card i have the letters UJ, the U should be for a USIM card but i'm not sure.. i'd guess its an USIM.
sms are working fine (sending and receiving).
i could receive calls and they were working fine.
but i still cannot make outgoing calls. USSD codes also aren't working.
btw: i got almost 48hours of uptime with no major errors, it's gonna be a fine rom!
still waiting for data, atm thats more important to me.
oh and i cannot send PMs until i have 10 posts...
Google PlayStore problem
I really like your ROM, have used it for week...
I have the last release - working (call, sms, headphones) ok and fast, but I'm not able to install apss from store (I got unknown error code 972 ).
I used the GApps from here: https://s.basketbuild.com/gapps . Which GApps are recommended for you ROM?
cajda77 said:
I really like your ROM, have used it for week...
I have the last release - working (call, sms, headphones) ok and fast, but I'm not able to install apss from store (I got unknown error code 972 ).
I used the GApps from here: https://s.basketbuild.com/gapps . Which GApps are recommended for you ROM?
Click to expand...
Click to collapse
Weird, I'm using same GApps for testing. Have you wiped your data partition before installing the ROM?
HaHaBuRGeR said:
Weird, I'm using same GApps for testing. Have you wiped your data partition before installing the ROM?
Click to expand...
Click to collapse
Yes, I'did.
I'll try tommorow again (the whole flash process) just to be sure. I don't know how to provide you more info...I'll try to look in syslog.
cajda77 said:
Yes, I'did.
I'll try tommorow again (the whole flash process) just to be sure. I don't know how to provide you more info...I'll try to look in syslog.
Click to expand...
Click to collapse
You can install and use adb to give me logs about errors. Here is a tutorial about how to use it http://forum.xda-developers.com/showthread.php?t=1726238
Unfortunate that this a GSM ROM because I'm on CDMA so I could possibly help out
Sent from my Evo 3D CDMA
HaHaBuRGeR said:
You can install and use adb to give me logs about errors. Here is a tutorial about how to use it http://forum.xda-developers.com/showthread.php?t=1726238
Click to expand...
Click to collapse
Probably the problem was that I used old recovery for flashing (TWRT, CWM), I got some errors. Today I have used the PhilZ Touch from here: http://forum.xda-developers.com/showthread.php?t=2764698 and GooglePlay installing apps seems to be working.
Thanks
Interesting! Seeing I still use my HTC Evo 3D as my daily driver, I'm going to try to work on a L version for CDMA and probably start here.
This would be my first try doing anything ROM related in terms of development, so it'll be interesting for me. I wish you luck in getting this thing into a daily driver on this old device . At least we are not forgotten!
No_file contexts
No_file contexts everytime I try to install it? On latest build It just stays on installing update.. adn nothing happens latest CWM recovery I really want to istall it
When I try to install the SELinux-disabled kernel I get this message in the photo. Is it normal? Flashing finishes OK, but when I reboot I still have no su access. I must mention that I have installed this ROM in dual-boot, so recovery sees my primary ROM environment which is ICS.
{
"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"
}
Sent from my Oppo Find 7a X9007 with rare/no GSM/3G reception
ergün
ergün kardeş bana face adresini versene sormam gereken şeyler varda.
dreccon said:
When I try to install the SELinux-disabled kernel I get this message in the photo. Is it normal? Flashing finishes OK, but when I reboot I still have no su access. I must mention that I have installed this ROM in dual-boot, so recovery sees my primary ROM environment which is ICS.
Sent from my Oppo Find 7a X9007 with rare/no GSM/3G reception
Click to expand...
Click to collapse
I have no idea for dual-boot but we don't need SELinux disabled kernel anymore for using su command. You can just flash superSU's latest version, it works well.

Chronicles of building Android-8.1.0_r15-G8342-Dual

Hello user space,
A couple days ago I decided to take a chance by building AOSP for my G8342 Dual, the experimentation was quite... let's call it adventurous. It all started by firing up my VM, which I currently use to build, unofficially, LineageOS for my Nexus 5. I'd set a side enough space for the VM to cover the LOS build, not remembering the amount space used I was oblivious. I then jumped on Sony dev site, just to find out the XZ1 had been added to the list of unlockable devices, sweet! I backed up my current XZ1 data not sure whether the bootloader unlock would wipe all data, after sweeping the web for more information, it was confirmed that data would be wiped. I should have known because my N5 did wipe data, which I take is a security measure.
Back on the VM, per Sony's dev site, I made sure the necessary packages were installed which was all of them minus maybe one that wasn't. After all this VM builds for another device so it should be 98% complete. With haste, I 'repo sync'd that bad boi, and 'repo_update'd and on to the 'make -j4'. Little did I know, I had space issues. Remember that space issue up there?^^ It came to haunt me later, like 78% building complete later. :/. #$%^&(* I created a new VM with more space for both N5 builds and Xperia. The build was completed successfully, 3.xx-hrs later.
AOSP was manageable on the N5 with Google proprietary vendor files, etc. But this XZ1 is just blah.. even with the sony binary(4.4). By the way, without the sony binary(fastboot flash oem *.img) the thing will not boot. I flashed an unofficial gapps package from back in Dec. 2017, which I believe is the only functional(per xda) one for Oreo. Needless to say, the gapps package works.
Here are my issues with the AOSP XZ1: Android-8.1.0_r15
-SIM2 is defunct. I selected option 48 from lunch menu. Option 48 was aosp-g8342-userdebug.
-The camera, I know, DRM is sorta still there, with limits :/.
a.) Noise reduction is nowhere to be found even under good light. This camera has a good f-stop.
b.) HDR? It's there but is it actually performing its best work? No.
c.) Camera focus at close range, under a foot? Problematic or mostly nada on screen tap.
-A minor change: screenshot capture is now Volume down + power button. Aosp style!
Non-issues:
-Its plain vanilla, flat as a soda that's been seating out open all day.
-Because I built a userdebug version, root is automagically embedded.
https://source.android.com/setup/building#choose-a-target
Code:
You take on the responsibility of your device. Backup your data because the images will wipe everything.
=============How to flash=============
Get a copy of the latest binary here: software-binaries-for-aosp-oreo-android-8-1-kernel-4-4-yoshino
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_<release version>_<platform>.img
====================================
===============8.1.0_r20==========================
-Grab a copy of this aosp-g8342_dual-userdebug:
AOSP_Android-8.1.0_r20_G8342_Dual.zip
-Grab a copy of this aosp-g8341_single-userdebug:
AOSP_Android-8.1.0_r20_G8341_Single.zip
===============8.1.0_r20==========================
Here are a few screenshots:
{
"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"
}
perhaps it was a nice story to tell.... have a nice day xda.
Hello. Nice story. I have the single Sim version so I don t know if this will work, but have you had a chance to check the fingerprint sensor? Thanks
Can u build g8341 aosp?
emyjojo said:
Hello. Nice story. I have the single Sim version so I don t know if this will work, but have you had a chance to check the fingerprint sensor? Thanks
Click to expand...
Click to collapse
It will not work with single sim. Yes I have checked the fingerprint even registered two of them. I've attached some pictures for you to see.
dcrin3 said:
It will not work with single sim. Yes I have checked the fingerprint even registered two of them. I've attached some pictures for you to see.
Click to expand...
Click to collapse
That's great news, as it was not working in the previous builds. Would you have the time to build a version for the single SIM model? Would like do give it a shot.
Thank you.
AOSP_Android-8.1.0_r15_G8342_Single
emyjojo said:
That's great news, as it was not working in the previous builds. Would you have the time to build a version for the single SIM model? Would like do give it a shot.
Thank you.
Click to expand...
Click to collapse
You know I just realized that my Dual device is not listed on the Supported devices and functionality page.
The XZ Premium has a dual edition listed but not the XZ1, I wonder why.
Well that makes some sense now.
Code:
Please be aware that I've not tested this package as I do not have the device(You take on the responsibility). Backup your data because the images will wipe everything.
Here is the single version:AOSP_Android-8.1.0_r15_G8341_Single.zip
You let me know if its at least fingerprint and sim1 functional.
see ya.
dcrin3 said:
You know I just realized that my Dual device is not listed on the Supported devices and functionality page.
The XZ Premium has a dual edition listed but not the XZ1, I wonder why.
Well that makes some sense now.
Here is the single version:AOSP_Android-8.1.0_r15_G8342_Single.zip
You let me know if its at least fingerprint and sim1 functional.
see ya.
Click to expand...
Click to collapse
Hi fingerprint is working rom boots fine thank you
yoyoyed said:
Hi fingerprint is working rom boots fine thank you
Click to expand...
Click to collapse
What do you think of its vanilla-ness? its tooo plain no?
dcrin3 said:
What do you think of its vanilla-ness? its tooo plain no?
Click to expand...
Click to collapse
I like it for me perfect can you please support this and keep it updated in the future. Thanks
Hello, It works fine for me as well, but we still need to do the trick with Google Play, in order to get it to work. Will test drive this for a while. Thank you for your efforts.
I have a couple of questions.
1: Does the data activate immediately or does it take several minutes to become active upon booting?
2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)
3: Is this package a flashable zip or do we have to install each file seperately via fastboot?
Thanks
N1ghtr08d said:
I have a couple of questions.
1: Does the data activate immediately or does it take several minutes to become active upon booting?
2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)
3: Is this package a flashable zip or do we have to install each file seperately via fastboot?
Thanks
Click to expand...
Click to collapse
Hello,
The data activates immediately upon booting, i do not use google assistant so can't really help about the second point. It is not a flashable zip, you will need to flash each .img via fastboot.
A new thing that I've noticed, the fingerprint sensor is always on, it can unlock the device with the screen turned off.
Hope this helps.
N1ghtr08d said:
I have a couple of questions.
1: Does the data activate immediately or does it take several minutes to become active upon booting?
2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)
3: Is this package a flashable zip or do we have to install each file seperately via fastboot?
Thanks
Click to expand...
Click to collapse
1 For me data working immidiately
2 ok google only on google app
3 package flash via fastboot
And instal gapps is no issue on this rom works fine
Thanks for the replies. The big issue for me is Google Assistant. If I can't use it from anywhere/with the screen off then it's a no go for me. I'm glad I asked this question before I flashed. Going back to stock is always time consuming.
---------- Post added at 12:08 PM ---------- Previous post was at 12:02 PM ----------
yoyoyed said:
1 For me data working immidiately
2 ok google only on google app
3 package flash via fastboot
And instal gapps is no issue on this rom works fine
Click to expand...
Click to collapse
Could you please try something for me? Delete your trained voice from the Google app then retrain it again but when saying the "ok Google" command, say each of the 3 commands from different distances from the microphone, for example the first really close to the phone, second about 1ft away, 3rd about 2ft away. After its retrained please answer back and let me know if there's any difference please.
I really rely on the Google Assistant so I'm hoping we can fix it somehow.
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
I also found this via search...
I opened the Google App and went to Settings in main menu. Then "'OK Google' detection". Then I disabled all 3 OK Google settings ("Say 'OK Google' any time", "Trusted voice", and "While driving"). Then I re-enabled all 3 and it asked me to retrain by saying "OK Google" 3 times (which is weird because I never explicitly deleted the training data). Then "OK Google" seemed to work fine again after Oreo upgrade.
Could you try that if the first one didn't work?
It seems that it was a false positive with the fingerprint scanner, at least for me. After a Day of usage, it says no fingerprint hardware. It works briefly after a reboot, but it stops.
I figured out a partial fix for Google Assistant not working. The only caveat is that it won't work from a locked screen and unlock the phone, but it works from any screen while the screen is on.
This problem that u have can occur if the Google app is not installed as a system app .
So to fix this ,follow the next few steps -
1) Convert Google app into system app using apps like Titanium backup or anything of your preference. (I found that doing this caused a never ending process and it is fixed by simply going to Titanium Backup so permissions then force stop the app.)
2) Using any root Explorer navigate to Root > system > app and search for an app named similar to 'googlesearchbox' and cut the app from this folder.
3) Now Navigate to Root > system > priv-app and paste the app.
4) Reboot and now the problem will be gone
5) Finally go to the app permissions of the Google app then clear the cache and data then reboot.
The problem should be solved and you should be able to retrain the voice commands.
@yoyoyed
"I like it for me perfect can you please support this and keep it updated in the future. Thanks"
I will certainly entertain the idea. I need to start utilizing twrp backup now that the bootloader is unlocked.
It takes too much time to restore this beast to its working condition.
@emyjojo
"Hello, It works fine for me as well, but we still need to do the trick with Google Play, in order to get it to work. Will test drive this for a while. Thank you for your efforts."
I may have a dirty trick to pull that off. I need to spend more time in the android playground, experimenting. You're welcome @emyjojo
@N1ghtr08d
"2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)"
That's a low possibility of it happening but along the same experimenting as above ^^^ it may come through. But I'm not promising.
"3: Is this package a flashable zip or do we have to install each file seperately via fastboot?"
That is possible with me spending more time in the playground.
@emyjojo
"It seems that it was a false positive with the fingerprint scanner, at least for me. After a Day of usage, it says no fingerprint hardware. It works briefly after a reboot, but it stops."
After testing out some of the ideas above I will opt to test the phone(AOSP) for a couple days. I want to see how the fingerprint handles on longer usage scenarios.
thank you all for testing it out.
see ya!
dcrin3 said:
@N1ghtr08d
"2: Does "OK Google" work from any screen as it does on the stock ROM. (I attempted to run a previous build of AOSP on my 8341 and that feature wouldn't work properly and it drove me insane as i use it all the time.)"
That's a low possibility of it happening but along the same experimenting as above ^^^ it may come through. But I'm not promising.
Click to expand...
Click to collapse
Bro, look at the post directly above yours. I solved the issue with Google assistant!
@dcrin3
I have a logcat of the fingerprint failure if it will help:
08:42:26.134 V/FingerprintService(952): request stop current client com.android.systemui
03-21 08:42:26.134 W/FingerprintService(952): stopAuthentication: already cancelled!
03-21 08:42:29.137 W/FingerprintService(952): Client com.android.systemui failed to respond to cancel, starting client com.android.systemui
03-21 08:42:29.138 V/FingerprintService(952): starting client AuthenticationClient(com.android.systemui), initiatedByClient = false)
03-21 08:42:29.164 W/FingerprintService(952): startAuthentication failed, result=1
03-21 08:42:29.780 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:32.176 V/FingerprintService(952): stop client com.android.systemui
03-21 08:42:32.179 W/FingerprintService(952): client com.android.systemui is no longer authenticating
03-21 08:42:32.180 V/FingerprintService(952): startAuthentication(com.android.systemui)
03-21 08:42:32.182 V/FingerprintService(952): request stop current client com.android.systemui
03-21 08:42:32.182 W/FingerprintService(952): stopAuthentication: already cancelled!
03-21 08:42:35.185 W/FingerprintService(952): Client com.android.systemui failed to respond to cancel, starting client com.android.systemui
03-21 08:42:35.185 V/FingerprintService(952): starting client AuthenticationClient(com.android.systemui), initiatedByClient = false)
03-21 08:42:35.210 W/FingerprintService(952): startAuthentication failed, result=1
03-21 08:42:42.948 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:48.287 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:50.184 I/PowerManagerService(952): Waking up from sleep (uid=1000 reason=android.policyOWER)...
03-21 08:42:50.211 E/KernelUidCpuTimeReader(952): Failed to read uid_cputime: /proc/uid_cputime/show_uid_stat (No such file or directory)
03-21 08:42:50.218 V/FingerprintService(952): stop client com.android.systemui
03-21 08:42:50.218 I/DisplayPowerController(952): Blocking screen on until initial contents have been drawn.
03-21 08:42:50.220 W/FingerprintService(952): client com.android.systemui is no longer authenticating
03-21 08:42:50.221 V/FingerprintService(952): startAuthentication(com.android.systemui)
03-21 08:42:50.221 V/FingerprintService(952): request stop current client com.android.systemui
03-21 08:42:50.221 W/FingerprintService(952): stopAuthentication: already cancelled
Very good job, nice to see people caring about bringing stock android to the XZ1.
What about treble generic ROMs? Did u try?
Can't wait to have a official treble Ressurection Remix!

Bank apps (RSA?) crashes on Mediatek MT6795 with Android 5.1 / Gionee E8 | Allview X2

Hello, I need help...
Searched and read a lot of last days, can't figure anything about my problem.
Device:
* Allview X2 Xtreme (Aka BLU Pure XL, Gionee Elife E8, ...)
** Mediatek MT6795 a'ka Helio x10
** 3GB RAM, 64GB internal
* Android 5.1, stock V5894 with security patch: 2016-02-01 (yeah, that sucks), rooted, Kernel: 3.10.72+
* HW X2_Soul_Xtreme_Mainboard_P3.1
* Using Lucky Patcher, AdAway, Busybox... typical apps with root.
The problem; TL;DR
Many banking apps crashes or cannot connect with bank on my device. It's not related with bank, not related with my SIM cards or SDCard. Not even related with userdata or system/boot image on device.
Any other applications which I tried and using over years works fine.
Probably hardware problem, but I can't figure it out.
The problem, whole story
About month ago mBank app (Polish bank) just crashed for me after making payment. I couldn't log in into it after typing pin. I though it's Bank API problem and i just waited 2-3 days, without changes, so I finally I've opened complaint - still they not replied to me!!
Ofc meanwhile I've tried to reset and pair application with account - no luck, still doesn't work.
Strange was that I was able to log on wife's S9+. However I still though it's bank problem with my specified smartphone - maybe IMEI identification or something, made a uniqueness violations or something in their databases or other stupid ideas... I'm also developer, so I have some guesses in my head.
Ofc before crash I did not made any changes in OS, not installed any new app or made breaking changes in configs... typical use. App works over year, sun still shines...
I begin to search on my own:
I was unable to debug or find any logs for mBank app.
My holiday approximates so I was started to thinking about new bank... and then I've tried "Moje ING" (ING Nederlands bank in Poland).. without account there's "demo mode"... tap: "You're device might be rooted bla bla bla. continue". -- "Cannot download data, try again". Hmm... It doesn't work on my phone, strange, because on wife's works.. damn.
Yet another application: "IKO" (PKO Polish Bank app) and demo works well. Uff... quite soothing... but it's demo, w/ever. Maybe ING app is broken on roots (S9+ wife without root).
Another app: "Kantor walutowy Alior Bank" (Alior's Bank Exchange)... crash just on start, however on that app I was able to tap "send report", and then what I saw in stacktrace: "Runtime Exception: Not able to create key". Sh1et, that's bother me totally.
I've decompiled class with that thrown, not analyzed it to much, but package is related to RSA and KeyPairs generators.
I've finally installed only other OS available to my device: CM 13 on Android 6. On clean system "Moje ING" not even start and it crashes, same with Alior's Bank. I was unable to test mBank app, because on that cook audio not works... (Polish banks make's call on app pairing with account - I wont hear IVR). Maybe I'll try to switch SIM card to other device and try that...
Strange researches or needles:
* lot of logs files like:
Code:
[email protected]_Soul_Xtreme:/data/system/dropbox # [email protected]
-- encrypted base64 binary or something, not sure what's that, but looks like google service...
My custom build.props over stock
Code:
ro.config.media_vol_steps=35
debug.sf.nobootanimation=1
ro.ril.enable.amr.wideband=1
ro.config.vc_call_steps=9
ro.config.hw_quickpoweron=true
debug.performance.tuning=1
ro.HOME_APP_ADJ=1
What did I tried
* Wiping data, even internal storage, dalvik, cache partition. Formatting /data
* unrooting
* changing app permissions, reverting ad blocks
* I've compared clean /system image with that on my device with hope that some binary corrupted... nope
* also compared BOOT with clean stock, no diffs
* eject SIM cards, SD Card
* flashed clear stock V5894 system, recovery and boot
* flashed only one other OS for that device: CM13 Android 6
* installed current open gapps
* read logcat and other logs with no inspirations
* cleared protect_s and protect_f... dropped SIM card support, but doesn't change anything, rebooted
* tried some other bank apps, nothing new and strange, I think demo modes work on mocks -- will try other sometimes
* wiped data and system: aliors bank app starts on CM13, need to try pair it with account
* replaced bunch of keystore binary from other 5.1 roms, 2-3 of them somehow works, but without whole success
* commented keystore / mobicore services from boot img - crashes on lockscreen / security settings
* compared partitions expdb frp lk para proinfo seccfg secro tee1 tee2 does they changed last day, nope, they wasn't... however I'm not forget about them
* made an app that tries to generate keypair on loop without success, tried to debug android.security packages
* flashed tee1 partition from mobicore.bin E8_amigo3.1.1_T3035.zip , E8_amigo3.1.12_T3149.zip, V5403_66d0c1f4c2dfe8abab357b3d5e6550bb.zip, V5894_160707_gn_system_update_ota.zip, compared with my readback
* tried to Android encrypt, but it nothing happened after reboot - probably bcuz changed recovery / not diggin more about that
* ...?
Stacktrace's
Alior bank:
Code:
java.lang.RuntimeException: Not able to create key
at pl.alior.c.c.a.a.c.a.a(Unknown Source)
at pl.alior.c.c.a.a.a.a(Unknown Source)
at pl.alior.c.c.a.a.a$1.run(Unknown Source)
(if any one what to help I'll upload apk), screenshot:
{
"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"
}
Moje ING
(crashed on CM13 if I good remember, probably other, not related problem, gonna try again)
Code:
java.lang.UnsatisfiedLinkError: com.guardsquare.dexguard.runtime.detection.RootDetector
at pl.ing.mojeing.utils.ja.b(SourceFile:2)
at pl.ing.mojeing.payment.hce.l.k(SourceFile:6)
at pl.ing.mojeing.utils.t.i(SourceFile:1)
...
Not tried, but I will:
- readback, change or do anything with preloaders RSA generation on what about I read here and I thing there might be some problem, but I can't find instructions how to do that / not enough experience right now. I've found that on tee1 and tee2 there's somekind "Crypto Driver, Build Feb 12 2015, 17:12:18 CR: t-base-Mediatek-MT6752-Android-302A-V006-39_39 "
- change IMEI, BT or WIFI MAC and any other identification numbers
- any ideas?
...
- finally I'll throw that brick**** f%$#ng mediatek furnace and buy something good.
Ok, I'm sure whats broken, but currently don't know how to handle/fix it.
My AndroidKeyStore which is hardware optimized in Allview X2 Xtreme is currently broken,
Proved with apps:
* andOTP great app which able to select what kind of store you want to use -- It crashes just after setting Android KeyStore:
Code:
java.lang.IllegalStateException could not generate key in keystore
I've found some other banking apps which probably use it and also crashes,
(Also made a second topic more specified to the device with suggested banking apps: https://forum.xda-developers.com/pure-xl/help/readback-tee1-tee2-partitions-help-t4020253 )
Today I was able to get same error "could not generate key in keystore" with Nest Bank's application (god bless differently handled exceptions each bank app...)... so I'm sure right now.
* Alior Bank (on sending report, other functionality works ;O ) - https://play.google.com/store/apps/details?id=pl.aliorbank.aib
* Alior Bank Kantor Walutowy - https://play.google.com/store/apps/details?id=pl.alior.mobile.exchange.prd
* Moje ING - https://play.google.com/store/apps/details?id=pl.ing.mojeing
* Nest Bank nowy - https://play.google.com/store/apps/details?id=pl.nestbank.nestbank
As I read changing security settings (unlock for swipe, pin, other sh1t) should force somekind of change on the store, but that's not happening in my case.
I'm gonna try to do that with CM13, however apps looks like they're works fine on it so maybe our handicapped ported rom isn't even support HAL / hardware chip/module responsible for the crypto. Ok, I checked: CM13 applications work fine, andOTP is also able to use store with Hardware optimization. Setting finger/swipe/pin to unlock gave me option "Clear all certificate data"... however it freezes: on changing security or on clear attempt.
I've found some code snippets for java on stackoverflow which might help / will find now some apps which might "move" my store or do whatever just to bump it...
Any advice, please?
____
seo tags: could not generate key in keystore, AndroidKeyStore, HAL cryptography, Android TEE, Trusted Execution Environment...
Finally after many many hours I have... only a workaround, but it's better that nothing :F
I've changed names for two libs:
Code:
/system/lib/hw/keystore.mt6795.so
/system/lib64/hw/keystore.mt6795.so
After reboot without with any errors or warnings android changed it's Cert Storage to /only software supported/.
Bank apps began to work after wiping it's data and re-pairing/re-activating... however it's not solution for me: on rooted device software based security storage it's too weak....
"Moje ING" still doesn't work and can't download data, however is unit specified problem - other test-cases works.
Still I've not figured out why CM13 (with Hardware Support) works well on my device.
Might be newer Android / Kernel / Dedicated HAL support included in Android 6.0. To much differences, I can't find that point vs. 5.1 stock.
I have almost gave up last days...

Categories

Resources