{
"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 LineageOS 14.1 for w7. The builds are very very experimental and it is recommended to NOT use this as daily ROM.What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Video Playback
Audio
Sensors
Camera
What's not working :
Everything is working, if you have any bug, report it with logs.
Instructions :
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Reboot
Downloads :
Builds: https://www.androidfilehost.com/?w=files&flid=146209 (Make sure to have lastest TWRP)
Google Apps: http://opengapps.org/
Credits :
Quarx
GrinningFerret
mosimchah
Me
CyanogenMod Team
Contributors
SlimShady's
GrinningFerret
Source Code: https://github.com/Nougat-w7
ROM OS Version: 7.1.1 Nougat
Version Information
Status: Beta
Created 2016-10-05
Last Updated 2016-10-05
Bug reports are welcome but make sure to include proper descriptions and logs(or screenshots if necessary)! ?
I have cm 14 from September, can I dirty flash this latest one?
D1358531 said:
I have cm 14 from September, can I dirty flash this latest one?
Click to expand...
Click to collapse
We'd highly recommend you to flash it clean, but of course you can try it.
GrinningFerret said:
We'd highly recommend you to flash it clean, but of course you can try it.
Click to expand...
Click to collapse
Thanks...I'll let you know if it works
No problem dirty flashing.
I'll wait until camera will work .
I've tested it for couple of days and it's really smooth , it brings new life to the L90 .
Ok i've seen some battery drain ,but it's ok , this builds are still experimental .
Great Work .
Thank you guys for doing this. The rom installs fine on a D405n. The camera doesn't work as you said, but I can't get the bluetooth to work either. Here's some logs:
Code:
10-06 17:55:03.712 18367 18367 E BluetoothVendorJni: register_com_android_bluetooth_btservice_vendor:
10-06 17:55:03.760 1358 1563 D BluetoothManagerService: Message: 20
10-06 17:55:03.760 1358 1563 D BluetoothManagerService: Added callback: [email protected]:true
10-06 17:55:03.764 18367 18367 I BluetoothVendorJni: classInitNative: succeeds
10-06 17:55:03.764 18367 18367 D BluetoothAdapterState: make() - Creating AdapterState
10-06 17:55:03.768 18367 18367 I bt_btif : init
10-06 17:55:03.770 18367 18382 I BluetoothAdapterState: Entering OffState
10-06 17:55:03.771 18367 18383 W bt_osi_thread: run_thread: thread id 18383, thread name stack_manager started
10-06 17:55:03.771 18367 18383 I bt_stack_manager: event_init_stack is initializing the stack
10-06 17:55:03.771 18367 18383 I bt_core_module: module_init Initializing module "osi_module"
10-06 17:55:03.772 18367 18383 I bt_core_module: module_init Initialized module "osi_module"
10-06 17:55:03.772 18367 18383 I bt_core_module: module_init Initializing module "bt_utils_module"
10-06 17:55:03.772 18367 18383 I bt_utils: init_soc_type
10-06 17:55:03.772 18367 18383 I bt_core_module: module_init Initialized module "bt_utils_module"
10-06 17:55:03.772 18367 18383 I bt_core_module: module_init Initializing module "btif_config_module"
10-06 17:55:03.772 18367 18383 E bt_osi_config: config_new unable to open file '/data/misc/bluedroid/bt_config.conf': No such file or directory
10-06 17:55:03.772 18367 18383 W %s unable to load config file: %s; using backup.: init
10-06 17:55:03.772 18367 18383 E bt_osi_config: config_new unable to open file '/data/misc/bluedroid/bt_config.bak': No such file or directory
10-06 17:55:03.772 18367 18383 W %s unable to load backup; attempting to transcode legacy file.: init
10-06 17:55:03.772 18367 18383 E %s unable to load XML file '%s': %d: config_t *btif_config_transcode(const char *)
10-06 17:55:03.772 18367 18383 E %s unable to transcode legacy file; creating empty config.: init
10-06 17:55:03.773 18367 18383 E bt_osi_alarm: timer_create_internal unable to create timer with clock 9: Invalid argument
10-06 17:55:03.773 18367 18383 E bt_osi_alarm: The kernel might not have support for timer_create(CLOCK_BOOTTIME_ALARM): https://lwn.net/Articles/429925/
10-06 17:55:03.773 18367 18383 E bt_osi_alarm: See following patches: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/?qt=grep&q=CLOCK_BOOTTIME_ALARM
10-06 17:55:03.773 18367 18383 F libc : system/bt/osi/./src/alarm.c:161: alarm_new_internal: assertion "false" failed
10-06 17:55:03.774 18367 18383 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 18383 (stack_manager)
Can someone port systemui from 14th to cm13?
Star_king12 said:
Can someone port systemui from 14th to cm13?
Click to expand...
Click to collapse
Use themes "Nougat" (Play Store or XDA Labs)
stojmenovski said:
Thank you guys for doing this. The rom installs fine on a D405n. The camera doesn't work as you said, but I can't get the bluetooth to work either. Here's some logs:
Click to expand...
Click to collapse
Will be fixed in next build, thanks
SlimShady's said:
Will be fixed in next build, thanks
Click to expand...
Click to collapse
awesome
Sent from my LG-D410 using Tapatalk
First of all, great job on this ROM! I immediately fell in love with the new UI, and I can't wait to use it as my daily driver!
That being said, nearly all the apps lagged to the point of non-functionality, Bluetooth kept crashing, the SMS app had a weird issue where if you opened an existing conversation, clicked on the textbox to reply, the textbox would disappear and the keyboard would be unusable. About 5 seconds later it would crash. I tried replacing the default app with Google Messenger and that did the same thing. YouTube also (I noticed that was one of the things not working before, so I figured I'd test it out) was stuck loading the home screen for forever. I could open the settings panel but it ignored me when I tried to click on the "search" button. The Camera just gave a black screen (didn't even bother to crash). The Contacts app worked perfect, though.
I was testing on a D415. I'm back to CM13 for now, but I eagerly await the next update!
BellaMay95 said:
First of all, great job on this ROM! I immediately fell in love with the new UI, and I can't wait to use it as my daily driver!
That being said, nearly all the apps lagged to the point of non-functionality, Bluetooth kept crashing, the SMS app had a weird issue where if you opened an existing conversation, clicked on the textbox to reply, the textbox would disappear and the keyboard would be unusable. About 5 seconds later it would crash. I tried replacing the default app with Google Messenger and that did the same thing. YouTube also (I noticed that was one of the things not working before, so I figured I'd test it out) was stuck loading the home screen for forever. I could open the settings panel but it ignored me when I tried to click on the "search" button. The Camera just gave a black screen (didn't even bother to crash). The Contacts app worked perfect, though.
I was testing on a D415. I'm back to CM13 for now, but I eagerly await the next update!
Click to expand...
Click to collapse
Give us logs, bug reports are useless without logs.
mosimchah said:
Give us logs, bug reports are useless without logs.
Click to expand...
Click to collapse
Done. Hope this helps... I did the flag *:W so it grabbed warnings, errors, and fatal errors but the log is like 5,000 lines!!
So what I did while making the logcat, first I tried turning on Bluetooth and waited for the dialog box to appear telling me that Bluetooth kept crashing and asking if I wanted to kill the app.
Then, I replicated the messaging failure. I opened a new thread (because there were no existing threads at that time), starting typing, then I hit the back button to get out of it. Everything was fine up until I tried to click on the box to type some more. Then the box disappeared (the keyboard was still up there) and the app froze and finally crashed.
Also I saw a whole bunch of stuff about the camera crashing so hopefully there's enough information about that.
The bug report (as a .txt file) just barely exceeded the file size limit at 532 kb (the limit is 512) so I compressed it in a .zip file. Hope it helps! Let me know if you'd like me to test anything more - I dug out my mom's old l90 (it's also a d415) so I can test stuff without ruining the setup on my daily driver.
I don't know if I did it right, but I've attached the log taken from SysLog app.
I use ROM Toolbox Pro, and when I went to the root browser, I wasn't able to change any of the permissions. Also, when using CM file manager, I wasn't able to read the external SD card even though I have root access. In my previous post, I attached a log, would either of those problems be seen in the log?
Sent from my LG-D415 using XDA Free mobile app
D1358531 said:
I use ROM Toolbox Pro, and when I went to the root browser, I wasn't able to change any of the permissions. Also, when using CM file manager, I wasn't able to read the external SD card even though I have root access. In my previous post, I attached a log, would either of those problems be seen in the log?
Click to expand...
Click to collapse
Did you clean flash?
mosimchah said:
Did you clean flash?
Click to expand...
Click to collapse
Yes.
D1358531 said:
Yes.
Click to expand...
Click to collapse
Are you using SuperSU? Can you see if it'll work with a different file manager, maybe try solid explorer?
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"
}
What's working
Touchscreen
GPS
Bluetooth
Wifi
Mobile and data
USB Mount
Sensors
Audio and
Rooted
What's not working
Camera
Slow in response, some apps are force closing at the moment (not every time)
And all bugs reported by users
Click to expand...
Click to collapse
Download ::
Beta 2 : Here
Beta 1 : Skipped
Test 1 : Here
Click Our Advert to support
Click to expand...
Click to collapse
• Download the ROM
• Copy the ZIP to Memory Card
• Start CWM
• Make a Full Wipe (factory reset, mount & storage > format /system, advanced > Erase Dalvik cache)
• Start the install
• Enjoy!
Click to expand...
Click to collapse
Disclaimer
I'm not responsible if this ROM bricks your lovely phone. Use it at your own risk!
Support facebook page (Latest News ) : DroidXDA
Screenshot : [Miuiv4]ICS Beta Series
Changelog : Beta 2
Updated to MiuiV4 2.3.23
New Miui Setting
Removed Unused lib
New Libs updated
Based On Latest CM9 Build
More Speed Improvement
I just tested the ROM. Not enough fast for daily usage yet but nice start. Go on guys!
Any screenshots ??? Will the gapps package from CM9 work on this ROM
what is the big difference between this and the one you posted before?
marcolameirinhas said:
what is the big difference between this and the one you posted before?
Click to expand...
Click to collapse
This is an android 4.0 modification named MIUI. For more information see here:
http://en.miui.com/
The one the posted before is cyanogenmods android 4.0. See here: http://www.cyanogenmod.com/
EDIT:
have someone tried performance governor on this rom?
Some testers in the other thread for cm9 reported that with performance governor cm9 is very fast.
.dot said:
This is an android 4.0 modification named MIUI. For more information see here:
http://en.miui.com/
The one the posted before is cyanogenmods android 4.0. See here: http://www.cyanogenmod.com/
EDIT:
have someone tried performance governor on this rom?
Some testers in the other thread for cm9 reported that with performance governor cm9 is very fast.
Click to expand...
Click to collapse
I`m flashing it right now, will report when it`s done
EDIT.
I couldn`t find a governor changing setting in this ROM, but when he loads an app to his memory he can open it very fast.
kemoba said:
Any screenshots ??? Will the gapps package from CM9 work on this ROM
Click to expand...
Click to collapse
Gapps are not necessary, google framework is there by default.
I have removed gmail and youtube, to fit the content in 150mb.
You can install them from market
kemoba said:
I`m flashing it right now, will report when it`s done
EDIT.
I couldn`t find a governor changing setting in this ROM, but when he loads an app to his memory he can open it very fast
Click to expand...
Click to collapse
Sorry you have to sse setCPU or overclockwidget from market
Screenshots
Sorry you have to sse setCPU or overclockwidget from market
Click to expand...
Click to collapse
I have a bit of a problem with Wi-Fi now, i can connect but i have no internet access, same thing hapened last night with CM9 ROM, but in the morning Wi-Fi works great. A lot of apps are force closing, like google search, it force closes when i type a single letter.
wifi not working for me logcat:
Code:
oadcast multicast]>
D/NetworkManagementService( 202): flags <[down broadcast multicast]>
D/CommandListener( 123): Setting iface cfg
D/CommandListener( 123): Trying to bring down tiwlan0
D/CommandListener( 123): broadcast flag ignored
D/CommandListener( 123): multicast flag ignored
E/wpa_supplicant( 2212): Set_key: Wrong Key
E/wpa_supplicant( 2212): Set_key: Wrong Key
E/wpa_supplicant( 2212): Set_key: Wrong Key
E/wpa_supplicant( 2212): Set_key: Wrong Key
E/WifiConfigStore( 202): Error parsing configurationjava.io.FileNotFoundExcepti
on: /data/misc/wifi/ipconfig.txt: open failed: ENOENT (No such file or directory
)
E/wpa_supplicant( 2212): prepare_filter_struct: type=3
E/wpa_supplicant( 2212): prepare_filter_struct: type=2
E/WifiStateMachine( 202): Failed to set country code US
E/WifiStateMachine( 202): Failed to set frequency band 0
E/WifiStateMachine( 202): set suspend optimizations failed!
I/ActivityManager( 202): Process com.android.updater (pid 2148) has died.
D/WifiLocator( 567): Too many cache misses. Need server request. hasLocation=0
noLocation=0 cacheMiss=5
I/System.out( 567): [INFO:2706874]: LogSource: Running flush
I/System.out( 567): [INFO:2706956]: LogSource: Sending payload [bytes=376]
I/System.out( 567): [SEVERE:2706996]: LogSource: AsyncHttpRequestImpl.run(): ex
ception thrown : Unable to resolve host "www.google.com": No address associated
with hostname: java.net.UnknownHostException
I/System.out( 567): [INFO:2706998]: LogSource: Resending com.google.masf.protoc
[email protected]
D/WifiLocator( 567): Too many cache misses. Need server request. hasLocation=0
noLocation=0 cacheMiss=5
E/WifiStateMachine( 202): set suspend optimizations failed!
E/GlsClient-query( 567): requestFailed
I/power ( 202): *** set_screen_state 0
V/AudioHardwareMSM72XX( 129): setParameters() screen_state=off
W/NetworkManagementSocketTagger( 202): setKernelCountSet(1000, 0) failed with e
rrno -2
D/SurfaceFlinger( 126): About to give-up screen, flinger = 0xf918
D/dalvikvm( 202): GC_CONCURRENT freed 870K, 24% free 12309K/16135K, paused 9ms+
17ms
D/LockScreen( 202): current status is Normal, and prev status is Normal
D/PhoneStatusBar( 449): disable: < expand icons alerts ticker system_info back
home RECENT* clock >
D/PhoneStatusBar( 449): disable: < EXPAND* icons alerts TICKER* system_info bac
k home RECENT clock >
D/PhoneStatusBar( 449): disable: < EXPAND icons alerts TICKER system_info BACK*
HOME* RECENT clock >
wifi has bug with this build
Wifi connects but no signal in status bar.
Browser does not work
Mail market other apps can still use wifi.
Sent from my Tattoo using XDA
it start to run better after a while of using and cpu changes! but still more to improve!
dont liked the launcher, but thats my opinion
keep working guys
marcolameirinhas said:
it start to run better after a while of using and cpu changes! but still more to improve!
dont liked the launcher, but thats my opinion
keep working guys
Click to expand...
Click to collapse
Well the point of MIUI is his laucher, and I like it, after the governor change it improved a bit.
I have a few questions:
1. Where can I disable screen off animation, cant find it anywhere in the menus
2. I have opened the torch application once, and clicked the lightbulb icon there and now when i unlock my device lockscreen doesn`t show only a flashlight, and I need to turn off the screen on my device and turn it back on to show a lockscreen, freacking annoying. I have deleted the torch app from /system/app/ problem stays, cleared Torch data and cache still the same
3. Does your device ring when someone calls you, I have deleted a lot of things from /system/app (First thing I do when I flash a ROM) and my device won`t ring, just trying to find out is this a problem with the ROM or I have deleted the wrong thing from my /system/app/
4. Will you fix the bugs on this ROM or this is just proof of concept ?
5. Battery life is too short, any fixes
Thanks
kemoba said:
I have a few questions:
1. Where can I disable screen off animation, cant find it anywhere in the menus
2. I have opened the torch application once, and clicked the lightbulb icon there and now when i unlock my device lockscreen doesn`t show only a flashlight, and I need to turn off the screen on my device and turn it back on to show a lockscreen, freacking annoying. I have deleted the torch app from /system/app/ problem stays, cleared Torch data and cache still the same
3. Does your device ring when someone calls you, I have deleted a lot of things from /system/app (First thing I do when I flash a ROM) and my device won`t ring, just trying to find out is this a problem with the ROM or I have deleted the wrong thing from my /system/app/
4. Will you fix the bugs on this ROM or this is just proof of concept ?
5. Battery life is too short, any fixes
Thanks
Click to expand...
Click to collapse
1. disable window and transition animations under developer options
2. Torch and lockscreen, weird, will remove the app in the next release.
3. Well flash the ROM again, without wiping your data partition,
wipe dalivk cache and reboot that should restore the apps and any issues should fixed
4. Bugs will be fixed as soon as we have a solution
5. Battery issue has been noted, kernel related see my reply in the other thread
(http://forum.xda-developers.com/showpost.php?p=23394736&postcount=55)
i tested the rom yesterday...the interface is great..now i can change between two roms,when i´m bored with one
speed is alright..but could get some improvments.
what means 2.3.2?is it the andriod version?is this rom slower/not so good as the nfinity rom which has 2.3.7?
thanks
So if there are bugs with wifi, can you provide us a version with these bugs fixed or tell us how to fix these bugs?
I found one more bug:
I can't use my headphones. When they are plugged in, music however comes out the phone speakers.
Anyway.. very good work!! Thanks for that!
I have a bug too, in settings teathering, when I try to enter it justs force closes, and it looks like the compass axis is inverted
Successfully ported. Partially working.
Whats working?
-Touchscreen
-Bluetooth
-GPU
-Camera
-Softkeys
-NFC
-Butter
-SDcard
-ADB
-USB
What's not working?
-Audio
-Wifi
-GSM
-libwvm
-More stuffs not working.
{
"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"
}
More Proper Screenshot
Download: http://files.mrks.me/JRN84D_NS.zip (md5: 28e935c14c31f38940b0c9ced0778766)
----------------------------------------------------------------------------------------------------------------------
SDK port by Steve676 (Wifi Working)
http://forum.xda-developers.com/showpost.php?p=28113909&postcount=258 No Gapps
DaXmax said:
Hey guys, i eventually trying to port Jelly Bean on our device, but its a no go, anyone can help here?
Code:
I/Netd ( 9965): Netd 1.0 starting
I/mediaserver( 9964): ServiceManager: 0x40ce2d80
I/AudioFlinger( 9964): Using default 3000 mSec as standby time.
I/CameraService( 9964): CameraService started (pid=9964)
W/AudioFlinger( 9964): findSuitableHwDev_l() loading well know audio hw modules
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d
evice_t**) wrong audio hw device version 0000
I/AudioFlinger( 9964): loadHwModule() error -22 loading module primary
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d
evice_t**) wrong audio hw device version 0000
I/AudioFlinger( 9964): loadHwModule() error -22 loading module a2dp
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d
evice_t**) couldn't load audio hw module audio.usb (No such file or directory)
I/AudioFlinger( 9964): loadHwModule() error -2 loading module usb
E/AudioPolicyManagerBase( 9964): Failed to initialize hardware output stream, sa
mplingRate: 0, format 0, channels 0
E/AudioPolicyService( 9964): couldn't init_check the audio policy (No such devic
e)
E/SchedPolicy( 9964): open of /dev/cpuctl/apps/bg_non_interactive/tasks failed:
No such file or directory
E/BandwidthController( 9965): runIptablesCmd(): failed /system/bin/iptables -t r
aw -N bw_raw_PREROUTING res=256
E/BandwidthController( 9965): runIptablesCmd(): failed /system/bin/ip6tables -t
raw -N bw_raw_PREROUTING res=256
D/MDnsDS ( 9965): MDnsSdListener::Hander starting up
E/Netd ( 9965): Unable to start MDnsSdListener (Invalid argument)
E/SocketListener( 9965): Obtaining file descriptor socket 'mdns' failed: Invalid
argument
I/Netd (10086): Netd 1.0 starting
I/ServiceManager( 72): service 'media.audio_flinger' died
I/ServiceManager( 72): service 'media.player' died
I/ServiceManager( 72): service 'media.camera' died
I/ServiceManager( 72): service 'media.audio_policy' died
I/Netd (10112): Netd 1.0 starting
Click to expand...
Click to collapse
Is this the whole log?
rlasalle15 said:
Is this the whole log?
Click to expand...
Click to collapse
Yes, i already fixed the kernel boot already, thats only the starting, do you want to work together so we can served a working JB till the official one comes?
DaXmax said:
Yes, i already fixed the kernel boot already, thats only the starting, do you want to work together so we can served a working JB till the official one comes?
Click to expand...
Click to collapse
yea I will send you a PM with my gmail addy
I'm not much of a expert but ,
something with audio drivers ? have you tried replacing them
E/AudioFlinger( 9964): int android::load_audio_interface(char const*, audio_hw_d evice_t**) wrong audio hw device version 0000
Click to expand...
Click to collapse
and also check files on bin folder . can't say much without goods on hand unfortunately , doesn't have the bandwidth to download the files right now
Oodie said:
I'm not much of a expert but ,
something with audio drivers ? have you tried replacing them
and also check files on bin folder . can't say much without goods on hand unfortunately , doesn't have the bandwidth to download the files right now
Click to expand...
Click to collapse
yea tons of fmjar edits are in order in addition to the audio files
I'm not good at this part, but one korean developer(jijonheyoni, galaxy s2 korean varient dev) said that this problem can be caused because kernel's library and platform library is not corresponding.....(I'm just translating..)
Sent from my Nexus S using xda app-developers app
ioplkj13 said:
I'm not good at this part, but one korean developer(jijonheyoni, galaxy s2 korean varient dev) said that this problem can be caused because kernel's library and platform library is not corresponding.....(I'm just translating..)
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
yeah , quite possible , since JB kernel is updated ( as i think lookin @ GN's screenshots ) & the kernel should correspond with audio/video drivers
& also there are huge improvements in video & audio in JB even wifi & network i guess .
There are multiple devs for One X and SGS3 that's got a booting and functional port of JB to their devices. You could try contacting one of them.
Sent from my Nexus S using Tapatalk 2
Oodie said:
yeah , quite possible , since JB kernel is updated ( as i think lookin @ GN's screenshots ) & the kernel should correspond with audio/video drivers
& also there are huge improvements in video & audio in JB even wifi & network i guess .
Click to expand...
Click to collapse
The ramdisks arent to much different. There are few new files though. init.trace.rc and init.usb.rc...but other then those its pretty close. Shouldnt we be able to use an ICS boot.img? I could be way off here but we are kinda backporting from a totally different device then what we have. I think a lot of fmjar edits could get it closer.
Have you tried packaging the from with a cm9 kernel, and then simply bring in all libraries, etc. it mentions?
Sent from my Nexus S using Tapatalk 2
treUse said:
Have you tried packaging the from with a cm9 kernel, and then simply bring in all libraries, etc. it mentions?
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Its gonna be a little tougher then that I think. When you bring over all the libs from CM or AOKP then you have to add in all the native methods in fmjar and services jar. I think we are gonna have to strace a lot of this and see what libs are playing nice and what ones arent.
rlasalle15 said:
yea I will send you a PM with my gmail addy
Click to expand...
Click to collapse
ok.
Oodie said:
I'm not much of a expert but ,
something with audio drivers ? have you tried replacing them
and also check files on bin folder . can't say much without goods on hand unfortunately , doesn't have the bandwidth to download the files right now
Click to expand...
Click to collapse
Could be, but the bin is already replaced with the sdk + Gnex's jb bin... And some are still ics because of Nexus S hardware.
rlasalle15 said:
yea tons of fmjar edits are in order in addition to the audio files
Click to expand...
Click to collapse
Neh, Faryaab didn't edit the fm.jar and it worked fine.
ioplkj13 said:
I'm not good at this part, but one korean developer(jijonheyoni, galaxy s2 korean varient dev) said that this problem can be caused because kernel's library and platform library is not corresponding.....(I'm just translating..)
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Oodie said:
yeah , quite possible , since JB kernel is updated ( as i think lookin @ GN's screenshots ) & the kernel should correspond with audio/video drivers
& also there are huge improvements in video & audio in JB even wifi & network i guess .
Click to expand...
Click to collapse
Nope. Kernel doesn't improves anything. It's only the framework.jar and the libs.
rlasalle15 said:
The ramdisks arent to much different. There are few new files though. init.trace.rc and init.usb.rc...but other then those its pretty close. Shouldnt we be able to use an ICS boot.img? I could be way off here but we are kinda backporting from a totally different device then what we have. I think a lot of fmjar edits could get it closer.
Click to expand...
Click to collapse
i edited the ramdisk, so the schedconfig didn't spammed on my log.
Looks like you're either missing libs or you have the incorrect libs in /system/lib/hw
Nope. Kernel doesn't improves anything. It's only the framework.jar and the libs.
i edited the ramdisk, so the schedconfig didn't spammed on my log.[/QUOTE]
What are you porting off of?
tgascoigne said:
Looks like you're either missing libs or you have the incorrect libs in /system/lib/hw
Click to expand...
Click to collapse
I added the power, keystore and timezone? Is that enough?
rlasalle15 said:
What are you porting off of?
Click to expand...
Click to collapse
Stock IMM76D.
twadda218 said:
If you get this up and running it would be a dream! especially since it'll be a daxmax!!!:good:
Click to expand...
Click to collapse
Yer, but i can't confirm to get this working.
Hi,
You are porting Jelly Bean with ICS libs ?
http://forum.xda-developers.com/showthread.php?t=1738197
This guy could help?
Sent from my Nexus S using xda premium
GalaxyUser said:
Hi,
You are porting Jelly Bean with ICS libs ?
Click to expand...
Click to collapse
nope. If i did that, ofc Jelly Bean wont boot.
Looking at the log, it seems like it's missing audio drivers that it is specifically looking for. It looks like the ICS kernels that you may or may not be using is probably missing the specific drivers that Jelly Bean is looking at.
I think it might help if you could maybe port the kernel that was originally compiled for Android 4.1 and ensure that it has the Nexus S drivers instead of the Galaxy Nexus drivers.
This is of course just a hypothesis and I could be absolutely wrong as I'm not a ROM developer.
deltatux
This thread is for the development progress of the Dell Streak 7 running Jelly Bean Android 4.1.2 using Cyanogenmod 10 as the basis.
It is now being moved up a version, from Alpha 0.4 to Alpha 1.0.
This reverts us to the ICS-B4 partition layout. The reason being is that Dell decieded to be different and it causes problems with the sdcard fuse daemon. But switching to this layout, it allowed the sdcard daemon to work correctly and give us more space.
Developers:
giveen - CM10 Port / Kernel Updates
geramy - Sound and other fixes.
DJ_Steve - Sound idea that worked.
Thanks:
Cyanogenmod team - for making the port actually pretty easy
geramy - for all your incredible help getting sound going.
snargledorf - basically rebuilding CM9 for the Dell Streak 7 , to which I was able to base my work off of.
DJ_Steve - for teaching me and all the tips and putting up with my annoying questions
My wife - giving me grace and putting up with the hours I put into this
(oops forgot a couple people)
_motley - for clues onto framebuffers and overlays failing, without him it would have never booted
Borkata - for help with wifi and other little hints.
pengus77 - for helping me fix wifi on CM10.1 (and invertly new changes on CM10 had the same problem)
https://github.com/giveen/android_device_dell_streak7
Alpha v1.1E
Working:
Boots!!!
Touchscreen
Hapatic feedback
External SD
Internal Storage (shows full space, can install apps to it, but you cannot store anything on it)
Power button
Brightness
Root
Capacitive buttons
Bluetooth (audio as well, so far the only way audio works)
WIFI
MTP to external SD
Sound
Headphones - are a bit loud and volume control doesn't always work
Speakers - is a bit quiet and sometimes takes a moment for it to adjust volumes
Not Working:
camera (what do you think I am...a miracle worker?)
GPS (turns on but doesn't lock on)
Sensors
What else doesn't work...I"m still checking it all out.
{
"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"
}
Recognized Donators:
azrael
Mohamad R. (let me know your screen name and I'll change this )
Robert Trier
Bradley F.
Fixed a bunch and it looks like surfaceflinger is segfaulting, will look at tomorrow morning
My errors
E/Netd ( 79): Unable to open quota2 logging socket
init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: using deprecated syntax for specifying property 'sys.usb.config', use ${name} instead
F/libc ( 81): Fatal signal 7 (SIGBUS) at 0x4102f1cc (code=2), thread 146 (SurfaceFlinger)
Cannot load library: link_image[1891]: 84 could not load needed library 'libaudio.so' for 'audio.primary.tegra.so' (reloc_library[1306]: 84 cannot locate
E/AudioFlinger( 84): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
I/DEBUG ( 80): pid: 81, tid: 146, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 80): signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 4102f1cc
D/SensorService( 270): nuSensorService starting...
E/SensorService( 270): couldn't load sensors module (No such file or directory)
W/EntropyMixer( 270): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory)
giveen said:
My errors
E/Netd ( 79): Unable to open quota2 logging socket
init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: using deprecated syntax for specifying property 'sys.usb.config', use ${name} instead
F/libc ( 81): Fatal signal 7 (SIGBUS) at 0x4102f1cc (code=2), thread 146 (SurfaceFlinger)
Cannot load library: link_image[1891]: 84 could not load needed library 'libaudio.so' for 'audio.primary.tegra.so' (reloc_library[1306]: 84 cannot locate
E/AudioFlinger( 84): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.primary (Invalid argument)
I/DEBUG ( 80): pid: 81, tid: 146, name: SurfaceFlinger >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 80): signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 4102f1cc
D/SensorService( 270): nuSensorService starting...
E/SensorService( 270): couldn't load sensors module (No such file or directory)
W/EntropyMixer( 270): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory)
Click to expand...
Click to collapse
attach your init.rc, init.goldfish.rc and init.streak7.rc files, I guess 2 people looking over this could provide more help than just one
See your PM's
Are you guys "teasing" all us Streak 7 owners with this Jelly Bean Rom thread?
ICS just dropped and Jelly Bean...?
What is the difference and is Jelly Bean going to be a easier build if so?
I thought Jelly Bean was just ascetic changes, not a revamp.
Please tell me you are really developing the rom cause I was about to gift it to a friend but now im holding off.... I would hate to indian give it....
Jb has better performance just like every new version of Android. Also a bunch if new features
Do you have an estimated time of when you want to complete this or is it as ling as it takes?
ashyk36 said:
Do you have an estimated time of when you want to complete this or is it as ling as it takes?
Click to expand...
Click to collapse
Don't ask for ETA's.. just be patient and wait like everyone else, we don't provide ETA's as we could have errors or other variables that could influence the completion of roms (from server going down to zombie apocalypse)
Who has Jelly Bean on the Dell Streak 7 booting right now....yeah this guy does.
I'd be interested in seeing if my flash script is stable enough to work on more then my 1 sucessful test flash.
If/when you're willing to seed me a copy to test stuff on my end, I'd be happy to report back on it. But I have a ton of backlog to keep me busy, so take your time.
Oh: I'm still a little confused, do you have a working version of CWM for ICS partitions?
I can blind-port a version if you give me the geometries of it.
(I'd like to see the output from a live system to check against the nvflash config)
Stuck at boot animation...but I can taste those yummy beans.... work on it tomorrow.
giveen said:
Stuck at boot animation...but I can taste those yummy beans.... work on it tomorrow.
Click to expand...
Click to collapse
get a logcat and see what errors are occurring
This isn't my first rodeo. Lol. Logcat will be up in the morning.
Sent from my Nexus 7
as long as we get everything working I guess its all good
Would love for camera to work.
Sent from my Nexus 7
take HS7R8 camera drivers and cross reference wih nexus 7 ones to see if anything is different (other than addressing... unless its the same in which case it may just work)
You'd need the source code for the camera drivers for that to work.
All we have are the binaries for them
Exactly.
Sent from my Nexus 7
Camera was working in froyo to my knowledge why not give the source for that a try? (unless that too is also just binaries)
I thought I might put this on this forum for any of the developers to help out with porting this dialer to other devices
Enclosed in the zip is the files I have obtained from from the Nexus 5 that supports caller-id lookup and business lookup on the dialer. Although the google dialer works, it will not handle calls with the teleservice.apk that is included with CM11. If you make or receive calls with the the google dialer, it will still use the old dialer for call handling, incoming or outgoing. You cannot delete the original dialer because you have no way to answer or end calls.
The biggest reason I decided to make a push for this port is the incoming caller-id business lookup. This will be expanded to G+ information on Caller-ID in January and who knows what's next.
EDIT: New Information as follows:
In the package I've downloaded, Nexus 5 Experience for Nexus 4 and NONE of the MD5's matched the files I have. So, I decided to make a flashable zip of Teleservice.apk and the odex file in system\priv-app and telephonyprovider.apk and the odex file in system/app as well as the GoogleDialer.apk and odex file in system\priv-app.
The Nexus 5 Stock DOES use TelephonyProvider.
Although the com.android.phone hangs relentlessly, HOWEVER!!! I do get a Verizon Wireless' signal until I finish the FC with the "OK" button.
Any help with this? I think I am getting close.
This is what happens if I flash the dialer AFTER I've already established cellular service by flashing CM11, booting into the system, rebooting and flashing the dialer.
Code:
[ 11-23 20:26:56.699 2585: 2585 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.phone, PID: 2585
android.database.sqlite.SQLiteException: Can't downgrade database from version 589832 to 524296
at android.database.sqlite.SQLiteOpenHelper.onDowngrade(SQLiteOpenHelper.java:361)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:255)
at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:188)
at com.android.providers.telephony.TelephonyProvider.query(TelephonyProvider.java:465)
at android.content.ContentProvider.query(ContentProvider.java:855)
at android.content.ContentProvider$Transport.query(ContentProvider.java:200)
at android.content.ContentResolver.query(ContentResolver.java:461)
at android.content.ContentResolver.query(ContentResolver.java:404)
at com.android.internal.telephony.dataconnection.DcTracker.createAllApnList(DcTracker.java:1910)
at com.android.internal.telephony.dataconnection.DcTracker.onRecordsLoaded(DcTracker.java:1257)
at com.android.internal.telephony.dataconnection.DcTracker.handleMessage(DcTracker.java:2139)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5062)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
at dalvik.system.NativeStart.main(Native Method)
This is what happens if I flash the dialer at the same time I flash the rom.
Code:
[ 11-23 15:44:14.477 7986: 7986 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.phone, PID: 7986
java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.SecurityException: Permission Denial: broadcast asks to run as user -1 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL or android.permission.INTERACT_ACROSS_USERS
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4392)
at android.app.ActivityThread.access$1400(ActivityThread.java:145)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1467)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5062)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.SecurityException: Permission Denial: broadcast asks to run as user -1 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL or android.permission.INTERACT_ACROSS_USERS
at android.os.Parcel.readException(Parcel.java:1461)
at android.os.Parcel.readException(Parcel.java:1415)
at android.app.ActivityManagerProxy.broadcastIntent(ActivityManagerNative.java:2382)
at android.app.ActivityManagerNative.broadcastStickyIntent(ActivityManagerNative.java:96)
at com.android.internal.telephony.uicc.IccCardProxy.broadcastIccStateChangedIntent(IccCardProxy.java:344)
at com.android.internal.telephony.uicc.IccCardProxy.setExternalState(IccCardProxy.java:387)
at com.android.internal.telephony.uicc.IccCardProxy.setExternalState(IccCardProxy.java:393)
at com.android.internal.telephony.uicc.IccCardProxy.<init>(IccCardProxy.java:117)
at com.android.internal.telephony.PhoneProxy.<init>(PhoneProxy.java:85)
at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:141)
at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:59)
at com.android.phone.PhoneGlobals.onCreate(PhoneGlobals.java:391)
at com.android.phone.PhoneApp.onCreate(PhoneApp.java:38)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1007)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4389)
... 10 more
I also included a full logcat of each type of instance and the files I am flashing.
http://www.tinozplace.com/moto-kitkat/GoogleDialerProject-NotFlashable.zip
Thanks to anyone getting involved. If you can't help, please at least try to turn some developers onto this post.
I've done a bit of apk reverse engineering before (disassembled smali code and what not). Do you have any background info on what's happening with it now? Crashes at certain points, lockups, or just general "it doesn't do what it's supposed to and there is no feedback"?
djuniah said:
I've done a bit of apk reverse engineering before (disassembled smali code and what not). Do you have any background info on what's happening with it now? Crashes at certain points, lockups, or just general "it doesn't do what it's supposed to and there is no feedback"?
Click to expand...
Click to collapse
Here is what I know so far from my own experiences and research:
- If you flash the dialer alone, it works well.
- If you flash the dialer and the Teleservices.apk (odex too) it will force close or possibly cause a bootloop.
My research:
-Teleservice calls googledialer up to prompt the user to answer the call, includes business caller id, etc.
-TelephonyProvider is a thing of the past with the google dialer.
My decompile showed differences in about 10-15 files and about 10-20 additions/subtractions of smali files to the apk.
I'd be more than willing to give you an adb logcat.
abuttino said:
Here is what I know so far from my own experiences and research:
- If you flash the dialer alone, it works well.
- If you flash the dialer and the Teleservices.apk (odex too) it will force close or possibly cause a bootloop.
My research:
-Teleservice calls googledialer up to prompt the user to answer the call, includes business caller id, etc.
-TelephonyProvider is a thing of the past with the google dialer.
My decompile showed differences in about 10-15 files and about 10-20 additions/subtractions of smali files to the apk.
I'd be more than willing to give you an adb logcat.
Click to expand...
Click to collapse
Ok, i'll see if i can dig into it over the weekend. Man, this is one of the things i miss about safestrap. I always had one slot for testing things like this. Made it a lot more painless.
I'll see about getting it on github and I'll continue to try to get more attention to this thread
EDIT: It's on github...
https://github.com/abuttino/teleservice.apk
First post edited.
abuttino said:
First post edited.
Click to expand...
Click to collapse
More explorations on this..
I tried a ROM with no teleservice.apk, telephonyprovider.apk and googledialer.apk, then installed them once I got into the system. Unfortunately that didn't work to pick cell service back up, and any phone settings I tried just crashed the dialer.
Here is the crash:
Code:
I/ActivityManager( 833): START u0 {act=android.intent.action.MAIN flg=0x4000000 cmp=com.android.phone/.CallFeaturesSetting} from pid 2190
E/AndroidRuntime( 2190): FATAL EXCEPTION: main
E/AndroidRuntime( 2190): Process: com.google.android.dialer, PID: 2190
E/AndroidRuntime( 2190): android.content.ActivityNotFoundException: Unable to find explicit activity class {com.android.phone/com.android.phone.CallFeaturesSetting}; have you declared this activity in your AndroidManifest.xml?
E/AndroidRuntime( 2190): at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1628)
E/AndroidRuntime( 2190): at android.app.Instrumentation.execStartActivity(Instrumentation.java:1424)
E/AndroidRuntime( 2190): at android.app.Activity.startActivityForResult(Activity.java:3423)
E/AndroidRuntime( 2190): at android.app.Activity.startActivityForResult(Activity.java:3384)
E/AndroidRuntime( 2190): at android.app.Activity.startActivity(Activity.java:3626)
E/AndroidRuntime( 2190): at android.app.Activity.startActivity(Activity.java:3594)
E/AndroidRuntime( 2190): at android.preference.PreferenceActivity.onHeaderClick(PreferenceActivity.java:1058)
E/AndroidRuntime( 2190): at android.preference.PreferenceActivity.onListItemClick(PreferenceActivity.java:1030)
E/AndroidRuntime( 2190): at android.app.ListActivity$2.onItemClick(ListActivity.java:319)
E/AndroidRuntime( 2190): at android.widget.AdapterView.performItemClick(AdapterView.java:298)
E/AndroidRuntime( 2190): at android.widget.AbsListView.performItemClick(AbsListView.java:1113)
E/AndroidRuntime( 2190): at android.widget.AbsListView$PerformClick.run(AbsListView.java:2904)
E/AndroidRuntime( 2190): at android.widget.AbsListView$3.run(AbsListView.java:3638)
E/AndroidRuntime( 2190): at android.os.Handler.handleCallback(Handler.java:733)
E/AndroidRuntime( 2190): at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime( 2190): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2190): at android.app.ActivityThread.main(ActivityThread.java:5062)
E/AndroidRuntime( 2190): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2190): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 2190): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
E/AndroidRuntime( 2190): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
E/AndroidRuntime( 2190): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 833): Force finishing activity com.google.android.dialer/.settings.GoogleDialerSettingsActivity
D/wpa_supplicant( 1006): RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c
D/wpa_supplicant( 1006): wlan0: Control interface command 'SIGNAL_POLL'
D/wpa_supplicant( 1006): nl80211: survey data missing!
W/ActivityManager( 833): Activity pause timeout for ActivityRecord{41da0018 u0 com.google.android.dialer/.settings.GoogleDialerSettingsActivity t2 f}
Once I cleared data, the com.android.phone was just relentlessly hanging with the permission problem stated in the main post.
I would hope that some developers are looking at this thread and this helps out.
Don't remember where I found this ( somewhere on xda) but flash this it will keep your regular dialer apk also so you'll see your old one in app drawer too.
https://copy.com/MFw1d
Sent from my MB886 using Tapatalk
tember1214 said:
Don't remember where I found this ( somewhere on xda) but flash this it will keep your regular dialer apk also so you'll see your old one in app drawer too.
https://copy.com/MFw1d
Sent from my MB886 using Tapatalk
Click to expand...
Click to collapse
The dialer also comes with Caller-ID lookup through google businesses (Places) and Google+. This is the purpose of the porting project, to have the dialer "fully functional" instead of just the business search for dialing.
abuttino said:
The dialer also comes with Caller-ID lookup through google businesses (Places) and Google+. This is the purpose of the porting project, to have the dialer "fully functional" instead of just the business search for dialing.
Click to expand...
Click to collapse
You mean this? Correct?
{
"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 MB886 using Tapatalk
Yes. But it doesn't actually function because the telephonyprovider.apk and teleservices.apk only talk to the aosp dialer.
Sent from my XT926 using Tapatalk
Oh got ya I don't think I've even got a phone call since I've flashed this. Sorry thought I could maybe help.
Sent from my MB886 using Tapatalk
If you know of any developers or can do a small social networking outreach (a post on Google+ or Twitter) that would help.
Sent from my XT926 using Tapatalk
It can be ported because Google has got it working on both Nexus 5 and Nexus 4 already. But I really don't know how to do it.
mushan3420 said:
It can be ported because Google has got it working on both Nexus 5 and Nexus 4 already. But I really don't know how to do it.
Click to expand...
Click to collapse
Thank you for at least taking a look at it. I appreciate it.
Do you have any idea of where to start?
Sent from my XT926 using Tapatalk
abuttino said:
Thank you for at least taking a look at it. I appreciate it.
Do you have any idea of where to start?
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
Please compare TeleService.apk in Nexus 4 with Nexus 5. Google has aready did an example porting it from one phone to another.
mushan3420 said:
Please compare TeleService.apk in Nexus 4 with Nexus 5. Google has aready did an example porting it from one phone to another.
Click to expand...
Click to collapse
There are NO differences in the SMALI code, none at all. I compared two bone stock versions from the Nexus 5 and Nexus 4
Here are the differences in the apk.
abuttino said:
There are NO differences in the SMALI code, none at all. I compared two bone stock versions from the Nexus 5 and Nexus 4
Here are the differences in the apk.
Click to expand...
Click to collapse
So the difference is the DPI? OK. Just change the DPI of images, and sign the modified apk with Android Platform Key.
And then, if it still doesn't work, please compare the teleservice.apk from Nexus 4 or 5 with the one from AOSP.
I am not sure if this will help, but please kindly have a try.
mushan3420 said:
So the difference is the DPI? OK. Just change the DPI of images, and sign the modified apk with Android Platform Key.
And then, if it still doesn't work, please compare the teleservice.apk from Nexus 4 or 5 with the one from AOSP.
I am not sure if this will help, but please kindly have a try.
Click to expand...
Click to collapse
I have already compared the Nexus 5 to AOSP and there are at least 10 smali files with differences that add/subtract hundreds of lines of code, and add/subtract serveral DPI files.
Compared the Nexus 5 to the Moto X as well.. About the same amount of difference..
EDIT.
abuttino said:
I have already compared the Nexus 5 to AOSP and there are at least 10 smali files with differences that add/subtract hundreds of lines of code, and add/subtract serveral DPI files.
Compared the Nexus 5 to the Moto X as well.. About the same amount of difference..
EDIT.
Click to expand...
Click to collapse
Ok, I separated the smali files with differences in two folders, one for CM11/AOSP and one for Nexus 5. There were also file count differences. I notated them in a text file as well as the png I just posted.
http://www.tinozplace.com/moto-kitkat/TeleserviceDiff.zip
Thanks for helping!
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 4.4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Huuuge thanks to @xpduyson , @TimSchumi and @wolfenders for keeping the security updates up !
----------| HOW TO INSTALL |----------
Clean
- Download ROM
- Download GApps ( optional )
- Reboot in recovery ( TWRP Recommended )
- Wipe --> Advanced Wipe --> Select : Dalvik / ART Cache , Cache , System and Data --> Swipe to Wipe
- Flash ROM
- Flash Gapps ( optional )
- Reboot
Dirty
- Download ROM
- Download GApps ( optional )
- Reboot in recovery ( TWRP Recommended )
- Flash ROM
- Flash Gapps ( optional )
- Reboot
----------| DOWNLOAD ZONE |----------
Latest Version : Here
TWRP_3.1.1-0 flashable zip : here
Open Gapps : here
Problems with EFS/IMEI/No network? here is the thread for you
Problems sending SMS? Check out this thread , PDU encoder is outdated so just scrol down on the warning page , and yes it will work for any ROM not just JB
XDA:DevDB Information
LineageOS 11.0, ROM for the Samsung Galaxy S III I9300
Contributors
rpdroky, LineageOS team
ROM OS Version: 4.4.4 KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: CWM or TWRP recovery
Based On: LineageOS
Version Information
Status: Stable
Created 2016-03-26
Last Updated 2016-06-13
LINEAGE OS 13.0
Latest Version : Here
Any gapps that you can recommend for this build?
really appreciate your time and hardwork for sharing this., thank you..
gonna try this later...
yethz said:
Any gapps that you can recommend for this build?
really appreciate your time and hardwork for sharing this., thank you..
gonna try this later...
Click to expand...
Click to collapse
Open GApps Pico , i will add the link to the download section
Cheers :highfive:
I'm testing this build right now. It have mDNIe, everything look very sharp, but you forgot to add "Advanced Display" on Display and Light setting, so I cant adjust sharpness.
xpduyson said:
I'm testing this build right now. It have mDNIe, everything look very sharp, but you forgot to add "Advanced Display" on Display and Light setting, so I cant adjust sharpness.
Click to expand...
Click to collapse
I didn't foget or remove any features from it , i just updated the sources , and if CM team decide to remove something , they must have a reason for it , and i don't remember that CM12.1 ever had such a feature , not even CM13 has it as i recall , anyway , you coul'd always try a custom kernel like Boeffla-Kernel , arter97 kernel or ArchiKernel (AOSP version) , maybe one of them has yre desired feature
Edit: yes indeed , i checked the old version and yes it had such a option , i'm gonna try to bring it back but i can't promise , sorry
Cheers :highfive:
@xpduyson: you can set mdnie-mode simply by editing /sys/class/mdnie/mode (try 4 for automatic). Smuggling a script into init.d doesn't work for me.
@rpdroky I'm using Boeffla kernel to control mDNIe. Your ROM working very smooth with boeffla.
anyway, thanks for continue support one of the best stable CM ROM for S3! CM11 look really old and CM13 still in nightly.
Thank You for supporting best rom on i9300 but I have a problem, when I try playing .webm files through browser or apps like clover the video doesn't show up and there is only audio I have to go through third party app like MX Player but those videos worked fine on CM12.1 By Trafalgar Square
wielku said:
Thank You for supporting best rom on i9300 but I have a problem, when I try playing .webm files through browser or apps like clover the video doesn't show up and there is only audio I have to go through third party app like MX Player but those videos worked fine on CM12.1 By Trafalgar Square
Click to expand...
Click to collapse
Honestly , i don't know why , but i will check it out , thanks for the info
Cheers :highfive:
wielku said:
Thank You for supporting best rom on i9300 but I have a problem, when I try playing .webm files through browser or apps like clover the video doesn't show up and there is only audio I have to go through third party app like MX Player but those videos worked fine on CM12.1 By Trafalgar Square
Click to expand...
Click to collapse
when I'm using Trafalgar Square's version, webm video freeze at first frame and no sound, others video format play fine. I assumed that the browser tried to play webm video with hardware accelerated.
Also in @rpdroky version, I can't play any video with HW+ accelerated in MX Player, logcat show something like this:
edit: HW+ was working in Trafalgar Square ROM
edit2: sometime both HW and HW+ not woking, logcat didn't show any error.
edit3: tried VLC, only work with software accelerated, not woking with hardware accelerated
Code:
03-28 07:44:40.000 2010-2432/? E/OMXNodeInstance: getConfig(3d:SEC.AVC.Decoder, ConfigCommonOutputCrop(0x700000f)) ERROR: NotReady(0x80001010)
03-28 07:44:40.000 7287-10934/com.mxtech.videoplayer.ad I/OMXCodec: [OMX.SEC.AVC.Decoder] video dimensions are 1920 x 1080
03-28 07:44:40.000 7287-10934/com.mxtech.videoplayer.ad I/OMXCodec: [OMX.SEC.AVC.Decoder] allocating 5 buffers of size 3133440 on input port
03-28 07:44:40.000 7287-10934/com.mxtech.videoplayer.ad I/OMXCodec: [OMX.SEC.AVC.Decoder] allocated buffer 0x42de2f71 on input port
03-28 07:44:40.000 7287-10934/com.mxtech.videoplayer.ad I/OMXCodec: [OMX.SEC.AVC.Decoder] allocated buffer 0x42de2f72 on input port
03-28 07:44:40.000 7287-10934/com.mxtech.videoplayer.ad I/OMXCodec: [OMX.SEC.AVC.Decoder] allocated buffer 0x42de2f73 on input port
03-28 07:44:40.000 7287-10934/com.mxtech.videoplayer.ad I/OMXCodec: [OMX.SEC.AVC.Decoder] allocated buffer 0x42de2f74 on input port
03-28 07:44:40.000 7287-10934/com.mxtech.videoplayer.ad I/OMXCodec: [OMX.SEC.AVC.Decoder] allocated buffer 0x42de2f75 on input port
03-28 07:44:40.000 7287-10934/com.mxtech.videoplayer.ad I/OMXCodec: [OMX.SEC.AVC.Decoder] OMX-buffers: min=2 actual=2 undeq=1+1
03-28 07:44:40.000 7287-10934/com.mxtech.videoplayer.ad I/OMXCodec: [OMX.SEC.AVC.Decoder] OMX-buffers: min=2 actual=6 undeq=4+1
03-28 07:44:40.000 2001-5201/? D/gralloc: int alloc_device_alloc(alloc_device_t*, int, int, int, int, const native_handle_t**, int*) added usage GRALLOC_USAGE_HW_ION because of format
03-28 07:44:40.000 2001-5201/? D/gralloc: int alloc_device_alloc(alloc_device_t*, int, int, int, int, const native_handle_t**, int*) added usage GRALLOC_USAGE_PRIVATE_NONECACHE because of format
03-28 07:44:40.000 2001-5201/? D/gralloc: int alloc_device_alloc(alloc_device_t*, int, int, int, int, const native_handle_t**, int*) added usage GRALLOC_USAGE_SW_WRITE_OFTEN because of format
03-28 07:44:40.005 7287-10934/com.mxtech.videoplayer.ad E/Surface: dequeueBuffer: IGraphicBufferProducer::requestBuffer failed: -2147483646
03-28 07:44:40.005 7287-10934/com.mxtech.videoplayer.ad E/OMXCodec: dequeueBuffer failed: Unknown error 2147483646 (2147483646)
03-28 07:44:40.005 7287-10934/com.mxtech.videoplayer.ad E/OMXCodec: [OMX.SEC.AVC.Decoder] init failed: -2147483646
03-28 07:44:40.005 7287-9136/com.mxtech.videoplayer.ad E/OMXCodec: [OMX.SEC.AVC.Decoder] OMX_EventError(0x8000101c, 0)
03-28 07:44:40.005 7287-10934/com.mxtech.videoplayer.ad E/MX.Video.Decoder.System: 10934 | Can't start OMX codec. error=-2147483646
Anyone have problem with GPS? In my friend's s3 all the app that use GPS says "GPS not active".
Inviato dal mio ONE A2003 utilizzando Tapatalk
New build will come today , most of the stuff shoul'd be fixed so be a little pacient cuz i have limited time
Cheers :highfive:
rpdroky said:
Open GApps Pico , i will add the link to the download section
Cheers :highfive:
Click to expand...
Click to collapse
I thought so
thanks and also, what could possibly be an issue, if I use the gapps 5.1 ( micro )? -
coz gapps (micro) package have google apps I mostly use, so I dont have to re-download some on playstore other than 3rd-party apps..
other than that, feel great for the updates today
cm-12.1-20160328-UNOFFICIAL-i9300.zip Online
- Advanced Display is back in the Display & lights menu
- webm files and GPS shoul'd work now
Cheers :highfive:
rpdroky said:
- Advanced Display is back in the Display & lights menu
- webm files and GPS shoul'd work now
Cheers :highfive:
Click to expand...
Click to collapse
weeehhh... high five bro
downloading now and the sickness of flashcoholic is running back into my nierves..
Wooohh... English grammar is the hardest part than modding or tweaking an android rom.. lol..
thanks again bro @rpdroky
yethz said:
I thought so
thanks and also, what could possibly be an issue, if I use the gapps 5.1 ( micro )? -
coz gapps (micro) package have google apps I mostly use, so I dont have to re-download some on playstore other than 3rd-party apps..
other than that, feel great for the updates today
Click to expand...
Click to collapse
Well you can use any version you like , i just recommended pico version to keep it simple
yethz said:
weeehhh... high five bro
downloading now and the sickness of flashcoholic is running back into my nierves..
Wooohh... English grammar is the hardest part than modding or tweaking an android rom.. lol..
thanks again bro @rpdroky
Click to expand...
Click to collapse
Glad to be helpfull
Cheers :highfive:
Nice to see that someone is developing cm12.1 further on
Thanks man
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
Only thing i noticed that nightmode is very laggy was also in cm 13 but they fixed it maybe its possible to do so also in cm12.1
What about the camera in this rom? somebody knows?