Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 07/19/2018 in all areas

  1. 1 point
    The only thing I can suggest is to try formatting the partitions from the advanced wipe menu & re-install Lineage
  2. 1 point
    Thanks for solution, Trapezio. Those are missing lines from build.prop. No need for repacking and flashing boot.img! Camera2 or Snapdragon Camera is dark?
  3. 1 point
    how can I do it? edit: Error during installation. Only last release NanoDroid-microG-17.4.20180731.zip works properly. @adeii This method works: Paste the following at the bottom of the build.prop. # Switch External With Internal persist.sys.vold.switchexternal=1 # Storage configuration ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1 Maybe a bug: the camera is very dark.
  4. 1 point
    I don't have any issues but I felt like replying anyway to thank you for making this ROM! I'm using it right now and it works great. Many thanks!
  5. 1 point
    Hey sorry, I didn't get a notification. Yes Google Pay working and Starling working. It's the same hardware we have in the UK just difference device ID and software. Bootloader is locked and working as normal. Brendan
  6. 1 point
    Another tip: to got bootable nougat/oreo kernel, toolchain had to be downgraded to 4.8! https://github.com/sonyxperiadev/device-sony-rhine/pull/210/commits/b5468ff42e505cf14487bc5b2d6e98a561e180d8
  7. 1 point
    So, to bring back some life to this device, decided to build Resurrection Remix (nougat) (available here). I just built using the exact same device tree, vendor blobs and kernel source from KonstaT's github without touching it. Replaced the telephony-common used in LinOS 14, copied libboringssl-compat.so (to make the camera work). Applied the hack mentioned here and made a u23 patch by just replacing the boot.img from the last patch for LinOS 14 (using the defconfig for u23). I didn't make any change regarding to SELinux. The roms seems similar to LinOS 14 regarding stability I recently saw this post: In the Resurrection Remix build, it's set as Enforcing. So the last thing I'm missing is to set it to Permissive to be as stable as LinOS 14? Probably I won't make many builds because my computer dies building android nougat, so I want to upload a stable build so I can delete the source code.
  8. 1 point
    The MoDaCo Classified Ads section is now open and allows you to buy and sell for free! Available at https://classifiedads.modaco.com, the section is open to all registered members and has some basic rules posted for everyone's benefit. It's worth noting that MoDaCo assumes no liability for any sales conducted in the forum, so use common sense when arranging a transaction. We have a feedback area for leaving buyer / seller feedback and also a wanted section if there's something you are specifically looking for. Finally, should you wish to find out about newly posted deals as quickly as possible, you can subscribe to the forum area or follow @MoDaCoAds on Twitter. Enjoy!
  9. 1 point
    Like many things in life, phone contracts are frustrating because as an existing customer, you can't get access to the same deals as new customers. I suspect that at some point in the coming years this may be outlawed, but until then, if you want a new customer deal without losing your number, you need to switch network. Or do you? We recently assisted a reader who was currently on 3 but wanted to get a great deal offered only to new 3 customers. The solution? Surprisingly straightforward. Cancel the current contract, requesting a PAC code (porting authorisation code) Pick up a PAYG SIM from another network (most networks will send them out for free via a form on their website) Port your number to the PAYG account Sign up with your previous provider again, taking advantage of the new customer deal Request a PAC code from the PAYG provider Port the number back off PAYG to your new account Simple!
  10. 1 point
    This is my port of Remix OS 2.0 for Chuwi Vi10 Plus, Hi10 Plus, Hi10 Pro, Hibook, Hibook Pro & Hi12. This ROM is based on Chuwi Hi10 Plus official Remix OS release build B2016092102. Do not mirror my builds! Please post a link to this page instead. RemixOS-B2016092102-chuwi_vi10plus.zip http://konstakang.com/devices/chuwi_vi10plus/RemixOS md5:bae3c864d458192ed782d1ded5b10c9f Working: Wifi Audio (playback/input/routing/headphones/etc) Bluetooth Camera Hardware video decoding & encoding Hardware acceleration and OpenGL rendering HDMI Keyboard dock Network/wifi location SD cards Stylus pen (HiPen H2) USB storage (MTP and PTP) & adb USB OTG (storage, mouse, keyboard) Touchscreen/multi-touch Sensors Not working: ??? Changes I've made compared to the original firmware: include source built kernel with updated mmc drivers to fix 'freezing issue' on Vi10/Hi10 Plus add configs for external keyboard docks to fix 'keyboard dock wake issue' remove suspicious TeleyService & YouTubeOem apps that are bundled with stock Remix OS on Chuwi devices add Widevine blobs from Cube iWork8 Ultimate to fix playback of DRM protected content with various media streaming apps disable dm-verity enable/disable 'reboot to Windows' option on different devices Sources: Kernel Thanks: Jide for Remix OS Jide Technology for releasing Linux kernel source code for Chuwi Vi10 Plus festlv for the keybord dock wake fix matrixsoul for B2016092102 dump Like my work? Donation Hall of Fame
  11. 1 point
    I've added CM12.1 and Remix OS compatibility patches for Hi10 Plus devices shipped with 20170504 firmware to my site. Those two media_profiles_*.xml configs do absolutely nothing with CM12.1 (see https://github.com/CM-CHT/android_frameworks_av/commit/ec43dabccae4fc3d5dc482fd2b95c15eff102c0e). Well done figuring out the rest. :)
  12. 1 point
    Yeah, all kinds of cool stuff you can do with rope. :o
  13. 1 point
    I managed to repartition my G330 to 450MB /cache, 5MB /cust, 1.1GB /system, 1GB /data and 930MB /storage/sdcard0 without losing any data. My installed installed SlimKat 9.0 still worked after this. (I have no clue how much /cache one needs, maybe less iss enough.) Note: Below, I have posted a reduced guide if you only want to increase /data at cost of internal SD size. This is how I repartitioned my G330: Prerequities: - installed CWM 6.0.4.4 (others may work, I just had this one installed) - adb (from Android SDK) - external SD card with >4GB free space - "resize2fs_s" from https://github.com/moddingg33k/android_kernel_y300_general/blob/master/ramdisk/synopsis/sbin/resize2fs_s - accepting that this may permanently brick your phone - being able to read & doing exactly what is written here - courage! Note1: I don't know if it's just my phone, but it spontaneously rebooted several times while in CWM (idle, copying files in phone or between phone and PC). Note2: I didn't check this guide. I just wrote it up after doing all this to my phone. Step 1: Planning the partition layout Boot the phone to recovery. Run "adb shell" from command line run: fdisk -H64 -S32 -l /dev/block/mmcblk0 to print the current partition table The last lines are (I added the mount points on the right hand side) Device Boot Start End Blocks Id System [..] /dev/block/mmcblk0p15 201 392 196608 83 Linux -> /cache /dev/block/mmcblk0p16 393 472 81920 83 Linux -> /cust /dev/block/mmcblk0p17 473 984 524288 83 Linux -> /system /dev/block/mmcblk0p18 985 1624 655360 83 Linux -> /data /dev/block/mmcblk0p19 1625 3728 2154496 6b Unknown -> /storage/sdcard0 ("internal SD card") "mmcblk0" is the phone-internal flash, and the "pXX" suffix enumerates the partitions in this flash. "Blocks" is in 1MB units. You can see /system is only 512MB This is what we are going to do: /dev/block/mmcblk0p15 202 649 458752 83 Linux -> /cache /dev/block/mmcblk0p16 650 659 10240 83 Linux -> /cust /dev/block/mmcblk0p17 660 1799 1167360 83 Linux -> /system /dev/block/mmcblk0p18 1800 2799 1024000 83 Linux -> /data /dev/block/mmcblk0p19 2800 3728 951296 6b Unknown -> /storage/sdcard0 Note 1: Make sure that each new partition is big enough to hold the current content. For p15-p18, you can use "resize2fs_s -P" (see step 3) to get the minimum required size. For p19, mount the phone as USB storage, then check in Windows how full the internal SD drive is. Note 2: The partition layout is somewhat inconsitent/corrupt if the first few partitions. To avoid problems from overlap, I chose to recreate /cache starting at 202, not 201. Step 2: Preparation Copy resize2fs_s to your external SD card root dir. On phone (under mounts & storage), mount /storage/sdcard1 (your actual SD card) and unmount /cache. Copy resize2fs_s to root partition & make it executable run: cp /storage/sdcard1/resize2fs_s . run: chmod a+x resize2fs_s Step 3: Make a backup of all relevant EXT partitions You need to do this step for all partitons you want to keep. Other partiton content will be lost. Suggestion: - backup /data and /cust - backup /system (unless you want to do a fresh ROM install after repartitioning AND don't need a fallback) - skip /cache (just format them in CWM after repartitioning) - skip /storage/sdcard0, this is a FAT partition and we need handle to handle this differently. We're resizing the partitions now to make them smaller (example is p15 = /cache here): run: ./resize2fs_s -P /dev/block/mmcblk0p15 This gives you the minimum partition size for mmcblk0p15 (=/cache) "Estimated minimum size of the filesystem: 14170" (in 4KB blocks) Now shrink to some size that is ~10% larger. run: ./resize2fs_s /dev/block/mmcblk0p15 15000 Then copy to shrunk partition image to external SD card. Partition p15 goes into a file "p15". Specify the copy size accordingly. run: dd if=/dev/block/mmcblk0p15 of=/storage/sdcard1/p15 bs=4K count=15000 Step 4: Make a backup of InternalSdCard FAT partition (/storage/sdcard0) In CWM, select "mount USB storage". On Windows, copy all files from internal SD card partition to some directory (e.g. "InternalSDcardBackup") on PC. (You should first enable display of hidden files, in case there are some) "Eject" both phone drives in Windows, then leave "mount USB storage" in CWM. In CWM unmount all partitions except /storage/sdcard1. Step 5: Change partition layout run: fdisk -H64 -S32 /dev/block/mmcblk0 Delete all partitions to be changed: (Enter d, then the partition number to delete) do: d [enter] 19 [enter] do: d [enter] 18 [enter] do: d [enter] 17 [enter] do: d [enter] 16 [enter] do: d [enter] 15 [enter] Create new partitions (automatically numbered in order): (Enter n, then the start block number, then the end block number) For the table above, it would be: do: n [enter] 202 [enter] 649 (for p15 = /cache) do: n [enter] 650 [enter] 659 (for p16 = /cust) do: n [enter] 660 [enter] 1799 (for p17 = /system) do: n [enter] 1800 [enter] 2799 (for p18 = /data) do: n [enter] 2800 [enter] 3728 (for p19 = /storage/sdcard0) Change partition type for p19 to "6b" (it was like this before, and recreating the partition changed it to 83): do: t [enter] 19 [enter] 6b [enter] Check that the new layout is what you want: do: p [enter] Write the new layout to flash: In CWM, make sure all partitons except /storage/sdcard1 are unmounted, otherwise you'll get an error here. do: w [enter] All partitons are now it the right size, but without right content. Step 6: Restore partition content. In CWM, make sure all partitons except /storage/sdcard1 are unmounted. For all EXT partitions you made a backup in step 3 (here for example p15 = /cache): Copy shrunk backup back into new partition: run: dd if=/storage/sdcard1/p15 of=/dev/block/mmcblk0p15 bs=4K Enlarge file system to full partition size: run: ./resize2fs_s /dev/block/mmcblk0p15 Repeat step 6 for all EXT partiton you want to have restored. For skipped partitons (except p19 = /storage/sdcard0), format the partition in CWM. Step 7: Restore InternalSdCard FAT partiton In CWM, go into USB storage mode. On PC, format the InternalSdCard partition (default settings). Windows will ask for it by itself. Copy files from InternalSDcardBackup to this empty partition. Unmount phone drives in windows, then reboot phone from CWM.
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×

Important Information

By using this site, you agree to our Terms of Use.